---------- Forwarded message ----------
From: Thomas Goirand <zigo@debian.org>
To: openstack-discuss <openstack-discuss@lists.openstack.org>
Cc: 
Bcc: 
Date: Mon, 14 Sep 2020 09:22:08 +0200
Subject: Re: Is Storyboard really the future?
On 9/14/20 8:59 AM, Radosław Piliszek wrote:

> On Sun, Sep 13, 2020 at 8:46 PM Thomas Goirand <thomas@goirand.fr> wrote:

>>

>> On 9/10/20 6:45 PM, Radosław Piliszek wrote:

>>> I feel you. I could not so far convince anyone to support me to work

>>> on it, mostly because

>>> Jira/GitHub/GitLab/Launchpad exists.

>>> Not to mention many small internal projects are happy with just Trello. :-)

>>

>> Did you just try to list all the non-free services you could in this

>> thread? Seriously, don't you care a little bit? You probably don't

>> realize it, but that's shocking, at least for me, and hopefully I'm not

>> the only one.

>

> I feel offended by the accusations.

> I *do* care about open source.

>

> Jeremy has already answered regarding GitLab and Launchpad.

> Let's not forget GitHub actually *is* the largest, diverse open source

> community,

> even though the service itself is not. It hurts me as well so please don't just

> randomly attack people mentioning non-free software.

> It can support open source software as well.



You're the one mentioning Jira, GitHub, Trello as possible solution to

solve the fact that you don't like Storyboard. This is IMO very far from

the spirit of free software. Sorry if you took it as a personal attack:

there's nothing personal here, just a strong opposition to using this

kind of services.



The fact that many projects are using these non-free services to produce

free software is actually a problem, not a solution. Same for Github

being (probably) the largest repository of free software: that's a huge

problem, as huge as the number of projects hosted. Lucky, many just

think of it as just free hosting and nothing more.



Gitlab being open-core, as Jeremy pointed out, is also a problem (anyone

that knows about the beginning of OpenStack and Eucalyptus knows why

open core is problematic).



> I did not propose that in any part. Launchpad is FLOSS and that is my proposal.

> The general idea behind my mail was to emphasise that Storyboard has

> great aspirations

> and assumptions but is far from delivering its full potential so

> should not be recommended without

> giving background and other possible solutions.



Launchpad is hardly installable, and is tightly connected to

Canonical/Ubuntu. It is a very good thing that the OpenStack community

has made efforts to get out of it. It is IMO counter-productive to push

projects to either go back to launchpad, or not migrate to Storyboard.



The only viable solution is to contribute and make Storyboard better, or

switching to another existing free software. There are many out there

that could have done the job.



Cheers,



Thomas Goirand (zigo)





_______________________________________________

openstack-discuss mailing list

openstack-discuss@lists.openstack.org

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss

Hi everyone,

So, thomas, your message was rude and can hurt because Yocto didn’t suggested to use those tools, he was answering you that he feel the pain as everyone is suggesting those tool when you talk with people on IRC etc.

Even if I do understand your point and know the importance of being autonomous and do not rely on non-FLOSS software, the thruth being all those discussions is the pain in the ass that it is to contribute to Openstack projects compared with other Open source software based on Github or Github like workflow.

The opensource community and especially the Openstack one need to understand that people really get a limited amount of time and so if you want to attract more people your contribution process have to be streamlined and on par with what most of us developers do experience on everyday. The foundation made a first step toward that by migrating every project on gitea, and honestly, I’m still amazed that while migrating those projects it wasn’t decided to use the issues/projects feature of gitea. There even is a cicd zuul plugin for gitea.

As a community we propose things, but if the community don’t use them, it’s because it’s not what they’re waiting for. We also need to step back from time to time and admit that one software need to sunset and be migrated elsewhere.

We want a fully floss project to host it? Fine it’s perfectly valid argument, then just reuse what’s already there with gitea and redirect development effort of the abandonned software to the new platform in order to support the missing part if ever required!