[development] New module makes custom menus from taxonomy - experienced coder wish to pick this up?
pwgdarchive at gmail.com
Thu Aug 28 12:57:13 UTC 2008
There's a Taxonomy code sprint coming up in Chicago next month-
The organizers have their own agenda, but it might make sense to get
it released before then when a lot of taxonomy stuff is going to be
You could do that simply by posting a link to the files at the
taxonomy group, http://groups.drupal.org/taxonomy
Agaric Design Collective
Open Source Free Software Web Development
On Thu, Aug 21, 2008 at 5:29 PM, robert crowther <r.crowther at zen.co.uk> wrote:
> Hello Adrian,
> It's taken me a few days to reply, apologies.
> First up, thank you for taking the time to mail back explaining what I
> should do. No need for people to do that, but lists and forums would be
> better for the effort.
> See, I didn't think it was releasable, so I didn't follow any links on
> Drupal contributions. I don't even have that much culture. I've never
> used a content versioning system, let alone know where to find the
> Drupal one. So I may take this route up.
> Any project has a curve of learning plotted against achievement. I have
> learned about not one but two Drupal menu systems, taught myself PHP,
> and written the modules. In a few weeks. This is the obvious place for
> me to stop. But given that there is an evident low level interest in
> such a module, I wondered if it should go out work somewhere.
> I was aware of
> "I can't be bothered to maintain this, can someone do it for me?"
> Hope the above explains.
> I'm also aware of the strangeness of posting to the dev list. But the
> module reads like a core module in places. It needs that quality of
> input to make it solid.
> Yes, maybe I wouldn't subscribe to a dev list normally, but I would
> always trawl the dev list archives on any project. Wouldn't anybody? I
> like to know what can be known before I set my compass.
> Thanks again for the information,
> On Tue, 2008-08-12 at 09:11 +0100, Adrian Simmons wrote:
>> robert crowther wrote:
>> > All you have to do is mail me back, and we can take it from there.
>> This is what Drupal's CVS contrib repository is for! :)
>> Seriously. Upload it to contrib, make a project and just have a development
>> release, in the project description tell people about it and that you
>> consider it alpha or beta quality. Say you're looking for a co-maintainer.
>> If people want to use it and find bugs, you'll get bug reports. If you're
>> lucky you'll also get patches. You may even get someone interested enough to
>> help maintain it.
>> But just posting to the dev list like this (is everybody that writes modules
>> even subscribed to this list?) has more of an air of "I can't be bothered to
>> maintain this, can someone do it for me?".
>> At worst it'll sit in contrib and nothing will happen, at best you may get
>> patches that teach you better php coding :)
More information about the development