# Devuan meet 2020-06-04 @20:30 UTC

Present: bgstack15, fsmithred, golinux, rrq, adam, plasma41

## Old Business

## Old Actions

### fsmithred
* Did we really do that???
* https://dev1galaxy.org/files/3.0-distrowatch.png
* How I Spent My Day Off: chimaera, openbox, connman

https://get.refracta.org/files/experimental/snapshot_chimaera_01-20200604_2013.iso
* n/m - I see it. Will there be a package named sysvinit in chimaera?
(Not as crazy as that question sounds.)

## New Business

### rrq
* https://gitea.devuan.dev is set up anew. After having reviewed it more
closely and in discussion with LeePen we have come to suggesting the
following new structure for the devuan projects: Noting that gitea and
gitlab differ slightly in group structuring; gitea has "organization"
and "team" (in organization) where gitlab has "group" (only?). On
gitea it'd be good to have a "devuan" orgnaization, with teams of
"infrastructure", "packages", "documentation", and "editors" (the last
separating end-user documentation from esp www authoring). Thus, all
devuan projects would be projects of "devuan" in git terms, and the
access for updating them would be governed by team membership. gitea
uses the term "repository", but I'll keep using the term "project".
E.g. devuan-editors/devuan-www.git would be migrated into the project
devuan/www.git under the custody of team "editors" of organization
"devuan". Similarly, devuan-infrastructure/devuan-releasebot.git would
be migrated into devuan/releasebot.git under the custody of team
"infrastructure" of organization "devuan:". The projects are all
viewable (publicly visible) by browsing the organisation, "devuan", or
in sub sets via the various teams. It of course also allows for
non-public project. LeePen and rrq will migrate the devuan* groups.
All users will need to (re-) register themselves and migrate their own
projects. Migration is terribly easy. We should probably migrate the
domain git.devuan.org first, and then have the name gitlab.devuan.org
for the old git store, keeping it available for users to migrate for a
reasonable though limited period. The build pipeline is to be
confirmed before the actual migration.

### LeePen

#### Beowulf
* Released the release! devuan-announce email still outstanding: Jaromil
said he would do it on Wednesday 3rd June.
* For the point release, can we consider reverting to ID=Devuan in
/etc/os-release? This has been the case in Ceres/Chimaera since March.
I have built base-files 10.3+devuan3.5 which is in
beowulf-proposed-updates to ease testing, find out what breaks (secure
boot?) and what is fixed (postgresql-common, grub boot screen). Report
of successful install in
[#424](https://bugs.devuan.org/cgi/bugreport.cgi?bug=424#18)
* eudev update for beowulf-proposed-updates still pending.

#### Ceres/Chimaera
* updated udisks2 again and distro-info-data (with beowulf release).
* apt and tomcat9 need updating again (amesser).
* removed wicd from chimaera: it is python2 and uninstallable. There is
a python3 version in debian experimental or we will need to change to
something else. connman? nm? Other suggestions?
* (fsr) We've had many requests for network-manager

### bgstack15
* Gitlab issue preservation: output is ready to be presented. Links will
be shared during the meeting. If approved, the assets should be
transferred to a final destination. Total disk space: 44MB

### golinux
* #debianfork in process
  * parazyd They're on it
  * parazyd I'll be sure to let you know when something happens wrt a
    discussion and possible namespace exception- fsr, bgstack, MinceR,
    CrystalMath, yeti

### plasma41
* http://paste.debian.net/plain/1150018
  * `beowulf` and `beowulf-security` had their Suites changed from
    `testing` and `testing-security` to `stable` and `stable-security`,
    respectively, but `beowulf-proposed-updates` had it's Suite changed
    from `testing-proposed-updates` to `beowulf-proposed-updates` rather
    than to `stable-proposed-updates`. Was this inconsistency
    intentional or accidental?
* https://devuan.org/os/announce/beowulf-stable-announce-060120 is
  missing links to the mailing lists. Should we fix that?

### adam
  * nothing to report.
  * still planning to test/verify net unattended pxe install on x86 &
    arm
  * thanks for new package maintenance guide!
  * i will contact manuella/ over 2019 financials
  * still to follow through package maintenance to test: zenroom & maybe
    dowse (ugly).

## New Actions
* point release asap
* Some kind of index for migrated issues. How to present it?
* ongoing issue with #debianfork. YAY! Looks like MinceR does already
have some power. He just banned the spammer's IP since he keeps
changing nicks.