[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:       Elvis Angelaccio <elvis.angelaccio () kdemail ! net>
Date:       2016-04-20 22:05:23
Message-ID: CALN1cnuAMqzOyjNnqdzC2yrQ0QmWPhO7znyq8uDRfy1_bqXFCQ () mail ! gmail ! com
[Download RAW message or body]

2016-04-20 23:09 GMT+02:00 Luca Beltrame <lbeltrame@kde.org>:

> Il giorno Wed, 20 Apr 2016 18:42:31 +0200
> Elvis Angelaccio <elvis.angelaccio@kdemail.net> ha scritto:
>
> > I think it would be nice to have travis builds for the (mirrored)
> > repositories that provides a .travis.yml configuration file. The
>
> -1. Aside the arguments moved by Albert, I add that the solution is
> finding ways to help whoever is working on CI rather than offloading to
> another service we do not control.
>

I don't see it as an offloading. More like a nice bonus to have. If it
works, good. If not (because it breaks and we don't have control on it),
who cares.
In a way, one could argue this is similar to the telegram case. We don't
have control over telegram either, but it works for some people and it's
not replacing the main communication channels. So it's just a nice addition
to have.


>
> 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.


>
> --
> Luca Beltrame - KDE Forums team
> GPG key ID: A29D259B
>

[Attachment #3 (text/html)]

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2016-04-20 \
23:09 GMT+02:00 Luca Beltrame <span dir="ltr">&lt;<a href="mailto:lbeltrame@kde.org" \
target="_blank">lbeltrame@kde.org</a>&gt;</span>:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Il giorno Wed, \
20 Apr 2016 18:42:31 +0200<br> Elvis Angelaccio &lt;<a \
href="mailto:elvis.angelaccio@kdemail.net">elvis.angelaccio@kdemail.net</a>&gt; ha \
scritto:<br> <span class=""><br>
&gt; I think it would be nice to have travis builds for the (mirrored)<br>
&gt; repositories that provides a .travis.yml configuration file. The<br>
<br>
</span>-1. Aside the arguments moved by Albert, I add that the solution is<br>
finding ways to help whoever is working on CI rather than offloading to<br>
another service we do not control.<br></blockquote><div><br></div><div>I don&#39;t \
see it as an offloading. More like a nice bonus to have. If it works, good. If not \
(because it breaks and we don&#39;t have control on it), who cares.<br></div><div>In \
a way, one could argue this is similar to the telegram case. We don&#39;t have \
control over telegram either, but it works for some people and it&#39;s not replacing \
the main communication channels. So it&#39;s just a nice addition to \
have.<br></div><div>  </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"> <br>
Also, another -1 from me is because I don&#39;t think we should use GitHub<br>
more than a mere mirror.<br></blockquote><div><br></div><div>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.<br></div><div>  </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <span \
                class="HOEnZb"><font color="#888888"><br>
--<br>
Luca Beltrame - KDE Forums team<br>
GPG key ID: A29D259B<br>
</font></span></blockquote></div><br></div></div>



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