From Fedora Project Wiki

  • Change Proposals in this category have been reviewed by the Wrangler and are ready for an ac
    1 member (0 subcategories, 0 files) - 13:18, 30 May 2013
  • This is a working space to hold proposals in progress. Please follow the example format of existing and completed obj
    498 bytes (62 words) - 14:04, 7 February 2024
  • Change Proposals pages in this category have been announced on devel-announce mailing list f
    4 members (0 subcategories, 0 files) - 16:25, 9 July 2018
  • ...lization team has done excellent work for Fedora 22 by working on 5 change proposals. There are also minor changes. Its time to convert these points from IMPACT
    485 bytes (68 words) - 04:05, 22 May 2015
  • == Accepted proposals == and unfunded proposals that we've accepted. Because of the way our funding works this time, we ar
    2 KB (245 words) - 04:26, 18 March 2011
  • The following proposals were considered:
    779 bytes (90 words) - 03:24, 21 December 2008
  • == Arising Proposals ==
    4 KB (629 words) - 22:34, 2 June 2008
  • == Talk Proposals ==
    3 KB (387 words) - 01:16, 7 August 2010
  • === Bugzilla Semantics - Discuss the proposals and feedback. ===
    2 KB (305 words) - 07:54, 18 September 2016
  • ...lease, and documenting an evolving release criteria as guidance for future proposals. The Release Selection criteria may be more restrictive than what is allow ...aseProcessAmendments| the proposal for optional Release Selection process proposals]] which require approval.
    6 KB (909 words) - 16:36, 24 May 2008
  • Here you can add your proposals for Interviews.
    679 bytes (113 words) - 21:13, 25 March 2009
  • * FESCo approved the following proposals to the Feature process:
    929 bytes (115 words) - 20:27, 7 July 2008
  • == Venue Proposals == We are going to use barcamp format but you are encouraged to list your proposals here to organize the agenda.
    3 KB (457 words) - 09:03, 13 August 2010
  • [a] accept and flag proposals Proposals from students:
    4 KB (579 words) - 09:24, 23 June 2010
  • ** Because rpm macros were initially derived from cmake variables the proposals should be compared with the variables defined in KDE4Internal.cmake. ** Proposals: "Best Practices", "Packaging Drafts"
    2 KB (308 words) - 15:46, 5 August 2009
  • ...mer Coding 2010]] this is the process to follow when commenting on student proposals. # For any discussions about proposals that happens on the [http://lists.fedoraproject.org/mailman/listinfo/summer
    2 KB (360 words) - 15:46, 9 April 2010
  • == How is this different from previous proposals? ==
    3 KB (462 words) - 10:21, 2 February 2015
  • Students may submit proposals to Google during the application period at the Summer of Code website. Stu
    1,012 bytes (137 words) - 16:37, 24 May 2008
  • # Review process proposals
    692 bytes (91 words) - 00:14, 28 July 2009
  • ...eir projects. The following projects were selected from among the awesome proposals:
    883 bytes (89 words) - 01:42, 15 January 2009
View ( | ) (20 | 50 | 100 | 250 | 500)