[CentOS-devel] CentOS Stream Feature Request SIG Proposal

Fri Apr 9 19:04:16 UTC 2021
Aoife Moloney <amoloney at redhat.com>

On Fri, Apr 9, 2021, 7:23 PM Amy Marrich <amy at redhat.com> wrote:

> Aiofe,
>
> So would presenting to the SiG be a starting point to requesting a new
> feature, or would the SiG monitor bugzilla and other channels for new
> submitted feature requests? I'm assuming either route would result in the
> SiG then championing them if they are a good fit for the project?
>

Yep that's exactly it Amy! We intend to have this SIG monitor bugzillas and
IRC channels for features that are already being developed in Stream for
when the person/group who have been working on those would like to see this
feature end up in RHEL. We would like to make sure these features get all
the way into the RHEL feature process and are not missed!

Were going to make space too in an office hours type venue to make sure
people can present to the group as well if they would like because we are
fundamentally dedicated to make sure community features that hold technical
merit which come from Stream *can* and *do* get into the RHEL process, but
ideally these features would be filed as a bugzilla with a note saying
'feature' in the extra info box on the service so we know what to look for.
We will then work with requestors to get their requests filed correctly. Or
indeed triaged to other areas of the project where those ideas would work
great in.


I'm really happy to see such positive reactions to this idea initially, and
Brian, I and others who are happy to be a part of this SIG initially if
approved, are happy to answer any questions people might have.


Thanks again for your engament!
Aoife



> Amy
>
>
> *Amy Marrich*
>
> She/Her/Hers
>
> Principal Technical Marketing Manager - Cloud Platforms
>
> Red Hat, Inc <https://www.redhat.com/>
>
> amy at redhat.com
>
> Mobile: 954-818-0514
>
> Slack:  amarrich
>
> IRC: spotz
> <https://www.redhat.com/>
>
>
> On Fri, Apr 9, 2021 at 11:38 AM Aoife Moloney <amoloney at redhat.com> wrote:
>
>> Hi everyone,
>>
>> I would like to share with you all a proposal I have submitted on
>> creating a SIG dedicated to reviewing and triaging feature requests that
>> come from CentOS Stream development intended for future RHEL releases.
>>
>> The full proposal can be read on the CentOS wiki [0] and an issue has
>> been opened on the CentOS board tracker [1] for review and decision.
>>
>> Here is the proposal summary and I welcome any thoughts, feedback and
>> discussion:
>>
>> Purpose
>> The purpose of this SIG will be to serve as a gate for feature requests
>> that are first developed in CentOS Stream from contributors who wish to
>> request these features to be included in future RHEL releases and are then
>> filed in bugzilla. The SIGs overall goal is to make sure that features
>> which have been filed and have technical merit are triaged internally to
>> the correct venue for further review and development. The SIG will take
>> ownership of regular bugzilla reviews filed under Stream and map feature
>> requests from these bugzillas against the formal RHEL Feature Request
>> criteria to identify and file qualifying requests inside Red Hat to achieve
>> this.
>>
>>
>> I hope you all have a lovely weekend!
>>
>> Kindest regards,
>> Aoife,
>>
>> [0] - https://wiki.centos.org/SpecialInterestGroup/StreamFeatureRequest
>> [1] - https://git.centos.org/centos/board/issue/33
>> --
>>
>> Aoife Moloney
>> Product Owner
>> Community Platform Engineering Team
>> Red Hat EMEA
>> Communications House
>> Cork Road
>> Waterford
>> _______________________________________________
>> CentOS-devel mailing list
>> CentOS-devel at centos.org
>> https://lists.centos.org/mailman/listinfo/centos-devel
>>
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel at centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20210409/424b8267/attachment-0005.html>