Posted by Bèr Kessels on May 17, 2006 at 8:44am
We need one drupal.org project node and a CVS in contribs where we can place all this. For that we need a maintainer.
I volunteer to be that. But maybe others want to volunteer too. Please comment if this sounds like a fun idea to you! Please also comment whether or not you already have CVS access, because that is a critical factor.
Comments
I'd be glad to help out in
I'd be glad to help out in any way and am also willing to be the maintainer or co-maintainer or neither and just contribute ideas and code. I have cvs access.
If you create a project on
If you create a project on drupal.org then you have the commit rights, can you do that?
http://www.webschuur.com | http://bler.webschuur.com
I can do that. What shall we
I can do that. What shall we call it? I was thinking of content_profile, both to indicate it goes with the content module and so it sorts right by the content module on the modules and download pages, but I don't really care what we call it.
profiles as nodes
simple. and to the point. After all. CCK is just a single use of this. not The Only one.
http://www.webschuur.com | http://bler.webschuur.com
long
profiles as nodes is quite long.. what about "nodeprofiles"?
Yes I was trying to decide
Yes I was trying to decide what to use as the module base. Does nodeprofiles seem reasonable or is that still too long? Also, while I agree that it might be nice to expand this to non-cck nodes, this discussion did start based on the use of a cck node as a profile, and the group description specifically refers to cck, so that was why I suggested a content name. If we don't want this limited to cck, the group description probably needs to be updated to reflect that.
I will upgrade the group description
and nodeprofiles sounds like a nice name to me.
http://www.webschuur.com | http://bler.webschuur.com
I hate to back up on a
I hate to back up on a commitment, but I am getting very busy with several modules that are a higher priority in my application than this is. This is an important project and I don't want to be holding things up, so maybe it would be better if someone else who is actively working on this now was the maintainer. I'll still help out whereever I can.
Might as well figure this out before starting the project page so the right person gets set up with commit rights.