On 12/11/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > Looks like a good start. If you can sort out the details of how to > manage this as a group effort and get a regular publication rhythm > going, I'll poke Jacob and Adrian and see what we can do.
Great. Thanks. I did ask Jacob if it were possible to tell Trac to not truncate the Changeset descriptions so short. As it is, I have to go into each changeset detail page to view the full details to include. This *could* be automated but it would be much simpler if truncation wasn't so short. I don't know Trac so I'm not sure if this is a setting or not. > One suggestion - another section that might be worth adding is > 'notable blog entries' - There are a few community members that keep > really good blogs (B-List being the most notable example, but there > are others); when they post a good article, it would be worth > mentioning in the weekly update. Definitely. I kept it short just to focus on the Trac stuff and dev list. As the week goes by I'm paying attention to my news reader and will flag blog posts throughout the week. I was also going to include bits from Django snippets, like the Active Directory thing that came through yesterday. What is a bit of a struggle is what to filter. All changesets is obviously too much and you can get that from the timeline anyway. I'm sure I'll often miss what's important to others. My goal is to focus on changesets that have a larger impact on the code base, or dev list threads that have a larger impact, etc. I'm sure that will always be a challenge. Thanks, 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 -~----------~----~----~----~------~----~------~--~---
