Replicant

h1. Replicant Project Online Meetings

{{toc}}

h2. Very first meeting.

h3. Date, time, location and protocols

18 June 2024 at 19:00 CEST

Mumble on the mumble.replicant.us self hosted Mumble server.

*Public announcement*: https://blog.replicant.us/2024/06/first-online-replicant-meeting/

h3. Meeting schedule

# Presentation of attendees (very short).

# Summary of the current work:

## WordPress conversion to a static website (GNUtoo);

## other tiny infrastructure work (GNUtoo);

## building 100% free Android SDKs (wizzard);

## status of PinePhone work (NLnet funded) (GNUtoo, dllud).

# Status of the Steering Committee and adding dllud to Steering Committee.

# Call for the (Community) Manager.

# How/when to setup the next meeting.

# Other discussions.

h3. Meeting summary

*Attendees*: dllud, GNUtoo, jack_kekzoz, Johannes__dolphinana, Putti, tct, thatch, wizzard

*Duration*: 1h30m

All scheduled topics were addressed.

h4. People's presentation:

First the people presented themselves. Both GNUtoo and wizzard also started presenting what they worked on in more details:

** dllud: <TODO: please dllud fill in your presentation if you remember it>.

** GNUtoo was recently involved in sysadmin work and on the conversion of the blog from Wordpress to a static website (with haunt). He also applied for funding for working on the PinePhone but got sidetracked with another somewhat related project (GNU Boot) because he initially planned to use Libreboot to produce the bootloader for the PinePhone.

** jack_kekzoz helps answering questions on IRC. jack_kekzoz is also a postmarketOS contributors for devices with an Exynos system on a chip. jack_kekzoz also has a Galaxy Note II LTE (TTN71005?).

** wizzard is involved in automatizing builds of a free Android SDK.

* Johannes__dolphinana wants to contribute to Replicant.

* As we understood, thatch is interested in community networks and devices that can work with them and wants to learn how to contribute to Replicant on work that goes in this direction.

* 'tct' couldn't talk due to microphones issues but 'tct' is most likely Tiberiu from Technoetical.

h4. Status of the work done before the meeting:

* For the conversion of the blog to a static website, GNUtoo explained:

** why we needed a static blog: we cannot easily collaborate to write a blog post in WordPress: we need to share the article by mail, discuss parts of it, include improvements, in a way that is transparent, and git + mail works best for that

*** why haunt was chosen for that: haunt is very flexible and he is also migrating the GNU Boot website to haunt, so that shares the burden of learning between both projects.

** The current status:

*** We still need to be able to have comments through the Replicant mailing list

*** We also need to not break URLs

*** As-is the blog is deployed on https://blog.test.replicant.us and the tools provided with its source code enable to import back the articles to WordPress so right now even if the work is not finished, we can still save a lot of time by collaborating by mail and/or with git.

* For the sysadmin work, GNUtoo also explained his current work:

** Issues with the git hosting: There are permission issues with users repositories. Work is done to clarify which permissions are needed and unify the apache, git, gitolite and cgit configurations as there were some discrepancies between some of them. At the time of the meeting we assumed that the issues were fixed but there are still problems with gitolite as pushing got broken.

** Work on mumble.replicant.us was made to enable this meeting.

* Work on SDK builds by wizard:

** This work is made possible through the combination of many pieces: Starfish maintains an "SDK-Rebuilds":https://codeberg.org/Starfish/SDK-Rebuilds project that has code to build the SDK. The Taler project gave us some server access, and wizzard is automatizing the builds with forgejo runner and integrating that into a Trisquel container to make sure they also work on an FSDG distribution.

** A Question was asked about signing the releases. And since the goal is to automatize as much as possible (otherwise maintenance takes too much time) if there are signatures, it would need to be automatized somehow or not done by wizzard.

** GNUtoo promised to open a new project for the SDK builds (now available "here":https://redmine.replicant.us/projects/sdk-rebuild).

** Due to constraints of the hosting, wizzard needs a Trisquel docker container. So as GNUtoo already worked on projects that create Trisquel containers he promised to producing one that wizzard could reuse.

h4. Other topics

* How/when to setup the next meeting

To be held in 2 months on the same medium (Mumble).

Non-scheduled topics that were addressed:

# The reasoning behind the drop of future support for all current phones: 2G and 3G sunset. We should write an article just about it.

# thatch addressed the need for independent communication infrastructures (e.g. meshnets) which unfortunately are out-of-scope for the time being (more developers needed on Replicant).

# jack_kekzoz and Putti showed interest on working on the Samsung Galaxy S III / Note 2 4G. The lack of VoLTE on these models may be address with https://github.com/phhusson/ims and https://github.com/DoubangoTelecom/imsdroid/

# Johannes__dolphinana raised the need for archiving and publishing the #replicant IRC logs. GNUtoo hinted that "matterbridge":https://git.replicant.us/infrastructure/matterbridge/ may have a logging function. Help on this task is appreciated.

h2. 2nd meeting

h3. Date, time, location and protocols

18 August 2024 19:00 CEST

mumble.replicant.us