1,885
edits
Changes
no edit summary
Take a look at the [http://rpmfusion.org/ RPMFusion] release RPM for an example.
=== ToDo To Do ===
By '''Wednesday, September 26''':
<!-- ---------------------------------------------------------------------------------------------- Week 5 ------------ -->
= Week 5 =
== Monday (October 1) == === Project Selection === == and Wednesday (October 3) == === Project Selection II === = Week 4 (Jan 31) = == Tuesday/Thursday ==
=== Project Selection ===
* Link your project title on the [[Winter 2012 SBR600 Participants|participants page]] to a page of the same name to create a project page. Copy the contents of the [[Sample Project]] page to your project page and fill in the details.
** Release 0.1: Proof of concept (e.g., a first draft of a package, a basic script, infrastructure set up on a test system) - Note that this must include the release of ''something'', not just research, and must be done in consultation with the community.
** Release 0.2: Initial working state - Whatever you are working on -- package, script, infrastructure configuration -- should be working, although it may not be feature-complete, fully deployed, or fully documented. Feedback from the community should be solicited. If there is a review process required to submit upstream, it should be started.
** Release 0.3: Completed working state - The work is complete and documented. Any upstream review, whether formal or informal, has been completed, feedback has been incorporated into the project, and the work has been committed beento the appropriate repositories (or released in an appropriate manner).
* You must have a strategy in place for reaching your targets.
Be prepared to give a professional, detailed, but very brief (2- to 4-minute) presentation on your project plan next Monday (October 8). Include:* Your approach to the problem.* Contacts and resources you've identified.* Your plans for each release. Note that at each release you will be expected to actually '''release''' something -- an RPM, a script, test results -- as appropriate to your project. Identify what you are intending to release at each stage:** 0.1 Release - proof of concept** 0.2 Release - initial functionality** 0.3 Release - tested and usable* Challenges and potential pitfalls that you have identified, and your approach to mitigating those challenges so that you can complete your project on time regardless of things beyond your control.* Time for a brief Q&A/Feedback session at the end.* During your presentation, you'll == Thursday = To Do === By Monday, October 8:* Prepare your project page and project plan presentation. <!-- ---------------------------------------------------------------------------------------------- Week 6 ------------ -->= Week 6 = == Monday (October 8) ==
=== Project Plan Presentations (0.0) ===
* Project pages are due. Link from the ''Projects'' column of the [[Winter 2012 SBR600 Participants]] table to a page for your project; use the [[Sample Project]] template for your project page, and fill in as much detail as possible.* Be prepared to give a professional, detailed, but very brief (2- to 4-minute) presentation on your project plan. Include:quick presentations** Your approach to the problem.** Contacts and resources you've identified.== Wednesday (October 10) ==** Your plans for each release. Note that at each release you will be expected to actually '''release''' something -- an RPM, a script, test results -- as appropriate to your project. Identify what you are intending to release at each stage:*** 0.1 Release - proof of concept*** 0.2 Release Project start- initial functionality*** 0.3 Release - tested and usable** Challenges and potential pitfalls that you have identified, and your approach to mitigating those challenges so that you can complete your project on time regardless of things beyond your control.** Time for a brief Q&A/Feedback session at the end.up discussions
<!-- ---------------------------------------------------------------------------------------------- Week 6 7 ------------ -->= Week 7 =
= Week 6 = Monday (Feb 14October 15) ==
=== Using GIT ===
* https://github.com/
== Thursday = To Do ===
GIT Lab
* Clone the repository at ssh://sbr600@scotland.proximity.on.ca/~/certs/
* Blog about your experience.
== Tuesday ==
