Unlike many open source projects, the Xcore open source project consists of many different classes of design, and we expect the number of classes may also grow over time. Each class may have its own conventions - for example, creating a v1 release of a software component will have a completely different set of requirements to the release of a v1 printed circuit board. There may be other differences relating to how a project is built and tested etc.
The following lists the different classes that we currently use and/or expect in the future. The links are to pages which describe attributes that they share in common, which could relate to build systems, test infrastructure, versioning etc. These restrictions enable the use of automated build and regression systems, which we can all use to interpret the status and maturity of development projects:
Follow the links above to find out more, or, to contribute your views in how the community should manage this diversity, post to the Xcore open source project user forum