Developers of Sympa

[David Verdin <address@concealed>]

However...

Now that the sympa7 branch exists in the main repository (sympa-7.0 
should be destroyed, nothing conclusive was done there) I think you're 
right; We should start working using pull requests. This is easier to 
have other people contributing to it.

So yes, I think that's what we will do now.

eiro, I suggest that we create branches for atomic changes: "Bulk.pm 
test", "Bulk.pm refactoring", "List.pm tests", "List.pm refactoring", 
and so on.

This has the added value of being able to contribute both to sympa7 and 
to current sympa6.2 by proposing test files.

Regards,

David


On 26/09/2018 09:29, David Verdin wrote:
> Hi Soji,
>
> We're working on Sympa7. That means we have a lot of things to change, 
> according to what was decided during last hackathon.
>
> Anyone is welcome to comment that work, but, honestly, if we start 
> working with pull requests for the huge work that represent the Sympa 
> 7 refactoring, it will be endless.
>
> That's why I prefer working that way, which also eases keeping track 
> of Sympa 6.2 changes.
>
> Best regards,
>
> David
>
>
> On 26/09/2018 03:40, IKEDA Soji wrote:
> > Hi Marc,
> >
> > If you want to try new things, please fork master repo, i.e.
> > sympa-community/sympa into your space on github i.e. eiro/sympa,
> > create your branch in it, work on that branch until you will be
> > satisfied.  Thereafter, please propose changes in master repo
> > (such as submitting pull request).
> >
> > I believe this is the best practice on community at the preasent.
> >
> > Regards,
> >
> > -- Soji

--
"Mieux vaut viser la perfection et la rater que viser la médiocrité et 
l'atteindre."
- Francis Blanche

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature