@strk has been putting in patches for the past couple months on the issue queue and has been a valuable resource in testing other patches. I have also spent a fair amount of time on IRC talking with him and trying my best to get him up to speed on the module. I think it would be very valuable to bring him in as a co-maintainer to the project.

Obviously we will need consensus on this, specifically @tmcw's opinion. If @phayes is still around, your opinion is always valuable as well.

Though its not written down anywhere, I feel we do try to do the following:

  • Discuss any significant changes via the issue queue and patches.
  • Practice good coding by adhering to Drupal coding standards (this applies to more than just PHP)
    Though we are not perfect on this, I feel like it would be beneficial for you to read up on these.
  • Aim for stability with each commit, and ensure that each official release is as stable as possible.
  • Try to be courteous and respectful of each other.

So, @strk, you should comment here that you do want this. If this is resolved favorably, then you will have to apply for a CVS account. Make sure to read everything carefully and site this issue in the application. Once that happens, let me know and I can review and (probably) approve your application.

Comments

strk’s picture

I'm happy to take up co-maintainance role.
Did read coding standards and agree on the each-commit-is-stable paradigm.

tmcw’s picture

Great, I'm fully in support of this.

zzolo’s picture

Awesome. @strk, go ahead and do the application process and make sure to link to this and then link me to the application issue and we can push it through.

strk’s picture

CVS application filed. Thank you.

zzolo’s picture

Hey @strk, can you provide a link?

zzolo’s picture

Status: Active » Fixed
strk’s picture

I'm on board, all fine.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.