[pkg-php-pear] Packaging Movim for Debian

[Thorsten Glaser]

Hi all,

I’ve added a few people to the Cc list who might be interested.

>Dominik George and me (tg at d.o but with Teckids hat) wish to package
>Movim, a Jabber-based “social network”, for Debian proper.

>The way things currently are is that we plan to work on this as a
>kind of “sprint” during the Mini-DebConf in Hamburg in May 2018:
> http://layer-acht.org/thinking/blog/20180215-mini-debconf-hamburg/

Would any of you wishing to be joining us for that sprint?

According to https://wiki.debian.org/Sprints/HowTo I’ve got to
figure out the number of participants and estimated travel costs
beforehand, so… please answer until next week’s Wednesday if
possible (if interested but unsure, please at least mail back
saying so, for feedback).

Thanks!

>For that,
>we’ll have to package a number of new packages (see #858367 for the
>list of blocker ITP bugs), but also *possibly* update your packages:
>
>• raintpl
>• php-markdown
>• php-htmlpurifier (ouch, yes, that means I’ll have to hack this again)
>• symfony (for newer php-symfony-console only)

I also hope we won’t need too new a version. I only know from the list
https://github.com/movim/movim/wiki/Packaging-Dependency roughly about
what’s needed, but “dev-master” isn’t a nice version indication, it
should at least say “larger than X.Y” when X.Y is the last released
version and not new enough, so we can easier figure out which ones
will indeed be necessary.

David Prévot indicated we should not use a version newer than 3.4,
the current LTS, for the last one. Timothée Jaussoin, can you maybe
enlighten us?

>Will you be amenable to join us there and/or bring your packages
>up to date in sid beforehand?

Do note that this is *not* a request to take over maintenance
of even more packages, considering…

>Also, would the Debian PHP PEAR Maintainers team consider maintaining
>some of the dependencies from the list in #858367?

… this. Nik wrote, regarding maintenance:

>We do not have many choices - everything we need to do ourselves should
>be done in close coordination with the PHP team, and we should do our
>best to co-maintain them, but motivate the PHP team to do so as well.

So the team for Movim packaging would probably be the Teckids FOSS
team, but that doesn’t mean we wish to maintain a whole rat’s tail
worth of dependencies.

It’s also likely we’ll need some help from Debian PHP PEAR Maintainers
not just in maintenance but also in coaching (what’s this “composer”
thingy PHP people seem to like to be using nowadays, and how is it
handled in Debian?).

Thanks in advance,
//mirabilos
PS: Coaching in how to best set this up as a Debian sprint also welcome
-- 
Thorsten Glaser (charter member)
Teckids e.V. — Erkunden, Entdecken, Erfinden.
https://www.teckids.org/