13 ms·

Ah, forgive me about the website license, I was looking for a LICENSE file. Not used to Gitlab that sets it at repo level. Privacy policy is needed when you ha

by rapnie 3y ago

Ah, forgive me about the website license, I was looking for a LICENSE file. Not used to Gitlab that sets it at repo level. Privacy policy is needed when you have a login and use e.g. the Github app. Even while you delegate everything to Github, you have access to some personal information. A relatively simple privacy policy should make you GDPR-compliant. ToS may be too formal, and FAQ can be enough. CoC I'd definitely include. As for matchmaking. Can any maintainer chime in once I joined? Or can I select the ones that can have access, and others I rather not grant that? Can I be assured that maintainers use the dev process of my preference? I guess CODESHELTER.md should describe that last bit. The website content is not bad at all. Still, honing it further might lower the barrier to use. Hope this small chunk of extra feedback is helpful.

stavros 3y ago
This is great, thanks! I'll ass a privacy policy and look into a CoC, thanks. Any maintainer can be added to the repo, yes. The idea is that there will be a community-driven process around ensuring that maintainers are following the creators' guidelines (and ensuring they adhere to the CoC), so it wasn't meant to be so enforced by technology. I should add a LICENSE file to the repo, now that you mention it, people will expect it there. Thanks for the additional feedback!
- rapnie 3y ago
  I had another thought, more unformed, and mostly only relevant once 'popularity strikes'. Maybe not relevant at all. Suppose a maintainer gets a real liking for a particular project, develops a passion and invests a load of time. They can be rug-pulled at any time when the project owner - on a whim - decides help is no longer needed. The project owners freedom is assured. They can do anything, like take the project commercial and go proprietary from then on. This might cause big "drama" esp. when a maintainer also built community. It might not reflect badly on Code Shelter, but may be something to think about these situations.
  - stavros 3y ago
    Yeah, there are definitely a bunch of edge cases like this, but the main problem right now is that there aren't enough people for these to even happen, so having that sort of stuff to deal with would be a good problem to have.

by rapnie 3y ago

stavros 3y ago

This is great, thanks! I'll ass a privacy policy and look into a CoC, thanks. Any maintainer can be added to the repo, yes. The idea is that there will be a community-driven process around ensuring that maintainers are following the creators' guidelines (and ensuring they adhere to the CoC), so it wasn't meant to be so enforced by technology. I should add a LICENSE file to the repo, now that you mention it, people will expect it there. Thanks for the additional feedback!

rapnie 3y ago
I had another thought, more unformed, and mostly only relevant once 'popularity strikes'. Maybe not relevant at all. Suppose a maintainer gets a real liking for a particular project, develops a passion and invests a load of time. They can be rug-pulled at any time when the project owner - on a whim - decides help is no longer needed. The project owners freedom is assured. They can do anything, like take the project commercial and go proprietary from then on. This might cause big "drama" esp. when a maintainer also built community. It might not reflect badly on Code Shelter, but may be something to think about these situations.
- stavros 3y ago
  Yeah, there are definitely a bunch of edge cases like this, but the main problem right now is that there aren't enough people for these to even happen, so having that sort of stuff to deal with would be a good problem to have.