Hi,
Git has always been my preferred way to receive patches (since we
switched from CV). We used to have a set of repos under
'people.quagga.net', and anyone who had patches more than once or twice
tended to be given a git repo to make it easy to pull stuff from them.
That fell away for various reasons, and Quagga went to an email
workflow. I was arguing to move away from that horribly inefficient
email-a-patch workflow and back to some git based work-flow /years/ ago,
but objections were raised by those who held the email work-flow dear.
That's not an issue anymore.
Since the old people.quagga.net, there are now nice web-frontends around
git. I really prefer self-hosting our data, if there isn't a good
non-commercial option, as we've been burned on commercial hosting
before. I've looked at:
- GitLab
- Pagure
- Gogs
They all look nice and capable. I've tested pagure and gogs, and settled
on Gogs as the more promising (v easy to install and maintain, compared
to pagure [which is a /little/ less so] and [esp.] GitLab). So, it seems
worth trying out Gogs a bit more widely.
So if you want to submit patches via Gogs, see:
https://gogs.quagga.net/
If you submit a half-decent patch, and/or do some useful reviewing work,
more than once or twice, you can join the "team" on Gogs and get pull
access into it if you wish. Do so consistently over the course of (say)
a year, show you can work to a consensus with others, and manage not to
be an almighty arse (don't worry, this is fairly easy for most people),
so as to build up trust in you with the existing maintainers, then you
may also be a maintainer if you wish.
The authoritative repo will still be 'master' on Savannah, and Balaji
and other maintainers will do final pushes to that.
regards,
--
Paul Jakma | paul@jakma.org | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
Most people need some of their problems to help take their mind off
some of the others.
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
Git has always been my preferred way to receive patches (since we
switched from CV). We used to have a set of repos under
'people.quagga.net', and anyone who had patches more than once or twice
tended to be given a git repo to make it easy to pull stuff from them.
That fell away for various reasons, and Quagga went to an email
workflow. I was arguing to move away from that horribly inefficient
email-a-patch workflow and back to some git based work-flow /years/ ago,
but objections were raised by those who held the email work-flow dear.
That's not an issue anymore.
Since the old people.quagga.net, there are now nice web-frontends around
git. I really prefer self-hosting our data, if there isn't a good
non-commercial option, as we've been burned on commercial hosting
before. I've looked at:
- GitLab
- Pagure
- Gogs
They all look nice and capable. I've tested pagure and gogs, and settled
on Gogs as the more promising (v easy to install and maintain, compared
to pagure [which is a /little/ less so] and [esp.] GitLab). So, it seems
worth trying out Gogs a bit more widely.
So if you want to submit patches via Gogs, see:
https://gogs.quagga.net/
If you submit a half-decent patch, and/or do some useful reviewing work,
more than once or twice, you can join the "team" on Gogs and get pull
access into it if you wish. Do so consistently over the course of (say)
a year, show you can work to a consensus with others, and manage not to
be an almighty arse (don't worry, this is fairly easy for most people),
so as to build up trust in you with the existing maintainers, then you
may also be a maintainer if you wish.
The authoritative repo will still be 'master' on Savannah, and Balaji
and other maintainers will do final pushes to that.
regards,
--
Paul Jakma | paul@jakma.org | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
Most people need some of their problems to help take their mind off
some of the others.
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev