We Kick Open Source Projects into High-Gear
This year we are once again sourcing projects from all over the community. They will all be open source, not-for-profit, and interoperable.
If you have a project that can benefit from the skills of a dev team at CloudFest Hackathon and also fits the open-source ethos. get in touch with us here. (Email to: email@example.com)
Domain Connect DNS Provider
Domain Connect is an open standard that makes it easy for a user to configure DNS for a domain running at a DNS provider to work with a Service running at an independent Service Provider. The user can do so without understanding any of the complexities of DNS.
In the Cloud Fest Hackathon we want to build a reference implementation of Domain Connect DNS-Provider on top of standard open source DNS project (PowerDNS or BIND). By doing so, we should help to accelerate adoption from DNS Providers that utilize these services.
ID4me Plugin Fiesta
ID4me is a standard for public, open, federated digital identity service that aims to provide two main functions:
- Authorization of a user for access to any third party accepting ID4me identifiers (“single sign-on” on an Internet scale);
- Controlled communication of the user’s personal information to the third parties accessed by the user.
ID4me is the ultimate independent SSO solution industry needs to turn separated ecosystems into seamless experience across the board.
In the Cloud Fest Hackathon we want to enable the hosting, cloud and SaaS providers in the process of adoption of the new standard, by developing libraries and plugins for as many languages, frameworks and projects as possible.
Application <=> Server Management Protocol (ASMP)
There’s currently no standardized protocol for server applications to request information about or changes to the underlying infrastructure. While we have APIs to provision such servers through code, we have no protocol or API to allow the applications that run on them to make changes after the provisioning.
I hereby suggest creating a communication protocol (tentatively named ASMP) between servers and applications that run on these servers that allows for bidirectional communication so that these two actors can coordinate.
This would allow such scenarios as a WordPress end user having the possibility to update the PHP or MySQL version from the admin backend, a provisioning script automatically adapting the server environment to meet the requirements described in the Composer configuration, or a server control panel showing latest updates to the server components in a user’s admin area. The protocol should be limited to querying capabilities and state and sending asynchronous requests, and all possible request types should be opt-in.
This allows for a gradual or partial introduction by the hosting providers. We should provide a reference implementation based on a common server distribution. Also, building implementations into popular server control panels would accelerate adoption.