RSS feeds for CVS: time for a breakup
Well, not really "a breakup", but time to break them up. Here is the background: In the beginning, there was only a handful of developers, and things were good. Only three committers to core were present, and commits for core were few and far between. Then more core committers were added, for past branch, present one, and HEAD. As well, more CVS committers were added, and a deluge of themes, modules and translations ensured. If someone is busy for a week, and comes back, there is no way to catch up. So, is it time to break the CVS messages into: core, modules, themes, and translations? This would make the lists more granular, and help with the information overload situation ... Thoughts?
So, is it time to break the CVS messages into: core, modules, themes, and translations? Agreed.
Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com Khalid B wrote:
Well, not really "a breakup", but time to break them up.
Here is the background:
In the beginning, there was only a handful of developers, and things were good. Only three committers to core were present, and commits for core were few and far between.
Then more core committers were added, for past branch, present one, and HEAD.
As well, more CVS committers were added, and a deluge of themes, modules and translations ensured.
If someone is busy for a week, and comes back, there is no way to catch up.
So, is it time to break the CVS messages into: core, modules, themes, and translations?
This would make the lists more granular, and help with the information overload situation ...
Thoughts?
I'm not sure there's a way to get a single feed for all modules, or all themes, but you can currently get a feed for just core or for an individual contrib project, right? For example, I use the following for core and CCK, respectively ... feed://drupal.org/cvs?rss=true&nid=3060 feed://drupal.org/cvs?rss=true&nid=48429 - Ray On Nov 26, 2006, at 9:11 PM, Rob Barreca wrote:
So, is it time to break the CVS messages into: core, modules, themes, and translations? Agreed.
Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com
Khalid B wrote:
Well, not really "a breakup", but time to break them up.
Here is the background:
In the beginning, there was only a handful of developers, and things were good. Only three committers to core were present, and commits for core were few and far between.
Then more core committers were added, for past branch, present one, and HEAD.
As well, more CVS committers were added, and a deluge of themes, modules and translations ensured.
If someone is busy for a week, and comes back, there is no way to catch up.
So, is it time to break the CVS messages into: core, modules, themes, and translations?
This would make the lists more granular, and help with the information overload situation ...
Thoughts?
participants (3)
-
Khalid B -
Ray Zimmerman -
Rob Barreca