Make stash-readme-barser plugin opensource

Create issue
Issue #31 new
Beau Smith created an issue

Any reason why this plugin is not open source?

I'm guessing that a majority of the code it uses/implements is open source.

Like myself, I'm sure others would love to submit patches to this plugin.

Comments (5)

  1. TheresaH

    Hi @beausmith ,

    yes, actually we gave it a thought...

    There different considerations to take into account:

    The plugin would still have our name on it. Others would have constributed to it, but it would still be our responsibility to

    • test the plugin functionality
    • create the marketplace releases (which include screenshots, description texts, ...)
    • manage which features to accept into the plugin

    Though we embrace the open source idea itself, it would probably come at a price (of our freedom to code), we are not so sure about. I hope you understand, that because of these problems we are still unsure about that.

    Is there a specific feature you are looking for or want to constribute?



  2. Christopher Hiller

    Hi Theresa,

    I'm a bit confused about your above post.

    • There's no reason you can't have your name on it and retain copyright. Adding a permissive license like MIT only allows contributors to make modifications and redistribute.
    • The responsibility of testing code is shared between maintainer and contributor. If a contributor attempts a pull request without tests, it is fully within your rights to decline it. This assumes, of course, that there are some tests somewhere in the first place.
    • If you do not want a feature, it's trivial to decline a pull request. However, if the community would feel better served by a feature that you have declined, expect it to be maintained in a separate fork out of your control.
    • You wrote, "I hope you understand." Unfortunately, I don't understand your concerns about your "freedom to code". The project remains yours and you are free to do with it as you see fit.
    • Official releases can still go to the marketplace, but releasing the code into a OSS license (and hosting on BitBucket or GitHub) would allow users to pick up fixes and features much more quickly (and install manually).

    Please note it may or may not be completely within your rights to keep this project closed-source, depending on the OSS project(s) you are using.

    There has not been much activity on this project recently, and I would like to see issue #32 addressed, as my fenced code blocks are breaking. If this project was open-source, I would attempt a fix myself, but I can't.

    I'm sure there are plenty of willing contributors like myself and @beausmith ready to help and improve this plugin. I cannot see how releasing the source would be a detriment to the project.

  3. Log in to comment