As said in the http://drupal.org/node/995890 issue (Port to D7), I would like to participate in the development of this module and particularly the upgrade to d7 by providing unit tests and adding features such as native object mapping from drupal entities to ActionScript classes (I already prototyped a working version for class mapping).

I would like to help snelson and other maintainer to make this module integrate nicely with the new Service API and I already provided a working version in the post mentionned !

I've read the requirements to ask for cvs account: http://drupal.org/cvs-application/requirements so this is the first step :)

Hope you'll appreciate my motivation.

Comments

snelson’s picture

snelson commented

Hi Sylvain,

I appreciate your willingness to step forward and contribute. Since you haven't contributed to other modules, I must tell you that the only difference between being an official co-maintainer and a regular contributor is the ability to make cvs commits. This means you can still write code and post/review patches and the like as a regular user, you'll just need a maintainer to commit them for you.

After a past bad experience with the Services module, I don't just hand out co-maintainership. Also, the AMFPHP module is a very simple module, and progress is mostly based on the progress of the Services module, so its development needs are minor, though the new ideas you mention above have been on the radar for awhile, and I would love to see them happen.

That said, you should proceed with obtaining your CVS account and familiarize yourself further with the contribution process, as this will allow you to contribute your own modules. If it turns out to be more efficient for you to be able to make commits directly, and our goals are in sync, then we can revisit co-maintainership. In the meantime, please do post patches to the issue queue and feel free to ping me directly if you want to bring attention to something. I'm happy to make commits and create releases as needed ... that's the easy part. The hard part is writing the code and reviewing patches, both of which can be done without commit access.

Thanks for all your hard work thus far, it looks like we'll be owing you the credit for a Services 3.0 compatible release.

Cheers!
Scott

sylvain lecoy’s picture

sylvain lecoy commented

Thank you for the reply,

To answer briefely I will continue contributing with patches and provides features that I mentionned with examples and tutorials, I just asked for CVS because clean-up patches are bad to apply, but its a small module as you said so we can afford patch submitting process !

Sylvain

sylvain lecoy’s picture

sylvain lecoy commented

I will continue contributing on my git (at github), are you familiare with git ?

snelson’s picture

snelson commented

I eagerly anticipate Drupal's move to GIT, have been using it for years now. CVS is extremely painful to me. However, to keep things simple for everyone else here, it'd be best to submit a patch to the issue once your work gets to a reviewable state. If you're not sure how to do that with GIT, you should be able to find some info somewhere here on D.org about it.

Thanks again,
Scott