Re: About partecipation into the development of ISAR

[Henning Schild <henning.schild@siemens.com>]

Am Wed, 4 Jan 2023 19:03:44 +0100
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:

> On Wed, 4 Jan 2023 at 18:33, Roberto A. Foglietta
> <roberto.foglietta@gmail.com> wrote:
> >
> > Hi all,
> >
> >  I wish to express my opinion about the participation into
> > development of ISAR  
> 
> POST SCRIPTUM
> 
> Quality and maintainability: the reasons because we use patches and
> simple commits. This is also the reason because it is useful to create
> branches, rebase the commits on it and merge branches among them.
> 
> So, for everything else which is more complex than an atomic bugfix or
> a simple feature addition, the git is THE definitive tool. Then, git
> cannot be left behind as a source of contribution because it is not
> only a way to track the changes and store the code but also a powerful
> {development, integration, test} tool especially when it is combined
> with documenting, ticketing and CI/CD tools like in github.
> 
> Finally, this is the reason Microsoft bought github!

The whole "should we adopt gitlab or github" instead of mailing lists
has been discussed several times. You do have very valid points and the
email based workflows cause all of us pain every once in a while.

But you must not confuse "github" (or any other lock-in hoster) with
git. Using plain "git" and "git-send-email" and a mailinglist for
issues and reviews is the "best in class" when it comes to OSS. You are
independent of any web-hoster, you can keep archives forever and switch
providers as you like and see fit.

Any project that does pull request, reviews and alike on some vendors
locked-in website will have a very hard time to stay in control and
switch the provider.

It is all about openness for contributors and the project, even before
Microsoft bought github. Maybe today also because they did ... we use
"git" and no funny vendor that swallows all our data without a way to
ever escape and move it to another place.

And when it comes to people working on Isar ... many work on other
projects that also opt for mailinglist-based, not just the kernel. So
it does not cause much headache ... what causes headache is keeping
issues and MRs open on the web-thingy the code might be hosted on at
the moment.

You seem to be proposing to walk into the vendor-lock-in arms of
Microsoft for convenience and mouse-web-stuff. No thanks, i already
suffer enough from not being able to SMTP with @siemens.com (nowaday
Microsoft powered) much like you could not SMTP from google. Or maybe i
should use Outlook ... and Windows while i am at it.

Henning

> Best regards, R-
>