On Tue, Apr 21, 2009 at 12:43 AM, Ryan Cross <drupal@ryancross.com> wrote:
This sounds like it would also have the knock-on effect of making it easier for more/different modules to get included in core over time, which I think many people are also keen on.
I think it'd make it easier to move modules in and out of core yes. With token specifically that'd be unlikely to be a module in Drupal core - it'd probably be part of system.module since everything else would need to use it. Views also would have to move into core proper since we'd want to use it for administrative pages etc. - so it's not a model that'd work for everything, and generally not for 'cool API-providing modules we want to see in core'. The only reason I'd suggest it for things like comment and forum is they don't provide far-reaching APIs.
I am not sure I followed the necessary cvs tag work flow completely, but I'm sure you're discussed the details and the overview sounds good. Would this mean that we would get a packaging script for install profiles?
We didn't discuss this in any depth, just the overview.
Side note - several people are commenting that comment.module is quite poor. Is there an alternative that people are using that I'm not aware of? It works for me usually.
comment.module works for most things, but the code, APIs, architecture and a few very annoying long-running bugs haven't changed much since Drupal 4.something. For the basic job of attaching comments to nodes it's completely fine, but it's not what it should be. For example you can't attach fields to comments in Drupal 7 yet, and no-one has started work on a patch. More on that general area here: http://groups.drupal.org/node/18705 - and no I'm not aware of any viable contrib alternatives except nodecomment. Nat