1. RPINVENTORY
Adventures in web systems

2. RPInventory History (circa 2008)

3. History
 Created as a part of Professor Moorthy’s “Open
Source Software Practices” Course, Fall 2008
 Ten different developers since inception
 839 commits (only on master)
 ~100,000 lines of code (181696 added, 79584
removed)

4. History
 A near infinite amount of information/learning
 Plans change!
 Scope drift
 What makes a project sustainable?

5. Project Sustainability

6. Things Learned
 Who will use your software?
 Why is it better than project “x”, “y”, and “z”?
 How can you make your life easier?

7. Things applied
 We have a community
 Don’t reinvent the wheel (without reason)
 Share and share alike
 Listen to your users

8. RPInventory Results
 Club interest
 Expand scope
 Fix issues/bugs submitted

10. RCOS Lab
Amos Eaton

11. Plans
 Grant from Lockheed Martin
 Create a space for RCOS, UPE, RPISEC, RPI ACM,
and the Networking Lab.
 An aesthetically-pleasing space for undergraduates

12. Currently
^^ To Walker and Sage Labs ^^
Hallway
CS Dept Empty/
Storage AE Lounge Networking Lab
Machine Room Storage
Hallway
VV To the Library and EMPAC VV

13. Proposed
^^ To Walker and Sage Labs ^^
Hallway
RPI ACM/
Networking Lab UPE/ RCOS RPISEC
Lounge
Hallway
VV To the Library and EMPAC VV

14. Ideas
 Have foldable walls between RPISEC, RCOS, and
ACM/UPE rooms
 Tables, chairs, and whiteboards
 Keep ACM/UPE more informal
 RPISEC & RCOS more formal

15. Benefits
 An area for project work sessions
 Ability to hold hands-on technical sessions
 Support group existence with physical space
 Support collaboration between organizations
 Cooled, hardware space