SLewis: Difference between revisions
From Modelado Foundation
imported>SLewis No edit summary |
imported>SLewis No edit summary |
||
| Line 33: | Line 33: | ||
======Big Data?====== | ======Big Data?====== | ||
=== | ===Value-Add=== | ||
====Community Development==== | ====Community Development==== | ||
| Line 46: | Line 44: | ||
*mailing lists | *mailing lists | ||
*conferencing/meetings | *conferencing/meetings | ||
*multi-project coordination (e.g. coordinated high quality releases) | |||
*release engineering (build/test/deploy) | |||
====Project Infrastructure==== | ====Project Infrastructure==== | ||
| Line 52: | Line 52: | ||
*git repos (public and private) | *git repos (public and private) | ||
*gerrit | |||
*bug tracking | *bug tracking | ||
*distro creation and deployment | *distro creation and deployment | ||
*integration (e.g. single sign on, gerrit+git, tooling/IDE, etc) | *integration (e.g. single sign on, gerrit+git, tooling/IDE, etc) | ||
=====Tools===== | =====Services and Tools===== | ||
*git/gerrit | |||
*bug tracking | |||
*IDE/tooling | |||
*web server (distros, repos) | |||
*automated build/test/CI | |||
=====Process===== | =====Process===== | ||
*How does 'open development' work in the large? (many projects, many developers, many years, many consumers) | *How does '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 | |||
====Provisioning - Build/Test/Deploy/Install/Update==== | ====Provisioning - Build/Test/Deploy/Install/Update==== | ||
*apt, rpm, osgi, etc | |||
====Maintenance and Support==== | ====Maintenance and Support==== | ||
*No HeartBleed | |||
* | |||
====Project Mentoring, Education, and Training==== | ====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==== | ====Architectural Coordination, Collaboration, and Direction==== | ||
====SW Integration | *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 | |||
Revision as of 21:03, May 2, 2014
Scott Lewis
Modelado Foundation
Email: slewis at modelado.org
Modelado Foundation Value Proposition
Target Communities
Existing XStack Projects
New/Other XStack Projects
Parallel Development Community
Distributed Systems Community
Developers
End Users
Applications
Simulations
Entertainment
Education
Business?
Big Data?
Value-Add
Community Development
- What is this?
Collaboration Infrastructure
- xstackwiki
- mailing lists
- conferencing/meetings
- multi-project coordination (e.g. coordinated high quality releases)
- release engineering (build/test/deploy)
Project Infrastructure
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
Process
- How does '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
Provisioning - Build/Test/Deploy/Install/Update
- apt, rpm, osgi, etc
Maintenance and Support
- No HeartBleed
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