January 03 2018 @20:30 UTC 🔼

Pad is here:

https://pad.dyne.org/code/#/1/edit/o7stK3GxgxOVAt-gJylDqw/JXymE3Dwz5xa6zOP-0Ot+xy8/

Meet here: https://vdc.dyne.org/devuan

  • Please post notes prior to the meet.
  • Please add your name as 'Present' below when you get to the meet.
  • When adding a comment in someone else's notes, please pre-pend your name like this: (whoever) whatever . . .

Present: parazyd(text/irc), NewGnuGuy, blinkdog, fsmithred, rrq, golinux, jaromil, Chillfan(text)

Agenda 🔼

Old Actions 🔼

  • transfer files.devuan.org on the new server (needed for space to upload both jessie and ascii on the same file distribution server) (KatolaZ) instance is ready there, and has plenty of space
  • devuan developer's manual

Completed actions 🔼

  • more or less completed, well Katolaz just found some more issues to tackle, however we are busy with the deb.devuan.org round robin

New Business 🔼

spam on #debianfork needs action 🔼

we could add blinkdog's bot to the channel waiting for people to reply on #devuan-ops coagen is the operator, lets wait he is back from vacations

wiki and translated wikis 🔼

what do we do with wikis? http://devuan-mx.org/wiki/index.php/Devuan another one is starting in spanish, do we go for mediawiki the mexican wiki is asking what to do with translations lets come up with an answer within the 10th

packaging documentation 🔼

as the devuan-developer's manual is ready will benefit from the experience of newgnuguy going through it while approaching the task of packaging and maintainership

outreach 🔼

fsmithred 🔼

  • Updated xfce configs in desktop-base to 4.12 versions.
  • found out the problem with GPT missing boot partition need to ask the installer
  • found out also more weirdness with grub: debconf does not always run when grub debs are installed in chroot.
  • need some advice on translation issues in packages it is about po
  • great work forward on the desktop-base which is now under good control

msiism 🔼

  • ASCII packages
  • Please don't forget to also rebrand XDM.
  • Graphics are on git.devuan.org
  • Instructions on how to modify the config file are to be found at: https://git.devuan.org/devuan-editors/devuan-art/issues/14#note_8196 (This is, however, not entirely correct as we've decided to go with the bw logo only. But the necessary adjustments should be obvious.)
  • Documentation:
  • The copyright notice in the Devuan Manual currently states that "[p]ermission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation". (https://friendsofdevuan.org/doku.php/devuan_doc:manual:1_jessie:start)
  • Is there any reason for which that should better be restricted to just GFDL 1.3 instead?
    • (NewGnuGuy) I see no detriment from having the "or later" clause and it could prevent a license conflict in the future. License conflicts are a pain.
  • Mailing lists: Shouldn't HTML e-mail better be banned?
  • (onefang): also, can we not base-64 encode text only emails?
  • (rrq) and only allow relevant emails, with short and to-the-point discussion threads.
  • (NewGnuGuy) plaintext email is best email
  • Dev1Galaxy: Would it be possible to introduce a tag for inline code (command and file names) like it exists on the wiki?
  • (rrq) hmm metaphysics: answer is "yes", of course. I now even know how :) Main problem is that it needs theme-ing = css addition into the 12 different styles. As of now, there is a "badly themed" [c]..[/c] enclosure available for testing. Need to add css class "span.bbc" (sibling to "span.bbs") to the themes. => golinux(?) .. thereafter I'll add it to the bbcode list. (maybe time for tool tips as well)
  • (msiism) nice. as for theming, monospace font + a slightly shaded background should be fine

rrq 🔼

holidays were good, nothing broke in the meantime so ... everytime a sysadmin has no news... is good news! :^) -jrml

Evilham 🔼

Stuck in a bus with shady internet will prob. not make .it

375gnu (99% won't attend) 🔼

  • Lintian questions: 1. What lintian tags should be disabled by default in Devuan? 2. Where to keep Devuan specific information: push it to upstream or keep in devuan-lintian-profile?
  • Discuss build profiles, https://wiki.debian.org/BuildProfileSpec. Ascii won't benefit much from them, but Beowulf/Ceres will as the number of packages will be rebuilt automatically without manual
  1. Actions to be taken to make package rebuild much easier: 1. Make 'nosystemd' profile supported in Debian 2. Configure Devuan Jenkins to run pbuilder with --profiles=nosystemd 3. Create patches and push them to Debian (Here is the example of such patch https://git.devuan.org/devuan-packages/light-locker/commit/bf08d485bdf7d01e9f52969d8eef36d65b705b57). 4. Setup a job rebulding packages. (KatolaZ) As I said, build automation is not easy for all the cases. Nevertheless, we must try this as well. I am happy to help.

Steps 1 & 3 I'll take care of. For 4 I can provide some scripts.

KatolaZ 🔼

  • Not attending. Sorry
  • worked on package version comparison -- incorporated in amprolla (don't remember if I reported on this or not)
  • worked/working on mirrors and deb.devuan.org -- we have 7 mirrors in the RR -- should be working by today (nextime is updating the DNS) -- will chase the other mirrors up to fix their config
  • worked/working on mirror monitoring and checking -- documenting the scripts as well

discussing checking issue its reasonable to have our bot checking the Release files signatures. important issue raised by @rrq is that a malicious mirror could serve a fake signature. therefore the bot should go through random IPs perhaps using Tor.

(KatolaZ) Yes, I thought about that as well. Checking through tor is a good idea. A malicious mirror could serve both a fake Release and a fake signature.

  • working on d1h to include injection and pbuilder support -- updated documentation will follow
  • finalising minimal live images for ASCII -- last touches missing
  • will be able to help with ASCII installers, if needed (this seems to be the last step before we can release ASCII beta, right?)
  • working on a little thing -- will have news by the end of the week, probably
  • want to work on Translations.gz, right after ASCII beta is out. This might be a good addition for ASCII RC, if we are lucky -- parazyd says this must be quite easy.

parazyd 🔼

  • attending text mode
  • finishing up on arm-sdk
  • still need to find an arm64 build host for util-linux
  • the overdrive in switzerland didn't work out because the stock kernel is missing some features, and i don't want to build another one on a machine we do not own
  • need to catch up on last week's devuan-dev@ emails. is there anything outstanding that needs my attention?

blinkdog 🔼

  • AlexLikeRock created a (Mexican) Spanish Devuan wiki
  • http://devuan-mx.org/wiki/index.php/Devuan
  • I didn't approach him about it yet.
  • It is running MediaWiki; I feel like we should go the other way (FoD -> ALR's wiki), any chance to change?
  • Coded some gtfobot; still needs some refactoring work
  • Question: Which Devuan server should I run this on?
    • Does it need proper packaging? Or is a tarball OK?

golinux 🔼

New Actions 🔼

  • ISO installers ASAP for ASCII beta. jrml, blinkdog and katolaz
  • files.devuan.org needs migration to ganeti jrml to add rrq (KatolaZ) the instance is there. Jaromil has access. I can help with that
  • ACTION: @rrq - sort out hosting of blinkdog's gtfobot
  *- maybe dev1galaxy; or new "node.js stuff" ganeti VM; check with KatolaZ perhaps have a single VM to host all present and future node.js stuff as it may be useful to have more but also to isolate on a single maintained npm instance (will it need an external IP?) (KatolaZ) we have many external IPs available. We can put a new instance, even if probably it is better to use an existing instance (galaxy?)