Help wanted: Difference between revisions
m (template typo) |
mNo edit summary |
||
Line 35: | Line 35: | ||
this seems to be the most popular entry point for newbie coders; the SoC students have a lot of good stuff here but someone needs to be there to welcome them and help them get started - or we need a really good tutorial and walkthrough (note: Kelcy once expressed interest in this. [[User:Mchua|Mchua]]) |
this seems to be the most popular entry point for newbie coders; the SoC students have a lot of good stuff here but someone needs to be there to welcome them and help them get started - or we need a really good tutorial and walkthrough (note: Kelcy once expressed interest in this. [[User:Mchua|Mchua]]) |
||
== Presentations == |
|||
G1G1 is going to release a lot of machines "into the wild," and people want demos. We need a place where people can list the locations of laptops and availability for those who'd like to play with them, so people without an XO can see where to get one ([[Presentations]] is out of date) and someone to make resources for the newbies who are going to be getting the machines so they can quickly contribute to the effort (at the minimum, it should teach them how to do a [[Demo]]). |
Revision as of 09:58, 10 October 2007
![]() |
NOTE: The contents of this page are not set in stone, and are subject to change! This page is a draft in active flux ... |
![]() |
This is a holding spot; need to come up with a better way of coordinating external volunteer resources. Much of this is taken from mcfletch's blog. Mchua 05:45, 10 October 2007 (EDT)
Testing
probably the most vital thing
- Experienced Q/A people needed to write test plans for the following (at least): mesh, Journal, suspend/resume, collaboration.
- Maybe less experienced Q/A people can run those test plans.
Emulation
probably the second most vital thing
- Someone needs to coordinate emulation and check up on what's happening with it. Someone to ride herd on the "quick start" developer's environments, ensuring that they are always available, work with the current versions of the packages, and allow for running all the various hardware
Documentation
API and development documentation, someone to push for regular updates and production of the documentation, someone to review the documentation that exists, collate requests, and flag the various tidbits that show up in discussions and add them to a queue somewhere to get added to the official documentation.
Accessibility
someone to advocate for the various accessibility projects, keep people abreast of developments, coordinate testing for accessibility, feed back problems into the developer communities, arrange for documentation and check that we're actually on track (there may be someone tasked with this, but the accessibility list has been very quiet despite that)
IDE development
needs someone to coordinate and communicate (note: not sure what Mike meant by this. Develop, maybe? Mchua)
Scientific platform
needs someone to make sure that the documentation is there for the various instruments (e.g. blueprints, plans, usage notes, that kind of thing), coordinate effort among the various hardware projects (and the software people), look for "missing elements" in the science-chest and get them started, and generally make sure that the science-chest is ready-to-go. (note: Arjun, perhaps. Mchua)
Games
this seems to be the most popular entry point for newbie coders; the SoC students have a lot of good stuff here but someone needs to be there to welcome them and help them get started - or we need a really good tutorial and walkthrough (note: Kelcy once expressed interest in this. Mchua)
Presentations
G1G1 is going to release a lot of machines "into the wild," and people want demos. We need a place where people can list the locations of laptops and availability for those who'd like to play with them, so people without an XO can see where to get one (Presentations is out of date) and someone to make resources for the newbies who are going to be getting the machines so they can quickly contribute to the effort (at the minimum, it should teach them how to do a Demo).