From Fedora Project Wiki
Page title matches
- 32 bytes (2 words) - 18:39, 12 July 2017
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 16:58, 15 February 2018
- 32 bytes (2 words) - 18:39, 12 July 2017
- Category for Release Engineering SOPs23 members (1 subcategory, 0 files) - 18:18, 14 February 2009
- {{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
- = 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
- 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
- ...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
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
- .../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
- ...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
- {{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
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 16:58, 15 February 2018
- Category for Release Engineering SOPs23 members (1 subcategory, 0 files) - 18:18, 14 February 2009
- #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
- #REDIRECT [[Community Platform Engineering/Flock]]50 bytes (5 words) - 16:58, 15 February 2018
- # 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