Difference between revisions of "StarlingX"
Ghada.khalil (talk | contribs) (→Planning & Process) |
Ghada.khalil (talk | contribs) (→Planning & Process) |
||
Line 34: | Line 34: | ||
== Planning & Process == | == Planning & Process == | ||
* [[StarlingX/Release_Plan|StarlingX Release Planning]] | * [[StarlingX/Release_Plan|StarlingX Release Planning]] | ||
− | * [[StarlingX/Feature Development Process|StarlingX Feature Development Process ( | + | * [[StarlingX/Feature Development Process|StarlingX Feature Development Process (not ready)]] |
* [[StarlingX/Defect Handling Process|StarlingX Defect Handling Process]] | * [[StarlingX/Defect Handling Process|StarlingX Defect Handling Process]] | ||
Revision as of 15:46, 12 September 2018
Welcome to the StarlingX Project
StarlingX is a fully featured and high performance Edge Cloud software stack that is based on the Wind River® Titanium Cloud R5 product. Intel and Wind River have jointly open sourced this software and we invite you to download, build, install, and run it.
Wind River Titanium Cloud was originally built on open source components, that were then extended and hardened to meet critical infrastructure requirements, including: high availability, fault management, and performance management. This software provides numerous features and capabilities to enable 24/7 operation of mission critical applications.
You can find an overview of the StarlingX project's features <insert link here>.
The StarlingX project opens all of these enhancements to the open source community. Please join us as we build the infrastructure stack for Edge Computing.
DocumentationThese three documents will help get you started building, installing, and validating your installation of StarlingX: CodeThe StarlingX project uses Gerrit as its web-based code change management and review tool.
Planning & Process
Story and Bug TrackingWe are using the OpenStack Storyboard tool for tracking feature development activities. Each new Story shall be marked with one or more Tags, and can optionally include one or more Prefixes in the description. See Tags and Prefixes for a description of how we use them. The StarlingX Storyboard project group is here. IMPORTANT: If you create a new story (of any kind), please mark it with the tag "stx.new" so we can find it, review it and assign it to the right team and a release. We are using Launchpad for tracking bugs. Link to the StarlingX Launchpad IMPORTANT: If you create a new bug, please use the StarlingX Bug Template. Sample queries:
References
OpenStack DocumentationThese are references to general OpenStack material:
GovernanceA very preliminary Governance document can be found here. It contains lot of feedback from various reviewers of the early drafts. A more polished version of the same document can be found on this page. |
CultureWe are proud to be an OpenStack Foundation project!
MeetingsWeekly callsThe list of meetings and dial-in information can be found on this page. PTG MeetingsWe are preparing for the Denver OpenStack PTG meeting. Draft agenda items can be found here: Status and PlanningThis section is under construction. Overall project planning pagesStarlingX ProjectsStarlingX is both a development project and an integration project that combines new services with many other open source projects into an overall Edge Cloud software stack. We've broken the overall project into a set of separate projects to help keep things manageable. Notes from the F2F discussion on how to organize sub-teams are here StarlingX main projectsInformation on the main StarlingX development projects can be found on the wiki pages below:
StarlingX supporting projectsIn addition to the main StarlingX development projects there are also additional projects to help us develop, maintain, document, build and release the overall StarlingX software stack.
StarlingX cross-project initiativesThere are several initiatives we are implementing that cross project boundaries:
ToDo:
Upstream StatusThe StarlingX code base contains a number of out-of-tree patches against other open source components. One of our highest priorities is to contribute those changes to their upstream communities. We are tracking our progress in a shared Google document. Please BruceJ @ Intel and send him a gmail.com email address for access to the document. |