Closed (fixed)
Project:
UC Node Access
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
18 Jul 2010 at 15:07 UTC
Updated:
24 Aug 2010 at 15:00 UTC
I noticed the community is still working on this and using it, but I don't see any of the maintainers here for almost 8 months despite there being some good patches to look at.
Just thought I would see if they are around and planning to support this thing.
Comments
Comment #1
rszrama commentedI'd happily add a competent co-maintainer to the project. I don't have time to work on this at the moment... not sure about Lyle.
Comment #2
jeremy.zerr commentedRyan,
I'd like to throw my hat in there to offer my help as a co-maintainer, you and Lyle both have way bigger things to contribute to and help with I'm sure. I'd be privileged to be able to help with a goal of getting uc_node_access 6.x out of dev into a stable release and ready it for the future.
Thanks,
Jeremy Zerr
http://www.zerrtech.com
Comment #3
rszrama commentedHey Jeremy, your help would be most appreciated. Do you have much experience with CVS and/or Drupal's method of tagging / branching? Also, are you comfortable with turning down patches until they're "perfect"? : D
Comment #4
jeremy.zerr commentedI have a lot of experience with CVS from working with a previous employer, developing large C++ semiconductor test programs, although I use svn now for my own projects. My experiences with Drupal projects involve contributing patches, testing patches after applying patch using CVS, but I am not a maintainer on any other modules so I don't have any experience doing any commits to any Drupal projects. There seems to be plenty of CVS instructions here: http://drupal.org/handbook/cvs/quickstart, and from looking at uc_node_access in particular, it looks like the branch naming standards are being followed, so I'd suspect that the available community documentation will be sufficient as a reference.
I do understand the need to scrutinize patches, especially in the case of uc_node_access where the only release for Drupal 6 is dev, which means every patch going into dev has to be perfect because that is the release that every user downloads. With the latest usage statistics showing 160 users of the 6.x branch, having patches that break dev is definitely NOT an option.
Thanks for your consideration...
Jeremy
Comment #5
rszrama commentedCool, well I'd be happy to have you do what needs to be done here to get a 6.x release out the door. I'm not sure how you personally use the module, but if there are features you intend to add, it'd probably be best to throw them into a 6.x-2.x branch.
It looks like this module was one where I followed a slightly altered CVS usage policy. The 6.x-1.x work instead of going on in HEAD is actually in the DRUPAL-6--2 branch. So, you'll need to switch there once you checkout and patch against it. When it comes time to call it a release, I tend to start with a release candidate... so you'd tag it DRUPAL-6--2-0-RC1.
I've pinged Lyle on this so he knows we've added you. I'm sure he'll be ok with it, but if not I'll point him to this issue. I honestly couldn't begin to tell you which issues need to be resolved before this is considered release ready. It probably just needs a full feature test to address any remaining bugs and then a release.
Comment #6
rszrama commentedOh yeah... there's some part in this process where we're supposed to make sure you have a CVS account. At the moment I can't make you a co-maintainer... :-/
Comment #7
avpadernoFYI, I made jeremy.zerr co-maintainer of the project.
Comment #8
rszrama commented@kiamlaluno - thank you! : )
Comment #9
rszrama commentedOh, and Jeremy, feel free to contact me if you have any questions.