Open source with Closed Contribution vs Open Source with Open Contribution. Feel free to fork. Feel free to read the code. Feel free to use as you like. But do

Open source with Closed Contribution vs Open Source with Open Contribution. Feel free to fork. Feel free to read the code. Feel free to use as you like. But don't bug me. Don't demand I add features. Don't complain that something doesn't work (especially if it actually works). Don't feel like I owe you anything, because I don't. vs. Feel free to fork. Feel free to read the code. Feel free to use as you like. Let me know how its going. Let me know which features you'd like tosee. Tell me when something doesn't work (even if it actually works). I want to be helpful as possible. Both are fine. Both are defensible. But projects should state prominently what they prefer. I have an OSS package on python. Its open source because they can read the code; it's just python, with only third-party package being pillow. But I host the code on a private git instance. I hope people find it useful. If they fork it and make it into something extraordinary, fantastic. But I'm uninterested in exposing myself to time-consuming demands of others.