On 12/8/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > 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.
I posted a quick proof of concept: http://rob.cogit8.org/blog/2007/Dec/10/django-week-review-dec3-dec92007/ I'll be monitoring a few resources throughout the week to hopefully do a bit better job of picking up on external resources and news. With guidance from the Symfony weekly update editor, I've written a Python script to parse the RSS feed of Django's Trac timeline to count tickets (open, updated, closed), changesets, and wiki updates. And to output Markdown formatted links to changesets so it's a copy/paste operation to pick the highlights. This can/will evolve each time I use it I'm sure. On 12/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I would be willing to take on this editor role for a week, once every > month/two months, if we just have a detailed checklist of what to do > during that week, and agree on a format for how to compile an django > roundup. What would be the best way to organize a group of newsletter editors? A mailing list? If so, let's kick it off. Sounds like fun. -Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
