I can't find the message where you discussed a 24 hour wait, VInzent, but I think we could generate some other principles that would help development:
1) Like Robert's Rules of Order, before beginning to make a solution for an issue, seek a "second" for your motion. That affirmation would indicate that someone thinks your proposal for a solution is worth pursuing. 2) Ideally, besides a second there should maybe be "thirds": one or more persons that would be willing to review the work. 3) Make a pull request when the work is finished. 4) After 24 hours, or when that pull request comes next in the queue, or when it is agreed that the pull should move forward...respond in a timely manner to keep the pull active. As to the processing of pull requests: if we processed pull requests in the order received or have some mechanism -- push credit based on lines reviewed? -- to decide when one might jump ahead, this would encourage review of existing requests. A pull request mightbe skipped over if the pull doesn't receive response to feedback within a day or some reasonable time frame. Just some thoughts. /c -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
