Is the AES module really abandoned? [#1067648]

@easyfit
The project page has this module labeled as abandoned yet I see recent activity in the issue queue and your last last commit was approximately 3 weeks ago. So the project hardly seems abandoned but I would like you to confirm.

Thanks.

Comments

Comment #1

easyfit CreditAttribution: easyfit commented 21 February 2011 at 15:20

Yes it is I'm afraid. I decided to abandon it right after I got the D7 version out, which was about 3 weeks ago.

I'm abandoning it partly because personally I haven't had any need for this module for a long time now (I basically just needed the D5 version - everything after that is just because I wanted to help other people out and it was fun to support it for a while). And partly because it's kind of a strange module in the way that it does 2 pretty separate things: it gives you readable/decryptable passwords, but it also acts as a general purpose encryption API; so 2 things which would technically be better to have as 2 separate modules.

But basically I just don't feel like supporting this module anymore, I have so many other things I want to do on my spare time (some of which are actually fun). However if someone else would want to take over maintainership and keep it alive (wink wink), I would be very happy to hand it over.

Comment #2

lee20 CreditAttribution: lee20 commented 21 February 2011 at 21:29

@easyfit

Thanks for taking the time to respond and thank you for everything that you put into this module. I certainly understand that contributing to a module can become a headache after it becomes irrelevant to your current work.

I definately see that this should have been designed as two separate modules packaged together.

I would offer to take over maintaining the module but I may need to find a co-maintainer for D7. When my client work starts to move towards Drupal 7 perhaps I can support the D7 release.

If you want to add me to the project and give me CVS access I can post fixes for the D6 branch. I will also consider writing and releasing a 2.x branch which breaks the functionality into two different modules: aes and aes_user

The module seems to be easily be configurable as "aes standalone" without touching user passwords but you still wind up with the unnecessary database table.

My only hesitation in taking over a module is my despise for CVS. It seems I always have to look up the CVS commands when I want to commit a patch. I am hoping to be able to make more commits when Drupal has successfully migrated to Git.

Thanks again.
Cheers.

Comment #3

easyfit CreditAttribution: easyfit commented 22 February 2011 at 07:59

That sounds awesome! It's great to hear you're willing to take over the module, and splitting it up into 2 is a good idea.

It just ended up having dual functionality sort of by chance. It was really just because at the time there were no other Drupal encryption modules, so I had to write a simple encryption API myself in order to have that functionality for this module, but then since I had written that little handy easy-to-use encryption API, I thought I might as well advertise it alongside the decryptable passwords thing, so that others could potentially benefit from having this module as a dependency to their own, which also happened, and which is cool, but of course in retrospect it's not very good from a design perspective.

I completely know what you mean about CVS, when doing new releases I would sometimes feel like I spent almost as much time figuring out CVS as I did coding and testing. It's not too bad though once you start memorizing the basic commands you need (which only took me a couple of years) :) and like you say they're moving to Git now anyway.

I've made you a maintainer and given you write access to CVS etc. And of course I'm available if you have any questions about the code or anything else. Well, good luck! :)

Comment #4

lee20 CreditAttribution: lee20 commented 22 February 2011 at 16:48

Status:

Active

» Fixed

@easyfit

Thanks for allowing me to jump in and support this module. I am very excited for the CVS to Git migration as it will hopefully help me as well as others in contributing more to the community.

I will be updating the project info as "Seeking Co-maintainers" in search of someone who may be interested in supporting the 7.x branch for a while.

Sometime in the next few months I will announce a 2.x branch that will split the modules in two and provide a clear upgrade path.

Thanks again for your work on this module and for offering assistance if I have any questions.

Cheers