On 12/05/17 02:00, Jaromil wrote:
> On Fri, 12 May 2017, Daniel Reurich wrote:
>
>> They can play where ever they like but we will only build from our
>> gitlab, so that is the correct place for contributions to devuan.
>
> Yes, I think this cannot change.
>
> My question is about the posture we take regarding people finding
> gitlab unhandy, which is understandable especially now.
indeed, but it's a temporary situation soon to be resolved.

>
>> We don't chase contributions from all over. They can provide
>> patches attached to bug reports or fork and merge request changes in
>> git.devuan.org.
>
> what if they don't? we loose the contribution?
>
well it would be up to the package maintainer as to how far they'd be
willing to go to get patches etc, and unless it was really a really
significant contribution that won't likely happen when contributions
don't come via our defined paths for them.

> I think this would be the wrong approach.

I agree it would be wrong to simply refuse contributions, but informing
them of our processes and how they can make their contributions easy for
our maintainers and thus more likely to be applied is the only approach
that will fly in the medium term.
>
> I'd like to have a common way to deal with such cases,
> nothwithstanding the importance to get gitlab back up and running
> (will be dismissed from its colocation very soon now, a matter of a
> week or two I think)

noted. I will look again at it tomorrow..
>
> ciao
>
> _______________________________________________
> devuan-dev internal mailing list
> devuan-dev@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
>


--
Daniel Reurich
Centurion Computer Technology (2005) Ltd.
021 797 722