Hi Burcin, On Sat, Oct 16, 2010 at 11:21 PM, Burcin Erocal <bur...@erocal.org> wrote: > We might be able to overcome this with a "bug-wrangler" team,
I would have thought "weed-wrangler" or "pest-wrangler". You know, Sage and horticulture :-) > people > who volunteer to > > - look at newly submitted tickets, notify the related developers, ask > for examples and test cases if the report doesn't provide them, > etc. Also make sure the newly created ticket has sufficient information to allow people to duplicate the bug. Things like linking to the original bug report, if it exists, on any of the Sage mailing lists, providing sample code to duplicate the bug (or weed or pest :-), make sure the newly created ticket is not a duplicate of an existing ticket, cross link tickets with that new ticket if possible. > Another advantage is that the members of this team don't need to be > developers, or even know how to code. It is enough to be able to listen > to user requests and use trac. > > This could also be a good starting point for people who want to get > into Sage development, since it provides an opportunity to look through > the library and become familiar with the internal structure of Sage. I support your proposal as it is another way to encourage more people to become familiar with the Sage library. -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
