> I was thinking of setting up trac to send a notice to a mailing list > for each new issue. Then people interested in this effort can follow > this list and help out. Is this possible? Can someone familiar with the > trac set up comment?
> IMHO, distributing work day by day, or weekly is still putting too much > load on one person. It should be enough if someone contributes to one > issue per day. > Perhaps we should come up with a locking mechanism, to prevent two > different people from trying to sort the same issue at the same time, > but it feels like too much organization at the beginning. My guess would be that we won't have the issue with locking very often (i.e. too many people doing too much work) but with no one feeling responsible. I guess for me your suggestion would turn out something like this: 1) I sign up to that mailing list since I feel a responsibility of contributing to Sage in such a way 2) For the first few days or weeks I go through newly opened tickets as you suggested. 3) Eventually, probably in some phase where I have less disposable time, I give up on dealing with this e-mail since "somebody else will take care of it". Of course, the answer could just be to not do step 3, but I would assume that it would happen to many of us. Being responsible for a week a time is something more local or short-time which would make it easier for me to commit. To given an example of the workload here's the list of tickets created on the 15th. It seems 3-5 new tickets a day is the normal load: * Ticket #10134 (Provide the enumeration of word morphisms from a range of integers) created by slabbe * Ticket #10133 (Make sure log(1) returns an Integer, not an int) created by kcrisman * Ticket #10132 (Differential Geometry via Sage) created by mikarm I am working in the field of differential geometry (research and teaching) … * Ticket #10131 (Add option to specifiy path for twistd's process ID (.pid) file) created by cschwan * Ticket #10130 (Revamp __hash__, __cmp__ and __richcmp__) created by roed There are a number of confusing and non-optimal features of the way Sage … Thus, as a rule of thumb we could say whoever is responsible for a day should deal with five tickets old and new. This seems like about 1-2h of work which seems doable to me. Of course, if many people feel differently then we should choose a different path. Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: martinralbre...@jabber.ccc.de -- 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
