On Tue, 4 Feb 2014, James Tanner wrote:

In more "enterprisey" bug trackers, there are many many fields a user has
to fill out when creating a ticket. Usually the end users are discouraged
by the number of fields and will simply stop filling them out or even
making tickets. However, these fields help project managers and other
contributors group issues into buckets to work smarter on solving lots of
tickets at once. Constantly context switching between issues of different
types is difficult for people like myself.

Our solution is to bring a little bit more "enterprise" to the github issue
tracker without slowing down issue creation for the users. We have built a
robot that will examine all new issues and verify the description matches a
*simple* markdown template.

https://github.com/ansible/ansible/blob/devel/examples/issues/ISSUE_TEMPLATE.md

If the description does not contain the headers in the template, a warning
will be added to the comments. If the description is not corrected within 7
days, the issue will be closed.

So "we cannot handle the number of contributions" is met with a "we will just make it harder for people to contribute".

This is silly, I send in a pull-request for an obvious bug in the uri module, and now I am asked to fill out a template or my pull-request will be closed in 7 days.

    https://github.com/ansible/ansible/pull/5869

Filling out the template is mork work than the patch.

Feel free to close my pull-request today and don't expect me to even bother sending anything upstream as long as this is considered a best practice.

PS Maybe you ought to set up your own bugzilla and disable the Github issue-tracker altogether, rather than going down this path...

--
-- dag wieers, [email protected], http://dag.wieers.com/
-- dagit linux solutions, [email protected], http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]

--
You received this message because you are subscribed to the Google Groups "Ansible 
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to