SDS:Feb 9-13 2009 Project Management

From Tetherless World Wiki

Jump to: navigation, search

Project Management (From January 28 meeting notes)

  • requirements, design, implementation, issue tracking, use case creation, well understood tools, code review, project life cycle, schedule, tasks, task assignments, software life cycle, software releases (demo, alpha, beta, release) release tracking.
  • Use Case Template


Tier Definition Criteria
Tier 4 Production Hardened
Tier 3 Test/demo Outside Linked from demo page. Must pass some sort of peer review. Project manager has final approval and sets criteria from when ready. This is what TW has already in place regarding demos.
Tier 2 Development Internal TW
Tier 1 Experiment Individual/Group


What does it take to move from tier to tier? (tiers)

  • svn (immediately) (1,2(3,4))
  • Home page (1,2,3,4)
  • issue tracking (2,3,4)
  • documentation (3,4)
  • scheduling (milestones) (1,2,3,4)
  • support plan (bug report, feature requirements) (3,4) (has a vcc part and a tw part)
  • Monitor (tier 4 looking at 4,3,2,1)
  • Redundancy for tier 4 machines


Main Server Admin Page - Server List and Administration Manual

  • Take the hardware table. Copy it and update it to add tier of the machine, project or public use, what projects and/or groups are using it.


VSTO is being ported from production at UCAR to the production machine escience. It is not a demo. Starting at tier 4, then starting to tier 2, then 3.

When it comes to including students there needs to be a shift from tier 1 to tier 2. So we need to identify what development machine will be used for the project.

Gateway machine

  • ldap
  • nfs
  • data
  • monitor
  • svn
  • doc (manuals, help pages, api documentation for public interfaces, etc...)

Action Items

  • What does it take to get from tier to tier
  • What is the policy for search engine crawling for tier 3 and tier 4 machines
  • Test case is onto.rpi.edu. What does it take to get onto from currently tier 2 to tier 3? Physically moving the machine as well as passing all our criteria for what it means to be a demo machine. (Thus we need a list of what is currently running on onto).
  • Stephan will take the lead spec'ing out a demo machine (virtualization, build and test with tinderbox)
  • Patrick will take the lead on installing Trac on escience, tie in to svn, use ldap?

Issue Tracking Software

  • We have decided on Trac to be installed on escience. Patrick will take the lead on this.
  • Would we use Google Code, or the OPenDAP approach of SVN with Trac, or try to find a MediaWiki solution
  • There is also the Issue List on the TW Wiki. This is only being used by Jie.
  • Li pointed out a MediaWiki extension IssueTracker
  • Jie says that the reason he created one is 1) he could not get IssueTracker to work (MW version issue, no longer a problem) and he wanted to be able to do searches on it using SMW
  • I (Patrick) was able to install IssueTracker and play around with it. Very simple insterface, but usable. Does not have the semantic search capabilities.
  • I (Patrick) am starting to wonder if it's not so much the software that is at issue here, it is getting people to use it. There are some available, but they aren't being used.
Retrieved from "http://tw.rpi.edu/wiki/SDS:Feb_9-13_2009_Project_Management"
Personal tools