Editing BioBoard/Time line

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
  -
=Week 1 (March 21st - March 27th)=
 
* team introduction
* explain Noisebridge hackerspace's philosophy, and provide a top level summary of your first week (Rikke, with collective revision and approval)
* write project plan, incl. time line and initial task list (Rikke)
* delegate/take on as many tasks as possible (everyone)
* start identifying sources for materials (Mike?, Charlie?, Marc?, Sean?)
* source ethernet shield for Arduino + schematics from DZL (Rikke)
* prepare schematics for living biomass probe (Rikke)
* deadline for first blog update is March 25th! (Rikke)
 
=Week 2 (March 28th to April 3rd)=
 
* provide a basic outline of the materials we will be using in our build: in other words, a pretty detailed plan for all hardware aspects of the project (Rikke; as this is already well under preparation, there should be no problems here)
* outline anticipated key challenges (content: everyone)
* prepare schematics for DO probe (Sean)
* source commercial probes - thermocouple, pH meter (Mike?, Charlie?)
* source materials for DIY probes (Mike?)
* prototype Arduino + ethernet shield setup (Marc)
* prototype DO probe (Sean)
* prototype living biomass (LB) sensor (Rikke, someone else?)
* deadline for Hackerspace Challenge Blog Post 2 is April 1st! (Rikke...fooled ya!)
 
=Week 3 (April 4th - April 10th)=
 
* provide status update of build w/ quick summary of obstacles + solutions (Rikke)
* refine DO/LB probes (Sean, Rikke, others?)
* refine graphics, website, user software interaction (Marc)
 
=Week 4 (April 11th to April 17th)=
 
* mandatory update: "Is everything going to plan? Perhaps provide footage of a visit to an educational institution you're working with"
* finish DO/LB probes (Sean, Rikke, everyone?)
* deadline for Hackerspace Challenge Blog Post 3 is April 15th! (Rikke)
 
=Week 5 (April 18th - April 24th)=
 
* provide a review of the challenge to date, incl. key lessons learned (content: everyone, collation: Rikke)
* assemble all components and test (everyone except Rikke, who'll be in Denmark from April 19th to May 5th)
* testing...testing...1...2...3...testing...
 
=Week 6 (April 25th - April 30th)=
 
* showcase our build, why it works and what features make it stand out, a.k.a. show off and shamelessly self-promote our project
* deadline for build is April 30th!!!
 
 
=Disclaimers=
 
* 1) The first two weeks are way more filled out than the last four, since the specific details of much that comes later depends on what happens this week and next (list of materials dependent on exact schematics + availability, task delegation dependent on who wants to do what, etc.), but that will naturally change as the project progresses.
* 2) We're "required to contribute to [our] profile page within the element14 community", but exactly how we do this when there are two projects in play remains unclear, so we'll get back to this after talking to the organizers.
 
=Questions for Mark Sanders/Silverfox=
 
* How do we share the Noisebridge user profile? Shared credentials --> access for all + tagged blog posts (e.g. @[BioBoard]Rikke: Today, we've started work on the bla bla bla...)?
* How do we distribute money between the two projects? Split budget + self-checking?
* Materials from other sources than element14?
Please note that all contributions to Noisebridge are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see Noisebridge:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)