From Fedora Project Wiki
Page title matches
- 32 bytes (2 words) - 18:39, 12 July 2017
- Category for Release Engineering SOPs23 members (1 subcategory, 0 files) - 18:18, 14 February 2009
- 32 bytes (2 words) - 18:39, 12 July 2017
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 16:58, 15 February 2018
- = Fedora Engineering Services = ...t volunteers are generally unable or unwilling to do. That's where Fedora Engineering Services(FES) fits in. Team members have promised a certain number of hour3 KB (426 words) - 15:51, 13 August 2010
- 30 bytes (5 words) - 19:15, 10 August 2010
- #REDIRECT [[Community Platform Engineering/Flock]]50 bytes (5 words) - 16:58, 15 February 2018
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source This page documents the Standard Operating Procedures for Fedora Release Engineering.33 members (0 subcategories, 0 files) - 17:48, 3 November 2015
- Community Platform Engineering is a team within Red Hat that has the following mission: The Community Platform Engineering Team are responsible for the infrastructure and services that support artif3 KB (439 words) - 14:43, 14 July 2021
- ...good communication skills. Below is the process for selecting the Council Engineering representative. ...ESCo members. It is recommended that they should be members of one of the engineering focused groups in FAS.3 KB (486 words) - 12:09, 29 September 2018
- 395 bytes (59 words) - 17:07, 4 January 2019
- #REDIRECT [[Community Platform Engineering/FY15 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- Potential [[Fedora Engineering Services]] members must meet each of the below descriptions:1 KB (192 words) - 15:34, 13 August 2010
- #REDIRECT [[Community Platform Engineering/FY16 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- 594 bytes (98 words) - 20:16, 20 February 2010
- 36 bytes (4 words) - 18:55, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY17 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- 2 KB (274 words) - 16:58, 15 February 2018
- 35 bytes (4 words) - 18:55, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY18 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- 4 KB (710 words) - 14:28, 4 February 2019
- 32 bytes (4 words) - 18:55, 10 June 2009
- 34 bytes (4 words) - 18:55, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY13 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- 30 bytes (4 words) - 18:57, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY14 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2016 (March 2015 - February 2016). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa8 KB (1,118 words) - 16:58, 15 February 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2017 (March 2016 - February 2017). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa7 KB (1,006 words) - 16:58, 15 February 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2018 (March 2017 - February 2018). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa5 KB (709 words) - 14:50, 31 August 2018
- 4 KB (707 words) - 12:06, 29 September 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2015 (March 2014 - February 2015).6 KB (946 words) - 16:58, 15 February 2018
- This document is Fedora Engineering's "working plan" for FY13. In FY13, Red Hat hopes to hire people to fill the following full-time Fedora Engineering positions:10 KB (1,632 words) - 16:58, 15 February 2018
- 38 bytes (5 words) - 18:54, 10 June 2009
- This document is Fedora Engineering's "working plan" for FY14. Fedora Engineering is constantly working on any number of initiatives, but for FY14, our focus12 KB (1,909 words) - 16:58, 15 February 2018
- =Previous Fedora Engineering Steering Committee Members=10 KB (1,294 words) - 12:12, 29 September 2018
- FESCo is the Fedora Engineering Steering Committee. It is a fully community elected body and represents th4 KB (583 words) - 12:05, 29 September 2018
- 951 bytes (139 words) - 12:13, 29 September 2018
- #REDIRECT [[Archive:Release Engineering Release Tickets]]57 bytes (6 words) - 12:54, 8 August 2014
Page text matches
- The [https://docs.pagure.org/releng/ Fedora Release Engineering documentation] is maintained in [https://pagure.io/releng/blob/main/f/docs [[Category: Release Engineering]]205 bytes (28 words) - 04:35, 10 October 2021
- == Fedora Engineering Steering Committee (FESCo) == L'amministrazione tecnica di Fedora è organizzata dal Fedora Engineering Steering Committee (FESCo).580 bytes (62 words) - 12:14, 9 March 2009
- ...ting Procedure] in the new [https://docs.pagure.org/releng/ Fedora Release Engineering Documentation] for the current documentation}} [[Category:Release Engineering SOPs]]317 bytes (43 words) - 21:53, 10 August 2018
- ...cs.pagure.org/releng/sop_sigul_client_setup.html here]| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]337 bytes (50 words) - 20:23, 31 March 2016
- .../docs.pagure.org/releng/sop_pushing_updates.html here]| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]336 bytes (49 words) - 16:29, 4 April 2016
- ...re.org/releng/sop_adding_side_build_targets.html here]| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]346 bytes (51 words) - 20:25, 31 March 2016
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/sop_mass_branching. [[Category:Release Engineering SOPs]]339 bytes (48 words) - 10:22, 14 June 2016
- '''The College of Engineering, University of the Philippines Campus, Diliman, Quezon City, Philippines''' * To create awareness about Open Source, Linux, and Fedora Project among UP Engineering students.560 bytes (65 words) - 09:10, 17 November 2009
- = Menu Category Proposal for Engineering software = | Engineering || Engineering software, e.g. CAD programs ||2 KB (187 words) - 13:47, 24 December 2008
- * B.Sc Computer Engineering * Ms Computer Control Engineering336 bytes (38 words) - 13:03, 5 March 2009
- I am a second year undergraduate student at Delhi College of Engineering, Delhi, India. I am currently pursuing my Bachelor of Engineering in Information Technology at the institute.884 bytes (160 words) - 16:33, 24 May 2008
- I work with Oracle India pvt ltd. for the Application platform engineering group. I have been involved in porting Oracle Applications developed in bas I hold my Bachelors in Engineering from Madras University and currently pursuing MS from Birla Institute of Te689 bytes (103 words) - 16:34, 24 May 2008
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 14:43, 30 January 2019
- Category for Release Engineering SOPs23 members (1 subcategory, 0 files) - 18:18, 14 February 2009
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/Flock]]50 bytes (5 words) - 16:58, 15 February 2018
- #REDIRECT [[:Category:Release Engineering SOPs]]48 bytes (5 words) - 18:52, 10 June 2009
- Members of the [[FES|Fedora Engineering Service]].28 members (0 subcategories, 0 files) - 10:33, 17 February 2010
- #REDIRECT [[Fedora Engineering Steering Committee]]51 bytes (5 words) - 21:45, 1 February 2010
- # Re-confirm that release day is on track with release engineering. # Confirm execution of ''rawhide rebase'' with Red Hat Engineering Operations967 bytes (140 words) - 19:26, 2 June 2009
- #REDIRECT [[Community Platform Engineering/FY18 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY13 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY14 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY15 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY16 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY17 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Previous Fedora Engineering Steering Committee Members]]68 bytes (7 words) - 21:00, 13 September 2017
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source Release Engineering is often asked by maintainers to remove branches in dist-git by maintainers857 bytes (122 words) - 17:56, 3 November 2015
- # Confirm ''End-of-life'' date with Fedora Release Engineering ...licable date for running of ''End of Life'' auto-close ticket with Red Hat Engineering Operations833 bytes (119 words) - 02:01, 24 February 2009
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source Release Engineering is responsible for producing the final .ISO and torrent files for custom sp906 bytes (134 words) - 17:52, 3 November 2015
- [[Category: Release Engineering]]204 bytes (20 words) - 12:29, 21 March 2019
- ...ty of South Florida for a double major in Nuclear Engineering and Computer Engineering. I have a stable job at DataComm Networks Inc. A Network Security Company l917 bytes (139 words) - 21:20, 10 March 2009
- # Draft ticket for Red Hat Engineering Operations requesting the rebase of rawhide bugs # Draft ticket for Red Hat Engineering Operations requesting ''End of Life'' warning added to applicable bugs426 bytes (56 words) - 21:31, 17 September 2016
- ''2th National Meeting of Engineering Students'' ...for Engineering Students. There will be on talk about Fedora and tools for Engineering, like Fedora Electronic Labs.2 KB (287 words) - 03:44, 5 June 2011
- ...a member of Red Hat's localisation team in June 2006, more responsible for Engineering Operations now, however, hope to combine both areas. More via http://ttrink195 bytes (29 words) - 16:26, 24 May 2008
- ''STIX scientific and engineering fonts'' ...preparation of a comprehensive set of fonts that serve the scientific and engineering community in the process from manuscript creation through final publication1 KB (162 words) - 20:34, 15 July 2008
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source This page documents the Standard Operating Procedures for Fedora Release Engineering.33 members (0 subcategories, 0 files) - 17:48, 3 November 2015
- === Tool Improvement / Engineering ===1 KB (153 words) - 19:33, 3 June 2008
- ...must be guaranteed for a 'rotating' spin as well. For example, if Release Engineering decided to make the dvd sized Developer Spin a permanent spin, then we must ...ire to use this option by the deadline, then the option lapses and Release Engineering no longer has to reserve the space in its decision making process.2 KB (346 words) - 16:37, 24 May 2008
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source 2. Update the release engineering ticket with the url:1 KB (155 words) - 17:52, 3 November 2015
- == Release Engineering == ...ora Release Engineering group. See the [[ReleaseEngineering|Fedora Release Engineering page]] for more information.2 KB (269 words) - 19:55, 6 January 2022
- = Fedora Events: August Penguin 2011 - Shenkar College of Art Design and Engineering, Ramat Gan, Israel = * Shenkar College of Art Design and Engineering, Ramat Gan, Israel648 bytes (102 words) - 10:50, 27 June 2011
- #REDIRECT [[Archive:Release Engineering Release Tickets]]57 bytes (6 words) - 12:54, 8 August 2014
- === Release Engineering ===2 KB (179 words) - 09:33, 8 March 2009
- Hi all, I am an Engineer from Bharati Vidyapeeth College of Engineering Pune (India) ...to pursue a higher Masters degree in US with a specialisation in Software Engineering.1 KB (220 words) - 11:58, 9 March 2009
- ...taka, India. I am pursuing Bachelor of Engineering in Computer Science and Engineering. My first linux experience came on Mandrake distro around 2 years back (as1 KB (154 words) - 19:05, 10 July 2008
- ...p://en.wikipedia.org/wiki/Durgapur Durgapur] studying Computer Science and Engineering. I am from a small town named [http://en.wikipedia.org/wiki/Malbazar Malbaz2 KB (263 words) - 07:01, 18 November 2008
- [[Category:Release Engineering SOPs]]236 bytes (37 words) - 17:36, 19 July 2016
- Hi , this is Jaydeep Rathava. I am graduate in mechanical engineering from M.S.University, Gujarat.284 bytes (37 words) - 16:31, 24 May 2008
- # File a ticket with Red Hat Engineering Operations requesting the rebase of rawhide bugs on release day # File a ticket with Red Hat Engineering Operations requesting that qualifying bugs receiving an ''End of Life'' war1 KB (154 words) - 23:41, 11 November 2008