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

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

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

sig fedora-10 && age < 12 weeks :: keep sig fedora-11 && age < 12 weeks :: keep

This page is [[SIGs/Medical|Fedora Medical SIG]]'s COVID-19 page.

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

...o be beneficial to the [https://fedoraproject.org/wiki/Respins-SIG Respins SIG] as it nicely aligns with their objective of providing a simple method for ...ora Workstation. Nevertheless, we are open to collaborating with all spins/SIG to transition their build pipelines to Image Builder. However, for the init

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

* Other developers: Negligible work outside Haskell SIG, but the SIG can try to help resolve any issues which should arise. [done] Very few packages with any Haskell dependencies outside the Haskell SIG.

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

{{CompactHeader|fonts-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.

= Perl for Server Spin/SIG =

[11:03] *** Kevin_Kofler sets the channel topic to "KDE SIG Meeting - [[SIGs/KDE/Meetings/2008-06-24]] - Init". [11:03] <Kevin_Kofler> KDE SIG Meeting start. Who's present?

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

{{admon/important|Page moved|Games SIG has a new documentation page at [https://docs.fedoraproject.org/en-US/gamin = Contributing roles in the Fedora Games 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.

{{CompactHeader|fonts-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.

...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 packages that fail to rebuild, mainly perl-sig users, will be asked using Bugzilla to fix or remove their packages from th

...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. ...G, though we are open to support from any of the few packagers outside the SIG

* [[:Category:Fonts_SIG| 폰트 SIG]] {{CompactHeader|fonts-sig}}

...thin SIG with limited impact outside SIG functional /area, accepted by the SIG

= Set inital-cc to 'perl-sig' = ...tial-cc list for bugzilla. This can be done by adding the user <code>perl-sig</code> to the initial CC list.

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

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

While separate from the [[SIGs/AI-ML|AI/ML SIG]], we do share communication channels for now. If you're interested, please * [https://discussion.fedoraproject.org/tags/c/project/7/ai-ml-sig #ai-ml-sig on Fedora's Discourse instance]

...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 will be driven by Python SIG, but a few packages may fail to build (with the failure message providing a This is a multi-release effort tracked in Python SIG's [[FinalizingFedoraSwitchtoPython3|"Finalizing Fedora Switch to Python3" d

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

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

== SIG deny list ==

{{CompactHeader|fonts-sig}} ...ses should be notified to the fontconfig maintainer and the Fedora [[Fonts SIG mailing lists|fonts list]], so the font family split can be eventually hidd

| Server SIG Pow-Wow|| || || || | Haskell SIG meeting|| || || ||

* Responsible WG: ARM SIG * Proposal owners: The ARM SIG will prepare the changes required for the disk images and u-boot uEFI suppo

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

== SIG blacklists ==

...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 ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

=== Fedora SIG KDE Meeting 2008-04-01 === === Fedora SIG Store Meeting 2008-04-02 ===

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

...ll happens. In order to have permission, it has been created in the python-sig group: https://copr.fedorainfracloud.org/coprs/g/python/platform-python-sta

...Fedora release. Exceptions will be for bug and security fixes that the KDE-SIG is able to backport.

...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 affected packages need to be included here. Alternatively, a SIG can

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

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

...technology, and build upon our vibrant community. So while this is a Pride SIG hosted activity, it's a "Let's have fun!" event for everyone to participate

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

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

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

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

...ring&short_desc=ghc&short_desc_type=allwordssubstr ghc bugs not CC haskell-sig] * 2007-05-10: Fedora SIG [http://fedoraproject.org/wikiold/SIGs/Haskell?action=recall&rev=1 formed]

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

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

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

...g that there will be around 200 packages that need such attention. The ELN SIG will be providing guidance and pull-requests to assist with this. ...feedback messaging into the ELN builds so that the maintainers and the ELN SIG will see what was attempted and what failed.

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

<!-- All fields on this form are required to be accepted by the Spins SIG ...tly under the umbrella of the [[SIGs/SciTech|Fedora Science and Technology 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.

...rs are outside of groups / SIGs / projects... there's (almost ?) a group / SIG / projct for each and every task you could want to do in Fedora. And who ca ...| bochecha: I agree with your point about how mentors should be part of a SIG, in fact, that's going to be my target

** '''Links for more info (if there is any) :''' - Join the [[Ruby SIG]] and/or ping the mentor for more info

* [[:Category:Fonts_SIG| Fonts SIG]] {{CompactHeader|fonts-sig}}

...g that there will be around 200 packages that need such attention. The ELN SIG will be providing guidance and pull-requests to assist with this. ...feedback messaging into the ELN builds so that the maintainers and the ELN SIG will see what was attempted and what failed.

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

...https://developer.fedoraproject.org/tech/languages/nodejs/SIG.html| Nodejs SIG]] ...https://developer.fedoraproject.org/tech/languages/nodejs/SIG.html| Nodejs SIG]] and we will help you find the easiest way to bundle your nodejs libraries

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

* [[:Category:Fonts_SIG| Tipos de Letra SIG]] {{CompactHeader|fonts-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.

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

{{CompactHeader|fonts-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.

=== Fedora SIG KDE Meeting 2008-04-08 ===

..., are much less formal. The process for [[Creating_a_Fedora_SIG|creating a SIG]] has no red tape. Different SIGs have different structures; some use forma

...der-width: 0px; background-color: #d8e0eb;"|{{projectline|SIGs|檢視所有特別興趣小組 (SIG)...||Echo-SIGs-48px.png}}

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

...this example (and always link to people or groups)'' [[SIGs/DotNet|DotNet SIG]] - [[User:Rhea|Radka (rhea) Janek]], ... ...el}} & {{fplistfull|example-list}} - Mentors email or mailing list of your 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. * Name: [[Haskell_SIG|Haskell 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.

...levels and areas of concentration. The Fedora [[SIGs/Robotics | Robotics SIG]] focuses on making the latest and greatest robotics software available to ...nt? Writing tutorials? Packaging? The Fedora [[SIGs/Robotics | Robotics SIG]] is always looking for new members. Get in touch with us if you want to h

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

...work connectivity as a service". This page tracks [[Cloud SIG|Fedora Cloud SIG]]'s effort to maintain Quantum in Fedora.

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

= Fedora Package Review SIG = This SIG is currently in its infancy and things are still being organized.

[[SIGs|Специальные группы в проекте Fedora]] (SIG) - другие активности внутри проекта Fedora, к

Fedora Language Testing Group [FLTG] is a SIG group of Fedora contributors taking care of language testing in Fedora.

=== Thursday, April 28 - Cloud SIG Test Day === ...8" | jlaska: I am editing the wiki and was wondering if QA is considered a SIG or a formal project?

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

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

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

* Name: [[User:petersen|Jens Petersen]], Fedora Haskell 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.

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

** SIG: Yes == Determining the Spins SIG workflow ==

=== KDE SIG Packages Status === ...placement KDE panel capable of handling Compiz and Beryl. Other Fedora KDE-SIG packages awaiting review are koverartist, klear, kdebluetooth, and keep. Sp

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

* The [[SIGs/Xfce| Xfce SIG]] (Special Interest Group) is a group of Fedora contributors that help imp

* Fedora Usability SIG Report: no report

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

<!-- All fields on this form are required to be accepted by the Spins 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. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

{{CompactHeader|fonts-sig}}

...:otaylor| Owen Taylor]], [[User:Ngompa|Neal Gompa]] [on behalf of the KDE SIG] ...d-party repositories must be approved by an active Fedora working group or SIG, or by FESCo. Groups who approve the inclusion of third party repositories

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

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

{{CompactHeader|fonts-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.

...COSMIC SIG''' || [[User:Rbrue|Ryan Brue]] || A talk on the Fedora COSMIC SIG || Session 1

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

The Fedora Cloud Working Group and Special Interest Group (SIG) has been busy leading up to Fedora 21. Cloud is now a top-level product fo ...work for Fedora 21, [[Changes/Modular_Kernel_Packaging_for_Cloud|the cloud SIG and kernel team split the kernel]] into two packages. One package contains

...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. * Name: [[Haskell_SIG|Haskell 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.

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

* [[SIGs/KDE| KDE 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.

...nsible WG: Workstation WG and Team Silverblue (formerly Atomic Workstation 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.

* Fedora Usability SIG Report: no report

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

* Fedora Usability SIG Report: no report

...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:Ankursinha| Ankur Sinha "FranciscoD"]], [[SIGs/NeuroFedora| NeuroFedora 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.

{{CompactHeader|fonts-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.

...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 SIG: Node.js 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. * Name: [https://pagure.io/cloud-sig Fedora Cloud 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.

...in working on packaging or reviews to help out the [[SIGs/bigdata|Big Data SIG]], this is the page to look at! ...tainers] page to get more information. You could also ask on the Big Data SIG mailing list for assistance and see if you can find a willing helper or spo

* Fedora Usability SIG Report: no report

* Fedora Usability SIG Report: no report

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

* Fedora Usability SIG Report: no report

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

* Fedora Usability SIG Report: no report

* Fedora Usability SIG Report: no report

* Fedora Usability SIG Report: no report

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

* Fedora Usability SIG Report: no report

* Fedora Usability SIG Report: no report

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

* Fedora Usability SIG Report: no report

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

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

* Fedora Usability SIG Report: no report

...ized infrastructure. Other groups may form [[Category:SIGs]]. Over time, a SIG which meets criteria for organization, impact, alignment with the Fedora m

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

...acceptance of new packaging sponsors, Special Interest Groups (SIGs) and SIG Oversight, the packaging process, handling and enforcement of maintainer is

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

...rmalizada. Otros grupos pueden formar [[Category:SIGs]]. Con el tiempo, un SIG que cumple con los criterios de organización, impacto y aliniamiento con l

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

| 027 || [[User:jreznik|Jaroslav Reznik]] || || X || || XXL || KDE SIG evil & sysconfig good || ...aslano|Marcela Mašláňová]] || || X || || S || mmaslano@redhat.com || Perl SIG

* [[SIGs/KDE| KDE 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.

...be a week before Release N+1 goes beta. Here, we shall hold a special Join SIG meeting to agree on what sessions we'll feature in the coming semester. We

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

...Matrix Space, please report within Matrix as well as alert the Fedora IRC Sig members by using the !ops command in the main Fedora channel.}} ...ppropriate activity in any Fedora IRC channels please alert the Fedora IRC Sig members by using the !ops command in the main Fedora channel. }}

...e page and clearing house for information for the [[SIGs/Desktop| Desktop SIG]] for Fedora. ...Desktop-releated features and projects; for people and meetings, go to the SIG

In addition to the Defensive Coding book the Security SIG is charged with creating training resources. Videos and smaller articles o

{{CompactHeader|fonts-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.

...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: ELN SIG <devel@lists.fedoraproject.org>

* Approved by Spins SIG and only require board approval for trademark usage | style="color: #42427e" | Board, Spins SIG, Rel-Eng

* Explore the possibility of a SIG like structure to continue the work on Fedora

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

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

* [[SIGs/KDE| KDE 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.

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

...ized infrastructure. Other groups may form [[Category:SIGs]]. Over time, a SIG which meets criteria for organization, impact, alignment with the Fedora m

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

...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. * Responsible SIG: Node.js 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. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

.... The objective will bring together Ambassadors, Ambassador Emeritus, Join SIG, and Advocates all under the same umbrella of CommOps in a clear and cohesi

* El [[SIGs/Xfce/es|Xfce SIG]] (Grupo de interés especial) es un grupo de colaboradores de Fedora que a

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

* Name: [[User:Petersen| Jens Petersen]] and [[Haskell_SIG| Haskell 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. * Name: [[Cloud SIG]]

* '''{{fpchat|#fedora-power}}''' - Chat related to the Power Management SIG ...{{fpchat|#fedora-science}}''' - Chat related to the Science and Technology SIG

The Fedora Cloud Working Group and Special Interest Group (SIG) has been busy leading up to Fedora 21. Cloud is now a top-level product fo ...work for Fedora 21, [[Changes/Modular_Kernel_Packaging_for_Cloud|the cloud SIG and kernel team split the kernel]] into two packages. One package contains

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

...ner-sig/issue/45 util-linux] and [https://pagure.io/ContainerSIG/container-sig/issue/46 shadow-utils] ...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.

{{CompactHeader|fonts-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. ...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. -->

| 12:00-12:30 || 16:00-16:30 || 18:00-18:30 || [Talk-25] '''Fedora Join SIG Ninjas''' - Vipul Siddharth, Alberto Rodriguez S., Akashdeep Dhar, Andi Art ...edorapeople.org/~davdunc/State-of-the-Cloud-SIG.odp The State of the Cloud SIG]''' - David Duncan

=== Fedora SIG EPEL Report Week 09/2008 === === Fedora SIG KDE Meeting 2008-02-26 ===

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

...red as an i686 SIG was to be created to handle issues going forward. That SIG has been largely unresponsive. The only thread so far this year has been a

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

The goal of the Embedded Systems SIG is to make Fedora the number one choice for developers of embedded systems

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

{{header|cloud-sig}} <!-- The code for this page is kept at https://pagure.io/cloud-sig/blob/main/f/PRD.mw and should be edited and merged from there -->

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

to -- please ask the EPEL SIG members in case you are in doubt if your repository. Thus the EPEL SIG wrote this policy that describes the

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

...formalizada. Outros grupos podem formar [[Category:SIGs]]. Com o tempo, um SIG que atenda aos critérios de organização, impacto, alinhamento com a miss

* Let them know there is something like Fedora Ruby SIG that they can join

...over IP applications as possible for Fedora. To that end, members of this SIG will assist in packaging VoIP applications and make reviewing VoIP-related ...''Applications/Libraries Being Packaged'' list. Interested in joining the SIG? Just add your WikiName to the list.

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

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

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

{{CompactHeader|fonts-sig}}

The PyTorch SIG meets bi weekly, contributing to the meeting is the best way to engage with

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

{{CompactHeader|fonts-sig}}

* Name: [[User:pviktori| Petr Viktorin]], [[SIGs/Python| Python SIG]] ...ists.fedoraproject.org/thread/ZCNUQBJLDUJUJXK2EOPP2MWL6FJKLBPS/ the Python SIG list discussion thread].

{{CompactHeader|fonts-sig}}

* [[Fonts SIG mailing lists|proponer]] buenas tipografías a Fedora. * [[Fonts SIG mailing lists|proponer]] buenas tipografías para Fedora,

...duction of cloud images for Fedora Linux 38 and Fedora Linux 39, the cloud-sig team did significant work to support transition from the current ImageFacto ...ns ideal qualities of our current tooling in a way that benefits the cloud-sig and the community at large. We have cultivated a strong relationship with t

Outros grupos podem formar [[Category:SIGs]]. Com o tempo, um SIG que satisfaça os critérios de organização, impacto, alinhamento com a m

* Cloud SIG - [[user:dustymabe|Dusty Mabe]] (dustymabe),

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

* Cloud SIG should discuss ordering of qcow downloads vs. vagrant vs. ec2 launch

<!-- All fields on this form are required to be accepted by the Spins SIG <!-- After the Spins SIG has reviewed and accepted your Spins Page the spins wrangler will change it

* [[SIGs/AudioCreation| Audio Creation SIG]] - This Special Interest Group is dedicated to the packaging of media pro

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

...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> ...ckage that will be installed by default on some Editions/Spins (each WG or SIG will need to make their own decision on whether to ship modules enabled by

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

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

* Email: pvalena@redhat.com, jprokop@redhat.com, ruby-sig@lists.fedoraproject.org

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

| {{result|warn|geraldosimiao}}<ref>no user switching since F35. KDE SIG aware</ref>

* Owner: Remi Collet and PHP SIG * Owner: Peter Lemenkov, Fedora Erlang SIG, Randy Barlow, Jeremy Cline

.../Cloud_Cooperation | Explore opportunities for cooperation with Cloud WG / SIG]] (IRC 2021-06-02)

* State of the SIG ** SIG page at https://fedoraproject.org/wiki/SIGs/Red_Team

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

<!-- All fields on this form are required to be accepted by the Spins SIG <!-- After the Spins SIG has reviewed and accepted your Spins Page the spins wrangler will change it

{{CompactHeader|fonts-sig}}

...ims to be directly under the umbrella of the Fedora Science and Technology SIG. || 2011-10-24 || Approved for F16 || Yes

...ims to be directly under the umbrella of the Fedora Science and Technology SIG. || 2011-10-24 || Approved for F18 || Yes

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

The Fedora KDE SIG has [[Changes/KDE411|rebased to KDE 4.11]] for Fedora 20. This release incl The Fedora Cloud SIG has been working hard to provide images that are well-suited for running as

| 9:00-9:30 AM || 2:00-2:30 PM || [https://youtu.be/G4iXisa_GVM Cloud Server SIG] || David Duncan|| A Look at Fedora 35 Cloud Base Image and the Working Gr

...ose, mentioned in FDSCo meeting today...I thought something like Rel Notes SIG, acting as an umbrella for all of the ... above might achieve this better c === Fedora SIG EPEL Report Week 05/2008 ===

...ficial Fedora kickstart files are kept in git, and maintained by the spins SIG.

{{CompactHeader|fonts-sig}}

{{CompactHeader|fonts-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. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

* Other developers: Owners of packages that fail to rebuild, mainly perl-sig users, will be asked using Bugzilla to fix or remove their packages from th

...newly created [https://fedoraproject.org/wiki/SIGs/Flatpak Fedora Flatpak SIG] aims to correct this situation, and will be the group that is responsible The SIG will work to improve the general state of Fedora Flatpaks, including docume

[[Category:Astronomy SIG|Packages]]

* Fedora Cloud Lead - Work closely with Fedora Cloud SIG, identify areas for cloud technology adoption, compose cloud strategies for ...et it done. Some old notes can be found at the [[Messaging_SIG | Messaging SIG page]].

{{CompactHeader|fonts-sig}}

current practices from the Go SIG. As a result of new RPM macros developed by Nicolas Mailhot, some members of the Go SIG wishes to

{{CompactHeader|fonts-sig}}

...amw discussed the Cloud SIG test day, tflink will follow-up with the Cloud SIG for an event recap # tflink to follow-up with cloud sig for test day recap

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

[[Category:Cloud SIG]]

* [[SIGs/KDE| KDE 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. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

* Members of the [[SIGs/Python|Python SIG]] from LATAM, EMEA and NA will get in touch.

...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. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...los empaquetados nuevos, Grupos de Interés Especial (SIGs), Supervisión de SIG, el proceso de empaquetado, manipulación y ejecución de cuestiones de man

* The Xfce SIG has chosen to drop totem and totem-mozplugin in favor of parole and parole- ...Xfce as the official browser of their Desktop Environment, we as the Xfce SIG would like to keep this browser showcased but we will continue to ship Mozi

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

The owners of this change are the HC SIG (https://fedoraproject.org/wiki/SIGs/HC)

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

...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> ...e, please contact the [https://fedoraproject.org/wiki/SIGs/Flatpak Flatpak SIG] matrix room.

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

* Name: [[User:Petersen| Jens Petersen]] (Haskell SIG)

* Let them know there is something like Fedora Ruby SIG that they can join

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

...The objective will bring together Ambassadors, Ambassador Emeritus, Join SIG, and Advocates all under the same umbrella of CommOps in a clear and cohesi * Completion of Role Handbooks for CommOps, Join SIG, Advocate, Ambassador, Ambassador Emeritus. Timeline: February 2021 - June

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

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

* Name: Maxwell G; Benjamin Beasley; Python SIG

...request block the [https://bugzilla.redhat.com/show_bug.cgi?id=1011110 ML-SIG Review Tracker] and send a link to the review request in at least [https://

* Name: [[Haskell_SIG|Haskell 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.

* Email: pvalena@redhat.com, vondruch@redhat.com, jaruga@redhat.com, ruby-sig@lists.fedoraproject.org

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

The Fedora Cloud SIG has been working hard on providing images that are well-suited to running a The Fedora KDE SIG has [[Changes/KDE411|rebased to KDE 4.11]] for Fedora 20. This release incl

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

* Name: [[User:Peter|Peter Lemenkov]], [[SIGs/Erlang|Fedora Erlang SIG]], [[User:bowlofeggs|Randy Barlow]], [[User:jcline|Jeremy Cline]]

* Email: pvalena@redhat.com, vondruch@redhat.com, jaruga@redhat.com, ruby-sig@lists.fedoraproject.org

...nct|See [https://gregdekspeaks.wordpress.com/2012/01/06/why-the-fedora-isv-sig-never-caught-fire/ Greg DeKoenigsberg's excellent postmortem blog post].}}

{{CompactHeader|fonts-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. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...ims to be directly under the umbrella of the Fedora Science and Technology SIG. || 2011-10-24 || Approved for F18 || Yes

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

...lock for the work that he has done with the Store SIG. I started the Store SIG a few months ago when I had some extra time, and as an attempt to bring som === Store SIG Update - a.k.a. State of the SIG ===

...ps://fedorahosted.org/irc-support-sig https://fedorahosted.org/irc-support-sig] is a perfect place for complaints or general feedback. You may also check ...to https://fedorahosted.org/irc-support-sig to file a feedback ticket. The SIG will discuss in their next weekly meeting.

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

* Name: [[User:Peter|Peter Lemenkov]], [[SIGs/Erlang|Fedora Erlang SIG]], [[User:bowlofeggs|Randy Barlow]], [[User:jcline|Jeremy Cline]]

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

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

{{CompactHeader|fonts-sig}}

[[Category:Astronomy SIG|Packages, wishlist]]

;SIG {{Anchor|SIG}} :Пожалуйста не используйте больше сокращение ГпИ, вместо него используйте 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. ...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. -->

The Fedora Cloud Working Group and Special Interest Group (SIG) has been busy leading up to Fedora 21. Cloud is now a top-level product fo

{{CompactHeader|fonts-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. ...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. -->

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

...kickstart file and will - once it's somehow ready - submit it to the Spin SIG for technical approval.</td></tr> ...ink it might be a good idea - not necessarily before submitting it to Spin SIG, but I think such a testing can't be too bad. So a +1 here.</td></tr>

Phosh is a Wayland shell for mobile devices based on Gnome. The mobility SIG has packaged up Phosh and related packages into a 'phosh-desktop' package g ...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.

[[Category:Summer Coding 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.

{{CompactHeader|fonts-sig}}

== Fedora Education SIG Meeting 5th June 2009 == | colspan="3" | * mchua is new to the edu sig - is our goal to make fedora useful to teachers (using it personally, using

* Owner: Owen Taylor, Neal Gompa [on behalf of the KDE SIG] * Owner: Petr Viktorin, Python SIG

* http://borntobeopen.blogspot.com/2012/02/be-active-kde-sig-fad-at-devconf-brno.html ...fedorapeople.org/devconf2012/jskarvad-PowerManagement.pdf Power management SIG] ''(coreOS)'' ||Michal Linhard - [http://rvokal.fedorapeople.org/devconf20

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

Scratchpad of ideas for reviving Fedora Games SIG * Grow interest with the SIG, gain new members, build up membership by explaining what our objectives ou

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

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

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

* Email: pvalena@redhat.com, vondruch@redhat.com, jaruga@redhat.com, ruby-sig@lists.fedoraproject.org

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

...n}} || {{caution}} || {{caution}} || AUS => BRU || en || Fedora DEI, Cloud SiG, CentOS ..., de, cz || Presenting in Distribution Devroom & CentOS Connect, Fedora i3 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. ...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. -->

{{CompactHeader|fonts-sig}}

* [[SIGs/KDE| KDE SIG]] (jreznik AT redhat DOT com)

==== SIG (groupes d’intérêt spécial) ==== * '''{{fpchat|#fedora-power}}''' – Conversation relative au SIG sur la gestion de l’énergie

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

...ed the KDE Red Hat project. He is also an active member of the Fedora KDE SIG. Rex lives in Omaha, Nebraska, with his wife, 2 children, and 4 cats. ...KDE, WebKit security team) and several Fedora subprojects (KDE SIG, WebKit SIG, Board...). In his free time he's one of the co-founders of Openmobility -

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

{{CompactHeader|fonts-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. ...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. -->

** Participation in the [[SIGs/FedoraMini|Fedora Mini SIG]] on behalf of Oregon State University's Computer Science Platform for Lear ** Fedora OLPC SIG member

{{CompactHeader|fonts-sig}}

* What has kept you from joining Ambassadors/CommOps/Join SIG? Join SIG -> Join SIG changes to Join Team to improve branding

...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. * Email: pemensik at redhat.com, dns-sig at fedoraproject dot org

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

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

* '''Fedora Games SIG Artwork''' - interested in developing artwork for some of the games in Fedo

...out environment and the future of that in the opinion of the Fedora Cloud SIG is OpenShift. We believe Fedora + OpenShift is the future of "The Platform"

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

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

{{CompactHeader|fonts-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. ...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.

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

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

* Email: pvalena@redhat.com, vondruch@redhat.com, jaruga@redhat.com, ruby-sig@lists.fedoraproject.org

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

{{CompactHeader|fonts-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. ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...ubjects are therefore heavily inter-related. There is a [[Cloud_SIG |Cloud SIG]] (Special Interest Group) dedicated to the subject, worth to follow as wel

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

See java SIG plans: https://jvanek.fedorapeople.org/devconf/2018/changesInjavaReleasePro * Owner: Peter Lemenkov, Fedora Erlang SIG, Randy Barlow, Jeremy Cline

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

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

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

* '''{{fpchat|#fedora-power}}''' - Chat related to the Power Management SIG ...{{fpchat|#fedora-science}}''' - Chat related to the Science and Technology 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. ...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. -->

...;"|{{projectline|:Category:SIGs|Voir tous les groupes d'intérêts spéciaux (SIG)…||Echo-SIGs-48px.png}}

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

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

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

...ims to be directly under the umbrella of the Fedora Science and Technology SIG. || 2011-10-24 || Approved for F18 || Yes || N/A || [[Scientific_Packages_T

* Cloud SIG - [[user:dustymabe|Dusty Mabe]] (dustymabe),

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

...r:alebastr| Aleksei Bavshin]], [[User:Fale|Fabio Alessandro Locati]], Sway 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. ...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. -->

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