Hi, all, A friendly reminder, prompted by this morning's round of ticket moderation...
The following is copy/pasted from the top of the ticket submission page ( http://www.fossil-scm.org/index.html/tktnew): ---------------- *Discuss your issue on the fossil-users mailing list <http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> first. Tickets for issues that have not previously been discussed on the mailing list are very likely to be deleted without comment and without consideration.* ---------------- So please don't be surprised if one or more of your submissions has been mysteriously deleted. Now the justification, for those who like that kind of thing... In the scope of the Fossil project, the majority of tickets tend to fall into one of the following major categories: a) misunderstands or user error which are easily resolved via a mail thread. Such cases are sometimes caused by lack of (or sub-par) documentation, and posting it to the list ensures that more developers will see it, increasing the chances that it will get resolved and increasing the number of eyes on it (which tends to lead to better solution). b) New feature ideas and RFEs (Requests For Enhancements). Many times simply suggesting a new feature is enough to get it integrated, sometimes even on the same day. (We don't think of all features by ourselves, and quite rely on newcomers to suggest things which have so far been overlooked!) Larger feature ideas should be filtered through the list first, as many suggestions are either not feasible (or are unduly difficult) for architectural or project-level philosophical reasons, or are simply deemed out of scope for the project. Sometimes a new feature idea justifies a ticket, but in practice we tend to use the mailing lists to post/follow development of major new features. c) "True bugs," i.e. broken behaviour. Posting to the mailing list will ensure a much quicker response than a ticket will, as all of us subscribe to the mailing list, but we do not all go and check the ticket list very often. (Other than via the ticket moderation queue, i very rarely go through the ticket list.) To be clear: we're NOT saying "don't report problems and feature requests," we're just asking that you do so on the mailing list(s) first, and following up with a ticket only if requested to by one of the developers (you'll know they're a developer if they ask you to submit a ticket ;). In practice (for this particular project), this works out better for both the reporter and the developers. One final hint: after submitting a ticket, it's a good idea to post a link to it back to the mailing list thread it originated from. This assists, among other things, users searching through the mail archives (or their own mail clients). Disclaimer: the above applies only to the Fossil project, and is not intended to imply any rules/guidelines/best practices for other projects. Thanks once again for your continued input and support, and Happy Fossiling! -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
