[bisq-network/proposals] Use a GRPC API as core API and use wrappers around for other API types (#136)

Julian Knutsen notifications at github.com
Thu Dec 12 22:06:43 UTC 2019


> Just to be clear, you mean 'let's try using a project board for the bisq-network/proposals repo, and use the (to be written) fresh grpc proposal as a guinea pig on that new board?

Yes.

> 
> I thought for a moment perhaps you were suggesting using per-proposal boards to track all related sub tasks as issues.

I don't think the projects need this level of granularity especially going from step 0 to step 1 with actual project tracking. Individual developers may choose to use per-task tracking if it makes their workflow easier, but that doesn't have to be part of GitHub or even publicly available. 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/136#issuecomment-565208413
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191212/c803c796/attachment-0001.html>


More information about the bisq-github mailing list