vgarvardt [vgarvardt]

Hello, and thank you for applying for a CVS account. Some volunteers will review your code, pointing out what needs to be changed.

As per http://drupal.org/cvs-application/requirements, the motivation message should be expanded to contain more details about the features of the proposed module, and it should include also a comparison with the existing solutions.

I am adding the issue tags.

Thanks for the expanded description.

Wow, thats pretty messed up. This should be escalated. I will go on IRC and check it out.

As the module code has been posted in a comment outside the CVS applications queue, I think there is few that can be done.

Well, I know there may not be any legal action, but as a community, something should be done, IMO. If nothing will be done by the drupal.org maintainers in some form to at least say that these actions are not cool, then I happy to be a vigilante.

Note that I started this thread to get more information: http://drupal.org/node/753802

I don't see how this is an issue? The code is credited and has been from day one. Would've been nice of dixon_ to ask before creating a project, but it's all open source and copyright would remain with vgarvardt, for what it's worth.

I'm sure this can be resolved between dixon_ and vgarvardt.

@kiam, in light of his work, can vgarvardt be given a CVS account?

@vgarvardt when you get a CVS account, raise an issue with dixon_'s issue queue asking to be co-maintainer or maintainer, since you wrote the original code. If dixon_ is not really an a**hole (as I suspect) then he'll have no issue with your request. I'm sure he just jumped the gun and didn't realise he'd cause offence. =)

I have spoken to Dixon and he has no problem to hand the project over to vgarvardt.

Kiam: can you please give cvs access to vgarvardt and transfer the module to him? Please add dixon_ as co-maintainer.

vgarvardt: Please contact dixon_ about the future strategy WRT that module.

Cross linking to my response for this: http://drupal.org/node/753802#comment-2770670

I have done as said by killes.

Thank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

I thank all the dedicated reviewers as well.