veyepar: 15 years and counting

Author(s):	Andreas Tille
Location	Rex
Date	aug Mon 07	Days Raw Files
Start	10:00	First Raw Start	error-in-template
Duration	00:45:00	Offset	None
End	10:45	Last Raw End
Chapters
Total cuts_time	None min.

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

assets release.pdf 15_years_and_counting.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

In 2002 some crazy Debian developer had the idea to pick some orphaned low popcon packages inside Debian covering life sciences and decided to add some more of this field and some covering the field of medicine.  Since that time the project gained some traction and convinced several people and institutes using Debian instead of some other Linux distribution.  While the outer view on the project which is called Debian Med Blend is quite good the Debian internal view does not really reflect the potential that Blends actually have.  Are you aware that more than 1% of the Debian developers confirmed that they are Debian developers only because the Debian Med project exist?  Can you imagine more of those Blends making Debian attractive in several workfields?

If you are not interested in life sciences and medicine at all this talk is for your despite the fact that it is covering Debian Med.  I'd like to prove on the example of Debian Med why Blends are helpful for the future of Debian, how the active support of Blends inside the Debian could have a positive effect onto the acceptance of Debian inside these workfields and beyond.  Blends have the power to bump the maintainer-package relation to a team-topic relation and can enhance the quality of packages covering a whole topic.

Comment:

production notes