well, I'm not prepared to pass commit procedures, I'm awaiting for
Samuli response whether or not he can handle those if I will send
patches directly to him
Well, if the patches would be 100% perfect all the time I probably would
not mind relaying them to the list. However, in that case you could more
easily just send them to the list yourself. I don't see much value for
you in me acting as a proxy. And I do see pain for me for doing that.
Now, Ilya is right in that we _could_ export all the data we want from
GitHub. So, one of the reasons why we originally chose mailing list
-based review is moot. The rest of the reasons should be written
somewhere, because people are increasingly using GitHub, and asking why
we don't accept PRs. I can probably dig up the previous rather lengthy
discussion on the topic and convert it to a Wiki page or add it to the
README, so that GitHub users can see it. What we have now is clearly
inadequate given the amount of complaints/discussion we get:
---
NOTE: Patches or "git pull requests" sent directly to a development tree
maintainer will be rejected.
From <https://community.openvpn.net/openvpn/wiki/DeveloperDocumentation>
---
I think these "GitHub PR discussions" go off the track almost the minute
they start. Before even starting them we should fully understand what
our goals as a project are. Then we could assess the tools and process
we use now, and those which we have at our disposal. Then, finally, we
could make an informed decision on where to go next. Or we could just
continue doing what we're doing.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
