Search results

...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. * Responsible WG: KDE SIG

{{deprecated|Server SIG and Server WG are [https://docs.fedoraproject.org/en-US/server-working-grou == Fedora Server SIG ==

* Responsible WG: KDE SIG ...Workstation WG as part of advancing the GNOME platform. It is now the KDE SIG's turn to do the same for the KDE platform. By making this change, we are h

...r:alebastr| Aleksei Bavshin]], [[User:Fale|Fabio Alessandro Locati]], Sway SIG * Proposal owners: change the default in comps

== Creating a SIG == ...tle red tape. If you're interested in forming one, see [[Creating a Fedora SIG]].

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

===[[Changes/Replace Comps Language Group With Langpacks | Replace Comps Language Group With Langpacks]]=== Language support groups in Comps file will get replaced by weak rich dependencies in the langpacks package.

...uddies of Budgie organization and a newly proposed [[ SIGs/Budgie | Budgie SIG ]]. Budgie Desktop was introduced in Fedora 37. A Fedora Budgie Spin would ** SIG request: [https://pagure.io/fedora-infrastructure/issue/11049 #11049]

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.