Difference between revisions of "DPS909 and OSD600 Fall 2010 0.1 Release"
Knovichikhi (talk | contribs) (→Submissions) |
(→Submissions) |
||
| Line 61: | Line 61: | ||
* '''0.1 Blog Post''': ''[http://manoutoftime.wordpress.com/2010/10/22/release-0-1 0.1 Release]'' | * '''0.1 Blog Post''': ''[http://manoutoftime.wordpress.com/2010/10/22/release-0-1 0.1 Release]'' | ||
* '''Source Code''': ''[http://github.com/manoutoftime/cssChecker Github Repo]'' | * '''Source Code''': ''[http://github.com/manoutoftime/cssChecker Github Repo]'' | ||
| + | |||
| + | |||
| + | * '''Name:''' ''Pete Leaning'' | ||
| + | * '''Project:''' ''Music.js'' | ||
| + | * '''Project URL:''' ''[[http://zenit.senecac.on.ca/wiki/index.php/User:Peleaning/project/ music]]'' | ||
| + | * '''0.1 Blog Post''': ''[http://blockrockinpete.blogspot.com/2010/10/jsmusic-01-release.html 0.1 Release]'' | ||
| + | * '''Source Code''': ''[http://github.com/peleaning/OSD600-project/blob/master/music.js Github repo]'' | ||
Revision as of 21:10, 22 October 2010
Introduction
Your 0.1 release is the first point at which you have a working release of your project. It often represents as much research as it does coding, but always includes a working first-version. Through the coming weeks and months, you will iterate on your 0.1 code and refine it, fix bugs, add new features, etc. The 0.2, 0.3, ... releases will see this first step grow into something more polished and full-featured.
Submission Instructions
In order to submit your release, you need to complete a number of steps:
- Release your code, either as a patch or commit on an existing project's repo, or start a new one
- Create and/or update a wiki page with technical details about your release. This will be your project's homepage, and should have links and info relevant to anyone wishing to use it or contribute
- Write a blog post announcing the release of your project's first milestone. If your code does something that can be demoed, make sure you include a live demo, screenshots, and perhaps a video on youtube if it is hard to setup and run. You should also include info about what is coming in 0.2.
After you have done the above steps, please add an entry below with relevant links. Here is a template you can use:
- Name: <your name>
- Project: <project name>
- Project URL: <project url or wiki page>
- 0.1 Blog Post: <link to your 0.1 release blog post>
- Source Code: <link to a git repo, bug with patch, etc.>
Submissions
- Name: Andrew Condinho
- Project: C3DL Build System
- Project URL: C3DL_Build_Bot
- 0.1 Blog Post: 0.1 Release
- Source Code: Github repo
- Name: Kevin Lasconia
- Project: BBB
- Project URL: BBB
- 0.1 Blog Post: 0.1 Release
- Source Code: Github repo
- Name: Christopher DeCairos
- Project: VideoSequencer.js
- Project URL: VideoSequencer
- 0.1 Blog Post: 0.1 Release
- Source Code: Github Repo
- Name: Kenneth Pangilinan
- Project: Candy.js
- Project URL: Candy-js
- 0.1 Blog Post: 0.1 Release
- Source Code: Github Repo
- Name: Brian Law
- Project: HTML5/Video Comic Book
- Project URL: Comicbook-js
- 0.1 Blog Post: 0.1 Release
- Source Code: Github Repo
- Name: Konstantin Novichikhin
- Project: cssChecker
- Project URL: CSS_Checker_JetPack_Extension
- 0.1 Blog Post: 0.1 Release
- Source Code: Github Repo
- Name: Pete Leaning
- Project: Music.js
- Project URL: [music]
- 0.1 Blog Post: 0.1 Release
- Source Code: Github repo
