From Fedora Project Wiki

Page title matches

  • = Fedora Astronomy SIG = * Community around Fedora Astronomy SIG have irregular [[SIGs/Astronomy/Meetings| meetings]] .
    11 members (0 subcategories, 0 files) - 07:34, 19 May 2022
  • = Go Programming Language SIG =
    965 bytes (140 words) - 04:56, 6 April 2018
  • ...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]
    12 KB (1,549 words) - 16:38, 20 February 2024
  • The LXQt SIG ([[SIGs |Special Interest Group]]) is a group of Fedora contributors that c * [https://pagure.io/fedora-lxqt/SIG Fedora LXQt SIG task tracker]
    4 KB (540 words) - 19:21, 26 January 2024
  • <!-- page was renamed from EnterpriseExtras/SIG == Joining the SIG ==
    2 KB (329 words) - 19:49, 6 January 2022
  • = Fedora Multimedia SIG = The purpose of the Fedora Multimedia SIG is to provide the best possible multimedia experience for Fedora users out
    1 member (0 subcategories, 0 files) - 10:40, 27 February 2024
  • ...erest Group reviews, tests and approves Fedora Spins. Participants in this SIG are delegates from QA, Release Engineering, the Fedora Project Board, Infra ...come to the Spins SIG for discussion and technical review. Once the Spins SIG comes to a consensus as to technical merit, the benefit to Fedora, and the
    5 KB (730 words) - 19:17, 8 August 2018
  • The LXDE SIG ([[SIGs |Special Interest Group]]) is a group of Fedora contributors that c ...edora 12 and above releases. It is now maintained collectively by the LXDE SIG.
    3 KB (477 words) - 20:53, 17 September 2018
  • {{header|container-sig}} = Fedora Container SIG =
    2 KB (315 words) - 07:40, 24 August 2020
  • {{header|cloud-sig}} = Fedora Cloud SIG =
    4 KB (645 words) - 08:50, 14 March 2024
  • This is the Official Wiki Page for the Respins SIG. 4) How to Join the SIG - You must have an FAS account and request to be added by asking in the #fe
    2 KB (269 words) - 10:15, 2 July 2021
  • {{header|fonts-sig}} ''The Fonts SIG could have been named the Text or Typography SIG. While fonts are a large part of what we do, our actual scope is larger.''
    26 members (6 subcategories, 0 files) - 09:44, 13 May 2020
  • 23 bytes (3 words) - 07:40, 20 April 2017
  • = Fedora Science and Technology SIG = The purpose of the Fedora Science and Technology SIG is to improve the number and quality of packages available for scientific a
    10 members (1 subcategory, 0 files) - 16:17, 15 April 2023
  • 23 bytes (3 words) - 09:54, 25 June 2020
  • 23 bytes (3 words) - 22:14, 27 July 2017
  • 1 member (0 subcategories, 0 files) - 21:38, 4 November 2021
  • = IRC Support SIG = = What is the IRC Support SIG =
    7 KB (1,256 words) - 15:09, 25 January 2021
  • Members of the LXQT SIG.
    0 members (0 subcategories, 0 files) - 21:03, 4 November 2021
  • = Spin SIG meeting information = [http://meetbot.fedoraproject.org/sresults/?group_id=spins-sig&type=team Meetbot logs]
    2 KB (271 words) - 23:15, 29 July 2015
  • ...ate the special interest group for [[Workstation/AtomicWorkstation]]. This SIG has regular bi-weekly meetings to keep the work on the project moving forwa
    3 KB (342 words) - 19:46, 30 July 2018
  • 56 bytes (7 words) - 13:21, 2 October 2015
  • #REDIRECT [[Changes/Features for Fedora 24 from Cloud SIG]]
    59 bytes (8 words) - 09:08, 14 December 2015
  • You can find SIG members regularly on IRC in: [[Category:Summer Coding SIG]]
    3 KB (449 words) - 16:06, 6 February 2017
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> The [[:Category:Fonts SIG| Fonts Special Interest Group]] is an informal group of Fedora Linux contri
    3 KB (449 words) - 22:04, 2 April 2016
  • {{DISPLAYTITLE:Categoria: Tipos de Letra SIG}} {{header|fonts-sig}}
    0 members (0 subcategories, 0 files) - 17:02, 19 August 2019
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> ...sting]] a font. Any help will be appreciated.}}<noinclude>[[Category:Fonts SIG|Signature]]</noinclude>
    542 bytes (73 words) - 22:12, 31 March 2016
  • 33 bytes (4 words) - 22:15, 27 July 2017
  • 32 bytes (4 words) - 22:14, 27 July 2017
  • == Agenda for the Workstation SIG meeting, February 19 == == Agenda for the Workstation SIG meeting, March 5 ==
    1 KB (152 words) - 18:26, 22 February 2018
  • Agenda: Workstation/AtomicWorkstation/SIG/Agenda
    9 KB (1,188 words) - 14:32, 30 April 2018
  • 36 bytes (5 words) - 22:14, 27 July 2017
  • ** Create tasks in container SIG and get help from community. * SIG
    2 KB (376 words) - 14:24, 10 August 2018
  • A SIG may develop over time into a more formal [[Subprojects|Subproject]], but th To create a SIG:
    3 KB (483 words) - 10:41, 9 March 2021
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> ...ess. Don't let this put you off. However. You are more than welcome on the SIG list or in any of our other forums.
    4 KB (642 words) - 22:12, 21 December 2016
  • == Fedora Join SIG 2019 retrospective == == SIG members ==
    4 KB (681 words) - 12:10, 17 February 2020
  • 9 KB (1,447 words) - 10:21, 13 May 2020
  • The Fedora Join Special Interest Group (SIG) aims to set up and maintain channels that let prospective contributors eng ...umented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great example of this. However, we often meet
    4 KB (660 words) - 09:33, 18 November 2019
  • 42 bytes (5 words) - 22:15, 27 July 2017
  • {{CompactHeader|fonts-sig}} Every once in a while a SIG status report is written and posted to the [[Fonts_SIG_mailing_lists|list]]
    700 bytes (91 words) - 20:49, 19 September 2015
  • 37 bytes (4 words) - 22:14, 27 July 2017
  • 37 bytes (4 words) - 22:14, 27 July 2017
  • 37 bytes (4 words) - 22:14, 27 July 2017
  • 37 bytes (5 words) - 22:14, 27 July 2017
  • [[Category:Summer Coding SIG]]
    7 KB (1,058 words) - 15:35, 18 September 2016
  • | name = Cloud SIG Fedora Test Day
    1 KB (214 words) - 21:20, 26 June 2015
  • [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?
    16 KB (2,471 words) - 08:10, 18 September 2016
  • ** SIG: Yes == Determining the Spins SIG workflow ==
    41 KB (5,857 words) - 09:11, 18 September 2016
  • = Changes/Features for Fedora 24 from Cloud SIG = This page contains the details for different changes Cloud SIG (and the working group) are proposing for Fedora 24 release. The details fo
    458 bytes (67 words) - 17:16, 6 January 2016
  • 42 bytes (5 words) - 22:14, 27 July 2017
  • 42 bytes (5 words) - 22:15, 27 July 2017
  • 42 bytes (5 words) - 22:15, 27 July 2017
  • | name = Cloud SIG BoxGrinder Build Fedora Test Day ...from executing the test cases. You can always [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Meta Appliance|download stable meta appliance]] based on F
    11 KB (1,643 words) - 23:35, 17 June 2015
  • | caption = Fedora Cloud SIG | website = [https://fedoraproject.org/wiki/Cloud_SIG Cloud SIG]
    2 KB (315 words) - 21:20, 26 June 2015
  • 6 KB (1,013 words) - 07:19, 24 August 2015
  • 62 bytes (8 words) - 22:14, 27 July 2017
  • 4 KB (469 words) - 15:48, 28 August 2022

Page text matches

  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> ...sting]] a font. Any help will be appreciated.}}<noinclude>[[Category:Fonts SIG|Signature]]</noinclude>
    542 bytes (73 words) - 22:12, 31 March 2016
  • {{CompactHeader|fonts-sig}} Every once in a while a SIG status report is written and posted to the [[Fonts_SIG_mailing_lists|list]]
    700 bytes (91 words) - 20:49, 19 September 2015
  • = ROCm SIG = ...t of the [[SIGs/HC|Heterogeneous Computing SIG]] or the [[SIGs/AI-ML|AI/ML SIG]].
    861 bytes (123 words) - 16:50, 29 August 2023
  • {{header|live-sig}} = Fedora Live SIG =
    1 KB (180 words) - 08:21, 20 July 2020
  • = Fedora Usability SIG (Special Interest Group) = The Fedora Usability SIG (Special Interest Group) aims to provide coherence, accessibility and intui
    904 bytes (113 words) - 14:17, 12 March 2018
  • The goal of this SIG is to coordinate packaging of Libreoffice Suite and related packages. ...office-sig FAS group: https://accounts.fedoraproject.org/group/libreoffice-sig/
    842 bytes (102 words) - 15:48, 16 June 2023
  • = NeuroFedora SIG = The NeuroFedora SIG's goal is to provide neuroscience researchers (and enthusiasts!) a strong,
    482 bytes (73 words) - 15:41, 15 February 2021
  • == BIOS Boot SIG == The goal of this SIG is to help the folks working on Fedora's bootloader stack to keep Fedora bo
    1 KB (197 words) - 17:44, 6 June 2022
  • = Fedora Multimedia SIG = The purpose of the Fedora Multimedia SIG is to provide the best possible multimedia experience for Fedora users out
    1 member (0 subcategories, 0 files) - 10:40, 27 February 2024
  • The emerging SIG Social Science is in the process of establishing itself. To join the SIG and appear as a member, please get in touch with @ingli or @py0xc3 or let u
    2 KB (300 words) - 11:41, 29 September 2022
  • ...intain the Budgie Desktop experience and Spins in the Fedora Project. This SIG is lead by Joshua Strobl, the lead of the upstream Buddies of Budgie organi ...the @budgie-sig FAS group: https://accounts.fedoraproject.org/group/budgie-sig/
    1 KB (158 words) - 21:44, 15 February 2023
  • = Fedora Miracle Desktop Environment Special Interest Group (SIG) = The Fedora Miracle SIG aims to prepare for and promote the upcoming Miracle window manager.
    1 KB (158 words) - 18:25, 1 April 2024
  • The Live DVD SIG (Special Interest Group) is a group of Fedora contributors that are interes Live DVD SIG will be rolling out one Live DVD per Fedora Release. The DVD will contain a
    1,002 bytes (168 words) - 03:58, 27 December 2018
  • = Fedora Pride SIG = ...rowing & evolving SIG, this is always a in-progress definition and we as a SIG will constantly reevaluate our priorities are based on the needs of contrib
    2 KB (252 words) - 23:02, 27 August 2023
  • File:FedoraLiveBanner.png
    Banner for Fedora Live SIG
    (468 × 60 (10 KB)) - 19:45, 5 April 2018
  • Members of the LXQT SIG.
    0 members (0 subcategories, 0 files) - 21:03, 4 November 2021
  • Communicate with the EPEL SIG or other EPEL contributors via the [http://www.redhat.com/archives/epel-dev * [[EPEL SIG]] - EPEL Special Interest Group
    1 KB (224 words) - 20:01, 6 January 2022
  • #REDIRECT [[Changes/Features for Fedora 24 from Cloud SIG]]
    59 bytes (8 words) - 09:08, 14 December 2015
  • === Fedora SIG EPEL Report Week NN/2008 === === Fedora SIG KDE Meeting 2008-04-08 ===
    2 KB (160 words) - 21:35, 20 September 2016
  • File:FedoraLiveBanner2.png
    Banner for the Fedora Live SIG wiki page.
    (468 × 60 (8 KB)) - 06:15, 10 April 2018
  • {{DISPLAYTITLE:Categoria: Tipos de Letra SIG}} {{header|fonts-sig}}
    0 members (0 subcategories, 0 files) - 17:02, 19 August 2019
  • = Fedora Astronomy SIG Meetings = Meetings of the Fedora Astronomy SIG are held regularly every second Saturday at 16h UTC.
    1 KB (145 words) - 15:23, 18 September 2016
  • = Fedora Atomic Desktops Special Interest Group (SIG) = SIG to co-ordinate efforts related to all [https://fedoraproject.org/atomic-des
    4 KB (560 words) - 18:20, 15 February 2024
  • For Fedora 40, the KDE SIG proposed the [https://fedoraproject.org/wiki/Changes/KDE_Plasma_6 KDE Plasm Thus, the KDE SIG created a COPR of those KDE Plasma packages that tracks our packages in Fed
    888 bytes (142 words) - 19:13, 29 January 2024
  • == Agenda for the Workstation SIG meeting, February 19 == == Agenda for the Workstation SIG meeting, March 5 ==
    1 KB (152 words) - 18:26, 22 February 2018
  • = Changes/Features for Fedora 24 from Cloud SIG = This page contains the details for different changes Cloud SIG (and the working group) are proposing for Fedora 24 release. The details fo
    458 bytes (67 words) - 17:16, 6 January 2016
  • 我们有一个 [[SIGs/Spins | Spins 兴趣小组 (SIG)]] 来更新 Spins 并确保符合我们的生产指南。有关 Spins SIG 的更多信息,请参阅 [[SIGs/Spins|wiki 页面]]。
    840 bytes (39 words) - 19:20, 2 February 2017
  • = R Special Interest Group (SIG) = R is a free software environment for statistical computing and graphics. This SIG is for people who are interested in improving R support in Fedora, which in
    1 KB (210 words) - 08:30, 3 August 2022
  • {{header|container-sig}} = Fedora Container SIG =
    2 KB (315 words) - 07:40, 24 August 2020
  • The DotNet SIG is a group of Fedora contributors that maintain [https://fedoraproject.org/ * Public mailing list: {{fplistfull|dotnet-sig}} [dotnet-team FAS Group]
    2 KB (312 words) - 22:03, 26 April 2024
  • {{header|fonts-sig}} ''The Fonts SIG could have been named the Text or Typography SIG. While fonts are a large part of what we do, our actual scope is larger.''
    26 members (6 subcategories, 0 files) - 09:44, 13 May 2020
  • The goal of this Special Interest Group (SIG) is: It should be easy and enjoyable to make music and work with audio on F ...essor in spirit to the former [[Audio_Creation| Audio Creation SIG]]. That SIG had similar objectives but almost exclusively focused on packaging. While p
    2 KB (249 words) - 21:51, 14 December 2023
  • You can help the Usability SIG in several ways: coding, writing some documentation about Usability, testin Usability SIG is also a meeting point between coders, artists and users to share their ex
    817 bytes (124 words) - 14:55, 12 March 2018
  • = Fedora COSMIC Desktop Environment Special Interest Group (SIG) = The Fedora COSMIC SIG aims to prepare for and promote the upcoming [https://github.com/pop-os/cos
    2 KB (240 words) - 23:58, 23 February 2024
  • * [[:Media:KDE-SIG-2008-11-18.txt|KDE-SIG-2008-11-18.txt]]
    922 bytes (114 words) - 07:43, 18 September 2016
  • Welcome to the Sway SIG! Sway is a tiling Wayland compositor similar to the i3 window manager. The goal of this SIG is to package all components and dependencies of sway and to provide a good
    2 KB (249 words) - 17:22, 4 October 2022
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    12 KB (1,660 words) - 13:44, 18 March 2019
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    9 KB (1,183 words) - 14:49, 31 January 2017
  • The goal of this SIG is to help the folks working on support for ARM-based Apple Macintosh compu To help with this, SIG members will maintain packages related to this support in Fedora Linux and
    2 KB (309 words) - 16:42, 2 August 2023
  • == Stewardship SIG == The goal of this SIG is to provide (temporary) maintenance of important packages that are in dan
    3 KB (540 words) - 15:26, 14 July 2020
  • {{#fedoradocs:https://docs.fedoraproject.org/en-US/epel/epel-packagers-sig/}} = EPEL Packagers SIG =
    4 KB (683 words) - 20:40, 8 September 2021
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    9 KB (1,217 words) - 14:51, 31 January 2017
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> ...ess. Don't let this put you off. However. You are more than welcome on the SIG list or in any of our other forums.
    4 KB (642 words) - 22:12, 21 December 2016
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> The [[:Category:Fonts SIG| Fonts Special Interest Group]] is an informal group of Fedora Linux contri
    3 KB (449 words) - 22:04, 2 April 2016
  • [[:Media:KDE-SIG-2009-06-30.txt|KDE-SIG-2009-06-30.txt]]
    872 bytes (102 words) - 09:10, 18 September 2016
  • <!-- page was renamed from EnterpriseExtras/SIG == Joining the SIG ==
    2 KB (329 words) - 19:49, 6 January 2022
  • ...a Medical SIG]]'s packaging guidelines page. Please discuss in the medical-sig mailing list to update this page for your ideas. ...cess#Review_Process Review Process - Review swaps], mailing to the medical-sig mailing list might help you.
    2 KB (284 words) - 08:08, 28 April 2020
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> Problems are tagged by CC-ing the SIG [[Fonts_SIG_mailing_lists | bugs list]] when the upstream issue tracker all
    3 KB (380 words) - 01:49, 24 June 2015
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    8 KB (1,070 words) - 14:53, 31 January 2017
  • = Go SIG = A SIG for people interested in using Go on top of the Fedora in any way. Are you
    2 KB (288 words) - 04:53, 10 July 2022
  • <noinclude>{{CompactHeader|fonts-sig}} ''fontpackages'' evolutions can be discussed on the Fonts SIG [[Fonts SIG mailing lists|mailing list]].
    1 KB (191 words) - 09:35, 22 November 2017
  • Quantum [https://fedoraproject.org/wiki/SIGs SIG] is a group of Fedora contributors/community members who are interested in The Fedora Quantum SIG mission is to learn and experiment with Quantum computing through Fedora wi
    930 bytes (133 words) - 10:18, 2 July 2021
  • = Fedora MTB SIG = * {{fplistfull|mtb-sig}} mailing list
    642 bytes (104 words) - 00:08, 16 February 2019
  • = Fedora SIG 2015 Meetings =
    318 bytes (40 words) - 22:14, 27 July 2017
  • = Fedora SIG 2016 Meetings =
    319 bytes (40 words) - 22:14, 27 July 2017
  • = Fedora Join SIG 2016 Meetings =
    324 bytes (41 words) - 22:14, 27 July 2017
  • = Fedora Join SIG 2015 Meetings =
    323 bytes (41 words) - 22:14, 27 July 2017
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    15 KB (2,030 words) - 19:52, 10 September 2018
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    16 KB (2,042 words) - 15:41, 1 June 2017
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    15 KB (1,849 words) - 13:32, 3 May 2018
  • = AI/ML Special Interest Group (SIG) = The Fedora AI/ML SIG is a grouping of like minded individuals and groups who are working towards
    2 KB (323 words) - 15:09, 15 August 2023
  • [[https://pagure.io/cloud-sig/issue/357 | Placeholder for checklist for release ]] 1. [[ https://pagure.io/cloud-sig/issue/318 | updating GCP image uploads ]]
    334 bytes (37 words) - 15:56, 3 February 2022
  • The Pantheon Desktop Environment (DE) SIG ([[SIGs |Special Interest Group]]) is a group of Fedora contributors that c We have informal chats about Pantheon SIG development in {{fpchat|#fedora-pantheon}} IRC channel in '''libera'''.
    8 KB (863 words) - 17:34, 8 April 2023
  • A SIG may develop over time into a more formal [[Subprojects|Subproject]], but th To create a SIG:
    3 KB (483 words) - 10:41, 9 March 2021
  • |style="border-width: 0px;"|{{projectline|SIGs/Rust|Rust SIG|Rust Special Interest Group|Application-x-rust.svg|}} = Rust SIG =
    2 KB (215 words) - 14:42, 21 July 2023
  • [[Category:Astronomy SIG]]
    185 bytes (20 words) - 20:08, 14 April 2017
  • ...t your software license and compatibility with Fedora standards? The ISV SIG can help. # Join the [http://www.redhat.com/mailman/listinfo/fedora-isv-sig-list mailing list].
    2 KB (291 words) - 21:50, 17 September 2016
  • == PyTorch Special Interest Group (SIG) == The intent of the PyTorch SIG is to bring together all people that are interested in AI/ML/HC/HPC in Fedo
    4 KB (532 words) - 19:18, 16 April 2024
  • ...raproject.org/mailman/listinfo/php-devel php-devel mailing list]. All PHP SIG members are encouraged to subscribe. == PHP SIG Documentation ==
    2 KB (296 words) - 07:13, 4 November 2022
  • The goal of this SIG is to help the folks working on eBPF development and adoption, and evangeli ...reation of bpfd—a system daemon streamlining eBPF program management. This SIG group is topics such as solutions, orchestration, deployment and developmen
    2 KB (249 words) - 10:26, 16 November 2023
  • GraphQL [https://fedoraproject.org/wiki/SIGs SIG] is a group of Fedora contributors/community members who are interested in The Fedora GraphQL SIG mission is to maintain, grow, guide and promote best practice of the develo
    967 bytes (123 words) - 10:25, 2 July 2021
  • ...ate-desc Search the Fedora Projects "meetingminutes" mailing list for "kde-sig" messages] ...oraproject.org/sresults/?group_id=kde-sig&type=team Search meetbot for kde-sig team meetings]. (Until [https://github.com/fedora-infra/mote/issues/112 iss
    16 KB (2,308 words) - 08:29, 21 June 2021
  • Fedora Medical Special Interest Group (SIG) is to enable a medical practice, the research, life sciences, bioinformati == Join Fedora Medical SIG and Contribute ==
    4 KB (554 words) - 07:23, 19 May 2022
  • == SIG Responsibilities == [[Category:Fedora special-interest groups|ELN SIG]]
    2 KB (256 words) - 16:36, 1 June 2020
  • The KubeDev SIG (Special Interest Group) is a group of Fedora contributors that discuss and == Joining the SIG ==
    3 KB (390 words) - 11:44, 24 April 2023
  • Each Working Group (or SIG/individual in such case) is responsible to keep this information up to date ...ch Fedora release and confirm it's correctness with each Working Group (or SIG/individual in such case).
    14 KB (1,782 words) - 08:25, 25 September 2017
  • = Fedora Minimal Core SIG = The Fedora Minimal Core SIG is a group of people interested in maintaining Fedora's ''minimal package s
    4 KB (539 words) - 03:43, 7 May 2016
  • = XR (VR/AR/MR) Special Interest Group (SIG) = The Fedora XR SIG is a grouping of like minded individuals and groups who are working towards
    4 KB (602 words) - 04:39, 14 April 2024
  • ...lman/listinfo/php-devel php-devel mailing list]. Todos los miembros de PHP SIG están invitados a suscribirse. == PHP SIG Documentación ==
    2 KB (296 words) - 18:37, 22 December 2018
  • ** Create tasks in container SIG and get help from community. * SIG
    2 KB (376 words) - 14:24, 10 August 2018
  • ...erest Group reviews, tests and approves Fedora Spins. Participants in this SIG are delegates from QA, Release Engineering, the Fedora Project Board, Infra ...come to the Spins SIG for discussion and technical review. Once the Spins SIG comes to a consensus as to technical merit, the benefit to Fedora, and the
    5 KB (730 words) - 19:17, 8 August 2018
  • {{header|cloud-sig}} = Fedora Cloud SIG =
    4 KB (645 words) - 08:50, 14 March 2024
  • = EPEL SIG Meetings = The EPEL SIG meeting are open for everyone and held each week on Wednesday in #fedora-me
    2 KB (287 words) - 19:58, 6 January 2022
  • ...istinfo/lista de discussão php-devel php-devel] . Todos os membros do PHP SIG são incentivados a inscrever-se. == Documentação PHP SIG ==
    2 KB (306 words) - 23:59, 22 February 2018
  • Os encontros do Xfce SIG atualmente ocorrem todas as terças-feiras às 21:00 UTC no #fedora-meeting
    208 bytes (30 words) - 04:48, 13 June 2017
  • ...[https://fedoraproject.org/wiki/SIGs/AtomicDesktops Fedora Atomic Desktops SIG].}} = Silverblue SIG =
    2 KB (338 words) - 14:42, 25 September 2023
  • The LXDE SIG ([[SIGs |Special Interest Group]]) is a group of Fedora contributors that c ...edora 12 and above releases. It is now maintained collectively by the LXDE SIG.
    3 KB (477 words) - 20:53, 17 September 2018
  • The Xfce SIG meets (currently) every tuesday at 21:00 UTC in #fedora-meeting on irc.free
    217 bytes (32 words) - 04:45, 13 June 2017
  • | caption = Fedora Cloud SIG | website = [https://fedoraproject.org/wiki/Cloud_SIG Cloud SIG]
    2 KB (315 words) - 21:20, 26 June 2015
  • The Fedora Spins SIG is pleased to announce the availability of the following Fedora Spins. ...Fedora 10 installation DVD). Brought to you by the [[SIGs/KDE|Fedora-KDE SIG]].
    3 KB (445 words) - 09:11, 18 September 2016
  • The KDE SIG (Special Interest Group) is a group of Fedora contributors that maintain [[ ...text chat if you prefer that. [https://apps.fedoraproject.org/calendar/kde-sig/ Here] is the meeting calendar.
    4 KB (604 words) - 19:09, 15 March 2024
  • * [https://src.fedoraproject.org/group/dns-sig dns-sig group sources] ...oard?groups=dns-sig packager dashboard] - bugs summary for packages in DNS SIG
    5 KB (642 words) - 22:10, 3 January 2024
  • = Fedora Desktop SIG = Welcome! This is the home page for the [[SIGs/Desktop| Desktop SIG]] for Fedora.
    3 KB (464 words) - 09:15, 13 October 2021
  • ...IGs_KDE_Meetings_2008(2d)04(2d)15_fedora-kde-sig-2008-04-15.txt|fedora-kde-sig-2008-04-15.txt]] * RexDieter asked if someone else from KDE-SIG will attend.
    2 KB (321 words) - 21:35, 19 September 2016
  • The LXQt SIG ([[SIGs |Special Interest Group]]) is a group of Fedora contributors that c * [https://pagure.io/fedora-lxqt/SIG Fedora LXQt SIG task tracker]
    4 KB (540 words) - 19:21, 26 January 2024
  • * State of the SIG ** Reminder that SIG page is at https://fedoraproject.org/wiki/SIGs/Red_Team
    2 KB (215 words) - 13:36, 7 November 2017
  • == Get involved with the Fedora Java SIG ==
    2 KB (262 words) - 11:13, 8 October 2015
  • ** If not planning to continue their spin should let the Spins SIG know. ** At spins freeze any spins that were not ready for the Spins SIG or approved, should have the discontinued spin process applied to them.
    3 KB (482 words) - 00:29, 29 August 2016
  • |style="border-width: 0px;"|{{projectline|SIGs/Flatpak|Flatpak SIG|Fedora Flatpak Packaging Special Interest Group|Flatpak Logo 200px.png|}} = Flatpak SIG =
    5 KB (720 words) - 22:00, 30 January 2024
  • ...that complies with the [[Spins_Guidelines|Spins Guidelines]] to the Spins SIG mailing list at [mailto:spins@lists.fedoraproject.org spins@lists.fedorapro ...ate access to the git repo until after their spin is approved by the Spins SIG (or Council if there is a potential trademark issue).
    9 KB (1,448 words) - 20:01, 20 August 2019
  • This SIG focuses on problems related to Universities and education, that is onboardi * Share with the Fedora community, find SIG members
    2 KB (297 words) - 09:49, 20 October 2021
  • |style="border-width: 0px;"|{{projectline|SIGs/Ruby|Ruby SIG|Ruby Special Interest Group|Application-x-ruby.png|}} A SIG for people who are interested in improving the state of Ruby in Fedora. Thi
    6 KB (898 words) - 09:20, 16 February 2023
  • Live upgrade SIG is a team of Fedora developers and users interested in making upgrades via The purpose of this SIG is to make live upgrades a well tested and supported option within Fedora.
    1 KB (197 words) - 19:48, 8 August 2018
  • The mission of the Fedora Education SIG (Edu SIG) is to optimize Fedora for use by teachers and learners, both within and ou == Joining the SIG ==
    4 KB (605 words) - 19:09, 8 August 2018
  • ...]. This is the independent software vendors (ISV) special interest group (SIG). * Announce the SIG presence within the Fedora universe
    5 KB (799 words) - 17:35, 5 November 2021
  • = Historical KDE SIG pages and content = The Fedora KDE SIG played an integral role in creating the Fedora 7 KDE-Live spin and continue
    2 KB (213 words) - 08:24, 21 June 2021
  • == Fedora Join SIG 2019 retrospective == == SIG members ==
    4 KB (681 words) - 12:10, 17 February 2020
  • The Store SIG (Special Interest Group) is a group of Fedora contributors working to creat == Joining the SIG ==
    3 KB (431 words) - 19:43, 8 August 2018
  • ...page is mostly out of date. The [[SIGs/AI-ML|AI/ML SIG]] has replaced this SIG and will be the better reference going forward.}} = Machine Learning SIG =
    6 KB (869 words) - 16:03, 15 August 2023
  • = Fedora KDE SIG planning list =
    344 bytes (53 words) - 08:24, 21 June 2021
  • * [http://meetbot.fedoraproject.org/fedora-meeting/2010-06-29/kde-sig.2010-06-29-14.05.html Meeting minutes] * [http://meetbot.fedoraproject.org/fedora-meeting/2010-06-29/kde-sig.2010-06-29-14.05.log.html Full log]
    2 KB (252 words) - 22:13, 17 September 2016
  • <!-- This page is drafted on top of LxQT SIG page. Thanks for their great document! --> This SIG would not attempt to create packages to be included into the core Fedora re
    3 KB (394 words) - 09:59, 8 February 2021
  • == Python Special Interest Group (SIG) == ...readability. [https://fedoralovespython.org Fedora loves Python] and this SIG is for people who would like to see this relationship flourish. We aim to a
    9 KB (1,202 words) - 11:14, 20 February 2024
  • Work on the [[Summer Coding SIG]] needs. # Complete workflow so mentors, admins, and SIG members know who, what, where, when, how, and why.
    2 KB (281 words) - 15:44, 9 January 2016
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude> <noinclude>[[Category:Fonts packaging]][[Category:Comps SIG|Fonts]]{{:Fonts_SIG_signature}}</noinclude>
    2 KB (247 words) - 09:14, 3 June 2016
  • Welcome to WASM SIG! WebAssembly (abbreviated Wasm) is a binary instruction format for a stack- ...d across various language ecosystems and technologies and the goal of this SIG is to help organize the effort of packaging and maintaining the packages wh
    3 KB (412 words) - 11:19, 26 January 2023
  • | [[:Category:Fonts_SIG|字型 SIG]] * 募集新的 SIG 成员、
    16 KB (734 words) - 09:35, 7 August 2021
  • This is a package of bookmarks for the [[SIGs/Education/Spin|Education SIG spin]]. It contains links to information about the spin and the open source
    852 bytes (120 words) - 09:09, 18 September 2016
  • {{CompactHeader|fonts-sig}} [[Category:Fonts SIG|Creative tasks]]
    2 KB (253 words) - 05:48, 17 April 2022
  • | Rust SIG || [[User:Decathorpe|Fabio Valentini]] || spot | Pantheon SIG || [[User:Decathorpe|Fabio Valentini]] || spot
    6 KB (890 words) - 15:09, 26 April 2023
  • ...lciregi|alciregi]], [[User:Jflory7|Justin W. Flory]] || Using current Join SIG docs as is, redirecting to this on the CommOps page | Role: Fedora Join SIG Team Member || Join SIG || Join SIG || https://pagure.io/fedora-join/fedora-join-docs/pull-request/10; https://
    12 KB (1,443 words) - 15:27, 13 January 2022
  • The Mono SIG is a group of Fedora contributors that maintain Mono (and related) packages The goal of the Mono SIG is to provide high-quality and usable Mono software packages to Fedora user
    4 KB (529 words) - 12:51, 21 September 2021
  • ...IGs_KDE_Meetings_2008(2d)02(2d)05_fedora-kde-sig-2008-02-05.txt|fedora-kde-sig-2008-02-05.txt]]
    2 KB (266 words) - 15:24, 18 September 2016
  • ...ning a Top-5-List of the "most-needed-next-topics" to work on (to give new SIG-Members an advice where we need the most work) ...IGs_KDE_Meetings_2007(2d)10(2d)23_fedora-kde-sig-2007-10-23.txt|fedora-kde-sig-2007-10-23.txt]]
    4 KB (552 words) - 15:24, 18 September 2016
  • = Joining the EPEL SIG = ...EPEL. A few are listed below. If you think of another way to help out the SIG, feel free to bring it up on our mailing list or at our weekly meetings.
    2 KB (269 words) - 19:55, 6 January 2022
  • This is the Official Wiki Page for the Respins SIG. 4) How to Join the SIG - You must have an FAS account and request to be added by asking in the #fe
    2 KB (269 words) - 10:15, 2 July 2021
  • = OpenStack SIG = A SIG for people interested in maintaining OpenStack clients in Fedora. This incl
    2 KB (244 words) - 19:40, 8 August 2018
  • == Joining the SIG == ...ts.fedoraproject.org/admin/lists/dotnet-sig.lists.fedoraproject.org dotnet-sig@lists.fedoraproject.org] mailing list
    3 KB (456 words) - 22:05, 26 April 2024
  • = IRC Support SIG = = What is the IRC Support SIG =
    7 KB (1,256 words) - 15:09, 25 January 2021
  • ...Developers Conference, Brno 2011]] - possibility of subsidy for Fedora KDE SIG or KDE upstream contributors * [http://meetbot.fedoraproject.org/fedora-meeting/2011-01-11/kde-sig.2011-01-11-15.01.html Meeting minutes]
    2 KB (225 words) - 21:36, 19 September 2016
  • ...esktop SIG defines the user experience for all of Fedora? What if another SIG disagrees? ...s responsible for the look and feel of Fedora. The [[SIGs/Desktop|Desktop SIG]] is responsible for the [[Default offering|default image]] and should work
    9 KB (1,446 words) - 11:35, 9 October 2021
  • = Go Programming Language SIG =
    965 bytes (140 words) - 04:56, 6 April 2018
  • == Contributing roles in the Design Software SIG == Design Software SIG has three channels for communication:
    5 KB (646 words) - 00:12, 10 April 2021
  • ...DOs and DONTs for Spins being submitted for review to the [[Spins_SIG|Spin SIG]] . ...MUST be tested thoroughly before submitting it to the [[SIGs/Spins| Spin SIG]] for technical review.
    3 KB (427 words) - 05:40, 18 April 2021
  • {{CompactHeader|fonts-sig}} ...quick summary to help newcomers undertand the [[:Category:Fonts SIG| Fonts SIG]] workflow.
    6 KB (886 words) - 11:11, 9 October 2021
  • * [[SIGs/Xfce| Xfce SIG]] (Special interest Group特别兴趣组)是Fedora的一个帮助提升Xfc
    1 KB (97 words) - 14:16, 6 April 2021
  • ...teriores. Ahora es mantenido colectivamente por los [[SIGs/Xfce/XfceLive| SIG de Fedora Xfce]]. El SIG Xfce (Special Interest Group) es un grupo de contribuyentes de Fedora que c
    5 KB (753 words) - 22:25, 19 June 2015
  • == Fedora PowerManagement SIG == The PowerManagement SIG (Special Interest Group) is a group of Fedora contributors that want to imp
    5 KB (652 words) - 19:43, 8 August 2018
  • * [[:Media:KDE-SIG-2008-09-09.txt|KDE-SIG-2008-09-09.txt]] * The KDE-SIG was represented by [[KevinKofler]], [[LukasTinkl]] and [[JaroslavReznik]].
    5 KB (662 words) - 21:35, 19 September 2016
  • ** Fedora Python SIG (by [[User:tomspur]]) ** How much time it takes to participate in Python SIG activities?
    2 KB (296 words) - 13:06, 1 June 2018
  • ...and other resources should work as a seamless whole. The Fedora Astronomy SIG aims to include the VO tools in Fedora and the Fedora Astronomy Spin. This [[Category:Astronomy SIG]]
    2 KB (340 words) - 11:38, 12 April 2017
  • ...ed32e3fa78f2d66b7cf52d3148f79e| How to get more people involved in the KDE-SIG?]] ...IGs_KDE_Meetings_2007(2d)09(2d)25_fedora-kde-sig-2007-09-25.txt|fedora-kde-sig-2007-09-25.txt]]
    4 KB (544 words) - 21:35, 19 September 2016
  • = Mission Statement and Plan for "Formal Methods" Fedora SIG = for a proposed "Formal Methods" Fedora SIG, per the [[Defining_projects|Defining projects]] page.
    7 KB (1,085 words) - 20:49, 19 September 2016
  • The Fedora Join Special Interest Group (SIG) aims to set up and maintain channels that let prospective contributors eng ...umented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great example of this. However, we often meet
    6 KB (881 words) - 16:24, 8 September 2023
  • * After packages are accepted in to Fedora, create a Fedora NoSQL SIG Spin * 2007/11/13: Start of the SIG page.
    5 KB (619 words) - 21:41, 31 December 2018
  • ...t is now maintained collectively by the [[SIGs/Xfce/XfceLive| Fedora Xfce SIG]]. The Xfce SIG (Special Interest Group) is a group of Fedora contributors that contribute
    6 KB (877 words) - 03:42, 8 March 2023
  • = Fedora Join SIG 2018 Meetings =
    2 KB (254 words) - 18:50, 7 August 2018
  • El SIG EPEL siempre esta buscando personas interesadas en ayudar. Siempre requerim == Comunicarse con el EPEL SIG ==
    6 KB (930 words) - 14:16, 17 January 2017
  • {{header|cloud-sig}} ...s next-generation cloud product. You may also be interested in the [[Cloud SIG]], which has a broader, more loosely defined mission covering all things re
    6 KB (961 words) - 21:03, 1 November 2022
  • (SIG, por las iniciales en inglés de Fedora Special Interest Group) ...ocs.fedoraproject.org]. Sus fuentes residen en un [https://pagure.io/neuro-sig/documentation/ pagure repository].
    5 KB (795 words) - 19:27, 22 December 2018
  • The purpose of the Fedora x86-64 SIG is to help fix any and all x86-64 related bugs
    683 bytes (96 words) - 10:41, 14 February 2019
  • ...perienced. These are pages not specifically under a sub-project or [[SIGs|SIG]]. === Project and SIG focused pages for contributors ===
    6 KB (859 words) - 21:17, 29 November 2015
  • = Fedora SIG 2017 Meetings =
    2 KB (224 words) - 22:14, 27 July 2017
  • = Fedora Join SIG 2017 Meetings =
    2 KB (262 words) - 19:41, 29 December 2017
  • {{CompactHeader|fonts-sig}}
    1 KB (108 words) - 16:29, 18 February 2022
  • ...Joining_EPEL| Junte-se ao EPEL]] para mais informações sobre como aderir à SIG. == Comunicando-se com o EPEL SIG ==
    6 KB (941 words) - 18:10, 19 June 2019
  • | Ask Fedora SIG | Fedora Join SIG
    5 KB (688 words) - 08:28, 17 January 2024
  • The Node.js SIG is a group of Fedora contributors that maintain Node.js packages in Fedora.
    980 bytes (140 words) - 11:16, 10 April 2021
  • ...perienced. These are pages not specifically under a sub-project or [[SIGs|SIG]]. === Project and SIG focused pages for contributors ===
    6 KB (878 words) - 01:14, 13 September 2019
  • The goal of the SIG is to bring together CI enthusiasts interested in developing tools, best pr * Join IRC channel and participate in Fedora CI SIG meetings
    3 KB (462 words) - 15:02, 16 June 2021
  • = Fedora Astronomy SIG = * Community around Fedora Astronomy SIG have irregular [[SIGs/Astronomy/Meetings| meetings]] .
    11 members (0 subcategories, 0 files) - 07:34, 19 May 2022
  • | 9 || Haskell SIG Update|| [[User:Petersen|Jens Petersen]] || Haskell SIG tools and activity for F25 and F26 || Developer Experience
    2 KB (321 words) - 15:56, 23 March 2019
  • ...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.
    5 KB (817 words) - 17:46, 21 August 2023
  • ...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.
    5 KB (819 words) - 15:26, 2 March 2022
  • {{CompactHeader|fonts-sig}} {{:Fonts_SIG_signature}}[[Category:Fonts SIG]]
    2 KB (397 words) - 22:10, 21 December 2016
  • * SIG: [[SIGs/KDE|KDE SIG]] ** The KDE SIG will submit the [https://pagure.io/pungi-fedora Pungi changes] needed to ad
    5 KB (830 words) - 17:50, 2 June 2021
  • ...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.
    5 KB (825 words) - 15:59, 8 July 2021
  • ...ipare ad EPEL]] per maggiori informazioni su come iniziare a contribuire a SIG. == Comunicare col SIG EPEL ==
    6 KB (878 words) - 06:03, 10 July 2016
  • * Responsible WG: KDE SIG * Proposal owners: The KDE SIG will make the kickstart and pungi changes needed to support adding the aarc
    4 KB (529 words) - 02:22, 7 December 2020
  • {{CompactHeader|fonts-sig}}
    1 KB (95 words) - 06:25, 30 December 2017
  • ...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.
    6 KB (805 words) - 15:17, 17 February 2022
  • ...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.
    6 KB (843 words) - 12:00, 25 August 2021
  • These are hours (in UTC) when various [[SIGs/Join|Fedora Join SIG]] team members are usually available in {{fpchat|#fedora-join}} (which is b
    2 KB (231 words) - 06:55, 29 September 2020
  • ; I understand you are part of the Fedora Cloud SIG. Can you tell us a bit about this group? ....org/mailman/listinfo/cloud. In addition to the EC2 initiatives, the Cloud SIG is working on other features for future releases of Fedora, including integ
    4 KB (787 words) - 08:10, 18 September 2016
  • == Fedora's KDE SIG == The [[SIGs/KDE| KDE SIG]] (Special Interest Group) is a group of Fedora contributors that [[Packag
    5 KB (744 words) - 10:40, 24 April 2024
  • ...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.
    6 KB (836 words) - 16:45, 7 January 2021
  • ...owners 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: [[SIGs/Budgie|Budgie]]
    6 KB (844 words) - 13:43, 25 May 2023
  • You can find SIG members regularly on IRC in: [[Category:Summer Coding SIG]]
    3 KB (449 words) - 16:06, 6 February 2017
  • ...is not active or holding meetings. The [[SIGs/Music & Audio| Music & Audio SIG]] has been created as a successor.}} The Audio Creation SIG is currently in a phase where we are concentrating on getting more audio re
    5 KB (830 words) - 21:52, 14 December 2023
  • {{CompactHeader|fonts-sig}}
    1 KB (142 words) - 16:44, 6 February 2018
  • {{DISPLAYTITLE:SIG - Grupo de Interesses Especiais}} == Criar um SIG ==
    0 members (0 subcategories, 0 files) - 12:50, 28 May 2020
  • ...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.
    6 KB (878 words) - 15:23, 28 May 2019
  • ...IGs_KDE_Meetings_2008(2d)01(2d)03_fedora-kde-sig-2008-01-03.txt|fedora-kde-sig-2008-01-03.txt]]
    3 KB (410 words) - 15:24, 18 September 2016
  • ...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.
    6 KB (867 words) - 18:39, 7 April 2020
  • * [https://copr.fedorainfracloud.org/groups/g/xr/coprs/ Fedora COPR XR SIG Group] - Pre-builds, automatic builds from upstream, used as a source to me ...up/xr-sig Fedora Source XR SIG Group] - Source control for packages the XR SIG has maintainership access.
    7 KB (914 words) - 23:45, 23 April 2024
  • * After packages are accepted in to Fedora create a Fedora Hams SIG Spin. * 2007/11/13: Start of the SIG page.
    6 KB (991 words) - 07:53, 8 October 2023
  • * Responsible WG: ARM SIG * Proposal owners: The ARM SIG will make the kickstart changes needed to add the desktop images to the com
    4 KB (539 words) - 02:50, 12 August 2019
  • A SIG for people who are interested in improving the state of Java in Fedora. Thi If you want to take the attention of the SIG members. Please open a bug report and make it block [https://bugzilla.redha
    7 KB (907 words) - 10:17, 14 July 2021
  • ...ives/list/erlang@lists.fedoraproject.org/ Erlang SIG Mailing list] for any SIG-related discussion. ...ject.org/thread/ZLRSPWBF2IVVTPOJAUDQCT5L6XPKDHNB/ Some work for the Erlang SIG (December 2018)]
    5 KB (683 words) - 11:20, 29 October 2022
  • ...ondary archs go here. If you think you qualify contact the secondary arch sig first. ...where. If you have a spin that needs to get approved see the Fedora Spins Sig page and get it approved.
    4 KB (639 words) - 17:17, 6 December 2023
  • This proposal impacts the Cloud SIG, Spins SIG, Fedora Rel-Eng and the infrastructure team. It does not require functional
    3 KB (390 words) - 21:51, 17 September 2016
  • ...hese packages are maintained by 35 different maintainers along with the Go SIG. [https://pagure.io/GoSIG/go-leaves/blob/main/f/leaves These leaves]([https ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
    8 KB (1,300 words) - 13:33, 11 May 2023
  • The Fedora Join Special Interest Group (SIG) aims to set up and maintain channels that let prospective contributors eng ...umented, SOPs (standard operating procedures) for joining their respective SIG. The infrastructure team is a great example of this. However, we often meet
    4 KB (660 words) - 09:33, 18 November 2019
  • * [[:Category:Fonts_SIG| Fonts SIG]] {{CompactHeader|fonts-sig}}
    7 KB (391 words) - 13:25, 17 February 2016
  • {{CompactHeader|fonts-sig}} {{:Fonts_SIG_signature}} [[Category:Fonts SIG]] [[Category:Localization|Font list]] [[Category: Internationalization]]
    3 KB (431 words) - 04:24, 9 February 2022
  • {{CompactHeader|fonts-sig}}
    1 KB (127 words) - 09:59, 30 December 2017
  • ...olos| Dan Čermák]], [https://docs.fedoraproject.org/en-US/i3/ Fedora i3 SIG] The Fedora i3 SIG began in May 2020 with a goal of creating an official Fedora Spin featuring
    10 KB (1,602 words) - 17:47, 7 January 2021
  • {{CompactHeader|fonts-sig}}
    1 KB (129 words) - 19:18, 2 December 2015
  • [[SIGs/AmateurRadio|SIG de Rádio Amador]] O SIG Big Data, no melhor estilo do Fedora, foca em fazer do Fedora a melhor plat
    0 members (0 subcategories, 0 files) - 01:25, 21 February 2018
  • = 3D Printing SIG = The Fedora 3D Printing SIG's goal is to make Fedora the best platform for 3D printing.
    6 KB (853 words) - 09:58, 17 March 2023
  • ...The goal is to develop a "funnel" of potential contributors that the Join SIG can help onboard into the community. In order to support this, we will take ** Record recruits' contact info and pass it to the Join SIG
    3 KB (448 words) - 20:09, 6 April 2020
  • = Confined Users Special Interest Group (SIG) = SIG to co-ordinate efforts related to different means to confine (which means a
    8 KB (1,131 words) - 11:31, 11 April 2024
  • ...mplement the solutions. The purpose of this Objective would be to create a SIG or WG dedicated to doing just that. ...e to create a SIG or WG dedicated to packager quality of life issues. This SIG/WG would consist of interested packagers who are willing to contribute to p
    6 KB (1,033 words) - 14:08, 7 February 2024
  • | [[:Category:Fonts SIG|Fonts SIG]] * Recruit new SIG members,
    16 KB (2,158 words) - 22:14, 22 November 2021
  • | [[:Category:Fonts_SIG|フォントSIG]] * 新しいSIGメンバーの紹介
    19 KB (1,034 words) - 21:42, 2 May 2021
  • This page is [[SIGs/Medical|Fedora Medical SIG]]'s memo page. Feel free to edit this page for your ideas.
    2 KB (212 words) - 10:53, 11 May 2020
  • ...ницы не относящиеся к какому либо подпроекту или [[SIGs| специальной группеSIG]]. === Project and SIG focused pages for contributors ===
    7 KB (631 words) - 21:52, 29 November 2015
  • ...Joining_EPEL | Joining EPEL]] page for more information on how to join the SIG. == Communicating with the EPEL SIG ==
    9 KB (1,402 words) - 16:20, 8 September 2021
  • = Fedora Perl SIG Mission = ...nd will be included in the upcoming [[Infrastructure/ProjectHosting| Perl SIG Infrastructure hosted project]].
    8 KB (1,131 words) - 12:20, 6 January 2023
  • = Fedora Formal Methods Special Interest Group (SIG) = The goal of the Formal Methods SIG is to make it easy to install formal methods tools in Fedora, to ease the p
    6 KB (873 words) - 03:49, 27 December 2018
  • ...3 Spin: How a dream can became true || English || I will talk about the i3 SIG, how it was formed and how it will become a formal Spin for F34 ...th contributing to Fedora Project || English || I will talk about the Join SIG, how it helps on boarding newcomers to Fedora and how one can get started w
    3 KB (468 words) - 00:39, 7 November 2020
  • ...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.''
    5 KB (715 words) - 10:28, 28 January 2018
  • {{CompactHeader|fonts-sig}}
    1 KB (147 words) - 06:18, 30 December 2017
  • * [[SIGs/Trusted_computing|Fedora Trusted Computing SIG page]]
    1 KB (204 words) - 22:14, 17 September 2016
  • * Fedora Join SIG members ...and interview a small group of contributors who both went through the Join SIG process or support as mentors. Collect feedback on strengths and weaknesses
    9 KB (1,251 words) - 02:22, 13 January 2024
  • {{CompactHeader|fonts-sig}}
    1 KB (168 words) - 08:49, 4 March 2024
  • ...discouraged. Please run changes by the [[SIGs/Minimal_Core | Minimal Core SIG]]. ...GNOME environment definition is maintained by the [[SIGs/Desktop | Desktop SIG]]. Please run changes through {{fplist|desktop}}.
    7 KB (1,109 words) - 21:59, 29 August 2022
  • ...hard to keep up with bugs and security issues. After discussion, the KDE SIG decided that twice a year update would give users the stability they want, ...when this gets difficult, particularly in the middle of the year. The KDE SIG will give a best-effort attempt to backport fixes from future stable releas
    3 KB (432 words) - 16:54, 20 July 2023
  • ...owners 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: Cloud
    7 KB (1,138 words) - 18:37, 5 August 2020
  • ...n the standard Fedora repositories are mainted by the [[SIGs/DotNet|DotNet SIG]]. '''[https://copr.fedorainfracloud.org/coprs/g/dotnet-sig/dotnet/ Our dotnet packages on copr]''' (open source)
    2 KB (258 words) - 21:59, 26 April 2024
  • ...is to make Fedora the premier distribution for robotics development. The SIG focuses on packaging free and open source software spanning a large variety This is a list of packages the SIG would like to see in Fedora. It serves as a to-do list for the group, and
    11 KB (1,482 words) - 22:44, 16 March 2021
  • {{CompactHeader|fonts-sig}}
    2 KB (193 words) - 13:25, 10 December 2017
  • * pagure.io:neuro-sig/NeuroFedora good+first+issue ankursinha * pagure.io:neuro-sig/documentation good+first+issue ankursinha
    5 KB (608 words) - 08:47, 15 February 2024
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    5 KB (748 words) - 08:43, 8 August 2017
  • ...d Hat contributions | innovation]] som Fedora driver, har dette fokus vist sig at have en tydelig og langtidsholdbar effekt. Nogen af de nyeste udviklinge Det modsatte er også rigtigt: ved at holde sig tæt til ''upstream''-udviklingsholdene, får Fedora ofte det nyeste softwa
    6 KB (881 words) - 13:43, 18 September 2016
  • Here is a list of things that need testing for the KDE SIG:
    1 KB (200 words) - 08:27, 21 June 2021
  • <noinclude>{{CompactHeader|fonts-sig}}</noinclude>
    1 KB (202 words) - 11:35, 22 October 2015
  • ...owners 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:raphgro| Raphael Groner]] ([[LXQt_SIG|LXQt SIG]])
    6 KB (893 words) - 11:40, 25 May 2016
  • Fedora-Spezialinteressensgruppen (Special Interest Groups - SIG's) sind andere Leistungen innerhalb des Fedoraprojekts, die nicht der Proje
    3 KB (433 words) - 20:33, 19 September 2016
  • == Creating a SIG == ...tle red tape. If you're interested in forming one, see [[Creating a Fedora SIG]].
    138 members (10 subcategories, 0 files) - 19:08, 13 March 2024
  • ...ement:''' KDE as a first-class citizen! I plan to represent [[SIGs/KDE|KDE SIG]] in FESCo and to ensure KDE enjoys a first-class role in Fedora. ...'Past work summary:''' Fedora contributor and KDE SIG member since the KDE SIG's inception in 2007, comaintainer of the core KDE packages in Fedora, maint
    8 KB (1,229 words) - 20:34, 19 September 2016
  • == Individual language SIG responsibilities == ...to provide the following for at least Fedora, and potentially for EPEL (if SIG members are interested in that):
    12 KB (1,791 words) - 00:53, 18 September 2015
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    5 KB (731 words) - 08:46, 8 August 2017
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    5 KB (723 words) - 12:10, 27 February 2017
  • ...-cloud/2010-02-04/fedora-cloud.2010-02-04-20.02.html minutes] of the Cloud SIG meeting of 2/4/2010. ...currently supported AMIs are available [[Cloud_SIG/EC2_Images|on the Cloud SIG EC2 page]].
    3 KB (517 words) - 21:42, 17 September 2016
  • [[ More_Go_packaging|current practices ]] from the Go SIG. As a result of new ...macros developed by [[User:nim| Nicolas Mailhot]], some members of the Go SIG wishes to
    6 KB (940 words) - 17:25, 9 July 2019
  • | name = Cloud SIG Fedora Test Day
    1 KB (214 words) - 21:20, 26 June 2015
  • * [http://meetbot.fedoraproject.org/fedora-meeting/2010-03-30/kde-sig.2010-03-30-13.59.html Meeting minutes] * [http://meetbot.fedoraproject.org/fedora-meeting/2010-03-30/kde-sig.2010-03-30-13.59.log.html Full log]
    2 KB (203 words) - 15:25, 18 September 2016
  • ...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.
    7 KB (1,131 words) - 13:06, 8 August 2018
  • | name = Cloud SIG BoxGrinder Build Fedora Test Day ...from executing the test cases. You can always [[Test Day:2011-04-28 Cloud SIG BoxGrinder Build Meta Appliance|download stable meta appliance]] based on F
    11 KB (1,643 words) - 23:35, 17 June 2015
  • |style="border-width: 0px;"|{{projectline|SIGs/Ruby|Ruby SIG|Ruby Special Interest Group|Application-x-ruby.png|}} Un SIG (Grupos de interés especial,por las iniciales en inglés de Fedora Special
    7 KB (1,051 words) - 16:58, 22 December 2018
  • {{CompactHeader|fonts-sig}}
    2 KB (152 words) - 01:21, 24 June 2015
  • [[:Category:Fonts_SIG|Fonts SIG]] * recruit new SIG members,
    17 KB (2,048 words) - 15:43, 16 September 2016
  • * Increased number of subscribers to Python SIG mailing list # Utilize the Python SIG list?
    4 KB (563 words) - 14:08, 7 February 2024
  • ...t of seven members -- the initial one was filled with the first seven EPEL SIG members who were also those who invested most of the time and work for the ...troversial topics require extra care. To make sure all steering committee, SIG, and community members have time to provide their voice on a topic, schedul
    5 KB (840 words) - 20:29, 6 September 2023
  • ...owners 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. -->
    5 KB (821 words) - 20:25, 28 February 2024
  • [[Category:SciTech SIG|Wishlist]]
    2 KB (324 words) - 11:18, 26 December 2015
  • * FESCo would like the Spins SIG to work on a proposal to make their guidelines(1) meet the QA Release Crite
    1 KB (197 words) - 08:02, 18 September 2016
  • [[File:Fedora-sound-SIG-logo.png]] == About the SIG ==
    7 KB (1,061 words) - 21:45, 31 December 2018
  • <!-- All fields on this form are required to be accepted by the Spins SIG [[SIGs/KDE|KDE SIG]]
    6 KB (976 words) - 22:14, 17 September 2016
  • ...everal years, it was determined that EPEL could function just as well as a SIG where folks just got things done and reached consensus, so EPEL moved to th
    1 KB (246 words) - 19:56, 6 January 2022
  • ...ed to the "audio creation" applications provided by the [[Audio Creation]] SIG, but also includes software like Solfege and LilyPond.
    2 KB (252 words) - 21:37, 17 September 2016
  • * Responsible WG: ARM SIG * Proposal owners: The ARM SIG will make the kickstart changes needed to add the desktop images to the com
    3 KB (508 words) - 16:58, 23 July 2019
  • = Fedora Science and Technology SIG = The purpose of the Fedora Science and Technology SIG is to improve the number and quality of packages available for scientific a
    10 members (1 subcategory, 0 files) - 16:17, 15 April 2023
  • === Páginas focadas ao Projeto e SIG para contribuidores === ...uns conteúdos podem ser focados no usuário final, mas pertencem ao projeto/SIG para referência.
    6 KB (996 words) - 15:13, 30 November 2021
  • ...IGs_KDE_Meetings_2008(2d)04(2d)08_fedora-kde-sig-2008-04-08.txt|fedora-kde-sig-2008-04-08.txt]]
    4 KB (547 words) - 15:24, 18 September 2016
  • ** [https://pagure.io/i18n/issue/37 #37: Should we need i18n-sig fas group?]
    2 KB (337 words) - 05:57, 4 October 2016
  • ...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.
    7 KB (1,068 words) - 12:01, 19 August 2020
  • * [[:Category:Fonts_SIG| Fonts SIG]] {{CompactHeader|fonts-sig}}
    6 KB (424 words) - 14:09, 30 April 2021
  • ...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.
    7 KB (1,178 words) - 22:46, 4 June 2015
  • [[:Category:Fonts_SIG|Tipos de Letra SIG]] * Recruit new SIG members,
    16 KB (2,204 words) - 01:40, 20 August 2019
  • = Fedora Static Analysis Special Interest Group (SIG) = (Note that this SIG is merely tentative for now)
    6 KB (861 words) - 21:51, 16 January 2017
  • ** [https://pagure.io/i18n/issue/37 #37: Should we need i18n-sig fas group?]
    2 KB (338 words) - 05:57, 4 October 2016
  • ...ne.org/gmane.linux.redhat.fedora.devel/64115 Announcing the Audio Creation SIG / CCRMA merger effort.] Hans announced the plan to merge as many of planetC
    2 KB (251 words) - 21:31, 17 September 2016
  • ...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.
    9 KB (1,436 words) - 12:37, 1 February 2016
  • ** [https://pagure.io/i18n/issue/37 #37: Should we need i18n-sig fas group?]
    2 KB (338 words) - 05:57, 4 October 2016
  • ...ting (IRC): https://meetbot.fedoraproject.org/packit/2021-04-22/source-git-sig.2021-04-22-13.01.html * 2nd meeting (gmeet): https://pagure.io/fedora-source-git/sig/blob/main/f/meeting-minutes/2020-05-05.md
    4 KB (601 words) - 09:04, 23 May 2023
  • The Fedora Mini SIG is a group of Fedora contributors that are interested in Fedora on small de The Fedora Mini SIG is a group of Fedora contributors that are interested in Fedora on small de
    4 KB (613 words) - 19:46, 8 August 2018
  • = Spin SIG meeting information = [http://meetbot.fedoraproject.org/sresults/?group_id=spins-sig&type=team Meetbot logs]
    2 KB (271 words) - 23:15, 29 July 2015
  • ...owners 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. -->
    6 KB (866 words) - 16:29, 19 April 2021
  • ...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.
    11 KB (1,790 words) - 16:22, 20 January 2016
  • ...top ([[Changes/WaylandByDefaultForPlasma|since Fedora Linux 34]]), and the SIG is confident in the quality and development around the Plasma Wayland exper ...e KDE Plasma stack and continue our feature-forward nature. The Fedora KDE SIG will maintain a single code stream for all supported distribution targets (
    12 KB (1,804 words) - 20:14, 28 February 2024
  • ...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.
    8 KB (1,306 words) - 20:55, 18 July 2018
  • '''We are looking for people to [[#Getting Involved|join the SIG]].''' ...ing Fedora on portable devices such as phones and tablets. The revitalised SIG relaunched when open phone and tablet devices started to become available s
    8 KB (1,323 words) - 12:30, 1 May 2024
  • ...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.
    10 KB (1,578 words) - 04:58, 2 December 2016
  • {{CompactHeader|fonts-sig}}
    2 KB (296 words) - 06:50, 18 September 2018
  • {{CompactHeader|fonts-sig}} [[Category:Fonts SIG|Lists]]
    5 KB (748 words) - 22:15, 21 December 2016
  • ...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.
    10 KB (1,602 words) - 14:49, 2 March 2018
  • Um SIG para pessoas interessadas em melhorar o estado do Java no Fedora. Isso incl Se você deseja chamar a atenção dos membros desta SIG, por favor abra um relatório de bug bloqueando-no [https://bugzilla.redhat
    8 KB (1,121 words) - 23:11, 22 February 2018
  • ...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.
    9 KB (1,385 words) - 14:48, 25 July 2017
  • sudo dnf copr enable @virtmaint-sig/virt-preview * Copr repo page: https://copr.fedorainfracloud.org/coprs/g/virtmaint-sig/virt-preview/
    2 KB (257 words) - 20:12, 14 June 2022
  • ...lf-introduction to the [mailto:python-devel@lists.fedoraproject.org Python SIG mailing list] explaining a bit about yourself. Are you new to contributing ...to this, tell us what [[SIGs/Python#Areas_of_contribution|areas of Python SIG]] you are most interested in contributing to and how WE can help YOU get st
    5 KB (729 words) - 11:15, 20 February 2024
  • ...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.
    10 KB (1,603 words) - 09:54, 5 December 2018
  • ...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.
    9 KB (1,415 words) - 11:18, 30 April 2016
  • ...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.
    9 KB (1,409 words) - 19:31, 15 June 2020
  • * [[OpenStack|Cloud SIG's OpenStack wiki]]
    4 KB (611 words) - 16:00, 27 May 2016
  • * [[:Category:Packaging_SIGs| 我愛打包 SIG]] - 處理散布版中特定領域的打包者非正式群組
    0 members (0 subcategories, 0 files) - 06:43, 29 July 2015
  • ...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.
    10 KB (1,617 words) - 09:00, 27 November 2019
  • Please note that the [[IRC_support_sig|IRC Support SIG]] does not manage all #fedora-* channels. We only manage #fedora, #fedora-s ...ps please feel free to file a ticket on our [https://pagure.io/irc-support-sig issue tracker]. Tickets are reviewed weekly.
    2 KB (259 words) - 22:52, 27 May 2021
  • ...Mono SIG [http://davidnielsen.wordpress.com/2009/02/23/welcome-to-the-mono-sig-paul-lange/ 1], however still maintaining fonts.
    4 KB (649 words) - 15:34, 18 September 2016
  • <!-- All fields on this form are required to be accepted by the Spins SIG * email: neuro-sig@lists.fedoraproject.org
    8 KB (1,186 words) - 19:30, 26 April 2021
  • ...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.
    9 KB (1,457 words) - 16:02, 26 February 2019
  • ...er:Ankursinha| Ankur Sinha "FranciscoD"]], [[SIGs/NeuroFedora| NeuroFedora SIG]] ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
    9 KB (1,412 words) - 14:47, 3 October 2019
  • ...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.
    8 KB (1,153 words) - 10:43, 17 August 2022
  • <!-- This page is drafted on top of LxQT SIG page. Thanks for their great document! --> ...//apps.fedoraproject.org/koschei/groups/mosquito/deepin-sig koschei deepin-sig group]
    4 KB (552 words) - 00:56, 3 April 2024
  • ...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.
    10 KB (1,625 words) - 19:02, 25 November 2021
  • ...owners 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. -->
    5 KB (674 words) - 18:21, 4 January 2023
  • ...the next major release of Fedora. We caught up with two members of the KDE SIG to talk about the work they're doing to get it ready for release, their own the KDE SIG is putting in a lot of work to change this perception. Do
    10 KB (1,662 words) - 21:04, 19 September 2016
  • ...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 their packages.
    9 KB (1,350 words) - 17:29, 3 January 2017
  • ; sig: true if any of the build's component rpms are signed with a matching key sig fedora-gold :: skip
    7 KB (1,124 words) - 15:51, 7 November 2022
  • {{deprecated|Server SIG and Server WG are [https://docs.fedoraproject.org/en-US/server-working-grou == Fedora Server SIG ==
    7 KB (1,021 words) - 14:34, 5 December 2021
  • ...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.
    11 KB (1,817 words) - 11:45, 1 May 2018
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG * Responsible WG: ARM SIG
    8 KB (1,306 words) - 15:50, 17 February 2020
  • * cwickert offered to report back to kde-sig about recent kdepim meetnig, about 4.6.x viability and release schedule
    2 KB (254 words) - 22:13, 17 September 2016
  • ...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.
    9 KB (1,420 words) - 02:38, 14 November 2017
  • {{CompactHeader|fonts-sig}} {{:Fonts_SIG_signature}} [[Category:Fonts SIG news|FAD, SCALE]]
    4 KB (662 words) - 11:09, 24 March 2019
  • ...een updated for it, or have not been actively maintained. While the **PHP SIG** strives to maintain a complete collection of PHP extensions in Fedora, so
    2 KB (310 words) - 01:31, 20 September 2016
  • [[:Category:Fonts_SIG|Fonts SIG]] * recruit new SIG members,
    23 KB (1,293 words) - 21:56, 21 December 2015
  • ...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.
    8 KB (1,144 words) - 11:18, 10 March 2022
  • [[:Category:Fonts_SIG|Fonts SIG]] * Recrutar novos membros do SIG,
    17 KB (2,453 words) - 18:29, 29 July 2020
  • *Active Contributor from other Fedora SIG
    2 KB (203 words) - 03:55, 11 December 2015
  • ...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.
    11 KB (1,664 words) - 13:18, 5 March 2021
  • ...owners 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 Haskell SIG may need an update to build with ghc-7.10, but the Haskell SIG can provide assistance if needed.
    7 KB (1,043 words) - 17:42, 11 September 2016
  • * [http://meetbot.fedoraproject.org/fedora-meeting/2010-03-16/kde-sig.2010-03-16-13.58.html Meeting minutes] * [http://meetbot.fedoraproject.org/fedora-meeting/2010-03-16/kde-sig.2010-03-16-13.58.log.html Full log]
    2 KB (246 words) - 07:44, 18 September 2016
  • Source String Contextualizing Group is a [https://fedoraproject.org/wiki/SIGs SIG] group of Fedora contributors working to make translators' life easy by pro
    2 KB (250 words) - 21:45, 31 December 2018
  • ...technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> ...e Manjaro already providing LXQt versions of their distributions. The LXQt SIG got several requests for a spin.
    5 KB (694 words) - 17:29, 10 January 2020
  • [[:Category:Fonts_SIG|Font SIG]] * reclutare nuovi membri SIG,
    17 KB (2,358 words) - 13:54, 24 February 2017
  • {{CompactHeader|fonts-sig}} {{:Fonts_SIG_signature}} [[Category:Fonts SIG|Template for describing fonts]] [[Category:International fonts]] [[Category
    5 KB (617 words) - 05:18, 22 August 2016
  • ...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.
    10 KB (1,484 words) - 19:15, 14 July 2021
  • {{CompactHeader|fonts-sig}} {{:Fonts_SIG_signature}} [[Category:Fonts SIG|Template for describing fonts]] [[Category:International fonts]] [[Category
    5 KB (623 words) - 16:41, 7 January 2018
  • ...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.
    10 KB (1,726 words) - 15:14, 4 September 2015
  • ...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.
    11 KB (1,777 words) - 15:54, 12 November 2015
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG * [[SIGs/DeepinDE|DeepinDE SIG page]]
    9 KB (1,401 words) - 02:56, 12 August 2019
  • * bpepple will contact the Server SIG to see if they were interested in taking up the offer from Russ Herrold. ht
    2 KB (274 words) - 08:01, 18 September 2016
  • ...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.
    10 KB (1,539 words) - 16:58, 12 December 2016
  • * {{fplist|spins}} - 流通量の少ない Spins SIG のメーリングリストです。 === プロジェクトと SIG ===
    32 KB (2,153 words) - 12:27, 24 February 2017
  • <!-- 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
    5 KB (791 words) - 04:03, 23 November 2015
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    7 KB (1,078 words) - 09:27, 13 October 2015
  • <!-- 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
    5 KB (915 words) - 20:10, 10 April 2021
  • ...page describes all currently open action items involved with the Usability Sig.
    3 KB (336 words) - 21:46, 19 September 2016
  • <noinclude>{{CompactHeader|fonts-sig}} * CC the fonts SIG bugs [[Fonts_SIG_mailing_lists|mailing list]].
    5 KB (790 words) - 11:07, 9 October 2021
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    6 KB (861 words) - 09:19, 21 March 2017
  • ...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.
    10 KB (1,548 words) - 14:45, 2 March 2018
  • ...owners 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: Python SIG
    7 KB (1,150 words) - 00:26, 1 August 2017
  • ...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.
    11 KB (1,815 words) - 10:37, 10 November 2015
  • * @DATE@ Fedora Haskell SIG <haskell@lists.fedoraproject.org> * @DATE@ Fedora Haskell SIG <haskell@lists.fedoraproject.org>
    13 KB (1,823 words) - 20:06, 21 December 2018
  • ...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.
    11 KB (1,803 words) - 09:42, 25 January 2016
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG * [[SIGs/DeepinDE|DeepinDE SIG page]]
    9 KB (1,458 words) - 01:50, 17 January 2019
  • ...or music and sound. Once you are a contributor to Fedora, you can join the SIG and communicate with the rest of the team in the usual [[Communicate| Fedo
    8 KB (1,055 words) - 16:10, 4 February 2020
  • ...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.
    11 KB (1,766 words) - 07:09, 25 January 2017
  • Want to join the Fedora Red Team SIG? It's easy! Just start showing up. See [[#How to contribute|how to contribu Get in contact with the SIG:
    10 KB (1,515 words) - 14:41, 18 March 2021
  • ...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.
    11 KB (1,766 words) - 20:48, 10 May 2016
  • {{CompactHeader|fonts-sig}}
    3 KB (366 words) - 09:23, 4 June 2019
  • ...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.
    13 KB (1,929 words) - 08:31, 12 December 2016
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG The focus of this SIG is to package and support neuroscience and neuroimaging applications, libra
    14 KB (2,230 words) - 17:35, 26 February 2016
  • * Responsible WG: KDE SIG ...Workstation WG as part of advancing the GNOME platform. It is now the KDE SIG's turn to do the same for the KDE platform. By making this change, we are h
    7 KB (1,028 words) - 20:06, 7 October 2021
  • ...owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages. ** SIG request: [https://pagure.io/fedora-infrastructure/issue/11856 #11856]
    5 KB (754 words) - 16:08, 24 April 2024
  • ...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.
    11 KB (1,791 words) - 08:33, 14 July 2016
  • ...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.
    11 KB (1,795 words) - 15:01, 2 March 2018
  • ...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.
    11 KB (1,809 words) - 08:55, 6 August 2015
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    7 KB (1,029 words) - 14:52, 2 March 2018
  • ...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.
    10 KB (1,377 words) - 10:14, 26 February 2019
  • {{CompactHeader|fonts-sig}} ...ated) fontconfig ruleset, please post it on the [[Fonts_SIG_mailing_lists| SIG list]] for review.}}
    8 KB (1,218 words) - 12:39, 10 October 2018
  • [[:Category:Fonts_SIG|Fonts SIG]] * නව SIG සාමාජිකයින් බදවා ගැනීම
    26 KB (1,613 words) - 15:43, 16 September 2016
  • ...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.
    11 KB (1,738 words) - 14:39, 14 July 2015
  • [[:Category:Fonts_SIG|Fonts SIG]] * Recruit new SIG members,
    18 KB (2,545 words) - 18:05, 4 January 2018
  • ...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.
    11 KB (1,781 words) - 08:48, 4 June 2018
  • ...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.
    11 KB (1,824 words) - 08:12, 12 April 2018
  • ...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.
    11 KB (1,770 words) - 15:06, 23 February 2016
  • ...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.
    11 KB (1,818 words) - 19:47, 5 July 2017
  • ...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.
    13 KB (2,010 words) - 15:05, 5 January 2017
  • ...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.
    12 KB (1,914 words) - 09:14, 23 May 2017
  • ...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.
    11 KB (1,846 words) - 13:54, 15 February 2016
  • ...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.
    11 KB (1,826 words) - 10:45, 30 May 2016
  • ...o que enfatiza la legibilidad del código. '''Fedora Loves Python''' y este SIG es para la gente que quisiera ver esta relación prosperar. Nuestro objetiv
    2 KB (258 words) - 04:46, 31 August 2017
  • ...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.
    12 KB (1,890 words) - 08:55, 12 January 2016
  • ...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.
    11 KB (1,858 words) - 08:15, 12 April 2018
  • ...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.
    11 KB (1,880 words) - 07:28, 30 May 2016
  • {{CompactHeader|fonts-sig}}
    2 KB (250 words) - 10:14, 31 October 2017
  • {{CompactHeader|fonts-sig}}
    2 KB (250 words) - 10:17, 31 October 2017
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG See java SIG plans: https://jvanek.fedorapeople.org/devconf/2018/changesInjavaReleasePro
    14 KB (2,268 words) - 07:34, 18 June 2018
  • ...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.
    11 KB (1,787 words) - 12:16, 15 July 2015
  • * Name: [[Education_SIG| Education SIG]] ...tools, documentation, and getting-started resources, the Fedora Education SIG achieves its goal of lowering the entry barrier to contributing as much as
    6 KB (833 words) - 21:37, 17 September 2016
  • ...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.
    12 KB (1,906 words) - 14:31, 23 August 2017
  • ...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.
    12 KB (1,874 words) - 21:57, 4 July 2017
  • ...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.
    11 KB (1,798 words) - 19:09, 28 September 2016
  • ...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.
    12 KB (1,893 words) - 21:20, 7 September 2018
  • ...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.
    12 KB (1,934 words) - 19:47, 4 March 2018
  • * 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
    5 KB (769 words) - 19:30, 26 June 2015
  • ...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.
    11 KB (1,855 words) - 04:21, 2 September 2015
  • {{CompactHeader|fonts-sig}} * Our SIG [[Font_package_lifecycle| workflow]] is organised around wiki pages that ad
    7 KB (969 words) - 12:42, 13 February 2016
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG See java SIG plans: https://jvanek.fedorapeople.org/devconf/2018/changesInjavaReleasePro
    14 KB (2,266 words) - 09:06, 17 October 2018
  • == Perl SIG == ...tial-cc list for bugzilla. This can be done by adding the user <code>perl-sig</code> to the initial CC list when creating the [[Package_SCM_admin_request
    12 KB (1,835 words) - 11:20, 15 June 2017
  • ...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.
    11 KB (1,837 words) - 15:38, 29 June 2020
  • ...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.
    12 KB (1,859 words) - 14:02, 2 March 2018
  • {{CompactHeader|fonts-sig}}
    2 KB (290 words) - 13:30, 27 June 2020
  • ...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.
    12 KB (1,970 words) - 18:51, 6 July 2017
  • ...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.
    12 KB (1,858 words) - 20:06, 25 March 2019
  • ...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.
    11 KB (1,772 words) - 08:25, 8 August 2017
  • ...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.
    12 KB (1,996 words) - 07:48, 9 April 2018
  • ...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.
    12 KB (1,924 words) - 10:13, 25 January 2016
  • ...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.
    12 KB (1,924 words) - 13:29, 13 August 2015
  • ...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.
    12 KB (1,900 words) - 20:13, 3 July 2015
  • ...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.
    11 KB (1,857 words) - 21:17, 22 April 2016
  • ...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.
    12 KB (1,910 words) - 13:53, 15 February 2016
  • ...owners 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:Remi| Remi Collet]] and [[SIGs/PHP|PHP SIG]]
    8 KB (1,261 words) - 05:27, 25 April 2024
  • {{CompactHeader|fonts-sig}}
    2 KB (263 words) - 10:15, 31 October 2017
  • {{CompactHeader|fonts-sig}}
    2 KB (263 words) - 10:18, 31 October 2017
  • ...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
    9 KB (1,372 words) - 18:09, 11 September 2016
  • ...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.
    11 KB (1,861 words) - 08:25, 12 April 2018
  • {{CompactHeader|fonts-sig}}
    2 KB (277 words) - 06:29, 22 April 2016
  • ...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
    9 KB (1,343 words) - 12:21, 20 April 2018
  • ...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.
    12 KB (1,918 words) - 13:46, 16 February 2016
  • ...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.
    12 KB (1,929 words) - 12:05, 30 April 2016
  • | [[:Category:Fonts SIG|폰트SIG]] * 새로운 SIG 구성원을 모집합니다,
    19 KB (550 words) - 15:39, 8 June 2021
  • ...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.
    12 KB (1,985 words) - 07:37, 5 June 2017
  • ...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.
    10 KB (1,654 words) - 05:38, 17 March 2017
  • ...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.
    12 KB (1,918 words) - 07:36, 29 April 2016
  • [[:Category:Fonts_SIG|Fonts SIG]] * Recruter de nouveaux membres pour l'équipe Fonts SIG
    22 KB (3,247 words) - 17:10, 28 May 2021
  • ...G] to co-ordinate across-variants work. One of the long term goals of this SIG is to work on making those variants the default option in Fedora, thus remo * https://discussion.fedoraproject.org/t/creating-the-fedora-atomic-desktops-sig/90757
    6 KB (895 words) - 18:18, 24 January 2024
  • * [http://fonts.fedoraproject.org/ Fedora Fonts SIG]
    5 KB (571 words) - 06:42, 13 February 2024
  • ...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.
    13 KB (2,114 words) - 09:35, 1 February 2016
  • ** The x86 SIG continues testing the i686 alternative architecture on legacy hardware. The x86 SIG will have to update the release notes for the i686 alternative architecture
    6 KB (804 words) - 07:44, 18 June 2018
  • # These are all go language based software. What role can or should the go-sig have?
    2 KB (298 words) - 22:23, 26 August 2022
  • ...owners 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. -->
    6 KB (871 words) - 20:28, 28 February 2024
  • ...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.
    10 KB (1,604 words) - 07:25, 20 April 2018
  • ...owners 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:omajid| Omair Majid]], [[SIGs/DotNet|DotNet SIG]]
    8 KB (1,350 words) - 15:33, 3 August 2020
  • ...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.
    12 KB (1,943 words) - 16:19, 25 July 2017
  • ...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.
    13 KB (2,057 words) - 21:57, 24 April 2017
  • ...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.
    10 KB (1,580 words) - 19:00, 28 July 2020
  • {{CompactHeader|fonts-sig}}
    2 KB (299 words) - 17:08, 5 March 2018
  • ...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.
    16 KB (2,492 words) - 15:02, 16 March 2020
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    9 KB (1,369 words) - 13:24, 26 February 2016
  • == Perl SIG == ...tial-cc list for bugzilla. This can be done by adding the user <code>perl-sig</code> to the initial CC list when creating the [[Package_SCM_admin_request
    11 KB (1,781 words) - 17:17, 28 April 2016
  • ...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.
    12 KB (1,947 words) - 15:11, 2 March 2018
  • ...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.
    12 KB (1,946 words) - 14:55, 2 March 2018
  • ...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.
    12 KB (1,859 words) - 07:57, 2 September 2016
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    9 KB (1,347 words) - 06:19, 15 February 2019
  • ...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.
    12 KB (1,953 words) - 06:46, 13 June 2016
  • ...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.
    12 KB (1,884 words) - 22:56, 23 June 2015
  • ...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
    10 KB (1,453 words) - 10:35, 9 July 2018
  • ...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.
    14 KB (2,295 words) - 19:48, 4 March 2018
  • ...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.
    12 KB (1,953 words) - 00:44, 22 August 2020
  • ...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.
    12 KB (1,989 words) - 18:18, 26 November 2018
  • * [[:Category:Fonts_SIG| Fonts SIG]] {{CompactHeader|fonts-sig}}
    6 KB (847 words) - 13:21, 21 December 2022
  • The [[SIGs/Robotics|Fedora Robotics SIG]] has packaged a lot of robotics related software and consists of upstream ...d by the Fawkes upstream project, and will involve members of the robotics SIG from this project and from the Player/Stage project. Finally the documentat
    8 KB (1,375 words) - 18:55, 27 July 2022
  • ...ng the positions listed below should contact [[Fedora_Join_SIG|Fedora Join SIG]].
    2 KB (387 words) - 06:55, 3 July 2018
  • ...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.
    13 KB (2,020 words) - 13:09, 17 July 2017
  • ...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.
    12 KB (1,992 words) - 17:12, 3 July 2019
  • ...ojects in the past, Marie, Sumantro, Vipul, Akashdeep.. (Existing Mentors, SIG POCs etc) *** Python SIG??
    8 KB (1,066 words) - 13:55, 19 December 2023
  • ...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.
    11 KB (1,743 words) - 14:55, 17 December 2015
  • ...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.
    12 KB (1,950 words) - 13:27, 26 April 2016
  • ...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.
    12 KB (1,841 words) - 16:23, 9 March 2018
  • ...owners 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. -->
    6 KB (913 words) - 20:42, 28 February 2024
  • ...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.
    11 KB (1,797 words) - 10:46, 24 October 2017
  • ...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.
    12 KB (1,982 words) - 15:03, 2 March 2018
  • [[Category:SciTech SIG]]
    2 KB (359 words) - 03:52, 7 January 2016
  • {{CompactHeader|fonts-sig}}
    2 KB (304 words) - 06:24, 22 April 2016
  • ...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.
    13 KB (2,028 words) - 12:26, 25 July 2016
  • [[Category:Cloud SIG]]
    2 KB (340 words) - 14:36, 26 May 2022
  • ...owners 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:Remi| Remi Collet]] and [[SIGs/PHP|PHP SIG]]
    9 KB (1,412 words) - 11:08, 20 July 2023
  • === Fedora SIG EPEL Report Week 11/2008 === === Fedora SIG KDE Meeting 2008-03-18 ===
    14 KB (2,029 words) - 21:36, 20 September 2016
  • <!-- 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
    6 KB (1,034 words) - 22:03, 19 March 2018
  • ...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.
    12 KB (1,951 words) - 14:35, 21 July 2020
  • ...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.
    12 KB (2,049 words) - 09:05, 21 February 2017
  • ...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.
    12 KB (1,937 words) - 17:35, 6 January 2022
  • ...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.
    12 KB (1,944 words) - 17:21, 7 January 2021
  • ...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.
    12 KB (1,798 words) - 15:19, 22 November 2016
  • ...nouncement", "Rawhide 20080328 Snapshot", "FUDCon Lodging", "Fedora Python SIG" and "Fedora Updates System" === Fedora Python SIG ===
    16 KB (2,252 words) - 21:35, 20 September 2016
  • ...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.
    13 KB (2,059 words) - 15:23, 5 July 2018
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG * Responsible WG: ARM SIG
    14 KB (2,199 words) - 15:09, 2 March 2018
  • ...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.
    12 KB (1,976 words) - 08:16, 13 March 2018
  • ...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. -->
    11 KB (1,773 words) - 07:45, 9 April 2018
  • ...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.
    12 KB (1,954 words) - 17:33, 6 January 2022
  • ...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.
    13 KB (2,110 words) - 15:57, 25 December 2015
  • ...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.
    13 KB (2,047 words) - 12:30, 16 March 2018
  • ...owners 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:Remi| Remi Collet]] and [[SIGs/PHP|PHP SIG]]
    9 KB (1,465 words) - 09:02, 22 November 2023
  • ...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.
    14 KB (2,156 words) - 17:20, 11 September 2016
  • ...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.
    13 KB (2,104 words) - 05:42, 26 October 2020
  • ...ate forum [https://pagure.io/irc-support-sig https://pagure.io/irc-support-sig] is a perfect place for complaints or general feedback. ...g] to appeal your case. Tickets are reviewed on a weekly basis at each IRC Sig meeting. Meetings are currently held on Thursdays at 18:00PM (UTC) in the [
    2 KB (383 words) - 10:09, 2 July 2021
  • ...ithin SIG with limited impact outside SIG functional area, accepted by the SIG
    7 KB (1,002 words) - 07:21, 23 April 2016
  • ...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.
    13 KB (2,040 words) - 05:19, 23 March 2018
  • ...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.
    12 KB (1,979 words) - 13:58, 31 August 2016
  • ...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.
    13 KB (2,066 words) - 14:43, 2 March 2018
  • ...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.
    12 KB (1,980 words) - 11:16, 9 January 2018
  • ...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
    10 KB (1,516 words) - 07:53, 6 March 2020
  • ...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.
    13 KB (2,095 words) - 12:39, 26 June 2018
  • ...owners 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:ignatenkobrain|Igor Gnatenko]] (on behalf of [[SIGs/Rust|Rust SIG]])
    11 KB (1,681 words) - 15:03, 2 March 2018
  • ...ate the special interest group for [[Workstation/AtomicWorkstation]]. This SIG has regular bi-weekly meetings to keep the work on the project moving forwa
    3 KB (342 words) - 19:46, 30 July 2018
  • ...re cases, exceptions will need to be made. Bring your case before the EPEL SIG at one of the weekly meetings and/or the {{fplist|epel-devel}} mailing list
    2 KB (398 words) - 20:02, 6 January 2022
  • ...Ambassadors, Mentor de novos embaixadores LATAM, Packager, Fedora Big Data Sig, etc.. || ...eca]] || Belo Horizonte || MG || Sim || Amateurs Radio SIG, Freemedia, L10N, FedoraQA ||
    15 KB (1,138 words) - 17:51, 15 February 2017
  • ...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.
    15 KB (2,496 words) - 17:29, 17 January 2020
  • * [[SIGs/KDE| KDE SIG]]
    2 KB (320 words) - 21:51, 17 September 2016
  • ...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.
    11 KB (1,797 words) - 16:01, 21 July 2022
  • === SIG === ...hi]]|| ||A presentation regarding the [[SIGs/FedoraMedical| Fedora Medical SIG]]||
    12 KB (1,592 words) - 21:18, 19 September 2016
  • ...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.
    13 KB (2,019 words) - 17:08, 17 January 2020
  • ...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.
    13 KB (2,041 words) - 12:49, 10 August 2018
  • ...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.
    13 KB (2,089 words) - 15:22, 25 July 2017
  • ...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.
    13 KB (2,068 words) - 14:36, 2 March 2018
  • ...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.
    13 KB (2,164 words) - 11:49, 6 February 2017
  • ...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.
    11 KB (1,837 words) - 14:37, 15 December 2021
  • ...owners 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. -->
    6 KB (994 words) - 19:46, 4 March 2018
  • ...owners 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. -->
    6 KB (877 words) - 20:43, 30 September 2017
  • ...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.
    13 KB (2,148 words) - 16:57, 26 April 2016
  • ...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.
    13 KB (2,116 words) - 13:25, 24 November 2016
  • ...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.
    14 KB (2,185 words) - 07:38, 7 September 2015
  • ...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.
    13 KB (2,103 words) - 07:10, 8 March 2018
  • * Fedora Amateur Radio SIG (fedora-hams)[https://fedoraproject.org/wiki/AmateurRadio?rd=SIGs/AmateurRa
    3 KB (358 words) - 03:57, 9 January 2024
  • ...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.
    13 KB (2,132 words) - 16:20, 27 October 2017
  • ...owners 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. -->
    6 KB (1,016 words) - 20:02, 22 April 2016
View (previous 500 | ) (20 | 50 | 100 | 250 | 500)