3 ms·

I've mentioned this for other projects, but why not do the work in the open too? Why not just make the code public as you work on it? It's hard to believe openn

I've mentioned this for other projects, but why not do the work in the open too? Why not just make the code public as you work on it? It's hard to believe openness and transparency are the goal if there is none during development (even if the code is ugly and you have to turn away too-early assistance/suggestions). No invites, nothing hidden. Also, wrt AGPL, as a contributor I would personally prefer a "commitment" the other direction. That I can contribute without putting restrictions on the recipient. I think in our current times, preventing commercial and closed source use has little value as people just go elsewhere. I don't want this to devolve into a pros/cons of copy-left discussion, but in general the fewer adoption restrictions the better I'd say for projects like these. I will say I agree with almost all of your other goals (except some of the stack :-).

cfabbro 8y ago
AFAIK it’s literally just a matter of not yet deciding on the license yet which is why deimorz solicited advice about it on the announcement. He already has gitlab set up and we are using it internally. Open Source is coming very soon, we promise. https://gitlab.com/tildes https://gitlab.com/tildes
- kodablah 8y ago
  Cool, it's OK to start code without a license and still let people see it. Similar to other "open" things, to be truly open you don't have to wait until things are set just right.
Deimorz 8y ago
As mentioned, the license is a factor, but there are a couple of other things I wanted to get done first as well. I feel that it's pretty important to have good documentation available immediately about how to get a dev version running, how things work, how to contribute, and so on. I don't want to just dump a pile of code out by itself, that's a bad experience for potential contributors. It won't be long until it's open-sourced - a week or two at most. Before today, the site hasn't had very many users at all, and it's definitely not something I'm going to be keeping hidden/closed while I continue to develop.

cfabbro 8y ago

AFAIK it’s literally just a matter of not yet deciding on the license yet which is why deimorz solicited advice about it on the announcement. He already has gitlab set up and we are using it internally. Open Source is coming very soon, we promise. https://gitlab.com/tildes https://gitlab.com/tildes

kodablah 8y ago
Cool, it's OK to start code without a license and still let people see it. Similar to other "open" things, to be truly open you don't have to wait until things are set just right.

Deimorz 8y ago

As mentioned, the license is a factor, but there are a couple of other things I wanted to get done first as well. I feel that it's pretty important to have good documentation available immediately about how to get a dev version running, how things work, how to contribute, and so on. I don't want to just dump a pile of code out by itself, that's a bad experience for potential contributors. It won't be long until it's open-sourced - a week or two at most. Before today, the site hasn't had very many users at all, and it's definitely not something I'm going to be keeping hidden/closed while I continue to develop.