[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-librejs] Making changes to the Savannah repo
From: |
Thomas Harding |
Subject: |
Re: [Bug-librejs] Making changes to the Savannah repo |
Date: |
Thu, 03 Aug 2017 14:22:25 +0200 |
User-agent: |
K-9 Mail for Android |
Le 3 août 2017 06:02:43 GMT+02:00, bill-auger <address@hidden> a écrit :
> On 08/02/2017 06:48 PM, Nathan Nichols wrote:
> > I would like to submit today's progress. How do I go about doing
> this?
>
>
> i have been wondering myself about the savannah workflow - the only
> documentation i see about this indicates that you need full write
> access
> to contribute via git
>
> what i have found it that although savannah supports git VCS, it does
> not seem to support any facets of modern git workflow such as forking,
> merge requests, peer review - i think it is expected that patches be
> sent to the mailing list, which is like the tail wagging the dog if
[...]
Savannah has a BTS, filling a bug report (on project, not Savannah) and attach
a patch is the standard way.
nongnu simply follows GNU projects way : having maintainers. Note you can
enlist several keys on project.
Note also Project Savannah has itself a mailing list and probably relies on BTS
where you can fill feature requests. Main keys to Savannah management are disk
room and bandwidth (almost no fees).
HTH,
TH
--
Je suis née pour partager, non la haine, mais l'amour
-- Sophocle (Antigone)
- [Bug-librejs] Making changes to the Savannah repo, Nathan Nichols, 2017/08/02
- Re: [Bug-librejs] Making changes to the Savannah repo, bill-auger, 2017/08/03
- Re: [Bug-librejs] Making changes to the Savannah repo, bill-auger, 2017/08/03
- Re: [Bug-librejs] Making changes to the Savannah repo, Nathan Nichols, 2017/08/03
- Re: [Bug-librejs] Making changes to the Savannah repo, Thomas Harding, 2017/08/03
- Re: [Bug-librejs] Making changes to the Savannah repo, Nathan Nichols, 2017/08/03