FAQ

Motivation: Our goal is to provide opportunities for open source communities to collaborate and build some of the most important technologies across the globe. Doing so often requires a deep, specific expertise on the part of the developers who build and test these components. Bringing those pieces together, however, is often challenging, not just for the developers, but for the real-world end-users who need to stitch together multiple open source and proprietary solutions. In this activity, multiple projects, communities, and companies collaboratively blueprint, prototype, and integrate real-world use cases to showcase the capabilities of open source projects in the context of the full ecosystem in which they exist.

What is an LFN Super Blueprint?

It is a community-driven integration/illustration of multiple open source initiatives coming together to show end-to-end use cases demonstrating implementation architectures for end users.
LFN Super Blueprints is one example, and this initiative allows open contribution for more use cases across Enterprise, Cloud and Telecom ecosystems, as resources and time allow.

What the LFN Super Blueprint is not

It is not a product; however, a blueprint may contain image files, scripts, documentation, etc. to allow it to be duplicated in an end-user environment.
It is not a project in the sense that ONAP, MAGMA, Akraino, Anuket, K8s, etc., are top level chartered projects; it is a proof of concept and integration across multiple open source projects and multiple company products of how to create something end-to-end using open source.
It is not a commercial distro.
It does not prove-out all non-functional requirements such as security, reliability, etc., unless the community adds a use case and resources for that specific purpose.
It is not an endorsement of any specific participating organization; it is an exercise in building a solution.
It does not prove-out full SDO compliance.

What is the long term vision of Blueprints?

LFN will create a structure and framework to develop blueprints as defined by a community-driven process, allowing more end-to-end solutions across use cases in various vertical markets.
If you'd like to create a future blueprint, we would love to hear from you.

How is the demonstration use case determined?

By those doing the work who not only bring to the table interesting ideas, but resources who are willing to put the work in.

Are you forking code for this?

No. Participants are required to bring any experimental work back to the main branch.

What license is this work being done under?

We are working with the LF legal team to determine what license headers we will need in our centralized repos.
Each upstream community has its own IPR regime; any code that is outside deploy, configure, experiment, or document needs to go upstream and follow that community's IPR policy.

Do you have a charter?

No. This is an exercise in bringing together components to answer questions and show solutions.

How do you make decisions?

Rough consensus and running code.
Do-acracy — folks who care about a use case bring to the table people and resources to get things done.
Listening — end user requirements, use cases and ideas are valued.

How are you facilitating transparency?

Can anyone participate?

Yes, all Technical projects with the Linux Foundation are open to all, including LFN Super Blueprints, and do not require any membership.

I want to be part of this! What do I do?

Join the mailing list. The projects, labs, and access are open to anyone who requests participation. Please reach out directly to LF staff: lilluzzi@linuxfoundation.org.