add FAQ about feedback, improve contact, update bin/status2html.sh

We added FAQ 0.5 about how to make a suggestion on IOCCC rules, guidelines and tools.

We added a mastodon tag for _contact.html#mastodon_.

We made a minor improvement to bin/status2html.sh about when
the IOCCC is open for submissions.

Changed `bin/status2html.sh` VERSION from "1.1.2 2024-03-26"
to "1.1.3 2024-04-12".

TODO: Complete content that hinted at by what is currently broken links.
      We pushed this change thru on the FAQ now, because we were aware of
      others wishing to submit a FAQ related pull request.
This commit is contained in:
Landon Curt Noll committed 2024-04-12 10:53:17 -07:00
1 parent 0a755f43a5
commit c549f6585e
3 files changed
+44 -5

No files matched your search

+7 -4
View File
@@ -99,7 +99,7 @@ shopt -s globstar # enable ** to match all files and zero or more directories an
# set variables referenced in the usage message # set variables referenced in the usage message
# #
export VERSION="1.1.2 2024-03-26" export VERSION="1.1.3 2024-04-12"
NAME=$(basename "$0") NAME=$(basename "$0")
export NAME export NAME
export V_FLAG=0 export V_FLAG=0
@@ -424,12 +424,15 @@ esac
echo "See the [IOCCC news](news.html) for details including the tentative" \ echo "See the [IOCCC news](news.html) for details including the tentative" \
"scheduled opening date." "scheduled opening date."
echo echo
echo "A preliminary IOCCC rules, guidelines, and tools have been posted." \ echo "A preliminary [IOCCC rules](next/rules.html], preliminary [IOCCC guidelines](next/guidelines.html)," \
"Comments and suggestions on these preliminary items are welcome." "and preliminary [mkiocccentry tools](https://github.com/ioccc-src/mkiocccentry) have been posted."
echo
echo "Comments and suggestions on these preliminary items are welcome, see [FAQ 0.5](faq.html#feedback)" \
"for information on how."
;; ;;
open) echo "# The IOCCC open for submissions" open) echo "# The IOCCC open for submissions"
echo echo
echo "See the [IOCCC news](news.html) page for details on rules, guidelines, tools and deadlines." echo "See the [IOCCC news](news.html) page for possible updates to rules, guidelines, tools and deadlines."
echo echo
echo "See [How to enter the IOCCC](faq.html#submit) FAQ for additional information." echo "See [How to enter the IOCCC](faq.html#submit) FAQ for additional information."
echo echo
+10 -1
View File
@@ -24,10 +24,19 @@ free to add a comment to the issue. If you do not find an it has
been reported, then fee free to open a [new IOCCC been reported, then fee free to open a [new IOCCC
issue](https://github.com/ioccc-src/winner/issues). issue](https://github.com/ioccc-src/winner/issues).
If you are trying to:
* Comment or make a suggestion on IOCCC rules - (see [FAQ 0.5](faq.html#feedback))
* Comment or make a suggestion on IOCCC guidelines - (see [FAQ 0.5](faq.html#feedback))
* Comment or make a suggestion on IOCCC tools - (see [FAQ 0.5](faq.html#feedback))
Those FAQ entries will help guide you on how to make public comments
and suggestion in the relevant places.
See the above FAQ entries for more details. See the above FAQ entries for more details.
# Try mastodon # <a name="mastodon"></a>Try mastodon
You may wish to follow us [IOCCC on Mastodon](https://fosstodon.org/@ioccc) You may wish to follow us [IOCCC on Mastodon](https://fosstodon.org/@ioccc)
as we use that platform to announce things such as the opening of a new IOCCC as we use that platform to announce things such as the opening of a new IOCCC
+27
View File
@@ -6,6 +6,7 @@
- [0.2 - What should I put in my entry's Makefile?](#faq0_2) - [0.2 - What should I put in my entry's Makefile?](#faq0_2)
- [0.3 - May I use a different source or compiled filename than prog.c or prog?](#faq0_3) - [0.3 - May I use a different source or compiled filename than prog.c or prog?](#faq0_3)
- [0.4 - What platform should I assume for my entry?](#faq0_4) - [0.4 - What platform should I assume for my entry?](#faq0_4)
- [0.5 - How may I comment or make a suggestion on IOCCC rules, guidelines and tools?](#faq0_5)
## Section 1 - [History of the IOCCC](#faq1) ## Section 1 - [History of the IOCCC](#faq1)
- [1.0 - How did the IOCCC get started?](#faq1_0) - [1.0 - How did the IOCCC get started?](#faq1_0)
@@ -354,6 +355,32 @@ even better. Being able to compile with other compilers like clang is also a
good thing. good thing.
### <a name="faq0_5"></a><a name="feedback"></a>FAQ 0.5: How may I comment or make a suggestion on IOCCC rules, guidelines and tools?
The [IOCCC judges](judges.html) to welcome feedback on the [IOCCC
rules](next/rules.html), [IOCCC guidelines](next/guidelines.html)
and on the [IOCCC mkiocccentry tools](https://github.com/ioccc-src/mkiocccentry).
To comment on the [IOCCC rules](next/rules.html) or the
[IOCCC guidelines](next/guidelines.html) please view the
[GitHub discussions for this repo](https://github.com/ioccc-src/temp-test-ioccc/discussions).
If there is an on-going discussion that seems relevant to what you
have to say, consider adding comments to that particular discussion.
Otherwise consider opening a [new IOCCC repo
discussion](https://github.com/ioccc-src/temp-test-ioccc/discussions/new/choose).
To comment on [IOCCC mkiocccentry tools](https://github.com/ioccc-src/mkiocccentry),
please view the [mkiocccentry repo discussions](https://github.com/ioccc-src/mkiocccentry/discussions).
If there is an on-going discussion that seems relevant to what you
have to say, consider adding comments to that particular discussion.
Otherwise consider opening a [new mkiocccentry
discussion](https://github.com/ioccc-src/mkiocccentry/discussions/new/choose).
As a very last resort and/or if you feel the need to engage in a private
discussion with the [IOCCC judges](judges.html), then see
[How to contact the IOCCC](contact.html).
## <a name="faq1"></a>Section 1: History of the IOCCC ## <a name="faq1"></a>Section 1: History of the IOCCC