[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Could we enable Travis-CI on our github mirrors?
From:       Michael Pyne <mpyne () kde ! org>
Date:       2016-04-23 1:12:04
Message-ID: 7367040.4qExLenDGd () midna
[Download RAW message or body]

On Fri, April 22, 2016 01:04:42 Albert Astals Cid wrote:
> El dijous, 21 d'abril de 2016, a les 15:04:57 CEST, Vishesh Handa va 
escriure:
> > On Thu, Apr 21, 2016 at 3:05 AM, Ben Cooksley <bcooksley@kde.org> wrote:
> > >>> Also, another -1 from me is because I don't think we should use GitHub
> > >>> more than a mere mirror.
> > >> 
> > >> It would still remain a mere mirror imho, i.e. strictly read-only. Btw
> > >> do
> > >> we have some written rule about our github presence somewhere? It seems
> > >> to me that some KDE project uses github as their main development
> > >> platform.>
> > > 
> > > Urls to those projects which "appear" to be using Github as their
> > > primary development platform would be appreciated.
> > 
> > I most certainly *always* link to code on github and to the documentation.
> > 
> > > Use of Github for anything other than mirror purposes, especially if
> > > it is being pushed as the primary means of making contributions is
> > > strictly prohibited under the Manifesto.
> > 
> > Except it isn't. Please point me to where it does.
> 
> I guess it depends of what you understand with "primary means of making
> contributions", if it's "pushing the code there first and then merging to
> kde repos" I think there's quite a few reasons against it in the Manifesto.

I mean, didn't we have like 3-4 huge threads about this very issue not that 
long ago? I too thought that the conclusion was that Github was OK as a mirror 
but not for use as any part of the actual development workflow (e.g. bug 
tracking, CI, pull requests, etc.).

Regards,
 - Michael Pyne
[prev in list] [next in list] [prev in thread] [next in thread]