public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Fri, 30 Sep 2022 11:51:03 -0400	[thread overview]
Message-ID: <18919068-9af7-8a8b-9ea4-19e2035d6d78@gotplt.org> (raw)
In-Reply-To: <CA+=Sn1mp1fadVPrwWiYea+n1A9f6=i7y-42H+Z19nOsa_7A8hw@mail.gmail.com>

On 2022-09-30 11:05, Andrew Pinski wrote:
> Again you think these two can be independent, Once a technical
> decision is made, a monetarial one needs to be made which can be
> stopped by the governing board. THIS IS A PROBLEM.
> They cannot be independent. Because also at anytime the governing
> board could just say fuck off. Unless there are bylaws in place which
> have not been sent out anywhere; just this high level picture of what
> will happen.

Like I said, if there is an irresolvable conflict with the governing 
board, we can step away from the LF.

> Again what is a "major" donor?

I don't know, maybe someone else can answer this.

>> That's just FUD :)
> 
> Again this was not FUD but rather pointing out what happened in the
> past and trying to correct it. If LF/kernel.org folks didn't learn
> about social engineering that well; then maybe they are not the best
> people to do this.

It's FUD because it's wild speculation and casting persistent doubt over 
someone based on a single past incident.  Unless you have credible 
reason to believe that they've not learned from the incident, you're 
only casting fear, uncertainty and doubt.

>> The overseers
>> archives too AFAICT were made public only recently and I only happened
>> to discover it last week.
> 
> The archives have been public (or rather semi-public) for over 10
> years now. It might not have been linked from anywhere but they have
> existed for a long time now and have been public for that while too.
> I am sorry you didn't know about the archives before; but that is on you.

Funny that you call it semi-public (whatever that means) and then also 
say that it's on me that I didn't find the archives.  FWIW, I've 
deliberately looked for the archives in the past and not found it.  In 
any case, we digress.

> Sounds like you have no idea how sourceware has function in general.

Sounds like you're in a mood to make ridiculous comments.  Please 
consider being a bit more thoughtful in your responses.  Both you and I 
have been in this community for over a decade and statements like this 
are just immature.

>>> ** I get where corporations want to do this because they can track
>>> where things come from. But this is very much anti-open/free source
>>> ideals and very much anti-small developers
>>
>> I disagree.
> 
> Disagree all you want but it is the truth. Companies are pushing for
> this because they want more control. I want less control and in the
> hands of companies and more control in nobody really.

Requiring signed commits does not have anything to do with software 
freedom.  In any case, that's a project-specific question.  You may 
discuss that within the gcc community whenever that question comes up there.

>> FWIW, there are no viable alternatives to bugzilla at the moment and
>> nothing's really intended to change here.
> 
> You didn't comment on funding parts but just saying bugzilla is it
> because of no viable alternatives. This is funny because we want ways
> of improving things and then you skip that point.

The GTI proposal talks about (1) sponsors and (2) an IT team that'll 
help us with maintenance and porting of what we currently have.  It's 
essentially an expansion of capacity.  In that context, bugzilla can 
move more or less unchanged.

Questions about funding improvements to bugzilla are things that we need 
to figure out as a community through TAC and it will compete for funding 
with anything else that we propose to do, e.g. improvements to 
patchwork, pre-commit CI, developer-triggered testing (e.g. 
build-many-glibcs), maybe even another patch review tool like gerrit or 
gitlab.  We're not there yet.

Sid

  reply	other threads:[~2022-09-30 15:51 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 19:59 Carlos O'Donell
2022-09-28 14:06 ` Frank Ch. Eigler
2022-09-29  9:51 ` Mark Wielaard
2022-09-29 14:45 ` Jonathan Corbet
2022-09-29 17:13   ` Joseph Myers
2022-09-29 18:40     ` Elena Zannoni
2022-09-29 18:54     ` Andrew Pinski
2022-10-19  5:47   ` Carlos O'Donell
2022-09-29 21:13 ` Andrew Pinski
2022-09-30 14:35   ` Siddhesh Poyarekar
2022-09-30 15:05     ` Andrew Pinski
2022-09-30 15:51       ` Siddhesh Poyarekar [this message]
2022-10-02 21:56         ` Mark Wielaard
2022-09-30 15:22     ` Christopher Faylor
2022-09-30 15:34       ` Siddhesh Poyarekar
2022-10-02 21:38   ` Mark Wielaard
2022-10-02 22:19 ` Mark Wielaard
     [not found] <d9cb6cf9-89f5-87bb-933b-a03240479e71@redhat.com>
     [not found] ` <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>
2022-10-02 20:47   ` Mark Wielaard
2022-10-04 13:46     ` Siddhesh Poyarekar
2022-10-04 14:01       ` Frank Ch. Eigler
2022-10-04 14:13         ` Siddhesh Poyarekar
2022-10-04 14:19           ` Frank Ch. Eigler
2022-10-04 14:33             ` Siddhesh Poyarekar
2022-10-04 14:41               ` Frank Ch. Eigler
2022-10-04 14:55                 ` Siddhesh Poyarekar
2022-10-04 15:07                   ` Frank Ch. Eigler
2022-10-06 21:42             ` Alexandre Oliva
2022-10-04 17:10       ` Christopher Faylor
2022-10-04 17:17         ` Siddhesh Poyarekar
2022-10-04 18:42           ` Christopher Faylor
2022-10-04 19:05           ` Mark Wielaard
2022-10-04 19:10             ` Siddhesh Poyarekar
2022-10-06 20:02               ` Mark Wielaard
2022-10-06 20:12                 ` Christopher Faylor
2022-10-06 21:37                   ` Siddhesh Poyarekar
2022-10-07 13:39                     ` Mark Wielaard
2022-10-06 21:07                 ` Siddhesh Poyarekar
2022-10-06 21:36                   ` Frank Ch. Eigler
2022-10-06 21:44                     ` Siddhesh Poyarekar
2022-10-06 22:57                       ` Frank Ch. Eigler
2022-10-11 13:02                         ` Siddhesh Poyarekar
2022-10-07  8:57                   ` Mark Wielaard
2022-10-11 13:24                     ` Siddhesh Poyarekar
2022-10-11 14:23                       ` Frank Ch. Eigler
2022-10-11 15:58                     ` Alexandre Oliva
2022-10-11 17:14                       ` David Edelsohn
2022-10-11 18:12                         ` Frank Ch. Eigler
2022-10-12  8:00                         ` Mark Wielaard
2022-10-12 13:18                           ` Florian Weimer
2022-10-12 21:23                             ` Mark Wielaard
2022-10-12 15:15                           ` Jonathan Corbet
2022-10-12 10:55                         ` Alexandre Oliva
     [not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
     [not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-02 20:54   ` Mark Wielaard
2022-10-03 19:24   ` Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18919068-9af7-8a8b-9ea4-19e2035d6d78@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=overseers@sourceware.org \
    --cc=pinskia@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).