Closed (fixed)
Project:
Links Package
Version:
6.x-2.x-dev
Component:
Code: API (links.inc)
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
19 Jul 2009 at 16:54 UTC
Updated:
18 Sep 2009 at 22:27 UTC
It looks the original maintainer is busy to give enough time devoted to this. Should we solicit additional help/mainter from the community? Just a message on the module page, need a maintainer will be a good start.
Comments
Comment #1
ajayg commentedComment #2
ajayg commented@syscrusher,
your contribution so far is very valued and my request above is just to solicit more help for you. I have realized several times the module maintainer is too busy and even don't realize they need help. Hence this request.
Comment #3
vm commentedThis isn't a bug report, changing category and priority.
Comment #4
syscrusher commented@ajayg
No offense taken at all. I think you are right -- I really do need some help on this module. If anyone is interested, please contact me.
I am still very committed to this module, and in fact use it on a number of my own production sites. The problem with my time has been:
1. I've gotten sucked into a number of volunteer efforts for nonprofit organizations *using* Drupal, as the technical admin.
2. I got a promotion at my job, which is great news but also came with more responsibilities. I don't have as much time for OpenSource R&D as I would like.
I feel strongly about the architecture of the Links API and would like to maintain release control over that part of the package personally. But I am very open to contributions from others, for review. And in the areas of user interface and integration with other modules (such as Views and CCK), I am more willing to turn loose some control and would actually welcome someone more experienced with those particular areas to take a lead role.
I hope this doesn't sound too hostile...it's just that, like most Open Source developers, I originally created Links to "scratch my own itch", and I don't wan the API to deviate so far from my original vision that my module fails to meet my own needs. But the Views and CCK side of things is something that I'm doing about 90% for the community and 10% for myself, so I feel that I can and should give up some leadership of that to the community.
Kind regards,
Scott (syscrusher)
Comment #5
ajayg commented@syscrusher
as I suggested, could you please write on the main page of the module "seeeking co-maintainer"?
Comment #6
vm commentedadded note to project page.
Comment #7
ZenDoodles commentedBased on our conversations earlier, I'd be honored to be your co-maintainer.
Comment #8
syscrusher commented@rsoper: I concur. To the CVS team, this has my approval as module owner, and I plan to add rsoper to CVS access list.
Comment #9
avpadernoI approved rsoper's CVS account, and granted him access to the project CVS.
Comment #10
syscrusher commented@KiamLaLuno
Thanks
Comment #12
avpadernoComment #13
syscrusher commentedWe do have an additional maintainer now -- rsoper has graceiously volunteered to step in and help. We have been conferring over the past week to set priorities and assign tasks, so things should start moving again shortly.
Syscrusher