On Thu, Oct 22, 2009 at 6:47 PM, mrts <mrts.py...@gmail.com> wrote: > > On Oct 22, 3:36 am, Russell Keith-Magee <freakboy3...@gmail.com> > wrote: > As I said, I don't think I'm actually in a pjosition to suggest > improvements to the workflow (being Nobody in that little story :)), > but I'd be most pleased to do the following if core thinks > this advances Django's cause: > * create a "mm-tree" on GitHub and share commit bits to a few > core-designated people, > * regularly review and apply pull requests to that branch, > * organize regular microsprints to get more tickets into the tree. > > The first step would be to write a proper proposal that describes the > workflow in greater detail -- should I do it?
No. Writing a proposal is exactly what you *shouldn't* do. If you want to contribute by developing an mm-tree, then start working on an mm-tree. Set up the tree. Work on it. Announce the your work on django-dev. Writing a formal proposal will in no way advance your cause. Like I keep saying - you don't need formal approval of a process, or approval of a plan of action - you need to do the work, and make a tree. The value in an mm-tree won't be realized in a week. It will be realized in 6 months when you have established that your branch is a rich source of vetted tickets that the core can exploit to advance trunk, and that you're committed to working on the branch for the long term. A formal proposal will not advance either of these goals. Writing proposals is easy. Actually doing the work is a lot harder. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
