EclipseSource is involved in several open-source projects and hosts many repositories. While some of them contain production-ready frameworks, others are proof-of-concept implementations, demonstrators, or template projects. To help you better understand the purpose and what to expect from each repository, we categorize them with the classification below.
Don't hesitate to contact us if you need active development, maintenance or long term support for a specific project, independently of its state.
Repositories can have one of the following statuses.
| Status | Badge (in_readme) |
Description |
|---|---|---|
| Active Development |  |
A repository that is under active development. The maintainers of this repository are actively developing new features and releasing new versions. |
| Feature Complete |  |
A repository that is considered to be feature complete. Thus, the maintainers are currently not actively developing new features. |
| Maintenance |  |
A repository that is in maintenance mode. The maintainers will focus on issues relevant to their adoption use cases only. |
| Deprecated |  |
A repository that is deprecated. The authors will not spend further effort on development or fixes. |
| Purpose | Badge (in_readme) |
Description |
|---|---|---|
| Proof of Concept |  |
A repository that is used to evaluate the feasibility of a certain concept or served as a one time demonstration. The purpose of this PoC is not to provide usable software. Consequently, the authors do not actively ensure that the PoC runs as expected and don't plan to support different set-ups or environments. Until stated otherwise, the authors do not intend to maintain this PoC, apply security fixes, update dependencies, fix issues or provide more documentation. Please feel free to browse the code although it is not meant as a blueprint, i.e. there might be expected and undocumented architectural shortcomings or workarounds. |
| Demonstrator |  |
A repository that is used to demonstrate a specific feature on a documented demo path. It is not meant to be used in production or as a template. Consequently, the authors do not actively ensure that anything other than the demo path works and don't plan to support different set-ups or environments. Until stated otherwise, the authors do not intend to apply security fixes, update dependencies, fix issues or provide more documentation. Please feel free to browse the code although it is not meant as a blueprint, i.e. there might be expected and undocumented architectural shortcomings or work around. |
| Blueprint |  |
A repository that is meant as a template for how specific things can be built. It is not meant as a productive framework or product. Consequently, there may be missing features or bugs. There may even be known bugs that won’t be fixed, if fixing them doesn’t necessarily avail the purpose of this blueprint. |
| Framework / Product |   |
A repository that is meant as a framework, library, or platform for implementing certain features or types of products, or can be used as a product directly. It is designed to be reusable, customizable, and ready for production. |