[bisq-network/proposals] Add incubator space (#122)

niyid notifications at github.com
Mon Oct 14 22:27:51 UTC 2019

> I think after the 1.2 release and the voting cycle we need to re-discuss the idea about incubator projects. The current situation that the project devs are the maintainers is dangerous. Being under the Bisq umbrella requires that a Bisq developer who has already earned enough reputation by past work is playing that role. Or maybe the incubator idea is not feasible with Bisq's current resources at all and we need to look out for other alternatives (keeping it in the project devs repo but find a model for compensation)?

Yes indeed. There has to be a discussion and the guidelines have to be cemented.

But I think @m52go has already provided the scaffolding to build on in [this post](https://github.com/bisq-network/proposals/issues/122#issuecomment-541198686) except you have reasons to have doubts on his suggested process implementation.

As you suggested, all issues should be ironed out after 1.2 release and the voting cycle.

In my opinion, the incubator project structure is a sound idea that only needs a bit of tweaking.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191014/197ef260/attachment.html>

More information about the bisq-github mailing list