Re: A few thoughts on Process 2 cents
Sorry about that. I was actually kind of interested in whether the 'process' aspect of admin (and possibly other contrib apps?) had undergone any changes, given that I've heard some sentiment about people hoping contrib was 'approaching zero'. -Steve On Sep 29, 4:39 pm, Jacob Kaplan-Moss wrote: > On Wed, Sep 29, 2010 at 3:21 PM, subs...@gmail.com wrote: > > Speaking of which... who is interested in admin these days? Been > > trying to scare up some feedback @http://code.djangoproject.com/ticket/5833 > > for some time now. > > Please don't derail threads with unrelated topics like this. It makes > discussions really hard to follow. Thanks. > > Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
Re: A few thoughts on Process 2 cents
On Wed, Sep 29, 2010 at 3:21 PM, subs...@gmail.com wrote: > Speaking of which... who is interested in admin these days? Been > trying to scare up some feedback @ http://code.djangoproject.com/ticket/5833 > for some time now. Please don't derail threads with unrelated topics like this. It makes discussions really hard to follow. Thanks. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
Re: A few thoughts on Process 2 cents
Speaking of which... who is interested in admin these days? Been trying to scare up some feedback @ http://code.djangoproject.com/ticket/5833 for some time now. On Sep 29, 2:39 pm, Jacob Kaplan-Moss wrote: > sense to have more area-specific committers. If someone's well-versed > in the admin, a lack of interest in the ORM certainly shouldn't be an -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
Re: A few thoughts on Process 2 cents
On Wed, Sep 29, 2010 at 1:34 PM, dartdog wrote: > So maybe subdividing the areas of responsibility might help? I know it > is generally recognized that certain comitters have specific expertise > but it might make it easier to shore up some of the bus areas like the > orm as well if the teams are more clearly understood? Yes, I agree that as we start to open up more it'll make a lot more sense to have more area-specific committers. If someone's well-versed in the admin, a lack of interest in the ORM certainly shouldn't be an issue. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
A few thoughts on Process 2 cents
I attended a Wordcamp recently (yeh, the dark side) but I was very interested that they only have 7-8 core comitters they add feature specific people for short, release cycles for specific features,, that sounds sort of odd,, but I think the most interesting thing was that that sub divide the responsibility to a large degree so that it is clearer to the outside who does which area. So DB is on person Front- end another admin another, of course there is overlap. but I think that might be worth exploring as an element of scaling so that not all issues are treated as core.. Increasingly there will be more and more subsystems that can have something of their own teams?? According to the Wordpress comitter @nacin , Drupal has only 4 or so... So by these metrics Django's 14 or so looks pretty good... So maybe subdividing the areas of responsibility might help? I know it is generally recognized that certain comitters have specific expertise but it might make it easier to shore up some of the bus areas like the orm as well if the teams are more clearly understood? Clearly I'm new and have no current aspirations to committing (still working on using!) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@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.
