veyepar: Laniakea - An approach at making building Debian derivatives easy

Author(s):	Matthias Klumpp
Location	Rex
Date	aug Mon 07	Days Raw Files
Start	12:30	First Raw Start	error-in-template
Duration	00:20:00	Offset	None
End	12:50	Last Raw End
Chapters
Total cuts_time	None min.

https://debconf17.debconf.org/talks/38/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Laniakea_An_approach_at_making_building_Debian_derivatives_easy.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

While founding the Tanglu Debian derivative, I did set up infrastructure to create and maintain a Debian archive (which includes Britney, Ben, Dak and friends) and maintain it for the derivative, which resulted in some custom code being written for Tanglu. Doing this turned out to be quite a big task for a small derivative which requires a lot of continuous human work.
After I started working on PureOS for Purism[1], I had the pleasure of doing the same thing again. Having learned the lesson in Tanglu, I developed a framework for setting up and maintaining infrastructure for a Debian derivative, called Laniakea.
Laniakea uses tools already present and in use at Debian itself, but allows to centrally manage them and aggregate their information in one database.
This allows to automate a lot more archive actions, saving human manpower, as well as showing new developers a nice coherent web interface for their packaging.

This talk will be about what Laniakea wants to be and what it can already do today for your derivative, and how it differs from other solutions like Fedmsg. I will also likely contain useful information in what (not) to do in case you are brave enough to attempt to set up your very own infrastructure based on the tools we use to build Debian.

[1]: https://puri.sm/

Comment:

production notes