|
|
# Debian Med sprint 2022-02-11 - 2021-02-13 or 2022-02-18 - 2021-02-20
|
|
|
|
|
|
(Final date to be decided)
|
|
|
|
|
|
This is the second Debian Med sprint done online.
|
|
|
It will continue a [series of in person meetings](https://wiki.debian.org/DebianMed/Meeting) done by the Debian Med team.
|
|
|
|
|
|
This page should coordinate activities of attendees:
|
|
|
|
|
|
## Communication
|
|
|
### Video conference channel / meeting room for socialising
|
|
|
|
|
|
There is a [Jitsi video conference channel](https://jitsi.debian.social/DebianMedCovid19). This video conference room will stay open for everybody from [2022-02-11 07:00UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Debian+Med+sprint&iso=20220211T07) to [2021-02-20 19:00UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Debian+Med+sprint&iso=20220220T19) (or earlier if someone opens that Jitsi session earlier / longer if someone might like to stay longer). Attendees are *not* supposed to sit all the time in front of their camera wearing a headset. This room can be rather used as a place to meet in breaks even to have dishes in common. From there people might agree to meet in separate rooms for smaller focused meetings. We will see how this might work out - it's our first virtual meeting.
|
|
|
|
|
|
Please make sure to switch off your camera and microphone if you are just hacking but want to lurk inside that room anyway. If you realize that there are bandwidth issues its better to enter the room only if you really want to meet somebody.
|
|
|
|
|
|
### Debian Med mailing list
|
|
|
You can always contact the [Debian Med mailing list](https://lists.debian.org/debian-med). It might be sensible to use a tag ``sprint`` inside the subject line. The mailing list should be used as always for serious technical discussion that should be *archived* inside the mailing list archive.
|
|
|
|
|
|
### Matrix channel
|
|
|
A [Matrix channel](https://app.element.io/#/room/#debian-med:matrix.org) was created to make recordable in time chats easily doable. Please use this channel.
|
|
|
|
|
|
### Debian Med IRC channel
|
|
|
The IRC channel [#debian-med](irc://irc.debian.org/debian-med) on [OFTC](https://wiki.debian.org/IRC). While this channel exists current attendees prefer the Matrix channel over IRC.
|
|
|
|
|
|
## Tasks for the Sprint
|
|
|
|
|
|
1. Work on RC bugs and check migration to testing of your packages
|
|
|
1. There is a [great spreadsheet](https://docs.google.com/spreadsheets/d/1tApLhVqxRZ2VOuMH_aPUgFENQJfbLlB_PFH_Ah_q7hM/edit?ts=5eb957ba#gid=543782716) that serves as some kind of todo list what software would be interesting to be packaged
|
|
|
1. There are interesting pages in the Blends framework that might guide attendees to open tasks
|
|
|
* [New QA page](https://blends.debian.org/med/qa/) featuring testing migration issues, failed autopkgtests and more
|
|
|
* The hopefully well known [bugs page](https://blends.debian.org/med/bugs/)
|
|
|
* The [tasks page](https://blends.debian.org/med/tasks/)
|
|
|
1. For those who are considering starting or finishing complex packages here might be a small list (with no specific order)
|
|
|
* [shiny-server](https://salsa.debian.org/science-team/shiny-server)
|
|
|
* [megan-ce](https://salsa.debian.org/med-team/megan-ce)
|
|
|
* [bcbio](https://salsa.debian.org/med-team/bcbio) dependencies
|
|
|
- [gatk](https://salsa.debian.org/med-team/gatk)
|
|
|
- [pyomo](https://salsa.debian.org/med-team/pyomo)
|
|
|
1. Write autopkgtests ([List of packages needing tests](https://salsa.debian.org/med-team/community/helper-scripts/-/blob/master/debian-med-tests.txt))
|
|
|
1. Contact upstreams of not yet freed software mentioned at [software liberation Wiki page](https://wiki.debian.org/DebianMed/SoftwareLiberation)
|
|
|
|
|
|
## Needs packaging training
|
|
|
* ''add your name here''
|
|
|
|
|
|
## Personal agendas
|
|
|
|
|
|
### Andreas Tille
|
|
|
|
|
|
1. Mentor newcomers how to fix bugs, write tests, build packages
|
|
|
1. Fix RC bugs in Debian Med and R-pkg team
|
|
|
1. Check for packages that did not migrated to testing yet
|
|
|
1. Check for new software to package in case all burning issues with existing packages are solved
|
|
|
|
|
|
## Personal reports
|
|
|
|
|
|
### Andreas Tille
|
|
|
|
|
|
|