Closed (fixed)
Project:
Mediawiki auth bridge
Version:
6.x-0.7
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
4 Mar 2010 at 03:45 UTC
Updated:
16 Feb 2011 at 18:50 UTC
While I'm still interested in keeping this project alive, my primary use case for it (for a client) has gone away (basically replaced by OpenID) so I have lost any way to test patches or work submitted through the trackers. Although there hasn't really been any patches submitted yet, there are some issues that could have been addressed if I still had the environment to actually test this stuff.
So I'm looking for help. I'd be happy to open commit access and release management rights to the project if someone would step up to do the work.
Otherwise I'll just stick around and let the natural review process take its due course.
Comments
Comment #1
seanburlington commentedHi,
I'd be happy to take on co-maintainership of this module
I'm currently using it on http://data.gov.uk/ and would like to supply a patch initially for #421050: move configuration to the database
My project has connections with the mediawiki team and will be using both products in the long terms so it'll be great to be able to help them work together.
I'll write the patch and happy to provide further info if you require.
Comment #2
anarcat commentedCool! Welcome to the project! I would like to see that patch before sharing the maintainership if you don't mind.
How long do you think you could get involved here?
Thanks.
Comment #3
seanburlington commentedHi anarcat
I've posted a first version of the patch at #421050: move configuration to the database
It'd be great if you could test it out and see if it looks OK.
Comment #4
anarcat commentedHi!
I reviewed the patch, and unfortunately, i feel there's more work needed so that it gets in the tree at this stage. It's a much needed cleanup, but there's still a little more to do I think.
Also, you haven't answered my question about how long you're ready to commit to maintaining this project. I feel it's important to know that because sometimes people just get maintainership, commit their stuff and leave and then we loose the "historical memory" of the project. :)
Thanks for your patience, we're almost there!
A.
Comment #5
seanburlington commentedHi,
thanks for the review - I wonder if you could say what kind of work is still needed?
I'd be willing to commit to work on this module for a year at least (during which time I'd keep one or more test environments available.
Comment #6
seanburlington commentedah OK - I've seen the comments in the other issue - will address
Comment #7
seanburlington commentedHi,
the patch is updated - I wonder if you've had a chance to look and see if it's suitable
Thanks :-)
Comment #8
anarcat commentedSorry for the delays, I've been veery busy with Aegir and other stuff.
This all looks good now.
I would like to give you CVS access so you can commit all those "reviews and tested" patches yourself. However, it seems your drupal.org account doesn't have CVS access yet, so you'll have to apply for that separately: http://drupal.org/cvs-application/requirements
Once you have that access, feel free to commit more fixes to the tree, but try to keep to the standards we have set here (no mixed commits, try to fix one issue per commit, etc). Ideally, report bugs or feature requests before closing issues so we can track more easily what's going on without having to look at the changelog.
Once you've done your much-needed cleanup, we should probably make a new release, I'd love to coordinate that with you.
This issue can stand as an agreement from me to accept you as a co-maintainer. You can link to this issue in your CVS application. Good luck!
Comment #9
seanburlington commentedHi Anarcat,
I now have a cvs account - I'm afraid that it came through at a time when I was fairly busyt and I'm only now getting around to using it.
I have logged in and am ready to start committing patches.
Can you give me commit access to this module.
I see that there are now people asking for updates which is great :-)
Sean
Comment #10
seanburlington commentedHi Anarcat,
I'm quite keen to get some code committed if possible
just a reminder as this has probably gotten lost in your inbox by now
Sean
Comment #11
anarcat commentedHi Sean!
Sorry for the delay, I missed that comment for some reason... Congratulations on your new account, hopefully you can get around the source tree and improve this module! Let me know if you want to make a new release...
Oh yeah, and you have CVS write access now of course. :)