[bisq-network/bisq] Update contributing.md (#3613)

erciccione notifications at github.com
Fri Nov 15 14:13:51 UTC 2019


> Would it hold you off to contribute if you want to?

Why is that a question for me? I already sign all my commits. I didn't raise the issue for myself, it's necessary to have a bigger picture when making workflow changes that effect everybody.

@freimair 

> The requirement of signed commits has been in force for quite some time now. Just adapting the documentation.

It doesn't really matter if it was in force or not. When you make it official it's the important (since, theoretically, that's the moment you can start enforcing a new workflow)

> If configuring PGP is too much for a dev, then I am not sure if we want that dev working on our project in the first place.

Are you serious? So if i am a noob developer who just want to contribute to Bisq and can only do it by fixing typos, i cannot because i don't know how to sign commits? So much for an open and inclusive community.

What personally put me off from contributing is stuff like the statement quoted above, which is against my idea of open source development, and the way the Bisq project is managed by some of the older contributors. Merging pull requests after few hours with no discussion (yes, this is the usual for this repo and others in the Bisq Ecosystem) is part of the problem.

-- 
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/bisq/pull/3613#issuecomment-554374076
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191115/e2ba670b/attachment-0001.html>


More information about the bisq-github mailing list