[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: [ELN] gcc is going to be updated to gcc11 in the ELN buildroot ahead of Rawhide
From:       Clement Verna <cverna () fedoraproject ! org>
Date:       2020-10-23 17:06:48
Message-ID: CAHTjmtahipaY9B3Jf8PBOYpnHysK-f4N8cFr1QX4KboVCusr6w () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, 23 Oct 2020 at 17:20, Miro Hron=C4=8Dok <mhroncok@redhat.com> wrote=
:

> On 10/23/20 2:45 PM, Aleksandra Fedorova wrote:
> > Sorry, but you just need to accept the fact that some _early
> > development_ work in Fedora can happen without your decision on it.
>
> I except (and accept) that most of the development work in Fedora happens
> without my decision on it.
>
> I would like you on the other hand to accept that major changes in Fedora
> are
> coordinated trough the change process and ELN is part of Fedora.
>

This for me highlights the fact that our change process is not adapted to
all parts of Fedora, in particular parts that need to move faster than the
6 month releases. I have in mind the Container base image, Fedora CoreOS
and ELN, IMO these artefact depends more on the content (the set of
packages included in them) rather then knowing which version of Fedora
release they are based on.
The Container base image and Fedora CoreOS are releasing every couple
weeks, ELN is just a rolling release, I think it is unfair to ask to follow
a change request system that is design for release that happen every 6
months.

I think we either need a new change request system that is light enough to
allow these group to iterate and make changes every week or so, or we need
to trust the people involved in these groups to make the best decisions for
the Fedora they care about and to also notify anyone that would be impacted
by these changes.

I also would like to point out that the Fedora's project mission statement
is to explicitly allow such group to be empowered to make their decisions,
at least this is what I understand in the following

```
*Fedora creates an innovative platform for hardware, clouds, and containers
that enables software developers and community members to build tailored
solutions for their users.*
*```*


> I would also like to you to tone it down with the personal accusations yo=
u
> are
> repeatedly making towards me. If you don't, this discussion is not
> productive.
>
> --
> Miro Hron=C4=8Dok
> --
> Phone: +420777974800
> IRC: mhroncok
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-leave@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o=
rg
>

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Fri, 23 Oct 2020 at 17:20, Miro Hrončok &lt;<a \
href="mailto:mhroncok@redhat.com">mhroncok@redhat.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10/23/20 2:45 PM, \
Aleksandra Fedorova wrote:<br> &gt; Sorry, but you just need to accept the fact that \
some _early<br> &gt; development_ work in Fedora can happen without your decision on \
it.<br> <br>
I except (and accept) that most of the development work in Fedora happens <br>
without my decision on it.<br>
<br>
I would like you on the other hand to accept that major changes in Fedora are <br>
coordinated trough the change process and ELN is part of \
Fedora.<br></blockquote><div><br></div><div>This for me highlights the fact that our \
change process is not adapted to all parts of Fedora, in particular parts that need \
to move faster than the 6 month releases. I have in mind the Container base image, \
Fedora CoreOS and ELN, IMO these artefact depends more on the content (the set of \
packages included in them) rather then knowing which version of Fedora release they \
are based on. <br></div><div>The Container base image and Fedora CoreOS are releasing \
every couple weeks, ELN is just a rolling release, I think it is unfair to ask to \
follow a change request system that is design for release that happen every 6 months. \
<br></div><div><br></div><div>I think we either need a new change request system that \
is light enough to allow these group to iterate and make changes every week or so, or \
we need to trust the people involved in these groups to make the best decisions for \
the Fedora they care about and to also notify anyone that would be impacted by these \
changes.</div><div><br></div><div>I also would like to point out that the \
Fedora&#39;s project mission statement is to explicitly allow such group to be \
empowered to make their decisions, at least this is what I understand in the \
following</div><div><br></div><div>```</div><div><em>Fedora creates an innovative \
platform for hardware, clouds, and containers that enables software developers and \
community members to build tailored solutions for their \
users.</em></div><div><em>```</em></div><div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> <br>
I would also like to you to tone it down with the personal accusations you are <br>
repeatedly making towards me. If you don&#39;t, this discussion is not \
productive.<br> <br>
-- <br>
Miro Hrončok<br>
--<br>
Phone: +420777974800<br>
IRC: mhroncok<br>
_______________________________________________<br>
devel mailing list -- <a href="mailto:devel@lists.fedoraproject.org" \
target="_blank">devel@lists.fedoraproject.org</a><br> To unsubscribe send an email to \
<a href="mailto:devel-leave@lists.fedoraproject.org" \
target="_blank">devel-leave@lists.fedoraproject.org</a><br> Fedora Code of Conduct: \
<a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" \
rel="noreferrer" target="_blank">https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br>
 List Guidelines: <a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" \
rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
 List Archives: <a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org" \
rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org</a><br>
 </blockquote></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic