On Fri, Feb 10, 2017 at 6:03 AM, Jehan Pagès <jehan.marmottard@xxxxxxxxx> wrote: > Hi, > > On Fri, Feb 10, 2017 at 10:20 AM, gregory grey <ror6ax@xxxxxxxxx> wrote: > > I know about build.gimp.org. > > > > I just wanted to raise this question to the attention of the team - of > > whether there is a need to support own CI if security is not an > > issue.It is literally only reason people do that now when we have > > travis-ci.org/https://circleci.com/etc.Travis is even free for > > opensource projects. > > > > https://build.gimp.org/plugin/disk-usage/ looks pretty full to me, for > > example. External CI do not have problems with that. > > We know of the disk usage issue: > https://bugzilla.gnome.org/show_bug.cgi?id=776631 > That's one of the many issues which triggered us into either looking > for alternative solutions or collaboration or whatever you want. > Basically we want something which works, is useful and reliable. The > "need" stops there. > > After, which software is it using? I think we don't really care. Now > obviously we'd prefer our whole infrastructure to run on Free > Software. And personally I like self-hosting for full control. But > then there is reality check: it requires contributor time and > administration skills. So in the end, the CI contributor(s) choose. In > the GIMP team, our policy is more or less that the one who *do* are > the one who are in charge of what they do. > > Jehan > Since I don't appear to be seen as a contributor or "doer" I'm happy to just step down completely and remove myself from the project. Much as I like GIMP I don't really like the tone of the thread. _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
