Closed (fixed)
Project:
Protected Node
Version:
6.x-1.5
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
21 Mar 2010 at 01:58 UTC
Updated:
29 Apr 2011 at 00:02 UTC
As discussed elsewhere - I'd like to become co-maintainer for this module (and make sure that the code I did in another issue, gets somewhere inside a drupal.org project tree :-p)
Creating this issue as a point of reference.
But I'm not in an immediate hurry. I could do some work before getting CVS access - e.g. review #286028: Would you consider a patch for inheriting node protections?, because that should be pushed through before any newer patches.
I do not currently have a CVS account. I have a module in the works; if I get that polished and approved within a few weeks, we can make me co-maintainer then.
Comments
Comment #1
mtolmacs commentedRoderik, you're welcome! Let me know when you have a CVS account and I try to add you as co-maintainer.
Comment #2
AlexisWilke commentedtolmi,
I'm finding a few issues, it looks like roderik has not moved forward... If you don't mind the help, I'd be pleased to fix a few things and help the way I can.
Thank you.
Alexis
Comment #3
mtolmacs commentedI'm all for this, please start submitting patches and do a review of Frank's patch on indexing, then I can consider it.
(Note that I've worked together with Roderik in person and he had to switch away from Drupal development)
Comment #4
AlexisWilke commentedAh! It does not look like he was working on the system since he did not say he had a CVS account... 8-)
Good, I have the problem with the cache as well. And a problem with PostgreSQL.
Do you prefer to get patches in an issue first? (rather than giving me CVS access)
Would you consider getting a 6.x-dev version? So that way we can let others test the changes without them having to get the code from CVS (really, a lot of people do not know anything about CVS.)
I'll test Frank's patch after I'm done testing the cache problems. I already wrote a little something to prevent boost caching.
Thank you.
Alexis
P.S. Oh! I see that this request is Roderick's and the patch is Frank's... 8-)
Comment #5
mtolmacs commentedI've worked with Roderik in the same company not on d.o
I'd rather have some patches from you and if it's going well I'm fine with giving you co-maintainership.
I will roll a 6.x-dev immediately.
Comment #6
roderikThanks guys. Go ahead. I'm just really slow in doing things, and not spending as much time on Drupal as I should. (Has it already been 3 months? Geeze,)
Will catch up with you sooner or later, and then see if I still need to help out here :)
Comment #7
AlexisWilke commentedI'll close this issue since I now have co-maintainership and I don't see too many of roderik's posts around... Although the node parent/child behavior sounds interesting to protect a whole book, for instance!
Thank you.
Alexis