SLewis: Difference between revisions
From Modelado Foundation
imported>SLewis No edit summary |
imported>SLewis |
||
| (One intermediate revision by the same user not shown) | |||
| Line 15: | Line 15: | ||
*architecture, planning...e.g. via PMC/Councils | *architecture, planning...e.g. via PMC/Councils | ||
*multi-project release coordination and engineering (build/test/deploy) | *multi-project release coordination and engineering (build/test/deploy) | ||
* | **hardware | ||
**software infrastructure (OS, APIs, middleware) | |||
**software applications | |||
**reports | |||
====Project Infrastructure==== | ====Project Infrastructure==== | ||
| Line 35: | Line 38: | ||
*web server (distros, repos) | *web server (distros, repos) | ||
*automated build/test/CI | *automated build/test/CI | ||
*automated report creation, generation, integration | *automated report creation, generation, integration e.g. via LaTex tooling and [https://github.com/sharelatex SharedLatex] | ||
===IP=== | ===IP=== | ||
Latest revision as of 21:18, September 23, 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
IT
Inter-Project Collaboration
- xstackwiki
- mailing lists
- architecture, planning...e.g. via PMC/Councils
- multi-project release coordination and engineering (build/test/deploy)
- hardware
- software infrastructure (OS, APIs, middleware)
- software applications
- reports
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)
- collaborative report creation
Development Services and Tools
- git/gerrit
- bug tracking
- Compilers, IDE, new tooling...
- web server (distros, repos)
- automated build/test/CI
- automated report creation, generation, integration e.g. via LaTex tooling and SharedLatex
IP
Management
- Licensing for commercial and non-commercial distribution models
- Copyright
- Patent
- Open Source
- consistent, clear policies wrt copyright, licensing, patents
RE (Release Engineering)
Provisioning - Build/Test/Deploy/Install/Update
- apt, rpm, osgi install/update/uninstall technology development
- Customized distro creation...for specific consumers
- Promotion/Marketing of Distros for Community Awareness
Maintenance and Support
- No HeartBleed. Avoid Tragedy of the Commons Problem
- Support Contracts with Enterprises, Developers, Users
Distro Creation and Support
Other
Community Development
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
- Rules of Project Engagement. Based upon technical contribution.
Conferences and Hackathons
- Setup, run, regular conferences
- Setup, run, regular hackathons
Project Mentoring
- 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)
Integration Services
- Exascale Computing for Data Analytics
- Simulation for Scientific Computing...i.e. Research and Education