Visnu, You can simply join the channels. See http://drupal.org/irc for an overview of available channels and make sure to choose the most appropriate channel for your needs. Marc PS When replying to the mailing list, please quote as little as possible. vishnu vardhan wrote:
Hi All , Can i join #drupal chaneel or do i need recomendation??? Visnu
On Tue, Dec 1, 2009 at 5:10 PM, <development-request@drupal.org <mailto:development-request@drupal.org>> wrote:
Send development mailing list submissions to development@drupal.org <mailto:development@drupal.org>
To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/mailman/listinfo/development or, via email, send a message with subject or body 'help' to development-request@drupal.org <mailto:development-request@drupal.org>
You can reach the person managing the list at development-owner@drupal.org <mailto:development-owner@drupal.org>
When replying, please edit your Subject line so it is more specific than "Re: Contents of development digest..."
Today's Topics:
1. Consolidating duplicate contrib modules for D7 (Brian Vuyk) 2. Re: Consolidating duplicate contrib modules for D7 (Andrew Berry) 3. Re: Ctools form wizard (Earl Miles) 4. Re: Consolidating duplicate contrib modules for D7 (Shai Gluskin) 5. alter theme registry, but only for some themes. possible? (David Cohen) 6. Re: Consolidating duplicate contrib modules for D7 (Martin Stadler) 7. Re: Consolidating duplicate contrib modules for D7 (Zoltan Varady)
----------------------------------------------------------------------
Message: 1 Date: Mon, 30 Nov 2009 14:44:58 -0500 From: Brian Vuyk <brian@brianvuyk.com <mailto:brian@brianvuyk.com>> Subject: [development] Consolidating duplicate contrib modules for D7 To: development@drupal.org <mailto:development@drupal.org> Message-ID: <4B1420BA.7010404@brianvuyk.com <mailto:4B1420BA.7010404@brianvuyk.com>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I know the whole 'duplication in contrib' issue has been discussed to death on this list, so I will try to keep this short.
Obviously, the duplication in contrib is something we are working hard as a community to avoid. Nevertheless, in some cases, duplication has still crept in, and this leads to a poorer user experience, and user confusion.
One prime example is the node access modules, which all perform nearly identical functions with more or less polish:
Node Access: http://drupal.org/project/node_access Nodeaccess: http://drupal.org/project/nodeaccess Content Access: http://drupal.org/project/content_access
Now, is there anything we as a community can do to clean up this sort of issue in contrib? I realize that in individual cases, the best policy is to post in the issue queues for the individual projects, but on a larger scale, is it worth starting something along the lines of #D7CX to consolidate the dupes in the name of a better user experience?
------------------------------
Message: 2 Date: Mon, 30 Nov 2009 15:22:55 -0500 From: Andrew Berry <andrewberry@sentex.net <mailto:andrewberry@sentex.net>> Subject: Re: [development] Consolidating duplicate contrib modules for D7 To: development@drupal.org <mailto:development@drupal.org> Message-ID: <53A37D3A-8063-4E4A-B679-19689DCE51E7@sentex.net <mailto:53A37D3A-8063-4E4A-B679-19689DCE51E7@sentex.net>> Content-Type: text/plain; charset="us-ascii"
On 2009-11-30, at 2:44 PM, Brian Vuyk wrote:
> Node Access: http://drupal.org/project/node_access > Nodeaccess: http://drupal.org/project/nodeaccess
IMO there should be a CVS policy disallowing namespaces to be differentiated with dashes, underscores, spaces, and so on. This is a perfect example of the confusion this can cause.
> is it worth starting something along the lines of #D7CX to consolidate the dupes in the name of a better user experience?
I think that if this is something you want to do, you should try and find some of the more popular maintained modules and try to get one or two sets of projects on board. Once there are a few big projects starting down this path, I think it would really help to encourage the smaller projects to work together.
--Andrew