Well. Sigh. I went through this myself only very recently, so I understand the question(s). Of course we have http://wiki.sagemath.org/TracGuidelines which already helps a lot, and http://sagetrac.org/sage_trac/ where also very valuable information is recorded, and links from http://www.sagemath.org/development.html to this information. As well as the "Sage programming" documentation, which has already improved quite a lot in the past months.
But there definitely lacks a down-to-earth "How To" describing the ticket life-cycle. Something more like a check list, and step-by-step instructions, than another high-brow "Guideline for the Review Process". But I don't think I open a ticket for this unless I have some lines, say at least a first draft for some third chapter of the prgramming doc. Cheers, gsw --~--~---------~--~----~------------~-------~--~----~ 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/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
