[development] Drupal core initiatives
sam at treslerdesigns.com
Tue Jun 14 15:02:16 UTC 2011
I could be mis-reading the issue at hand, but isn't this remarkably similar to how the Internet Engineering Task Force does RFC's? If the problem is attempting to manage proper circulation of concepts that core developers are working on, then it seems appropriate to assign statuses: "Informational", "historic", "experimental", etc.
If that is the goal, then A) Angie is spot on with the need to call for writers with free time. B) No, a mailing list is not the proper venue. and C) probably g.d.o. isn't either.
Sorry to not have a specific solution in mind, but maybe the above methodology, refined since 1969 - might be a good place to look for a model?
On Tue, 14 Jun 2011, Greg Knaddison wrote:
> On Tue, Jun 14, 2011 at 6:31 AM, Earnie Boyd
> <earnie at users.sourceforge.net> wrote:
>> It would be nice if I could login to my g.d.o account, go to this group
>> landing page and have an option to follow content to my subscribed email
>> account. That is similar to what happens with the project issues
>> queues. I can flag the project issues as interesting to watch so that I
>> can help if necessary or time permits.
> This is prevented by bugs in OG and messaging/notifications.
> See http://drupal.org/project/issues/search/?issue_tags=gdolove for
> more details.
> Greg Knaddison | 720-310-5623 | http://growingventuresolutions.com
> Security Services for Drupal sites: http://drupalscout.com
More information about the development