[Contributors meeting] February 27th, 2018

Contribute Room
,
2

Attendees

  • Alex
  • Bram
  • frju365
  • jean-baptiste
  • Josue
  • ljf
  • Maniack
  • vey
  • cireuil

Misc news since last time

Introducing vey and cireuil, general discussion about the project, …

Let’s Encrypt rate limit for .nohost.me certificates

Let’s Encrypt rates state that you can only ask for certificates 20 times per period of 7 days. We expected this to quickly become a problem one year ago. Turns out we didn’t until now. We’ve finally reached it, sadly (a user recently reported the corresponding error). What should we do?

Two strategies :

  • Register to LE as an organization to have higher rates (already tried a few months ago - no response)
  • Register to the Public suffix list : https://github.com/publicsuffix/list/pull/250 (abandonned PR, need someone to give his/her real name as contact)

TODO: (ljf) create an account on saperlipopette and create the PR (exemple with netlib.re https://github.com/publicsuffix/list/pull/500 )

Images: Testing / validating and pushing Maniack’s ISO

Maniack produced new ISOs, how do we test / validate them before making them public ?

c.f. https://github.com/YunoHost/cd_build/pulls and https://ci-apps.yunohost.org/build/
(Also related to this discussion : https://github.com/YunoHost/doc/pull/670 )

  • Test that the new ISOs boot on a “real machine” ?

  • Are we happy with the partitioning ?

    • During the meeting, Maniack C confirms that the new isos have a good partitioning, with /boot and / (the old ones have a partitioning with /tmp, /var, /home and /)

  • Test dd and Etcher ?

TODO : (Alex) test with dd and Etcher with a USB key

New app : unattented-upgrades

Just for info, https://github.com/YunoHost-Apps/unattended_upgrades_ynh
And because, this app could be, one day…, a core feature

(unattented-upgrades is a program that trigger automatic upgrade / dist-upgrade every day)

Apps : let’s make the official.json app list point directly to master/HEAD !

Follow-up of a discussion at the last Brique Camp : currently, changes in the apps repositories need to be propagated to the official.json / community.json since they contain hard-coded commits of the “stable” version. The discussion at the Brique Camp led to the conclusion that this could be fixed by generalizing the use of “testing” branches in the repo for tests purpose, and merge it to master once people are happy with the testing. Then, we could simply make the official/community json lists point to HEAD of master, avoiding the burden of constantly updating manually (and often forgetting to do so) the commit. Now that the use of testing branch is generalized (at least for official apps), we should implement this.

We discussed alternative scheme to solve this issue, the constrains of the problem, and the technical feasability.

We decide to move forward with the following plan :

  • Make a proof of concept on a non-critical app, like Hextris or 243.
  • We might need to tweak the script that builds the “real” list.json to see if things works as expected (they probably won’t right away, list_builder might be confused with HEAD, also the upgrade stored the commit number - to be investigated)
  • Once this is ready, we could apply this to all official apps
  • On the mid-term, for community : let packagers decide if they want to use this practice

Chatrooms : IRC Channels, bridges

During the last weeks, we got back the control over the #yunohost IRC channel on freenode. This has been done in parallel of the bridging Matrix<->IRC and IRC<->XMPP

  • Announcement here + on the forum : Jean-Baptiste wanted to do a post to sum up our “things” to communicate.
  • Group contact : frju365 (We can change it if you want)
  • Who moderate it ? Does this belongs to the Com Group ? (Perhaps add this in our Orga github md file https://github.com/YunoHost/project-organization )
  • Cloaks for members of the organization ?
  • Perhaps time to Introduce the different Matrix Channels too + the community.

Remaining item :

  • Shall we bind irc.freenode.net#yunohost to support@xmpp ?

    • During the meeting, we decide that yes and this is done a few minutes / hours later

Todo: add Matrix and IRC on this doc page https://yunohost.org/#/help

Chatrooms : which model on the mid/long-term

  • Short discussion about what should be the default mean of communication that we recommend to our users, also given the fact that “bot like” bridges can be confusing.
  • Not much more to say now, we conclude that “we will see” and see how the current situation goes.

Communication: Promoting Yunohost

  • I (frju365) spoke of it in my PM to the Conseil and to the different groups: https://forum.yunohost.org/t/promouvoir-yunohost/4342
    Another interesting thing said by @pierreozoux :
    [Meeting] February 6th, 2018
  • Dev to companies. Promote the software to the different “Open Companies”(I mean the companies who try to integrate Free Softwares) like OVH, Gandi, other VPS provider…
    cf. https://github.com/indiehosters/awesome-librehosters (Strategy : make easier for them to provide a complete infrastructure to their customers + making easier for the customer to install things.) Some of these LibreHosters uses already Yunohost.
  • How ? We send a mail to them. :wink:
  • Institution have choices of structures we can use : they make campaigns and promote sometimes one or two Softwares. We can try to mail them and intrduce Yunohost. Perhaps one day, the name of Yunohost could appear on one of the articles of the EFF, the Linux Foundation or the FSFE.

Todo :

  • Define a communication strategy : Which public(s) ? Question(s) ? How ? Why ?
  • Avoir une manière de communiquer
  • Present concrete question/project at the next meeting

Documentation : discussion about possible improvements

Todo :

  • Documentation UX from the first step (starting self-hosting) to the last (contributing)
  • Posts to encourage contributions : show that it’s easy to contribute, e.g. translation (tbd with Jean-Baptiste), documentation
  • Rewrite / integrate how-tos and resolution from forum’s posts into the documentation (possibly Discourse Wiki as backend)
  • Future : automatize this

Install script / instructions : are we okay for curl | bash ?

(Discussion reported as it’s not an urgent topic)

c.f. :

Proposal is to simplify this page https://yunohost.org/#/install_manually with :
1. A “quick install” with curl https://install.yunohost.org | bash
2. Propose a “cautious install” which does the same thing but with integrity/authenticity checks (and possibly reading the code…)

Stretch status

Next meeting

6th March, 2018 (first tuesday of the month)