Replicant contributors meeting the 27,28 July in France¶

Date¶

The meeting will take place the 27 and 28 July 2019.

Location¶

The event will take place in the April office. April is an association for the defense and promotion of free software.

Precise location: April, 44/46 rue de l'Ouest, bâtiment 8, 75014 Paris (It's accesible through the "place de la Catalogne", on the left of the "Biocoop" supermarket). Select "April" on the intercomm.
map: https://www.agendadulibre.org/events/19754
Phone number of the April office: 01 78 76 92 80.

The April office is relatively close to the Gare Montparnasse railway station.

In addition to trains, Gare Montparnasse railway station has also, in the same building, there is a metro station where you can access the metro lines 4, 6, 12 and 13.

Related events¶

On Friday, a dinner will take place.

Dinner meeting time: From 18h30 to 18h45
Dinner meeting location: Near the Montparnasse tower . The Montparnasse tower is very close to the Montparnasse railway station.

At 18h45 we will try to find a Restaurant nearby.

Airports¶

The two main airports near Paris are the Roissy Charles de Gaulle International Airport and the Paris Orly Airport.

Roissy Charles de Gaulle International Airport <-> Gare Montparnasse railway station¶

To get to the Gare Montparnasse railway station from the Roissy Charles de Gaulle International Airport by public transportation, you can take the RER B metro line up to the Denfert-Rochereau station where you can take the line 6 up to the Gare Montparnasse railway station.

Paris Orly Airport <-> Gare Montparnasse railway station¶

To get to the Gare Montparnasse railway station from the Paris Orly Airport by public transportation, you can take the Orlyval up to the Antony stop, and from there take the RER B metro line up to the Denfert-Rochereau station where you can take the line 6 up to the Gare Montparnasse railway station.

More information¶

• Visa and other border requirements
• How to stay safe
• The climate
• Information on the public transportation
• SIM cards

It also has pages on the Roissy Charles de Gaulle International Airport and the Paris Orly Airport with more details on the public transportation lines to use to go to Paris, which tickets to buy, etc.

Contacting the organizers¶

You can use the Replicant private contact mail address in advance to obtain the cellphone number of an organizer to be able to use it in case of issue (like being lost, not finding the location of the meeting, etc).

Confirmed presentations¶

• On Sunday, the April offices will be closed at 16h, so we need to already have packed everything and left the room at this time.

Still being defined, to be confirmed¶

Precise schedule:
Saturday: 10:00 -> 17:00 (possibly continuing to the night)?
Sunday: 10:00 -> 14:00?

Poll for using the April offices: https://framadate.org/ReplicantContributorMeetingJuly2019RoomOccupation

Presentations:¶

• The Graphic stack in Replicant 9
• Porting Replicant to Android 9 by Joonas Kylmälä?
• A discussion about Upstream components, design choices, and cultural re-appropriation of technology?
  • How subjective security is, threat models, and the difference between free software and device maker point of view
  • Sharing work with GNU/Linux to enable more political control and cultural re-appropriation of mobile device in the long run, and the risk associated with it
  • Android upstream anti-features and political design choices
  • Issues when combining together different build systems (Example: Android build system with Kconfig)

Over a cup of coffee:¶

• Fil is available for informal chatting about RepWifi

Hardware¶

Devices¶

• It would be a good idea to put your name on a sticker on the device if possible

Debug utilities¶

Discussion results¶

• The people involved in local Replicant install parties (in Paris) will help local Replicant users to update the recovery
• Technoethical previously stated that the users having bought devices already running Replicant through them are either able to install new recoveries or that they are able to help them do it |\2. * Keys usage in the short term: Developers sign with their keys
• Keys usage in the longer term (requires time to implement it): use a keyring with the public key of several Replicant developers, like it is done in Parabola with the parabola-keyring package
• Keep checking signatures by default in the recovery | | Improve information for current and potential Replicant users |\3. * Fil Bergamo plans to work on an unified table that has various information on devices supported by Replicant:
• He plans to add in information about what hardware feature are supported or not
• He plan to add information about how likely are the devices to be supported in the next Replicant 6 and 9 releases | | Improving the Replicant website |\3. *It would be nice to make information for users more accesible on the main page (https://replicant.us) | | Making it easier for anyone to contribute to Replicant | | Funding work on f-droid | | Funding work on oFono RIL | | FSDG compliance and How to moderate the forums |\3. One of the main issue was the fact that people might have legitimate interest in linking to post from XDA which would contain both very valuable technical information, while not respecting the FSDG guidelines at all and pushing users to run nonfree software.
  Legal issues were raised as well when linking to external material and such.
  Some examples were given on how to handle some common issues:
• Link to a book chapter advocating for DRM on the FSF website:
  URL: https://www.fsf.org/blogs/sysadmin/the-management-engine-an-attack-on-computer-users-freedom
  

    For more information about Digital Restrictions Management and the Management Engine,
    see from page 191 [...].
    This chapter tries to justify the usage of Digital Restrictions Management (DRM).
    DRM is totally unacceptable as it requires the users not to be in control of their
    computers to effectively prevent them from exercising their legal rights (such as fair
    use, or being able to copy published works). That chapter clearly shows the link between
    preventing users from controlling their hardware and effective DRM.
    

• Link to service manuals etc:
  URL: NexusSI902xSerial
  

    These documents are the propriety of Samsung Electronics and are not
    hosted by the Replicant project. However, some excerpts from these documents
    are provided, for the purpose of providing technical evidence of the facts that
    are mentioned in this page. We believe that this particular use of the copyrighted
    work is fair use.
    

• Mention of proprietary software in Replicant wiki, including how to "use" it:
  URL: SamsungGalaxyBackdoor
  

    
    The following analysis was conducted using the libsec-ril.so binary file
     (the incriminated proprietary software) as extracted from the CyanogenMod 10.1.3
     system zip for the Galaxy S 3 (I9300), from location system/lib/libsec-ril.so.
    

• GNU Kind Communications Guidelines:
  URL: https://www.gnu.org/philosophy/kind-communication.html
  

    By contrast, to suggest that others use nonfree software opposes the basic
    principles of GNU, so it is not allowed in GNU Project discussions.
    

• Trisquel Community Guidelines:
  URL: https://trisquel.info/en/wiki/trisquel-community-guidelines
  

    Our community's resources --the forum, documentation, etc--
    are for free software only. Please do not distribute,
    recommend, or support non-free software here.
    

People in this discussion realized that the forum is relatively small so it's doable to have it moderated.

Plan of action:
1. Describe what should is acceptable or not for the forums, wiki, etc
=> "Please do not distribute, recommend, or support non-free software here"
=> Also describe the above examples there if possible to help people linking to information in the right way.
2. How to handle violations of the policy
=> On case by case basis. Help educate people on the matter and how to deal with it, especially on how to link to external information. |

Video encoding¶

Sound¶

The microphone was mono, with only a channel from the left. So we need to create mono audio files from the videos.

To make the sound go in both channel, do the following in Audacity:

• Create a new project with File -> New
• Import the video file with File -> Open
• Click on the audio channel -> Split Stereo to Mono
• Delete the second channel
• File -> Export -> Export Audio

Video¶

• A camera that outputed mp4 files on an SD card
• One wireless microphone

=> Next time ask if they have a second microphone available for questions.

• The videos are splitted in several mp4 files
• The part before the presentation has to be removed

Kdenlive is being used for that.

Using kdenlive with Nouveau (with default settings), xfce4 under Parabola manage to freeze the screen (there are some messages like "nouveau: kernel rejected pushbuf: Cannot allocate memory" that can be observed when launching kdenlive through SSH).

• gnome3 (probably under wayland)
• pushbuffer enabled in the module parameters for nouveau

=> It's still slow while zomming in the timeline but it manage not to freeze the whole graphics stack.

• create a project, and select the right resolution (720p 25fps here)
• Import the videos files to use with project->Add clip
• Also import the mono audio files that you just converted with audacious
• Import the clips from the Project bin into the timeline with drag and drop
• Right click on the imported click in the timeline and select Ungroup
• Right click on the audio below, and select remove
• Import the mono audio file from the Project bin in the timeline with drag and drop

• In the timeline you can zoom at the maximum level
• Use the cisors to divide the zone in two, you only need to click once with the left click to separate two zones
• Select the arow again (on the left of the cisors) and right click on the zone to remove, and select remove
• Do that for both the video and the audio tracks, then move both to the left to remove the gap done by the removal if there is one.

Files¶