1,885
edits
Changes
no edit summary
= Week 4 - Project Selection =
=== Project Selection ===
*** See what work has already been done related to that project. Check the Seneca wiki for work by previous SBR600 semesters, the upstream project's wiki and mailing list archives for information about the current state of the project, and the web for related information (similar projects being done by other groups).
*** Join the mailing lists and IRC channels of the upstream community.
** Update the [[Winter 2012 2013 SBR600 Participants]] table with your project information, according to the instructions at the top of that page.
* On Thursday we'll sort out project conflicts.
* [[User:Chris Tyler|Your professor]] will approve your project selection via the [[Winter 2012 2013 SBR600 Participants|participants page]].* Link your project title on the [[Winter 2012 2013 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.
This week, finalize your project plans and get started on your project:
* The project page must be filled in, including your 0.1, 0.2, and 0.3 targets. Ensure that you have a link from the ''Projects'' column of the [[Fall 2012 DPI908/2013 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.
** 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 Basic Technical Work Complete - 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 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 to the appropriate repositories (or released in an appropriate manner).
* You must have a strategy in place for reaching your targets.
* 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 Proof of conceptConcept** 0.2 Release - initial functionalityBasic Technical Work Complete** 0.3 Release - tested and usableCompleted Working State
* 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.
=== To Do ===
* Prepare your project page and .* Prepare your project plan presentationfor Week 6.Book your time slot on the [[Fall 2013 SBR600 Presentation Schedule| the presentation schedule page]]
<!-- ---------------------------------------------------------------------------------------------- Week 5 ------------ -->
{{Admon/important|Thanksgiving|Monday, October 14 is the Thanksgiving Holiday.}}
{{Admon/caution|No Class October 15 & 17|Our class will not be meeting this week. Your professor will be at a Polytechnics Canada meeting in Calgary but will be communicating by e-mail (and possibly IRC). Please use this time to work on your 0.1 Project Milestones. You can meet with your professor on Monday or Friday, by appointment.}}
<!-- ---------------------------------------------------------------------------------------------- Study Week ------------ -->
= Study Week and FSOSS =
* Your professor will be around campus most of the week, working on FSOSS. He is also available to meet regarding projects from Monday to Wednesday, by appointment.
* [http://fsoss.ca FSOSS 2012] is Thursday/Friday October 24/25.
<!-- ---------------------------------------------------------------------------------------------- Week 8 ------------ -->
= Week 8 - Project Work =
{{Admon/caution|No Class October 19 & 31|Our class will not be meeting this week. Your professor will be at Linaro Connect / ARM TechCon in California but will be communicating by e-mail (and possibly IRC). Please use this time to work on your 0.1 Project Milestones.}}
<!-- ---------------------------------------------------------------------------------------------- Week 9 ------------ -->
= Week 9 - Project Work =
{{Admon/caution|No Class November 5 & 7|Our class will not be meeting this week. Your professor will be hiding in a secret location with no Internet access whatsoever.}}
<!-- ---------------------------------------------------------------------------------------------- Week 10 ------------ -->
= Week 10 - Presentations =
* Please book your time slot on [[Fall 2013 SBR600 Presentation Schedule| the presentation schedule page]] on a first-come first-serve basis.
* Each presentation should take no more than 10 minutes.
<!-- ---------------------------------------------------------------------------------------------- Week 11 ------------ -->
= Week 11 - Practical Quiz & Project Work =
=== Problem Solving ===
* We will brainstorm on solutions to project problems.
<!-- ---------------------------------------------------------------------------------------------- Week 12 ------------ -->
= Week 12 - Presentations =
* Please book your time slot on [[Fall 2013 SBR600 Presentation Schedule| the presentation schedule page]] on a first-come first-serve basis.
* Each presentation should take no more than 10 minutes.
<!-- ---------------------------------------------------------------------------------------------- Week 13 ------------ -->
= Week 13 - Wrap-up =
