Re: [development] Was, write a simple field type for CCK, now module
This list is for Drupal core development,
Where, then, should those seeking help with module development turn? There's a themes list, but not one for modules.
John Summerfield
This list was originally for core development. The core developers have (for understandable reasons) decided that all public core development conversations should take place on d.o or g.d.o. As such this list has no real point without changing its raison d'etre. For what it's worth, I'd be happy for this to be the list that handles more technical activity than support (e.g. if you're writing a custom module and are having difficulties with hooks or the API etc) and accept that there will be some grey areas with the support list, which could be more installation/how do I do this orientated.
On 29/02/12 12:38, David Hart wrote:
This list is for Drupal core development,
Where, then, should those seeking help with module development turn? There's a themes list, but not one for modules.
John Summerfield
This list was originally for core development. The core developers have (for understandable reasons) decided that all public core development conversations should take place on d.o or g.d.o. As such this list has no real point without changing its raison d'etre.
For what it's worth, I'd be happy for this to be the list that handles more technical activity than support (e.g. if you're writing a custom module and are having difficulties with hooks or the API etc) and accept that there will be some grey areas with the support list, which could be more installation/how do I do this orientated.
This would be very welcome, I for one could do with somewhere to ask questions regarding API and module development that are well above what support is likely to offer but are not core. -- ----------------- Bob Hutchinson Midwales dot com -----------------
I agree that this list should be repurposed for technical development discussions. Let's get out of the habit of scolding users for posting development questions to the development list. Regards, Richard -- http://fs.io/ http://dgo.to/@psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/
I agree as well. There is a valid use case for a list that addresses development of modules and actual problems people encounter when developing new functionality that is separate from support. This would hopefully end the pattern, of late, of the list being dead until someone has a support question and someone else smacks it down. Regards, Sam Tresler On 02/29/2012 08:06 AM, Richard Burford wrote:
I agree that this list should be repurposed for technical development discussions.
Let's get out of the habit of scolding users for posting development questions to the development list.
Regards,
Richard
-- http://fs.io/ http://dgo.to/@psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/
Agreed, as well. Given that most core discussion has moved elsewhere, I don't see the problem in repurposing this list for general module development (as opposed to support being general Drupal "how-do-I" questions). Regards, Todd On 29 February 2012 09:45, Sam Tresler <sam@treslerdesigns.com> wrote:
I agree as well. There is a valid use case for a list that addresses development of modules and actual problems people encounter when developing new functionality that is separate from support. This would hopefully end the pattern, of late, of the list being dead until someone has a support question and someone else smacks it down.
Regards, Sam Tresler
On 02/29/2012 08:06 AM, Richard Burford wrote:
I agree that this list should be repurposed for technical development discussions.
Let's get out of the habit of scolding users for posting development questions to the development list.
Regards,
Richard
-- http://fs.io/ http://dgo.to/@psynaptic http://twitter.com/psynaptic http://drupalcontrib.org/
On Wed, Feb 29, 2012 at 7:38 AM, David Hart wrote:
This list is for Drupal core development,
Where, then, should those seeking help with module development turn? There's a themes list, but not one for modules.
John Summerfield
This list was originally for core development. The core developers have (for understandable reasons) decided that all public core development conversations should take place on d.o or g.d.o. As such this list has no real point without changing its raison d'etre.
Other than proving that self moderation can maintain control of a list, I agree.
For what it's worth, I'd be happy for this to be the list that handles more technical activity than support (e.g. if you're writing a custom module and are having difficulties with hooks or the API etc) and accept that there will be some grey areas with the support list, which could be more installation/how do I do this orientated.
I'll agree with this as well *if* you can get the description for the mail list changed both at http://drupal.org/mailing-lists and http://lists.drupal.org/mailman/listinfo. -- Earnie -- https://sites.google.com/site/earnieboyd
participants (6)
-
Bob Hutchinson -
David Hart -
Earnie Boyd -
Richard Burford -
Sam Tresler -
Todd