Date: Thu, 28 Mar 2024 19:04:42 +0000 (UTC)
Message-ID: <1869807308.28776.1711652682725@aws-us-west-2-lfn-confluence-1.web.codeaurora.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_28775_793087071.1711652682725"
------=_Part_28775_793087071.1711652682725
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Information sources to Join this Cross-Community Effort<=
/strong>
Web
Wiki
Mailing List
Bi-Weekly Meeting Calendar=
Sla=
ck Channel
Meeting Agenda/Minutes
Motivation: Our goal is to provide opportunities for open s=
ource communities to collaborate and build some of the most important techn=
ologies across the globe. Doing so often requires a deep, spec=
ific expertise on the part of the developers who build and test these compo=
nents. 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 act=
ivity, multiple projects, communities, and companies collaboratively bluepr=
int, prototype, and integrate real-world use cases to showcase the capabili=
ties of open source projects in the context of the full ecosystem in which =
they exist.
What is a Super Blueprint?
- It is a community-driven integration/illustration of multiple ope=
n source initiatives coming together to show end-to-end use cases demonstra=
ting implementation architectures for end users.
- 5G Super Blueprint is one example, and this initiative allows ope=
n contribution for more use cases across Enterprise, Cloud and Telecom ecos=
ystems, as resources and time allow.
What the 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, Anuke=
t, K8s, etc., are top level chartered projects; it is a proof=
of concept and integration across multiple open source projects and multip=
le company products of how to create something end-to-end using open source=
.
- It is not a commercial distro.=
li>
- It does not prove-out all non-functional requirements such as sec=
urity, reliability, etc., unless the community adds a use case and resource=
s for that specific purpose.
- It is not an endorsement of any specific participating organizati=
on; 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 a=
s defined by a community-driven process, allowing more end-to-end solutions=
across use cases in various vertical markets.
- If you=E2=80=99d like to create a future blueprint, we would love=
to hear from you. Just please remember that it=E2=80=99s sometimes easier =
to put things down on paper than it is to actually build them. So, please b=
ring interesting ideas to this community initiative along with contributors=
to realize the vision.
How is the demonstration use case determined?
- By those doing the work who not only bring to the table interesti=
ng ideas, but resources who are willing to put the work in. The community w=
ants to show something exciting and marketable but also within the realm of=
the resources available.
Are you forking code for this?
- No. We recognize that there are caveats and nua=
nces. If we are curious about a feature and want to use a local branch to t=
ry it out, we can. But like open source best practices, participants are re=
quired to bring it 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 h=
eaders we will need in our centralized repos.
- Each upstream community has its own IPR regime; this is not an op=
portunity to have opinions about any of those, but any code that is outside=
deploy, configure, experiment, or document needs to go upstream and follow=
that community=E2=80=99s IPR policy. Please see the above question and ans=
wer about forking code.
Do you have a charter?
- No. This is an exercise in bringing together components to answer=
questions and show solutions. We do not intend to create IPR or do somethi=
ng that requires legal incorporation.
How do you make decisions then?
- Rough consensus and running code -- it=E2=80=99s more important t=
o figure out how things work and to demonstrate that than it is to be ideol=
ogically =E2=80=9Cpure.=E2=80=9D
- Do-acracy -- folks who care about a use case bring to the table p=
eople and resources (e.g., labs) to get things done. The best idea in the w=
orld that no one is willing to work on is of little value.
- Listening -- we do recognize that many of our end users do not br=
ing developers to the table, but our ecosystem benefits by understanding en=
d user requirements, use cases and ideas.
What is the process to engage projects (within and outside LFN) =
that are either identified as part of Super Blueprint OR need to be include=
d?
- LF will help facilitate the initial introduction. All TSCs will b=
e provided an opportunity to participate and help drive the collaboration.&=
nbsp;
- There is a requirement on open source licensing for projects that=
needs to be validated prior to integration.
- Please see above questions about coming to the table with enthusiastic =
people -- we want technical breadth and depth, but all individuals involved=
only have so many hours to devote to this work. It=E2=80=99s very easy to =
say =E2=80=9Csomeone should do this,=E2=80=9D but much harder to commit =E2=
=80=9CI will do this.=E2=80=9D
How are you facilitating transparency?
- Like all good builders, through our tools and actions:
- Every single person is welcome to show up and use all of these tools, t=
o examine work, and to help make the work better.
Can anyone participate in a Blueprint Initiative?
- Yes, Blueprints and technical collaborations under LF Networking =
(LFN) and the Linux Foundation (LF) are fully open to all in the open sourc=
e community.
Do Blueprints require membership?
- No. All Technical projects with the Linux Foundation are open to =
all, including LFN=E2=80=99s initiative on 5G Super Blueprint, and do not r=
equire any membership.
What is the relationship between DARPA project OPS 5G with the L=
inux Foundation and Super Blueprints?
- DARPA is one of many end users of community open source work. Oth=
ers, including several countries in the EU/Africa, are looking at open sour=
ce blueprints as a quick step to innovation. All work will be carried out u=
pstream in open source communities including participating TSCs.
Can we get other projects and proprietary products added to the =
5G Super Blueprint?
- The 5G Super Blueprint is meant to stimulate collaboration across=
open source project communities within and outside the LF. The community c=
an work on a framework process to allow derivative blueprints that include =
other projects or products. The community can, for example, if desired, tak=
e notes from building/writing the process sim,.ilar to the LF Edge Akraino =
project that has written a community document on blueprint lifecycle manage=
ment which includes multiple projects and proprietary products. Commercial =
distributions and commercial products leveraging the community blueprint wo=
rk are welcomed and encouraged. The 5G Super Blueprint work is not itself a=
distribution.
What is the path of Blueprints into open source official release=
s of projects? And conversely, what is the process of adjusting the initial=
vision of Blueprints based on community work in progress?
- This will be part of the Community Document that will outline the=
process of operations and is currently being worked in conjunction with TS=
Cs across the projects. Feel free to contact the program manager for this.&=
nbsp;
I want to be part of this! What do I do?
- At the top of this page are a set of helpful links. We recommend =
you start by filling out the interest form on the website and joining the m=
ailing list. The projects, labs, and access are open to a=
nyone who requests for participation. You might show up o=
n a call where you don=E2=80=99t know anyone and feel intimidated. That=E2=
=80=99s ok! Please reach out directly over zoom chat to LF staff to request=
context (bwick@linuxfoundation.org & lilluzzi@contractor.linuxfoundation.org). We rea=
lly do want to hear from you. This is, literally, our job.
------=_Part_28775_793087071.1711652682725--