On 12/8/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > > Hi Devs, > > I've been missing the weekly updates that Clint Ecker was doing and so > I thought I'd write in to pitch an idea and offer some help if I > could. I'd say a good goal to keep these going would be to not rely > in a single person as much. If we can come up with a weekly format > that is not very time consuming, some tools to generate parts of it, > and maybe a mailing list for people to push ideas to, anyone could > gather up the pieces and push a weekly update out.
I'm not sure I'd be a fan of a completely automated mechanism - Django has a certain sense of style and finess that isn't conveyed by simply aggregating all updates into a single message. As a result, there will always be a task to edit and review the results of whatever the automated mechanism can generate. At some point, you need to look at how much effort would be involved in building the tools for an automated mechanism, and balance it against the effort required to manually troll the relevant RSS feeds and compile a weekly summary. As always, it's easy to propose a technical solution, but ultimately what we need is a warm body - and they're a lot harder to come by. If you're volunteering to be that warm body, you're welcome to help out. However, there is also an interesting analog with recent Django code development to be observed here. You may have noticed that there has been a recent push to encourage people to develop their Django plugins externally to the Django repository itself - if a change is required to the core framework (such as registering user-space management commands, or allowing user-registered database backends), we have been making those changes in an attempt to stimulate the external ecosystem of plugins and features. The same is true of a weekly Django update message. There is absolutely nothing stopping you from writing a weekly blog message and publishing it somewhere. If you think you have some magnificent technical solution that will assist with compiling this update, build it and trial it out (all the data you need should be available from various mailing list and RSS feeds). If you run your personal Django summary blog for a few months, we may just say 'hey, want to publish this direct to the Django website?' and make it the 'official' resource. > Thoughts? Is the mailing list idea for notices/updates possible? I'd > be willing to kick this off and post to said mailing list for weeks I > can't compile an update. In the weekly summaries we can publish the > mailing list so people know where to send update notices. This is a reasonable 'starting summary' for a weekly update - and corresponds fairly well to what Clint was doing a few months back. > Personally, I think it's important to do summary updates, especially > as we're pushing towards a major release. As do I - The weekly summary is a valuable contribution to the community, regardless of whether we are pushing towards a major release or not. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
