On 4/19/10 10:19 AM, "Jacob Kaplan-Moss" <[email protected]> wrote:
> Hi folks -- > > I'd like to try to reboot the discussion that's been going on about > Django's development process. > > I'm finding the current thread incredibly demoralizing: there's a > bunch of frustration being expressed, and I hear that, but I'm having > trouble finding any concrete suggestions. Instead, the thread has > devolved into just going around in circles on the same small handful > of issues. > > So: here's your chance. You have suggestions about Django's > development process? Make them. I'm listening. > > Jacob One suggestion that jumped out at me (which I admittedly know very little history about with regards to Django or other projects) was the "trunk ready" branch(es) [1]. Perhaps an effort to outline what that process might entail in detail, to determine if it would address any concerns? For my part, I see that it could be helpful to let some patches/ideas get a shot at integration without having to endure the (necessarily) more rigorous core commit trails. I'm not really comfortable suggesting any concrete plans for how that might happen though. A single almost-trunk branch? A branch per lieutenant/component? I'm wary of adding too much bureaucracy and overhead. I think it's pretty clear that the core Django process is successful, and this seems like a low impact (though potentially high effort?) way to involve more of the community. Peter [1] http://groups.google.com/group/django-developers/msg/ef8ec23d565dd07b -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
