Closed herbdool closed 2 years ago
I would rather then handover the maintenance to a wider community. I am happy to take this on and make this a community extension as it is a useful extension.
"Deprecated" sounds like the wrong designation for this scenario. It sounds to me like "Seeking Maintainer". I don't know what "community maintenance" means: are there processes in place for such a designation?
It's my own pet peeve when people talk as if maintainer status not being handed over is a block to any volunteer contributions. It should be the reverse... any "Seeking Maintainer" extension should be a sign for others to donate freely, and if someone establishes a track-record, they can petition the previous maintainer or the community to get the official status.
FYI, I have no intention of using this extension in the future. ;-)
@ginkgomzd with community I mean that several people have merge rights on this repo so that when someone submits a pull request it gets merged and it is not dependent on one specific person. I am happy to take that on but lets see what @nganivet thinks about that.
@jaapjansma Thanks for offering to maintain this extension in the future. Do you a) have clients that use this extension, and b) have a test environment in place for testing incoming PRs?
@herbdool I see no reason this extension should be deprecated. Could you please suggest a language that would indicate this extension is "seeking maintainer" according to the lifecycle documents mentioned in your first post? I will then update the README.md accordingly. Thanks.
@nganivet I have two clients who are using sparkpost. Those are long term clients and I work with them regularly. Both are in need for the transactional email bounce handling. (See #105) and one of them funded this. Both are behind CiviProxy and both use https://github.com/systopia/be.aivl.sparkpostbounceapi to track bounces through CiviProxy.
@jaapjansma @herbdool @mlutfy , per this and #103 it would make sense to merge these forks (incl. @JoeMurray's) into a single extension maintained on lab.civicrm. Is this something you can co-ordinate between the 3 of you?
Yes I am happy to coordinate. @herbdool and @mlutfy and @JoeMurray are you joining?
We would be willing to help out some as we use the extension for a few clients, though we have been migrating lately to other services in some cases.
Thank you @jaapjansma, tell me if you need anything on my end.
I've got too much on my plate at the moment. I'll continue to make PRs or reviewing them when I can.
If you could add JMA as maintainers after yourself, Jaap, that would be great.
@herbdool thanks no problem.
@JoeMurray as soon as I am a (co-)maintainer I will add you.
@nganivet I have two questions for you:
Thanks @jaapjansma 1. is Done, and I would vote yes on 2 since it is now community maintained. @mlutfy, can you please facilitate migration to lab.civicrm.org?
Thanks!
Here is the doc for moving from Github to Gitlab:
https://lab.civicrm.org/extensions/extensions-directory/-/wikis/import-from-github (create a token, import to Gitlab, then ping me on mattermost's extension channel, or here)
Thanks @mlutfy I have imported the project to https://lab.civicrm.org/jaapjansma/com-cividesk-email-sparkpost can you move it to https://lab.civicrm.org/extensions/com.cividesk.email.sparkpost?
The extension is moved to https://lab.civicrm.org/extensions/sparkpost/
According to https://docs.civicrm.org/dev/en/latest/extensions/lifecycle/ it seems that if the extension is no longer being maintained that it should either be marked as deprecated, or be reported to https://lab.civicrm.org/extensions/extension-review-requests/issues to be delisted or unpublished.