Plugin Contributors
I'm very proud to be the maintainer of a module (Export Sheet to PDF) that is getting many, many contributions to the point that I'm now making many releases without doing any work on the code myself.
These fantastic contributors are typically submitting a small plugin file (I call them "mappings") which contains some code, but is completely distinct from what I consider as the main code base.
Because of this, I'm concerned with my current approach to incrementing my package's version number as if those updates were to the main code (i.e. with semver I increment the minor version for new features and the patch version for fixes). Does anyone have any ideas on a better alternative to versioning that I can use going forward, but that still mostly complies with semver.
I'm also looking for advice on how I can attribute these contributors to make them feel appreciated. I currently ping them in the release notes and discord channels to thank them publicly and I also provide a file where they can leave their name and contact info in the repo (https://github.com/arcanistzed/pdf-sheet/blob/main/mappings/README.md).
Another thing that I'm looking to discuss is some best practices for keeping in contact with contributors regarding keeping their contributions up to date.
These fantastic contributors are typically submitting a small plugin file (I call them "mappings") which contains some code, but is completely distinct from what I consider as the main code base.
Because of this, I'm concerned with my current approach to incrementing my package's version number as if those updates were to the main code (i.e. with semver I increment the minor version for new features and the patch version for fixes). Does anyone have any ideas on a better alternative to versioning that I can use going forward, but that still mostly complies with semver.
I'm also looking for advice on how I can attribute these contributors to make them feel appreciated. I currently ping them in the release notes and discord channels to thank them publicly and I also provide a file where they can leave their name and contact info in the repo (https://github.com/arcanistzed/pdf-sheet/blob/main/mappings/README.md).
Another thing that I'm looking to discuss is some best practices for keeping in contact with contributors regarding keeping their contributions up to date.
Similar Threads
Was this page helpful?
