There are many crucial outstanding issues in the queue, at least for 7.x.

I am applying for co-maintainership so that those can be committed. This is important to me since I am the maintainer of the 7.x branch of the Salesforce API module, which strongly recommends this module. I would have difficulty recommending people use the 7.x version of this module in its current state.

If accepted, I wouldn't be doing anything beyond bug fixes for this module, and only for 7.x.


EvanDonovan’s picture

lee20’s picture


Thanks for your contribution to the AES module. As I have not found the time that I anticipated to serve as the sole maintainer of this module, it would be great to have your assistance.

If it's my place to accept you as a co-maintainer, you are accepted! You may also consider yourself as the primary maintainer at this point as I won't have much time to contribute in the foreseeable future.


EvanDonovan’s picture

Thanks, sounds good.

EvanDonovan’s picture

Status: Active » Fixed
EvanDonovan’s picture

Status: Fixed » Active

Actually I'm not seeing myself as having access yet. Did you go in to edit the project and add my nick as a maintainer?

rfay’s picture

Status: Active » Reviewed & tested by the community

Would like to see this happen!

EvanDonovan’s picture

Status: Reviewed & tested by the community » Fixed

Sorry, this was granted to me apparently, but I didn't hear about it as far as I could tell, so I didn't know it.

I will try to make the commits by this weekend at the latest.

Status: Fixed » Closed (fixed)

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