I have a strong preference for using GitHub at least for vetting out most bugs.
We're not going to use GitHub for the actual patch merging process - that
is "mailing list, public ACK, merge, push to github + sourceforge", at
least today.
For review, PRs should be doable.
Speaking of reviewing PRs... there are many of those, and some could be
merged trivially or closed with "feature-NACK". I can have a quick look.
I'm sure there are tons of other things to do besides reviewing these
PRs, However, reviewing PRs in timely manner would probably get more
developers involved in the OpenVPN project. This is not purely
speculation: when OpenVPN-GUI was moved to GitHub it was stagnating. Now
there are five people with 5+ commits:
<https://github.com/OpenVPN/openvpn-gui/graphs/contributors>
All of the people except me came pretty much out of nowhere. Two of them
(ffes, leobasileo) are not involved in any other OpenVPN-related
projects afaics, and there was no way to know they even existed.
As Gert said, the reviewed patch should be sent to the mailing list. It
can stay there for a few days waiting for further comments and if there
are none, then get merged based on lazy-ACK.
At first, the reviewed patches could be relayed by people already on the
list, for example by me. When we identify the people who contribute to
OpenVPN often, we can suggest that they subscribe to the mailing list
and send their patches themselves.
It might also be possible to generate an email (to openvpn-devel ml)
from each PR. This would fit better with our current workflow, and
ensure people are notified when PRs arrive.
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
