Project

General

Profile

ContributorsMeetingJuly2019 » History » Version 169

Denis 'GNUtoo' Carikli, 08/07/2019 02:40 PM

1 1 Denis 'GNUtoo' Carikli
h1. Replicant contributors meeting the 27,28 July in France
2 2 Denis 'GNUtoo' Carikli
3 154 Denis 'GNUtoo' Carikli
{{toc}}
4
5 31 Denis 'GNUtoo' Carikli
h2. Date
6 2 Denis 'GNUtoo' Carikli
7 32 Denis 'GNUtoo' Carikli
The meeting will take place the 27 and 28 July 2019.
8 2 Denis 'GNUtoo' Carikli
9 13 Denis 'GNUtoo' Carikli
h2. Location
10
11 139 Denis 'GNUtoo' Carikli
The event will took place in the "April":https://en.wikipedia.org/wiki/April_(French_association) "office":https://april.org/en/contact-us. April is an association for the defense and promotion of free software.
12 1 Denis 'GNUtoo' Carikli
13 90 Denis 'GNUtoo' Carikli
*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.
14
*map:* https://www.agendadulibre.org/events/19754
15
*Phone number of the April office*: 01 78 76 92 80.
16
17
The April office is relatively close to the "Gare Montparnasse railway station.":https://en.wikipedia.org/wiki/Gare_Montparnasse
18 13 Denis 'GNUtoo' Carikli
19 24 Denis 'GNUtoo' Carikli
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":https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_4, "6":https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_6, "12":https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_12 and "13":https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_13.
20 16 Denis 'GNUtoo' Carikli
21 91 Denis 'GNUtoo' Carikli
h3. Related events
22
23 140 Denis 'GNUtoo' Carikli
On Friday, a dinner took place.
24 92 Denis 'GNUtoo' Carikli
25
*Dinner meeting time:* From 18h30 to 18h45
26 97 Denis 'GNUtoo' Carikli
*Dinner meeting location*: "Near the Montparnasse tower":https://redmine.replicant.us/attachments/1614/Friday_dinner_meeting.jpeg . The Montparnasse tower is very close to the Montparnasse railway station.
27 92 Denis 'GNUtoo' Carikli
28 140 Denis 'GNUtoo' Carikli
At 18h45 we planned to  try to find a Restaurant nearby.
29 91 Denis 'GNUtoo' Carikli
30 17 Denis 'GNUtoo' Carikli
h3. Airports
31
32
The two main airports near Paris are the "Roissy Charles de Gaulle International Airport":https://en.wikipedia.org/wiki/Charles_de_Gaulle_International_Airport and the "Paris Orly Airport":https://en.wikipedia.org/wiki/Orly_Airport.
33
34 25 Denis 'GNUtoo' Carikli
h4. Roissy Charles de Gaulle International Airport <-> Gare Montparnasse railway station
35 26 Denis 'GNUtoo' Carikli
36 21 Denis 'GNUtoo' Carikli
To get to the Gare Montparnasse railway station from the Roissy Charles de Gaulle International Airport by public transportation, you can take the "RER":https://en.wikipedia.org/wiki/R%C3%A9seau_Express_R%C3%A9gional B metro line up to the "Denfert-Rochereau station":https://en.wikipedia.org/wiki/Denfert-Rochereau_(Paris_M%C3%A9tro) where you can take the "line 6":https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_6 up to the Gare Montparnasse railway station.
37 25 Denis 'GNUtoo' Carikli
38
h4. Paris Orly Airport <-> Gare Montparnasse railway station
39 26 Denis 'GNUtoo' Carikli
40 33 Denis 'GNUtoo' Carikli
To get to the Gare Montparnasse railway station from the Paris Orly Airport by public transportation, you can take the "Orlyval":https://en.wikipedia.org/wiki/Orlyval up to the "Antony":https://en.wikipedia.org/wiki/Antony_(Paris_RER) stop, and from there take the "RER":https://en.wikipedia.org/wiki/R%C3%A9seau_Express_R%C3%A9gional "B":https://en.wikipedia.org/wiki/RER_B metro line up to the "Denfert-Rochereau station":https://en.wikipedia.org/wiki/Denfert-Rochereau_(Paris_M%C3%A9tro) where you can take the "line 6":https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_6 up to the Gare Montparnasse railway station.
41 21 Denis 'GNUtoo' Carikli
42 18 Denis 'GNUtoo' Carikli
h2. More information
43
44 19 Denis 'GNUtoo' Carikli
"Wikivoyage":https://en.wikivoyage.org has a page on "Paris":https://en.wikivoyage.org/wiki/Paris and "France":https://en.wikivoyage.org/wiki/France which have many practical information such as:
45
* Visa and other border requirements
46
* How to stay safe
47 1 Denis 'GNUtoo' Carikli
* The climate
48 18 Denis 'GNUtoo' Carikli
* Information on the public transportation
49 19 Denis 'GNUtoo' Carikli
* SIM cards
50 18 Denis 'GNUtoo' Carikli
51 29 Denis 'GNUtoo' Carikli
It also has pages on the "Roissy Charles de Gaulle International Airport":https://en.wikivoyage.org/wiki/Paris_Charles_de_Gaulle_Airport and the "Paris Orly Airport":https://en.wikivoyage.org/wiki/Paris_Orly_Airport with more details on the public transportation lines to use to go to Paris, which tickets to buy, etc.
52 20 Denis 'GNUtoo' Carikli
53 34 Denis 'GNUtoo' Carikli
h2. Contacting the organizers
54
55 141 Denis 'GNUtoo' Carikli
You could use the Replicant [[PrivateContact|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).
56 34 Denis 'GNUtoo' Carikli
57 133 Denis 'GNUtoo' Carikli
h2. Presentations
58 36 Denis 'GNUtoo' Carikli
59 148 Denis 'GNUtoo' Carikli
|_. Topic |_. Source code |_. Slides |_. Video |_. Rationale of the talk |
60
| Replicant history |/5. <pre>
61 167 Joey Hewitt
$ git clone --recursive https://git.replicant.us/GNUtoo/presentations.git
62 148 Denis 'GNUtoo' Carikli
$ cd path/to/presentation
63
$ make
64
</pre> | "pdf":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-history.pdf | Recorded
65
needs editing:
66
the curtains were left open 
67
=> We need to remove people in the street for privacy/intimity reasons
68
also needs encoding | * Has some context that might be useful for new Replicant contributors
69 146 Denis 'GNUtoo' Carikli
* Has information on the relationship between Replicant and GNU/Linux |
70 156 Denis 'GNUtoo' Carikli
| Replicant and bootloaders | "pdf":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-bootloaders.pdf | "720p webm":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-bootloaders.webm | * The Galaxy SIII (and similar devices) bootloader status is complicated and relevant to Replicant 9 |
71
| Replicant and modems: introduction | "pdf":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-modems-introduction.pdf | "720p webm":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-modems-introduction.webm |/3. * Meant to enable new contributors to work on the modem part |
72
| Replicant and modems: Samsung IPC | "pdf":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-modems-samsung-ipc.pdf | "720p webm":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-modems-samsung-ipc.webm |
73
| Replicant and oFono based Java RIL | "pdf":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-ofono-based-java-ril.pdf | "720p webm":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-ofono-based-java-ril.webm |
74 155 Denis 'GNUtoo' Carikli
| Porting AOSP for a new device | Made with Libreoffice which leaks metadata | "pdf":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/porting-aosp-for-a-new-device.pdf | Not recorded | |
75 156 Denis 'GNUtoo' Carikli
| Graphics acceleration on Replicant | Needs to be published | Needs to be published | "720p webm":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/graphics-acceleration-on-replicant.webm | |
76 134 Denis 'GNUtoo' Carikli
77 149 Denis 'GNUtoo' Carikli
*License:* "CC-BY-SA 4.0 International":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/COPYING
78 63 Denis 'GNUtoo' Carikli
79 1 Denis 'GNUtoo' Carikli
h2. Planned discussions
80 64 Denis 'GNUtoo' Carikli
81 157 Denis 'GNUtoo' Carikli
The discussions were not recorded for privacy/intimacy reasons but a sumary of some of the important ones are available [[ReplicantContributorsMeetingJuly2019#Discussion-results|below on this page]].
82
83 64 Denis 'GNUtoo' Carikli
|_. Topic |_. Time and dependencies |_. Status |_. Rationale |
84 1 Denis 'GNUtoo' Carikli
| Discussions on the bootloader situation on the Galaxy SIII and similar smartphones | After the talk on the bootloaders | | |
85
| Discussions on minimal requirement to accept a device in Replicant:
86 64 Denis 'GNUtoo' Carikli
* Do we still accept devices with modems that are not isolated?
87 65 Denis 'GNUtoo' Carikli
* Do we have plan to require free software bootloaders? 
88 66 Denis 'GNUtoo' Carikli
* Do we require replacable batteries? | After the talk on modems and bootloaders | | |
89
| Discussions on the future of Replicant:
90
* Which devices do we target
91
* Do we continue focusing on devices with signed bootloaders
92
* Allwinner tablets, upstream Linux, and scalability
93
* Devices with non-replacable batteries | After the talk on Replicant history | |
94 103 Grim Kriegor
| Discussion about Upstream components, design choices, and cultural re-appropriation of technology
95 36 Denis 'GNUtoo' Carikli
* [[Upstream]]
96 135 Denis 'GNUtoo' Carikli
* Issues when combining together different build systems (Example: Android build system with Kconfig)
97 47 Denis 'GNUtoo' Carikli
* 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
98 142 Denis 'GNUtoo' Carikli
* Android upstream anti-features and political design choices
99 131 Denis 'GNUtoo' Carikli
* How subjective security is, threat models, and the difference between free software and device maker point of view | Please take a look at [[Upstream]] before attending if possible. | | |
100 2 Denis 'GNUtoo' Carikli
101
h2. Known schedule constraints
102
103 99 Denis 'GNUtoo' Carikli
* On Sunday, the April offices had to be closed at 16h, so we needed to already have packed everything and left the room at that time.
104 98 Joonas Kylmälä
105 46 Denis 'GNUtoo' Carikli
h2. Still being defined, to be confirmed
106 47 Denis 'GNUtoo' Carikli
107 46 Denis 'GNUtoo' Carikli
Precise schedule:
108 37 Denis 'GNUtoo' Carikli
*Saturday:* 10:00 -> 17:00 (possibly continuing to the night)?
109 43 Denis 'GNUtoo' Carikli
*Sunday:* 10:00 -> 14:00?
110 7 Denis 'GNUtoo' Carikli
111 2 Denis 'GNUtoo' Carikli
*Poll for using the April offices*: https://framadate.org/ReplicantContributorMeetingJuly2019RoomOccupation
112 4 Denis 'GNUtoo' Carikli
113 5 Denis 'GNUtoo' Carikli
h3. Presentations:
114
115 1 Denis 'GNUtoo' Carikli
* The Graphic stack in Replicant 9
116
* Porting Replicant to Android 9 by Joonas Kylmälä?
117 61 Denis 'GNUtoo' Carikli
* A discussion about [[Upstream]] components, [[Upstream#Design-decisions|design choices]], and cultural re-appropriation of technology?
118 37 Denis 'GNUtoo' Carikli
** How subjective security is, threat models, and the difference between free software and device maker point of view
119 45 Fil Bergamo
** 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
120
** Android upstream anti-features and political design choices
121
** Issues when combining together different build systems (Example: Android build system with Kconfig)
122
123 37 Denis 'GNUtoo' Carikli
124
h3. Over a cup of coffee:
125
126
* Fil is available for informal chatting about RepWifi
127 85 Denis 'GNUtoo' Carikli
128
h3. Hardware
129
130 67 Denis 'GNUtoo' Carikli
h4. Devices
131 70 Denis 'GNUtoo' Carikli
132 69 Denis 'GNUtoo' Carikli
Good practices:
133
* It would be a good idea to put your name on a sticker on the device if possible
134
135
|_. Person |_. Hardware |_. Comments |_. Usage |
136 67 Denis 'GNUtoo' Carikli
|/12. GNUtoo | Galaxy SIII (I9300) with the stock bootloader | |
137
| Galaxy SIII 4G (I9305) with the stock bootloader | |
138
| Galaxy SIII 4G (I9305) with u-boot | |
139 69 Denis 'GNUtoo' Carikli
| Galaxy Nexus (I9250) with the stock bootloader | |
140
| Galaxy SII (I9100) with the stock bootloader | |
141
| GTA04 A3 | | |
142 76 Denis 'GNUtoo' Carikli
| GTA04 A4 | | |
143 74 Denis 'GNUtoo' Carikli
| Optimus black (P970) | | |
144 75 Denis 'GNUtoo' Carikli
| GTA01 |/4. Used in a presentation about Replicant history | |
145
| GTA02 | |
146
| HTC Dream | |
147
| N900 | Testing the battery charger driver is still needed but require a heavy PSU |
148 67 Denis 'GNUtoo' Carikli
|/4. Fil | Galaxy Note 2 (N7100) stock bootloader | [Working] Available for non-critical tests | * Test the upstream touchkey driver
149 81 Denis 'GNUtoo' Carikli
=> TODO:
150 110 Denis 'GNUtoo' Carikli
* Bring a Parabola microSD (GNUtoo)
151 119 Denis 'GNUtoo' Carikli
* Test the patch with an I9300
152 104 Denis 'GNUtoo' Carikli
* Rebase the patch on master or linux-next |
153 79 Denis 'GNUtoo' Carikli
| Galaxy SIII (I9300) stock bootloader | [Working] Test Subject available for any experiment | |
154 80 Denis 'GNUtoo' Carikli
| Galaxy SIII (I9300) stock bootloader | [Bricked] available for hardware hacking | * Test "fixing the phone":https://media.ccc.de/v/34c3-8784-emmc_hacking_or_how_i_fixed_long-dead_galaxy_s3_phones |
155 37 Denis 'GNUtoo' Carikli
| Galaxy Tab 2 7.0 (GT P3100) | Property of the Replicant Project | * -Add support for it in the [[BackupTheEFS]] instructions- |
156 168 Denis 'GNUtoo' Carikli
|/2. Paulk | Galaxy Note (N7000) | | * -Add support for it in the [[BackupTheEFS]] instructions- |
157 169 Denis 'GNUtoo' Carikli
| Galaxy Tab 2 10.1 (P5100) | | * Add support for it in the [[BackupTheEFS]] instructions |
158 71 Denis 'GNUtoo' Carikli
|\2. Looking for a Galaxy Note 8.0 (N5100) | | * Add support for it in the [[BackupTheEFS]] instructions |
159 84 Denis 'GNUtoo' Carikli
| | Add devices you can bring here or you want other to bring | Add comments, requirements, etc | Add what you want to do with the device or other people's device |
160 37 Denis 'GNUtoo' Carikli
161
h4. Debug utilities
162 108 Denis 'GNUtoo' Carikli
163 84 Denis 'GNUtoo' Carikli
|_. Person |_. Hardware |_. Comments |_. Usage |
164 37 Denis 'GNUtoo' Carikli
|/6. GNUtoo | Serial port cable with variable resistors |  |
165 44 Fil Bergamo
| Multimeter |  |
166 105 Denis 'GNUtoo' Carikli
| Simtrace 1: Can get the dialog between the modem and the SIM card in wireshark |  |
167
| SIM card that is not recognized in Replicant (STK related?) | Test on Replicant 4.2 and on Replicant 6.0 |
168
| SIM card + phone that can trigger the audio call issue | |
169
| Sigrok compatible adjustable power supply | Not sure to bring it (heavy) |
170 107 Denis 'GNUtoo' Carikli
|/1. Fil | SIM card that is not recognized in Replican 6 | |
171 129 Denis 'GNUtoo' Carikli
172 128 Denis 'GNUtoo' Carikli
h2. Discussion results
173 129 Denis 'GNUtoo' Carikli
174 158 Denis 'GNUtoo' Carikli
h3.  Do we care about supporting devices with non-removable batteries? 
175
176
Points that were mentioned or discussed:
177
* This impacts the design decisions as supporting new devices through upstream code takes longer than hacking together the vendor code not to require nonfree libraries.
178
179
* Because of that either users, repair shops or Replicant device vendors will need to have a viable way to change the non-removable battery.
180
181
* If this is not the case it would force the Replicant project to race to try to support a device while it's still being sold new. If not users buying devices would have a battery that doesn't last enough when bought second hand.
182
183
* It's too hard, even for vendors like Technoethical which have some expertise in that area to upgrade non-removable batteries when the case is sealed. Practically speaking that could be done but the end result would not be as good as the new device, like the sealing would not be as good, making users damage the phone as they would expect the sealing to work.
184
185 162 Denis 'GNUtoo' Carikli
Consensus in that meeting:
186
* The cost for Replicant would be too high, so participant thought that not caring about devices without non-removable batteries and prioritize to support devices in Replicant through upstream project was better
187 158 Denis 'GNUtoo' Carikli
188 160 Denis 'GNUtoo' Carikli
h3. Do we require free software bootloaders ?
189 158 Denis 'GNUtoo' Carikli
190
Points that were mentioned or discussed:
191
* The Pinephone should be released in the next months (3 months?) but it's not released yet.
192 1 Denis 'GNUtoo' Carikli
* Some other devices with free software bootloaders are not released yet either
193
* Some concerns were raised on the fact that the Librem5 bootloader might contain nonfree software, which Replicant doesn't want to redistribute. A link to "Purism's plans":https://puri.sm/posts/librem5-solving-the-first-fsf-ryf-hurdle/ was also mentioned. Paul also mentioned that it might be possible that replacing the nonfree part was doable and that it would solve the issue
194
195 162 Denis 'GNUtoo' Carikli
Consensus in that meeting:
196
* Too early to do that: Replicant 9 is not out yet and it will work on devices with nonfree bootloader at first, but the work could be reused later by devices with free software bootloaders
197 160 Denis 'GNUtoo' Carikli
198
h3. Do we require isolated modems ?
199
200
Points that were mentioned or discussed:
201
* On one hand it would make it easier for users to understand the freedom privacy and security they are getting with Replicant. The information is often distorted up to the point where some users think that Puri.sm laptops are running only free software (while in reality there are non-free software involved in the boot such as the FSP, and a minimal Management Engine firmware). 
202
* On the other hand some users might already have devices that were supported by Replicant before and that don't have an isolated modem. This would leave such users with old versions of Replicant.
203
204
Consensus in that meeting:
205
* The devices with non-isolated modems might not be easy to support in Replicant 9 anyway, so we could drop them
206
* This will need to be announced for the Replicant 9 release as this way the information would propagate more efficiently to people.
207 158 Denis 'GNUtoo' Carikli
208
h3. How to handle the various keys used to sign releases, and other related things and should the recovery check signatures 
209
210
Points that were mentioned or discussed:
211
* The installation instructions need to be as simple as possible => If users have to check the signatures only once it's better. So now users check the recovery only, which then checks the rest.
212 1 Denis 'GNUtoo' Carikli
* The people involved in local Replicant install parties (in Paris) will help local Replicant users to update the recovery
213 158 Denis 'GNUtoo' Carikli
* 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 
214
215
Consensus in that meeting:
216
* Keys usage in the short term: Developers sign with their keys
217 1 Denis 'GNUtoo' Carikli
* 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 
218 158 Denis 'GNUtoo' Carikli
* Keep checking signatures by default in the recovery
219
220
h3. Improve information for current and potential Replicant users
221
222
Points that were mentioned or discussed:
223
* Fil Bergamo plans to work on an unified table that has various information on devices supported by Replicant:
224 1 Denis 'GNUtoo' Carikli
* He plans to add in information about what hardware feature are supported or not
225 158 Denis 'GNUtoo' Carikli
* He plan to add information about how likely are the devices to be supported in the next Replicant 6 and 9 releases
226
* A "device getting guide" was also mentioned, to help users find which supported devices are the best for them
227
228
h3. Improving the Replicant website
229
230 1 Denis 'GNUtoo' Carikli
Points that were mentioned or discussed:
231 161 Denis 'GNUtoo' Carikli
* It would be nice to make information for users more accessible on the main page (https://replicant.us)
232 1 Denis 'GNUtoo' Carikli
233 159 Denis 'GNUtoo' Carikli
Consensus in that meeting:
234
* Also enable translations in other languages than English in the wiki, but warn readers that the information might be outdated when it's translated.
235
236 1 Denis 'GNUtoo' Carikli
h3. Making it easier for anyone to contribute to Replicant
237
238 159 Denis 'GNUtoo' Carikli
Points that were mentioned or discussed:
239
* A question was raised about making a welcome page for new Replicant contributors. That page is supposed to already exist in the wiki => Find it and look at it.
240
241
Consensus in that meeting:
242
* Create working groups on various part of Replicant (such as the documentation, f-droid issues, etc) and split the Redmine instance in sub-project accordingly. It would also enable to have different settings for the subgroups.
243
* Modify the [[People]] page to enable any contributor or potential contributors to add themselves in that page with the topic they would want to work on and the skills they have. The Replicant front page (https://replicant.us) would be modified to make sure that this is visible to potential contributors.
244
* Add pointers to C courses and to where to get the skills required to contribute to the Replicant system source code.
245
* Try to find a way to make a *simple* presentation on Replicant, that would give a simple overview how how Replicant and the hardware works.
246 158 Denis 'GNUtoo' Carikli
247
h3. Funding work on f-droid
248
249 163 Denis 'GNUtoo' Carikli
Consensus in that meeting:
250
* Enabling Fil Bergamo to work on making F-Droid FSDG compliant through NlNet funding
251 1 Denis 'GNUtoo' Carikli
252 163 Denis 'GNUtoo' Carikli
h3. Using oFono RIL
253 1 Denis 'GNUtoo' Carikli
254 163 Denis 'GNUtoo' Carikli
Points that were mentioned or discussed:
255
* Enabling Fil Bergamo to work on making that through NlNet funding
256
257
Consensus in that meeting:
258
* Using oFono RIL is a good idea, even if it's unmaintained. Replicant would then become its maintainer
259 158 Denis 'GNUtoo' Carikli
260
h3. FSDG compliance and How to moderate the forums 
261
262
Points that were mentioned or discussed:
263
* 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.
264
* Legal issues were raised as well when linking to external material and such.
265
* Some examples were given on how to handle some common issues:
266
** Link to a book chapter advocating for DRM on the FSF website:
267 124 Denis 'GNUtoo' Carikli
  *URL:* https://www.fsf.org/blogs/sysadmin/the-management-engine-an-attack-on-computer-users-freedom
268
  <pre>
269
  For more information about Digital Restrictions Management and the Management Engine,
270
  see from page 191 [...].
271
  This chapter tries to justify the usage of Digital Restrictions Management (DRM).
272 1 Denis 'GNUtoo' Carikli
  DRM is totally unacceptable as it requires the users not to be in control of their
273 124 Denis 'GNUtoo' Carikli
  computers to effectively prevent them from exercising their legal rights (such as fair
274
  use, or being able to copy published works). That chapter clearly shows the link between
275
  preventing users from controlling their hardware and effective DRM.
276 1 Denis 'GNUtoo' Carikli
  </pre>
277 158 Denis 'GNUtoo' Carikli
** Link to service manuals etc:
278 1 Denis 'GNUtoo' Carikli
  *URL:* [[NexusSI902xSerial]]
279 125 Denis 'GNUtoo' Carikli
  <pre>
280
  These documents are the propriety of Samsung Electronics and are not
281
  hosted by the Replicant project. However, some excerpts from these documents
282 1 Denis 'GNUtoo' Carikli
  are provided, for the purpose of providing technical evidence of the facts that
283
  are mentioned in this page. We believe that this particular use of the copyrighted
284
  work is fair use.
285
  </pre>
286 158 Denis 'GNUtoo' Carikli
** Mention of proprietary software in Replicant wiki, including how to "use" it:
287 1 Denis 'GNUtoo' Carikli
  *URL*: [[SamsungGalaxyBackdoor]]
288
  <pre>  
289
  The following analysis was conducted using the libsec-ril.so binary file
290
   (the incriminated proprietary software) as extracted from the CyanogenMod 10.1.3
291
   system zip for the Galaxy S 3 (I9300), from location system/lib/libsec-ril.so.
292
  </pre>
293 158 Denis 'GNUtoo' Carikli
** GNU Kind Communications Guidelines:
294 1 Denis 'GNUtoo' Carikli
  *URL:* https://www.gnu.org/philosophy/kind-communication.html
295
  <pre>
296
  By contrast, to suggest that others use nonfree software opposes the basic
297
  principles of GNU, so it is not allowed in GNU Project discussions.
298
  </pre>
299 158 Denis 'GNUtoo' Carikli
** Trisquel Community Guidelines:
300 1 Denis 'GNUtoo' Carikli
  *URL:* https://trisquel.info/en/wiki/trisquel-community-guidelines
301
  <pre>
302
  Our community's resources --the forum, documentation, etc--
303 125 Denis 'GNUtoo' Carikli
  are for free software only. Please do not distribute,
304
  recommend, or support non-free software here.
305
  </pre>
306 158 Denis 'GNUtoo' Carikli
307 1 Denis 'GNUtoo' Carikli
People in this discussion realized that the forum is relatively small so it's doable to have it moderated.
308 158 Denis 'GNUtoo' Carikli
309 1 Denis 'GNUtoo' Carikli
Plan of action:
310 158 Denis 'GNUtoo' Carikli
* Describe what should is acceptable or not for the forums, wiki, etc
311
** "Please do not distribute, recommend, or support non-free software here"
312
** Also describe the above examples there if possible to help people linking to information in the right way.
313
* How to handle violations of the policy
314
** 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. |
315
316
317
h3. Do we ship some external applications in Replicant
318
319
Points that were mentioned or discussed:
320
* Yes, but how does the selection process would look like?
321 152 Denis 'GNUtoo' Carikli
* Which browser we should add => One that works and that doesn't have freedom privacy or security issues 
322 158 Denis 'GNUtoo' Carikli
* Firefox Lite was mentioned but it was dismissed due to very concerning privacy issues with its privacy policy
323
324
h3. Using wayland for the graphic stack?
325 1 Denis 'GNUtoo' Carikli
326 164 Denis 'GNUtoo' Carikli
Points that were mentioned or discussed:
327
* Using "wayland":https://www.collabora.com/news-and-blog/blog/2019/04/01/running-android-next-to-wayland/ for the graphics backend
328
* Might loose some performance due to the fact that Wayland plug in Android too low in the stack
329
* No performances test were performed with Wayland.
330 158 Denis 'GNUtoo' Carikli
331
h3. AOSP vs LineageOS
332
333
Points that were mentioned or discussed:
334
* Using LineageOS repos makes less sense due to consensus about supporting devices with removable batteries.
335 111 Denis 'GNUtoo' Carikli
* AOSP has stable/tagged releases whereas LineageOS lacks that 
336 147 Denis 'GNUtoo' Carikli
* AOSP is also better documented
337 113 Denis 'GNUtoo' Carikli
Since:
338 117 Denis 'GNUtoo' Carikli
* LineageOS uses many repositories from AOSP already (Implicit at the time of the talk, not explicited)
339 1 Denis 'GNUtoo' Carikli
* we still want some of the features from LineageOS (like root)
340
We will need to look into more details which repositories to use from LineageOS and from AOSP 
341 158 Denis 'GNUtoo' Carikli
342 162 Denis 'GNUtoo' Carikli
Consensus in that meeting:
343
* Getting closer to AOSP
344 117 Denis 'GNUtoo' Carikli
345 165 Denis 'GNUtoo' Carikli
h3. Android upstream vs GNU/Linux upstream
346
347
Consensus in that meeting:
348
* Getting closer to GNU/Linux upstream (for hardware support like modems, etc)
349
350
351 117 Denis 'GNUtoo' Carikli
h2. Video encoding
352 113 Denis 'GNUtoo' Carikli
353
h3. Sound
354
355
The microphone was mono, with only a channel from the left. So we need to create mono audio files from the videos.
356
357
To make the sound go in both channel, do the following in Audacity:
358
359
* Create a new project with File -> New
360
* Import the video file with File -> Open
361
* Click on the audio channel -> Split Stereo to Mono
362
* Delete the second channel
363
* File -> Export -> Export as WAV
364
365 114 Denis 'GNUtoo' Carikli
h3. Video 
366
367
The videos were recorded with some equipement that was lent to us:
368
* A camera that outputed mp4 files on an SD card
369
* One wireless microphone
370
371
=> Next time ask if they have a second microphone available for questions.
372
373
* The videos are splitted in several mp4 files
374 115 Denis 'GNUtoo' Carikli
* The part before the presentation has to be removed
375
376
Kdenlive is being used for that.
377
378
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).
379
380 116 Denis 'GNUtoo' Carikli
To workaround that the following was used:
381
* gnome3 (probably under wayland)
382 1 Denis 'GNUtoo' Carikli
* pushbuffer enabled in the module parameters for nouveau
383
384
=> It's still slow while zomming in the timeline but it manage not to freeze the whole graphics stack.
385
386
To edit a video with kdenlive:
387
* create a project, and select the right resolution (720p 25fps here)
388
* Import the videos files to use with project->Add clip
389
* Also import the mono audio files that you just converted with audacious
390
* Import the clips from the Project bin into the timeline with drag and drop
391
* Right click on the imported click in the timeline and select Ungroup
392
* Right click on the audio below, and select remove
393
* Import the mono audio file from the Project bin in the timeline with drag and drop
394
395
Once that is done you can remove the part before the presentation this way:
396
* In the timeline you can zoom at the maximum level 
397
* Use the cisors to divide the zone in two, you only need to click once with the left click to separate two zones
398
* Select the arow again (on the left of the cisors) and right click on the zone to remove, and select remove
399
* 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.
400
401
h2. Files