Search results

Session Proposals are due March 21, 7PM

Please report all bugs, issues or enhancement proposals to the '''[https://github.com/coreos/fedora-coreos-tracker/issues Fedora Co

The following proposals were considered:

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...t to accept proposed alternatives. This section is optional for all change proposals, but is strongly suggested. Incorporating feedback here as it is raised giv

This proposals is a new implementation of "explictly enable third-party repositories". The ...t to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised give

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

== Fedora 20 Accepted System Wide Changes Proposals == == Fedora 20 Accepted Self Contained Changes Proposals ==

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

# New proposals

For change proposals to qualify as self-contained, owners of all affected packages need to be in ...t to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised give

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

...olor: #407a40">any other thoughts about this?&nbsp;&nbsp;I'll send up some proposals.</td><td class="time">13:56</td></tr> ...88888"> wwoods</th><td class="text" style="color: #488888">yeah, make some proposals so we can get other people to find places we might be forgetting about</td>

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> For change proposals to qualify as self-contained, owners of all affected packages need to be in

...r [http://dev.ryzom.com/projects/nel/wiki/GSoC2009WritingProposals writing proposals]. We encourage Summer Coding code to include tests. [[Category:Summer Coding 2010 proposals]]

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> For change proposals to quality as self-contained, owners of all affected packages need to be in

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...t to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised give

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->