On 11/09/2017 03:49 PM, Assaf Gordon wrote: > On 2017-11-08 08:10 AM, Jim Meyering wrote: >> On Tue, Nov 7, 2017 at 11:51 PM, Assaf Gordon <[email protected]> >> wrote: >>> Github offers an option of creating an "issue template" >>> that will be shown whenever someone opens a new issue. >> >> That sounds like a fine idea.
I'm also okay with it. Overall, the proposed templates look sane. > > ISSUE_TEMPLATE.txt > > > # Reporting GNU Coreutils Issues > > Please **do not** send pull-requests or open new issues on Github. Maybe a quick "why" would be warranted; whether: This is because Github is just a downstream mirror and is not frequently monitored, all development is coordinated upstream on GNU resources. or even a link to some essay (does rms have an essay on Github?). > ## Mailing List Etiquette > > When sending messages to [email protected] or [email protected] : > > * Send messages as plain text. > * Do not send messages encoded as HTML nor encoded as base64 MIME nor > included as multiple formats. > * Avoid sending large messages, such as log files, system call trace > output, and other content resulting in messages over about 40 kB. > * Avoid sending screenshots (e.g. PNG files). When reporting errors > you encounter on the terminal, copy and paste the text to your message. > Maybe also mention: List policy is reply-to-all, and non-subscribers may post. There may be a moderation delay for a first-time post, whether or not you subscribe. > PULL_REQUEST_TEMPLATE.txt > > > # Contributing to GNU Coreutils > > GNU Coreutils welcomes contributions. > > Please *do not* send pull-requests or open new issues on Github. Again, a quick "why" may be in order. > See "hacking resources" below for recommended alternatives. > ... > Before suggesting a new feature, read the list of rejected features requests: > https://www.gnu.org/software/coreutils/rejected_requests.html > > *Do not* send pull-requests on github. > Send a patch as an email attachment to [email protected] (for new features) > or [email protected] (for bug fixes). > Patches can be generated with `git format-patch` (the HACKING links above > provide > examples of generating a patch). Is this redundant with the top of the document? -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
