Email list hosting service & mailing list manager

disabled Github issue tracker Arthur A. Gleckler (23 Jul 2016 21:14 UTC)
Re: disabled Github issue tracker Jeremy Steward (23 Jul 2016 21:19 UTC)

Re: disabled Github issue tracker Jeremy Steward 23 Jul 2016 21:19 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/23/2016 03:14 PM, Arthur A. Gleckler wrote:
| I've disabled the Github issue tracker for this SRFI. Please report
| all issues to this mailing list instead.
|
| I intend to disable Github issue tracking for all SRFIs, but since
| there are so many, I want to automate that work first using the
| Github API.
|
| Thanks.
|
|
| SRFI Editor
|

Since you have disabled it, is there another way for users who
discover the Github repo to know where to report issues? As an
alternative I would suggest adding something to any README files in
the repository as needed. I imagine something like:

~~~~~~~~
## Issues

Please report all issues to our mailing list at:
[srfi-121@srfi.schemers.org](mailto:srfi-121@srfi.schemers.org)
~~~~~~~~

Many users new to Scheme might see the Github repository and choose to
contribute issues from there, because they may not be aware that the
mailing list is the primary discussion channel. If issues are
disabled, they may try emailing the repository owner, however as the
owner is the "scheme-requests-for-implementation" organization on
Github, there is no address listed. So adding something to the README
could be a good alternative.

I can see this being cumbersome though, as it means every project
would now need at least a basic README.md file just to provide this
information. Alternatively, you could create a CONTRIBUTING or ISSUES
file that fulfills the same purpose in each repository.

In any case, I figured it's not immediately obvious to new users where
to report issues, so maybe something like this _could_ help. Then
again most of us know where http://srfi.schemers.org is anyways so it
might just be extra effort for little gain.

- --
Jeremy Steward

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXk99TAAoJEKflx7ZMcbY7cJgP/A7+amvmNXcmGT4OJLIOv9r5
XtulhgUfo9uZVBbTVgmF3JwNyicu5T4640Ld5eiBChXkXKnzvjO4W3Ft09HGFTCY
7odnz3CwLkIz9rPyrFvVWrPlpPCHJ9BwaywqTwrj+UNVWvdybS1YW4GsYjPZaeao
F0z5zBPpj+e4Tw8CjHsrC0YQo5RYY0m6BfeGy6OvtpRUCtJQAEs89hxCRGigYPWt
N+Eh5lbz4sn3OOwnOByV9ftpLT5Gpk0AkCSWCAORWjElPfoH3kVdWEY7DkPXEOpE
v3WFPwpNHuAqQBXP1txQQSZ9wpscybAqrErwHVeJkaE68unSF1uc3oNxtS5RN0os
7Ix2wwI8VmE7bEXAuzWrxbyQXMxN7SHfXdLoIElOENHIjK9DyFS/2uFycKNUX2Ga
uqKUKqrbMH9P5ZA+mebUV6kfiD8Q5+tBulBEUd6YggY28m/dnQuqBeWy78GrjWdB
x5OHLeJhTwnxaU6hXeLu7Kh8bo+sIm4mkQzGT54YVdosAH7O0pNSLke+b6gzWpKj
Kb9O3olqTTx2UajW+xDqTjpBKn83AQndP5sbgqISdrSDvDNXsvTRI13uyDs/wjsO
QK6t4L80FCqwu2iJpInqLjaiOiLJH6tJPs6q1AbqKCB7UvSwl2eJA+o80i6pqbE0
hUr+mlsCWvQi39dVsasb
=xTPQ
-----END PGP SIGNATURE-----