Offering to co-maintain Subscriptions

Hi Ilcho,

Thank you for your offer! I will be happy to work with you.

Please have a look at Best practices for co-maintaining projects. Does that make sense to you?

There are a few open ends in D7 that I'd like to tie down and then make a release as a base for branching.

Have you had a chance to work with Subscriptions and to have a look at the current code yet? I think the overall modular organization is sound, but it's very much in D5/6/7 land, with hooks and generic programming. Essential parts of Subscriptions are also its integration with Mail Editor and its extensions to Token.

We need a robust OO design that respects and supports Subscriptions and Mail Editor as an extensible framework for entities in core and beyond. Does that make sense?

@ilchovuchkov No, you have not been removed.
You are still co-maintainer of this project, with the Maintain issues permission. You cannot administer releases, or commit code, but you can assign issues to other maintainers, or re-open issues already closed.

I need to clean up the issues queue, reach a stable state, and make a D7 release before I can create a D8 branch, as mentioned in #2.