Re: [edk2-devel] edk2setup.sh shortcomings

["tlaronde@polynum.com" <tlaronde@polynum.com>]

Le Thu, Feb 02, 2023 at 04:06:13PM -0700, Rebecca Cran a écrit :
> On 2/2/23 14:49, Brian J. Johnson wrote:
> 

This above is misleading: this is not Brian J. Johnson who wrote what is
below: this is me (Thierry Laronde):

> > Hum... There is a very lethal weapon actually in use: the pillow. I
> > already sent various patches and they are silently ignored...
> > 
> > If my contribution will be ignored as others have been till now, honesty
> > should be to clearly state: "we don't care and we won't care" so that
> > I can use my time trying to solve the problems I want to address at a
> > different level than UEFI...
> 

And you wrote (Rebecca Cran):

> I prefer to think that patches I've submitted are _missed_ rather than
> ignored. It's still frustrating to realize that patches I've sent 6 months
> ago were never committed, even if they were reviewed.
> 
> I suspect part of the problem is that many people working on edk2 are in
> companies which use Outlook, which can make keeping track of high traffic
> mailing lists difficult.
> 
> And even in Thunderbird, if all edk2-devel emails go into a single folder it
> can be difficult to keep track of patches.
> 
> I'm hoping that moving to Github PRs will improve things, with queries like
> "is:open is:pr review-requested:@me" letting people easily find PRs that
> need attention - though the UI looks like it could use some work to allow
> people to save their queries etc.

Not to mention the fact that to have the obligation to send endlessly the same
patches does nothing to decrease the trafic on the mailing list.

I ask only for honesty: if this is open source but not open development,
or if this is restricted open development i.e. only to big firms providing either
hardware or OSes, this is no problem with me as long as it is stated.
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C