<div dir="ltr">Hi,<div><br></div><div>Could the devroom include topics such as Yocto or Buildroot as there is no "embedded" devrom this year?</div><div><br></div><div>thx</div></div><br><div class="gmail_quote"><div dir="ltr">Le jeu. 1 nov. 2018 à 10:13, Brian Exelbierd <<a href="mailto:bex@pobox.com">bex@pobox.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The Distributions devroom will take place Sunday 3 February 2019 at<br>
FOSDEM, in Brussels, Belgium at the Université Libre de Bruxelles.<br>
<br>
As more and more workloads are being considered for containerization in<br>
the future and are finally landing in virtualized environments today,<br>
distributions remain a critical success factor and are more important<br>
than ever. Containers, like virtual machines, are not magical and<br>
rely on piles of software being assembled in a way that is repeatable,<br>
reliable, and functional. This is at the very heart of the problem that<br>
distributions have always solved.<br>
<br>
Each distribution is responsible for building, testing, and releasing<br>
software as well as managing the lifecycle of each application in the<br>
collection. Additionally, distributions do very important work in ensuring<br>
that various versions of upstream software work well together and can<br>
co-exist. Distributions are also, often responsible, for "de-vendoring"<br>
upstream software so that security fixes can be applied more quickly.<br>
<br>
We welcome submissions targeted at contributors interested in issues<br>
unique to distributions, especially in the following topics:<br>
<br>
# Topics and Areas of Focus<br>
<br>
## Focus Areas<br>
<br>
- The ways that distribution technologies can be leveraged to allow<br>
for easier creation of a multi-verse of artifacts from single source<br>
trees. This includes the increasing move toward self-contained<br>
applications and providing multiple non-parallel installed versions<br>
of software.<br>
<br>
- Efforts being made in shared environments around Build/Test/Release<br>
cycles.<br>
<br>
- Topics related to the delivery problem as it impacts updates in<br>
terms of both size and rollback/reliability are expected to be featured.<br>
<br>
## Additional Topic Ideas<br>
<br>
- Distribution and Community collaborations, eg: how does code flow from<br>
developers to end users across communities, ensuring trust and code<br>
audibility<br>
<br>
- Automating building software for redistribution to minimize human<br>
involvement, eg: bots that branch and build software, bots that<br>
participate as team members extending human involvement<br>
<br>
- Cross-distribution collaboration on common issues, eg: content<br>
distribution, infrastructure, and documentation<br>
<br>
- Growing distribution communities, eg: onboarding new users, helping<br>
new contributors learn community values and technology, increasing<br>
contributor technical skills, recognizing and rewarding contribution<br>
<br>
- Principals of Rolling Releases, Long Term Supported Releases (LTS),<br>
Feature gated releases, and calendar releases<br>
<br>
- Distribution construction, installation, deployment, packaging and<br>
content management<br>
<br>
- Balancing new code and active upstreams verus security updates, back<br>
porting and minimization of user breaking changes<br>
<br>
- Delivering architecture independent software universally across<br>
architectures within the confines of distribution systems<br>
<br>
- Effectively communicating the difference in experience across<br>
architectures for developers, packagers, and users<br>
<br>
- Working with vendors and including them in the community<br>
<br>
- The future of distributions, emerging trends and evolving user demands<br>
from the idea of a platform<br>
<br>
Ideal submissions are actionable and opinionated. Submissions may<br>
be in the form of 25 or 50 minute talks, panel sessions, round-table<br>
discussions, or Birds of a Feather (BoF) sessions.<br>
<br>
Dates<br>
------<br>
Submission Deadline: 02-Dec-2018 @ 2359 GMT<br>
Acceptance Notification: 7-Dec-2018<br>
Final Schedule Posted: 14-Dec-2018<br>
<br>
How to submit<br>
--------------<br>
Visit <a href="https://penta.fosdem.org/submission/FOSDEM19" rel="noreferrer" target="_blank">https://penta.fosdem.org/submission/FOSDEM19</a><br>
<br>
1.) If you do not have an account, create one here<br>
2.) Click 'Create Event'<br>
3.) Enter your presentation details<br>
4.) Be sure to select the Distributions Devroom track!<br>
5.) Submit<br>
<br>
What to include<br>
---------------<br>
- The title of your submission<br>
- A 1-paragraph Abstract<br>
- A longer description including the benefit of your talk to your target<br>
audience, including a definition of your target audience.<br>
- Approximate length / type of submission (talk, BoF, ...)<br>
- Links to related websites/blogs/talk material (if any)<br>
<br>
Administrative Notes<br>
----------------<br>
We will be live-streaming and recording the Distributions Devroom.<br>
Presenting at FOSDEM implies permission to record your session and<br>
distribute the recording afterwards. All videos will be made available<br>
under the standard FOSDEM content license (CC-BY).<br>
<br>
If you have any questions, feel free to contact the<br>
devroom organizers: <a href="mailto:distributions-devroom@lists.fosdem.org" target="_blank">distributions-devroom@lists.fosdem.org</a><br>
(<a href="https://lists.fosdem.org/listinfo/distributions-devroom" rel="noreferrer" target="_blank">https://lists.fosdem.org/listinfo/distributions-devroom</a>)<br>
<br>
Cheers!<br>
<br>
Brian Exelbierd (twitter: @bexelbie) and Brian Stinson (twitter:<br>
@bstinsonmhk) for and on behalf of The Distributions Devroom Program<br>
Committee<br>
<br>
_______________________________________________<br>
FOSDEM mailing list<br>
<a href="mailto:FOSDEM@lists.fosdem.org" target="_blank">FOSDEM@lists.fosdem.org</a><br>
<a href="https://lists.fosdem.org/listinfo/fosdem" rel="noreferrer" target="_blank">https://lists.fosdem.org/listinfo/fosdem</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><pre style="margin-top:0px;margin-bottom:0px;padding:0px;font-size:12px;color:rgb(51,51,51);white-space:pre-wrap!important">Pierre FICHEUX -/- CTO Smile ECS, France -\- <a href="mailto:pierre.ficheux@smile.fr" style="color:rgb(1,134,186)" target="_blank">pierre.ficheux@smile.fr</a>
<a href="http://www.smile.fr/" style="color:rgb(1,134,186)" target="_blank">http://www.smile.fr</a>
<a href="https://smile.eu/fr/offres/embarque-iot" style="color:rgb(1,134,186)" target="_blank">https://smile.eu/fr/offres/embarque-iot</a>
I would love to change the world, but they won't give me the source code</pre></div></div>