Project

General

Profile

ContributorsMeetingJuly2019 » History » Version 154

Denis 'GNUtoo' Carikli, 07/31/2019 05:26 PM
Add table of contents

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 150 Denis 'GNUtoo' Carikli
$ 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 148 Denis 'GNUtoo' Carikli
| Replicant and bootloaders | "pdf":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-bootloaders.pdf | "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 | "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 | "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 | "webm":https://ftp.osuosl.org/pub/replicant/conferences/replicant-contributors-meeting-july-2019-france/replicant-and-ofono-based-java-ril.webm |
74 153 Denis 'GNUtoo' Carikli
| Porting AOSP for a new device | Made with Libreoffice which leaks metadata | "pdf":https://redmine.replicant.us/attachments/download/1618/Porting-AOSP.pdf (final PDF?) | Not recorded | |
75 148 Denis 'GNUtoo' Carikli
| Graphics acceleration on Replicant | Needs to be published | Needs to be published | "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
|_. Topic |_. Time and dependencies |_. Status |_. Rationale |
82 1 Denis 'GNUtoo' Carikli
| Discussions on the bootloader situation on the Galaxy SIII and similar smartphones | After the talk on the bootloaders | | |
83
| Discussions on minimal requirement to accept a device in Replicant:
84 64 Denis 'GNUtoo' Carikli
* Do we still accept devices with modems that are not isolated?
85 65 Denis 'GNUtoo' Carikli
* Do we have plan to require free software bootloaders? 
86 66 Denis 'GNUtoo' Carikli
* Do we require replacable batteries? | After the talk on modems and bootloaders | | |
87
| Discussions on the future of Replicant:
88
* Which devices do we target
89
* Do we continue focusing on devices with signed bootloaders
90
* Allwinner tablets, upstream Linux, and scalability
91
* Devices with non-replacable batteries | After the talk on Replicant history | |
92 103 Grim Kriegor
| Discussion about Upstream components, design choices, and cultural re-appropriation of technology
93 36 Denis 'GNUtoo' Carikli
* [[Upstream]]
94 135 Denis 'GNUtoo' Carikli
* Issues when combining together different build systems (Example: Android build system with Kconfig)
95 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
96 142 Denis 'GNUtoo' Carikli
* Android upstream anti-features and political design choices
97 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. | | |
98 2 Denis 'GNUtoo' Carikli
99
h2. Known schedule constraints
100
101 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.
102 98 Joonas Kylmälä
103 46 Denis 'GNUtoo' Carikli
h2. Still being defined, to be confirmed
104 47 Denis 'GNUtoo' Carikli
105 46 Denis 'GNUtoo' Carikli
Precise schedule:
106 37 Denis 'GNUtoo' Carikli
*Saturday:* 10:00 -> 17:00 (possibly continuing to the night)?
107 43 Denis 'GNUtoo' Carikli
*Sunday:* 10:00 -> 14:00?
108 7 Denis 'GNUtoo' Carikli
109 2 Denis 'GNUtoo' Carikli
*Poll for using the April offices*: https://framadate.org/ReplicantContributorMeetingJuly2019RoomOccupation
110 4 Denis 'GNUtoo' Carikli
111 5 Denis 'GNUtoo' Carikli
h3. Presentations:
112
113 1 Denis 'GNUtoo' Carikli
* The Graphic stack in Replicant 9
114
* Porting Replicant to Android 9 by Joonas Kylmälä?
115 61 Denis 'GNUtoo' Carikli
* A discussion about [[Upstream]] components, [[Upstream#Design-decisions|design choices]], and cultural re-appropriation of technology?
116 37 Denis 'GNUtoo' Carikli
** How subjective security is, threat models, and the difference between free software and device maker point of view
117 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
118
** Android upstream anti-features and political design choices
119
** Issues when combining together different build systems (Example: Android build system with Kconfig)
120
121 37 Denis 'GNUtoo' Carikli
122
h3. Over a cup of coffee:
123
124
* Fil is available for informal chatting about RepWifi
125 85 Denis 'GNUtoo' Carikli
126
h3. Hardware
127
128 67 Denis 'GNUtoo' Carikli
h4. Devices
129 70 Denis 'GNUtoo' Carikli
130 69 Denis 'GNUtoo' Carikli
Good practices:
131
* It would be a good idea to put your name on a sticker on the device if possible
132
133
|_. Person |_. Hardware |_. Comments |_. Usage |
134 67 Denis 'GNUtoo' Carikli
|/12. GNUtoo | Galaxy SIII (I9300) with the stock bootloader | |
135
| Galaxy SIII 4G (I9305) with the stock bootloader | |
136
| Galaxy SIII 4G (I9305) with u-boot | |
137 69 Denis 'GNUtoo' Carikli
| Galaxy Nexus (I9250) with the stock bootloader | |
138
| Galaxy SII (I9100) with the stock bootloader | |
139
| GTA04 A3 | | |
140 76 Denis 'GNUtoo' Carikli
| GTA04 A4 | | |
141 74 Denis 'GNUtoo' Carikli
| Optimus black (P970) | | |
142 75 Denis 'GNUtoo' Carikli
| GTA01 |/4. Used in a presentation about Replicant history | |
143
| GTA02 | |
144
| HTC Dream | |
145
| N900 | Testing the battery charger driver is still needed but require a heavy PSU |
146 67 Denis 'GNUtoo' Carikli
|/4. Fil | Galaxy Note 2 (N7100) stock bootloader | [Working] Available for non-critical tests | * Test the upstream touchkey driver
147 81 Denis 'GNUtoo' Carikli
=> TODO:
148 110 Denis 'GNUtoo' Carikli
* Bring a Parabola microSD (GNUtoo)
149 119 Denis 'GNUtoo' Carikli
* Test the patch with an I9300
150 104 Denis 'GNUtoo' Carikli
* Rebase the patch on master or linux-next |
151 79 Denis 'GNUtoo' Carikli
| Galaxy SIII (I9300) stock bootloader | [Working] Test Subject available for any experiment | |
152 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 |
153 37 Denis 'GNUtoo' Carikli
| Galaxy Tab 2 7.0 (GT P3100) | Property of the Replicant Project | * -Add support for it in the [[BackupTheEFS]] instructions- |
154 1 Denis 'GNUtoo' Carikli
|/2. Paulk | Galaxy Note (N7000) | | * Add support for it in the [[BackupTheEFS]] instructions |
155 37 Denis 'GNUtoo' Carikli
| Galaxy Tab 2 10.1 (P5100) | | * -Add support for it in the [[BackupTheEFS]] instructions- |
156 71 Denis 'GNUtoo' Carikli
|\2. Looking for a Galaxy Note 8.0 (N5100) | | * Add support for it in the [[BackupTheEFS]] instructions |
157 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 |
158 37 Denis 'GNUtoo' Carikli
159
h4. Debug utilities
160 108 Denis 'GNUtoo' Carikli
161 84 Denis 'GNUtoo' Carikli
|_. Person |_. Hardware |_. Comments |_. Usage |
162 37 Denis 'GNUtoo' Carikli
|/6. GNUtoo | Serial port cable with variable resistors |  |
163 44 Fil Bergamo
| Multimeter |  |
164 105 Denis 'GNUtoo' Carikli
| Simtrace 1: Can get the dialog between the modem and the SIM card in wireshark |  |
165
| SIM card that is not recognized in Replicant (STK related?) | Test on Replicant 4.2 and on Replicant 6.0 |
166
| SIM card + phone that can trigger the audio call issue | |
167
| Sigrok compatible adjustable power supply | Not sure to bring it (heavy) |
168 107 Denis 'GNUtoo' Carikli
|/1. Fil | SIM card that is not recognized in Replican 6 | |
169 129 Denis 'GNUtoo' Carikli
170 128 Denis 'GNUtoo' Carikli
h2. Discussion results
171 129 Denis 'GNUtoo' Carikli
172 128 Denis 'GNUtoo' Carikli
|_. Topic |_. Impact |_. Result |_. Consensus in that meeting |
173 118 Denis 'GNUtoo' Carikli
| Do we care about supporting devices with non-removable batteries? | 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. Because of that either users, repair shops or Replicant device vendors will need to have a viable way to change the non-removable battery. 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. |  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. | 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 |
174
| Do we require free software bootloaders |\2. * The Pinephone should be released in the next months (3 months?) but it's not released yet.
175
* Some other devices with free software bootloaders are not released yet either
176
* 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 |  Too early to do that:
177
* 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 |
178 121 Denis 'GNUtoo' Carikli
| How to handle the various keys used to sign releases, and other related things and should the recovery check signatures  | * 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.
179 120 Denis 'GNUtoo' Carikli
* The people involved in local Replicant install parties (in Paris) will help local Replicant users to update the recovery
180
* 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
181 121 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 
182 122 Denis 'GNUtoo' Carikli
* Keep checking signatures by default in the recovery |
183 123 Denis 'GNUtoo' Carikli
| 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:
184
* He plans to add in information about what hardware feature are supported or not
185 125 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 |
186
| Improving the Replicant website |\3.  *It would be nice to make information for users more accesible on the main page (https://replicant.us) | 
187
| Making it easier for anyone to contribute to Replicant |
188 124 Denis 'GNUtoo' Carikli
| Funding work on f-droid |
189
| Funding work on oFono RIL |
190
| 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.
191
Legal issues were raised as well when linking to external material and such.
192
Some examples were given on how to handle some common issues:
193
* Link to a book chapter advocating for DRM on the FSF website:
194
  *URL:* https://www.fsf.org/blogs/sysadmin/the-management-engine-an-attack-on-computer-users-freedom
195
  <pre>
196
  For more information about Digital Restrictions Management and the Management Engine,
197
  see from page 191 [...].
198
  This chapter tries to justify the usage of Digital Restrictions Management (DRM).
199
  DRM is totally unacceptable as it requires the users not to be in control of their
200
  computers to effectively prevent them from exercising their legal rights (such as fair
201
  use, or being able to copy published works). That chapter clearly shows the link between
202
  preventing users from controlling their hardware and effective DRM.
203
  </pre>
204
* Link to service manuals etc:
205
  *URL:* [[NexusSI902xSerial]]
206
  <pre>
207
  These documents are the propriety of Samsung Electronics and are not
208
  hosted by the Replicant project. However, some excerpts from these documents
209
  are provided, for the purpose of providing technical evidence of the facts that
210
  are mentioned in this page. We believe that this particular use of the copyrighted
211
  work is fair use.
212
  </pre>
213
* Mention of proprietary software in Replicant wiki, including how to "use" it:
214
  *URL*: [[SamsungGalaxyBackdoor]]
215
  <pre>  
216
  The following analysis was conducted using the libsec-ril.so binary file
217
   (the incriminated proprietary software) as extracted from the CyanogenMod 10.1.3
218
   system zip for the Galaxy S 3 (I9300), from location system/lib/libsec-ril.so.
219
  </pre>
220
* GNU Kind Communications Guidelines:
221
  *URL:* https://www.gnu.org/philosophy/kind-communication.html
222
  <pre>
223
  By contrast, to suggest that others use nonfree software opposes the basic
224
  principles of GNU, so it is not allowed in GNU Project discussions.
225 1 Denis 'GNUtoo' Carikli
  </pre>
226
* Trisquel Community Guidelines:
227 125 Denis 'GNUtoo' Carikli
  *URL:* https://trisquel.info/en/wiki/trisquel-community-guidelines
228
  <pre>
229
  Our community's resources --the forum, documentation, etc--
230
  are for free software only. Please do not distribute,
231
  recommend, or support non-free software here.
232
  </pre>
233
People in this discussion realized that the forum is relatively small so it's doable to have it moderated.
234
Plan of action:
235 127 Denis 'GNUtoo' Carikli
1. Describe what should is acceptable or not for the forums, wiki, etc
236
   => "Please do not distribute, recommend, or support non-free software here"
237
   => Also describe the above examples there if possible to help people linking to information in the right way.
238 130 Denis 'GNUtoo' Carikli
2. How to handle violations of the policy
239 111 Denis 'GNUtoo' Carikli
   => 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. |
240
| Do we ship some external applications in Replicant |\3. * Yes, but how does the selection process would look like?
241 1 Denis 'GNUtoo' Carikli
* Which browser we should add => One that works and that doesn't have freedom privacy or security issues 
242 112 Denis 'GNUtoo' Carikli
* Firefox Lite was mentioned but it was dismissed due to very concerning privacy issues with its privacy policy |
243 152 Denis 'GNUtoo' Carikli
| Using wayland for the graphic stack? | | |
244
| AOSP vs LineageOS |\2. * Using LineageOS repos makes less sense due to consensus about supporting devices with removable batteries.
245
* AOSP has stable/tagged releases whereas LineageOS lacks that 
246
* AOSP is also better documented
247
Since:
248
* LineageOS uses many repositories from AOSP already (Implicit at the time of the talk, not explicited)
249
* we still want some of the features from LineageOS (like root)
250
We will need to look into more details which repositories to use from LineageOS and from AOSP | Getting closer to AOSP |
251 113 Denis 'GNUtoo' Carikli
252 112 Denis 'GNUtoo' Carikli
h2. Video encoding
253
254
h3. Sound
255
256
The microphone was mono, with only a channel from the left. So we need to create mono audio files from the videos.
257 111 Denis 'GNUtoo' Carikli
258
To make the sound go in both channel, do the following in Audacity:
259 147 Denis 'GNUtoo' Carikli
260 113 Denis 'GNUtoo' Carikli
* Create a new project with File -> New
261 117 Denis 'GNUtoo' Carikli
* Import the video file with File -> Open
262
* Click on the audio channel -> Split Stereo to Mono
263
* Delete the second channel
264
* File -> Export -> Export as WAV
265
266
h3. Video 
267
268 113 Denis 'GNUtoo' Carikli
The videos were recorded with some equipement that was lent to us:
269
* A camera that outputed mp4 files on an SD card
270
* One wireless microphone
271
272
=> Next time ask if they have a second microphone available for questions.
273
274
* The videos are splitted in several mp4 files
275
* The part before the presentation has to be removed
276
277
Kdenlive is being used for that.
278
279
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).
280
281 114 Denis 'GNUtoo' Carikli
To workaround that the following was used:
282
* gnome3 (probably under wayland)
283
* pushbuffer enabled in the module parameters for nouveau
284
285
=> It's still slow while zomming in the timeline but it manage not to freeze the whole graphics stack.
286
287
To edit a video with kdenlive:
288
* create a project, and select the right resolution (720p 25fps here)
289
* Import the videos files to use with project->Add clip
290 115 Denis 'GNUtoo' Carikli
* Also import the mono audio files that you just converted with audacious
291
* Import the clips from the Project bin into the timeline with drag and drop
292
* Right click on the imported click in the timeline and select Ungroup
293
* Right click on the audio below, and select remove
294
* Import the mono audio file from the Project bin in the timeline with drag and drop
295
296 116 Denis 'GNUtoo' Carikli
Once that is done you can remove the part before the presentation this way:
297
* In the timeline you can zoom at the maximum level 
298 1 Denis 'GNUtoo' Carikli
* Use the cisors to divide the zone in two, you only need to click once with the left click to separate two zones
299
* Select the arow again (on the left of the cisors) and right click on the zone to remove, and select remove
300
* 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.
301
302
h2. Files