SLewis: Difference between revisions
From Modelado Foundation
imported>SLewis No edit summary |
imported>SLewis No edit summary |
||
| Line 5: | Line 5: | ||
==Modelado Foundation Value Proposition== | ==Modelado Foundation Value Proposition== | ||
[[Target Communities]] | See [[Target Communities]] for an initial list of stakeholder target communities | ||
===Value-Add=== | ===Areas for MF Value-Add=== | ||
====Community Development==== | ====Community Development==== | ||
====Inter-Project Collaboration Infrastructure==== | |||
====Collaboration Infrastructure==== | |||
*xstackwiki | *xstackwiki | ||
| Line 23: | Line 21: | ||
====Project Infrastructure==== | ====Project Infrastructure==== | ||
=====Team Collaboration===== | =====Development Team Collaboration===== | ||
*git repos (public and private) | *git repos (public and private) | ||
| Line 39: | Line 37: | ||
*automated build/test/CI | *automated build/test/CI | ||
=====Open Source Process===== | =====Open Source Development Process===== | ||
*How does/can/should 'open development' work in the large? (many projects, many developers, many years, many consumers) | *How does/can/should 'open development' work in the large? (many projects, many developers, many years, many consumers) | ||
| Line 45: | Line 43: | ||
*Maintain quality (over teams, releases, etc) | *Maintain quality (over teams, releases, etc) | ||
*Continuous Innovation | *Continuous Innovation | ||
====Conferences and Hackathons==== | ====Conferences and Hackathons==== | ||
Revision as of 20:44, May 12, 2014
Scott Lewis
Modelado Foundation
Email: slewis at modelado.org
Modelado Foundation Value Proposition
See Target Communities for an initial list of stakeholder target communities
Areas for MF Value-Add
Community Development
Inter-Project Collaboration Infrastructure
- xstackwiki
- mailing lists
- conferencing/meetings
- multi-project coordination (e.g. coordinated high quality releases)
- release engineering (build/test/deploy)
Project Infrastructure
Development Team Collaboration
- git repos (public and private)
- gerrit
- bug tracking
- distro creation and deployment
- integration (e.g. single sign on, gerrit+git, tooling/IDE, etc)
Services and Tools
- git/gerrit
- bug tracking
- IDE/tooling
- web server (distros, repos)
- automated build/test/CI
Open Source Development Process
- How does/can/should 'open development' work in the large? (many projects, many developers, many years, many consumers)
- Example: Eclipse Development Process
- Maintain quality (over teams, releases, etc)
- Continuous Innovation
Conferences and Hackathons
- Setup, run, regular conferences
- Setup, run, regular hackathons
Provisioning - Build/Test/Deploy/Install/Update
- apt, rpm, osgi, etc
Maintenance and Support
- No HeartBleed. Avoid Tragedy of the Commons Problem
- Support Contracts with Enterprises, Developers, Users
IP Management
- Licensing for commercial and non-commercial distribution models
- consistent, clear policies wrt copyright, licensing, patents
Project Mentoring, Education, and Training
- Project Education: Rhythm of Open Development
- Releng 'in the large' (100 projects, 1000 developers, > 1 million consumers)
- Developer Education: How to use exascale APIs, sw abstractions, tooling (debuggers, etc)
Architectural Coordination, Collaboration, and Direction
- Councils: e.g. Architecture and Planning Council at EF
- Open, based upon participation, not controlled by one or few members
SW Integration Services
- Exascale Computing for Data Analytics
- Simulation for Scientific Computing...i.e. Research and Education