Search results

<noinclude>{{CompactHeader|fonts-sig}}</noinclude> Problems are tagged by CC-ing the SIG [[Fonts_SIG_mailing_lists | bugs list]] when the upstream issue tracker all

<noinclude>{{CompactHeader|fonts-sig}}</noinclude> ...g is achieved through [[How_to_use_and_edit_comps.xml_for_package_groups| comps]] groups.

== How comps is used == ...nment groups (as defined by the {{code|environment}} keyword in {{filename|comps.xml}}) are listed down the left-hand side. All optional groups (defined by

= Fedora Minimal Core SIG = ...[[How to use and edit comps.xml for package_groups#Core|Core group in the comps file]], and any packages installed by the Anaconda installer by default.

...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 = Replace Comps Language Group With Langpacks =

{{CompactHeader|fonts-sig}} ! Comps group

{{CompactHeader|fonts-sig}} ...quick summary to help newcomers undertand the [[:Category:Fonts SIG| Fonts SIG]] workflow.

* [http://meetbot.fedoraproject.org/fedora-meeting/2010-03-16/kde-sig.2010-03-16-13.58.html Meeting minutes] * [http://meetbot.fedoraproject.org/fedora-meeting/2010-03-16/kde-sig.2010-03-16-13.58.log.html Full log]

...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. -->

<noinclude>{{CompactHeader|fonts-sig}} * CC the fonts SIG bugs [[Fonts_SIG_mailing_lists|mailing list]].

...ithin SIG with limited impact outside SIG functional area, accepted by the SIG # update fedora-comps to install the Chinese Sans and Serif fonts by default

...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 = Update comps to use python3 <!-- The name of your change proposal --> =

{{DISPLAYTITLE:SIG - Grupo de Interesses Especiais}} == Criar um 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. ** SIG request: [https://pagure.io/fedora-infrastructure/issue/11856 #11856]

[[SIGs/AmateurRadio|SIG de Rádio Amador]] O SIG Big Data, no melhor estilo do Fedora, foca em fazer do Fedora a melhor plat

...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. * 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.

...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. -->

* Owner: Jens Petersen, Fedora Haskell SIG ===[[Changes/Update comps to use python3 | Update comps to use python3]]===

...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. -->

...ý]], [[User:Fale|Fabio Alessandro Locati]] as well as the rest of the sway-sig ...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. ...tt> and <tt>systemd-container</tt> as necessary for other packages, modify comps. Make sure anaconda installs <tt>systemd-udev</tt> by default.

...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. -->

...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. ...to not install fedora-repos-modular by default ([https://pagure.io/fedora-comps/pull-request/849 PR merged])

...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. -->

...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. -->

...er generating metadata in sqlite database format by default and simplified comps xml type in repodata. ...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.

...er generating metadata in sqlite database format by default and simplified comps xml type in repodata. * Owner: Possibly others since it may touch -comps, systemd-boot, etc

...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. ** Modify comps accordingly

Created 2 new groups in F12 comps.xml (critical-path-base and critical-path-gnome). Combining those two grou ...Jlaska directed curious contributors to the page describing how to propose comps.xml changes (see http://fedoraproject.org/wiki/PackageMaintainers/CompsXml)

...This page is no longer updated regularly. Talk to the [[SIGs/Python|Python SIG]] if you want to discuss it. }} ** See also: [[Changes/Update_comps_to_use_python3|Update comps to use python3]] ([[Releases/29 | Fedora 29]])

| irc-support-sig || 3269 || yes || yes || yes | comps || 404 || no || no || no

...r with participants in the discussion including Yaakov on the grounds that comps were a consistent scheme. === Fedora SIG KDE Report Week 2008-02-12 ===

...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. ...dhat-rpm-config PR #167], [https://pagure.io/fedora-comps/pull-request/704 comps PR #704]

| style="color: #42427e" | and thanks to the great work of the Fonts Fonts SIG fonts support is getting much better in the recent releases with more fonts | style="color: #42427e" | comps

| style="color: #488888" | | gst-mixer is in f11 repos and in comps | style="color: #4b904b" | | sig leaders I suppose