html5-img
1 / 17

OHS/DKR Proposed Plan of Action

OHS/DKR Proposed Plan of Action. Eugene Eric Kim <eekim@eekim.com> Thursday, March 30, 2000. Presentation Overview. Overall mission Project mission Managing the project Technical agenda Bootstrapping opportunities Funding strategy. Overall mission.

zelda
Download Presentation

OHS/DKR Proposed Plan of Action

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OHS/DKRProposed Plan of Action Eugene Eric Kim <eekim@eekim.com> Thursday, March 30, 2000

  2. Presentation Overview • Overall mission • Project mission • Managing the project • Technical agenda • Bootstrapping opportunities • Funding strategy

  3. Overall mission • Well-defined by Doug and the Bootstrap Institute • http://www.bootstrap.org/vision_mission.html • Guiding principle for the project: • Bootstrap everything!

  4. Project Mission • Build the Open Hyperdocument System (OHS) and a Dynamic Knowledge Repository (DKR)

  5. Managing the Project

  6. Comments on Hierarchy • Applies to multiple task forces • Designed to maximize the effort, time, and contribution of motivated individuals • Accountability and conflict-resolution • A role for everyone • Not every position needs to be filled

  7. Task Forces • Development team • Maintaining the DKR • Intellectual Property • Advocacy • Fundraising

  8. Management Agenda • Solicit/assign task force leads • Compile list of interested task force contributors and their contact information • Discussion forums for task forces • Devise short-term agendas and schedules

  9. Technical Agenda • Adam Cheyer’s Session 4 proposal as our framework • Technical features well-documented by Doug • Initial requirements list by Eric Armstrong • Highly iterative development process (bootstrapping again!) • Small set of requirements, aggressive scheduling

  10. Technical Agenda (cont.) • Encourage volunteers to bootstrap on top of our efforts

  11. Open Source Issues • Standards • Forking is not a bad thing! • Licensing • Software • Documents

  12. Initial Technical Objectives • E-mail • World Wide Web • Augment • Source code

  13. Initial Approach • Define XML schemas • Publishing documents • Different views • Editing/browsing • Actions and filters

  14. Case study: E-mail • Record and publish unrev-II and other related discussion lists • Features: • Granular addressability • Back-link management • Annotations

  15. Case Study: Web/Augment • Publish all of the documents, papers, and presentations we generate using our system • Software requirements management • Conversion of existing Augment documents

  16. Bootstrapping Opportunities • Internal bootstrapping • Software development infrastructure • Open source project management • Intellectual property • Funding

  17. Funding Strategy • Funding efforts should occur in parallel with OHS/DKR development effort • Determine funding needs • Investigate creative contributions • Bootstrap Institute handles distribution of funds

More Related