Project

General

Profile

TasksFunding » History » Version 274

Denis 'GNUtoo' Carikli, 01/14/2020 01:04 PM

1 1 Denis 'GNUtoo' Carikli
{{>toc}}
2
3 181 Denis 'GNUtoo' Carikli
h1. Funding
4 1 Denis 'GNUtoo' Carikli
5 181 Denis 'GNUtoo' Carikli
h2. Funding procedure
6
7 258 Denis 'GNUtoo' Carikli
h3. Background and rationale for funding work through the NLnet foundation
8
9
The NLnet foundation managed to get some European Union grants to fund work on privacy and trust technologies.
10
11
It's then up to individuals to apply to it, and to define tasks that can improve privacy and trust on the Internet, which then the NLnet foundation can choose to fund.
12
13 260 Denis 'GNUtoo' Carikli
This could for instance be used to fund the advancement of software (Tor, Replicant, etc) and hardware freedom (RISC-V, etc).
14 258 Denis 'GNUtoo' Carikli
15 263 Denis 'GNUtoo' Carikli
The only requirement (beside improving privacy and trust) seem to be that the project needs to have an European Union component (like the people applying for the grant living in the European union, etc).
16 258 Denis 'GNUtoo' Carikli
17 1 Denis 'GNUtoo' Carikli
They are then paid once tasks defined and/or the deliverables mentioned in the task have been completed.
18 260 Denis 'GNUtoo' Carikli
19
The NLnet foundation also have some resources to help pushing changes upstream and try to push the applicants into making their work as useful as possible by engaging with upstream communities.
20 258 Denis 'GNUtoo' Carikli
21
References:
22
* "Fosdem Lightning talks on the topic":https://fosdem.org/2019/schedule/event/nextgen_internet/
23
24 259 Denis 'GNUtoo' Carikli
h3. Tasks accepted for funding by the NLnet foundation
25 186 Denis 'GNUtoo' Carikli
26 247 Denis 'GNUtoo' Carikli
* [[Tasks_funding#"Finish porting Replicant to a newer Android version" nlnet Grant application|Finish porting Replicant to a newer Android version]]
27 248 Denis 'GNUtoo' Carikli
* [[TasksFunding#Graphics-acceleration|Graphics acceleration]]
28 84 Denis 'GNUtoo' Carikli
29 249 Denis 'GNUtoo' Carikli
The application criteria wrere handled by the NLnet foundation.
30 93 Denis 'GNUtoo' Carikli
31 84 Denis 'GNUtoo' Carikli
h3. Discussions
32
33
There is "a thread about funding on the mailing list":https://lists.osuosl.org/pipermail/replicant/2019-January/001774.html about that
34 76 Denis 'GNUtoo' Carikli
35 257 Denis 'GNUtoo' Carikli
h3. Mistakes
36
37 262 Denis 'GNUtoo' Carikli
* When submitting a task to the NLnet Foundation make sure to select a call in "Please select a call", like "NGI Privacy & Trust Enhancing Technologies". I for instance forgot to select the right call.
38
* The amount requested was too high as the grant is not taxed. The amount was changed after the submission and acceptation.
39 274 Denis 'GNUtoo' Carikli
* The tasks had to be grouped in themes and not in months (like make the modem work)
40
* The tasks/themes need to have an amount associated on the MOU document. Though the amount can be calculated with fixed costs and hours.
41 257 Denis 'GNUtoo' Carikli
42 273 Denis 'GNUtoo' Carikli
h2. Porting Replicant to a Android 9
43
44
*Status*: [[PortingToAndroid9]]
45 113 Denis 'GNUtoo' Carikli
46 266 Denis 'GNUtoo' Carikli
h3. Documents
47 264 Denis 'GNUtoo' Carikli
48 269 Denis 'GNUtoo' Carikli
* "LaTeX source of the MOU in git":https://git.replicant.us/contrib/GNUtoo/documents/tree/NLnet/porting_replicant_to_android9
49 1 Denis 'GNUtoo' Carikli
* "Signed MOU from GNUtoo":https://redmine.replicant.us/attachments/download/1656/porting_replicant_to_android9_signed_dc.pdf
50 268 Denis 'GNUtoo' Carikli
* "Signed MOU from both parties":https://redmine.replicant.us/attachments/download/1655/2019-02-105_signed.pdf
51 271 Denis 'GNUtoo' Carikli
* [[PortReplicantToAnewerAndroidVersionInitialApplication]]: Initial Grant application (outdated, modified later)
52 272 Denis 'GNUtoo' Carikli
* [[PortReplicantToAnewerAndroidVersionInitialDescription]]: Initial wiki task description
53 250 Denis 'GNUtoo' Carikli
54 165 dl lud
h2. Graphics acceleration
55 1 Denis 'GNUtoo' Carikli
56 173 dl lud
Currently, all supported devices on Replicant lack a free software driver for their GPU. This means that OpenGL ES (GLES) rendering must be done on the CPU (software rendering). The current approach to software rendering on Replicant 6 is based on "libAGL":https://android.googlesource.com/platform/frameworks/native/+/master/opengl, an optimized GLES 1.x implementation that uses "libpixelflinger":https://android.googlesource.com/platform/system/core/+log/master/libpixelflinger software renderer. Development on both these libraries ceased in 2013 and no work was done to support newer GLES versions.
57 226 dl lud
The major consequences of this are that:
58 173 dl lud
* Critical applications like web browsers crash due to lack of GLES 2.0 (#705). Replicant currently uses an out-dated browser that has many security flaws.
59 1 Denis 'GNUtoo' Carikli
* Replicant relies on patches to the Android framework to make things like the camera application work.
60 166 dl lud
* The rendering speed has degraded over the newer Android versions, like Android 6. Even applications that do not crash become difficult to use due to the huge rendering delays.
61 235 dl lud
62 1 Denis 'GNUtoo' Carikli
This task aims to fix all these severe issues by putting together a new graphics stack for the Android 9 port. This new graphics stack must be compatible with Android 9 Hardware Abstraction Layers (HAL) and provide at least GLES 2.0 rendering. It should be flexible enough to do software rendering with "Mesa":https://www.mesa3d.org/intro.html or "SwiftShader":https://swiftshader.googlesource.com/SwiftShader (Google's current software renderer), and also GPU rendering on devices where a free GPU driver is available.
63 235 dl lud
64 1 Denis 'GNUtoo' Carikli
"Joonas Kylmälä":https://redmine.replicant.us/users/8585 has done some introductory work on the Android 9 port for the i9305, and found a way to have it rendering to the screen. He put together a graphics stack composed of: gbm_gralloc ("Gralloc HAL":https://source.android.com/devices/graphics/implement#gralloc_hal) + drm_hwcomposer ("Hardware Composer HAL":https://source.android.com/devices/graphics/implement#hardware_composer_hal) + Mesa with kms_swrast driver with softpipe backend (CPU software renderer for GLES). This will be the starting point for this task.
65 235 dl lud
66 1 Denis 'GNUtoo' Carikli
Joonas' prototype shows that Replicant can use "gbm_gralloc":https://osdn.net/projects/android-x86/scm/git/external-gbm_gralloc/summary, an existing graphics memory allocator (gralloc) HAL maintained(ish) by Android-x86, in conjunction with "drm-hwcomposer":https://gitlab.freedesktop.org/drm-hwcomposer/drm-hwcomposer, a libre implementation of Android's Hardware Composer HAL based on Linux's DRM, to achieve software rendering with Mesa. This solution avoids the need to write a custom gralloc for Replicant, and takes advantage of the hardware acceleration for composition provided by drm-hwcomposer on devices with a free software DRM driver (e.g. exynos-based smartphones and tablets).
67 236 dl lud
68 237 dl lud
Much more testing is needed to confirm that gbm_gralloc can be the definitive gralloc HAL on Replicant 9. It still wasn't tried with SwiftShader, or even Mesa's llvmpipe backend, which is a must since the softpipe backend is too slow to be usable.
69 235 dl lud
Joonas' tests showed that some other components will need our attention, mostly the drm/exynos driver. In order to make drm/exynos work with gbm_gralloc and drm-hwcomposer Joonas had to disable "DRM-Auth":https://en.wikipedia.org/wiki/Direct_Rendering_Manager#DRM-Master_and_DRM-Auth and hack some missing pixel formats into it by using the default pixel format for everything. Besides drm/exynos, we will also have to make the graphics stack work with the "virtual GEM (vGEM) driver":https://www.phoronix.com/scan.php?page=news_item&px=DRM-vGEM-Mesa-Software, in order to support devices that lack a real drm driver.
70
71
The major and first goal of this task is thus to build upon Joonas's prototype and put together a stable and fully free graphics stack, compatible with GLES 2.0, that does software rendering through Mesa's llvmpipe with a decent performance.
72 1 Denis 'GNUtoo' Carikli
73 165 dl lud
*Hardware requirements*: A computer that is able to build Replicant. A Samsung Galaxy S3 or S3 4G to run the [[Porting_Replicant_to_Android_9|current Replicant 9 port]].
74 1 Denis 'GNUtoo' Carikli
75
*Difficulty*: Medium / Hard
76
77
*Requirements/Prerequisites*: Knowledge of C++, kernel interfaces knowledge or the ability to learn them
78
79 235 dl lud
*Expected outcomes*:
80 226 dl lud
* Graphics stack with decent performance on software rendering
81 1 Denis 'GNUtoo' Carikli
* Working GLES 2.0 implementation
82
* Fast enough graphics
83 209 dl lud
* F-Droid applications not crashing anymore because of GLES.
84 1 Denis 'GNUtoo' Carikli
85 210 dl lud
*Time +estimation+*:
86 1 Denis 'GNUtoo' Carikli
87 237 dl lud
|_. Step |_. man-hours |
88
| Set up the development environment, including the current Replicant 9 port on the test device. |>. 24 |
89
| Read AOSP documentation and understand all details of the graphics stack. |>. 16 |
90
| Adapt the build files to use Mesa's llvmpipe backend instead of softpipe. Fix potential LLVM version incompatibilities between Mesa and Android. |>. 40 |
91
| Properly implement the missing pixel formats in drm/exynos and try to have it merged into upstream. |>. 72 |
92
| Find a proper way to use DRM-Master and DRM-Auth with gbm_gralloc and drm-hwcomposer. |>. 40 |
93 238 dl lud
| Create test scenarios and check if the graphics stack works as expected. Consider "alternative grallocs":https://redmine.replicant.us/projects/replicant/wiki/GraphicsResearch#Gralloc if necessary. |>. 40 |
94 234 dl lud
| Make the graphics stack work with vGEM driver besides drm/exynos. |>. 40 |
95 1 Denis 'GNUtoo' Carikli
| Document the design decisions. |>. 16 |
96
|_. TOTAL |_>. 288 |
97 252 Denis 'GNUtoo' Carikli
98 1 Denis 'GNUtoo' Carikli
h3. Subtasks
99
100 235 dl lud
The following sub-tasks could also be worked on after finishing writing the gralloc:
101 1 Denis 'GNUtoo' Carikli
* [[Tasks_funding#SwiftShader|SwiftShader]]
102
* [[Tasks_funding#llvmpipe optimizations|llvmpipe optimizations]]
103
* [[Tasks_funding#Lima driver|Lima driver]]
104 252 Denis 'GNUtoo' Carikli
105 235 dl lud
h3. SwiftShader
106 238 dl lud
107 1 Denis 'GNUtoo' Carikli
"SwiftShader":https://swiftshader.googlesource.com/SwiftShader is Google's current software renderer that is capable of GLES 2.0 and is now "under work to support Vulkan":https://swiftshader.googlesource.com/SwiftShader/+log/master.
108 238 dl lud
109 232 dl lud
Mesa is the preferred renderer on Replicant for several reasons such as its support for both software and hardware (GPU) rendering, and its big community, with hundreds of active contributors. However, Mesa lacks a Vulkan software renderer. With Vulkan soon becoming a "requirement for new Android versions":https://android-developers.googleblog.com/2019/03/introducing-android-q-beta.html, we must make sure that Replicant's graphics stack can use SwiftShader in order to become futureproof. Furthermore, SwiftShader was built with performance in mind, specially for ARM CPUs, and may bring speed improvements on some devices.
110 238 dl lud
111 233 dl lud
The goal of this sub-task is thus to create a compile-time or run-time option that allows using Replicant 9 with SwiftShader as it's software renderer instead of Mesa.
112 232 dl lud
113 1 Denis 'GNUtoo' Carikli
*Hardware requirements*: A computer that is able to build Replicant. A smartphone or tablet that is supported by Replicant to be able to test the result.
114
115
*Difficulty*: Medium
116
117
*Requirements/Prerequisites*: Knowledge of C++, Makefiles and git. Android's graphics stack knowledge or the ability to learn them.
118
119 238 dl lud
*Expected outcomes*:
120
* SwiftShader running on Replicant.
121 1 Denis 'GNUtoo' Carikli
* Working Vulkan implementation.
122 211 dl lud
123
*Time +estimation+*: 40 man-hours.
124 252 Denis 'GNUtoo' Carikli
125 1 Denis 'GNUtoo' Carikli
h3. llvmpipe optimizations
126
127
Mesa is a highly versatile library that can be extended with device drivers to allow it to be used in different environments ranging from software emulation to complete hardware acceleration. One such driver is the "Gallium llvmpipe driver":https://www.mesa3d.org/llvmpipe.html, which is a software rasterizer that uses LLVM to do runtime code generation. It only needs a CPU to run graphics computations and thus brings full GLES support to all Replicant devices.
128
129
"llvmpipe has been integrated in Replicant 6":https://git.replicant.us/replicant/external_mesa3d/log/ but it's not activated by default yet as it is very slow. It is also not fully complete.
130
131
To fix that, llvmpipe and/or the integration of it in Replicant should be optimized. We should first start by configuring llvmpipe and/or Mesa "to not implement very expensive OpenGL operations":https://www.mesa3d.org/perf.html. If that's not sufficient, or if that breaks application compatibility, various software or hardware features ("ARM NEON":https://www.arm.com/products/processors/technologies/neon.php, hardware 2D acceleration, etc) could be used to improve the speed.
132 231 dl lud
133
Considerable speed improvements may be achieved with a fine-tuned emulation for division instructions. The ARM cores on many Replicant devices do not have hardware "support for the SDIV/UDIV instructions":https://community.arm.com/processors/b/blog/posts/divide-and-conquer. We should profile some apps and check whether GLES functions requiring divisions are to blame for the poor performance.
134 1 Denis 'GNUtoo' Carikli
135
*Hardware requirements* : A computer that is able to build Replicant. A smartphone or tablet that is supported by Replicant to be able to test the result.
136
137
*Difficulty*: Medium / Hard (depending on the amount of optimizations required)
138
139
*Requirements/Prerequisites*: See with Mesa project
140
141 211 dl lud
*Expected outcomes*: faster llvmpipe on ARM devices, able to run apps such as Fennec F-Droid (Firefox).
142
143
*Time +estimation+*:
144
145 234 dl lud
|_. Step |_. man-hours |
146
| Setup a "testing and benchmarking environment":https://source.android.com/devices/graphics/testing |>. 40 |
147
| Disable expensive OpenGL operations. Check speedup and stability. |>. 24 |
148
| Recap matrix operations (Linear Algebra) and study ARM NEON. |>. 48 |
149 242 dl lud
| Do a profiling of several apps to find the most used GLES operations. |>. 32 |
150 234 dl lud
| Use "Ne10 library":https://github.com/projectNe10/Ne10 or "Neon Intrinsics":https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics for the most used GLES operations. |>. 80 |
151
| Fix bugs, re-write the code where needed, get it stable. |>. 80 |
152 1 Denis 'GNUtoo' Carikli
|_. TOTAL |_>. 304 |
153 252 Denis 'GNUtoo' Carikli
154 1 Denis 'GNUtoo' Carikli
h3. Lima driver
155
156
"Lima":https://gitlab.freedesktop.org/lima is a free software Mesa driver for ARM Mali-4xx (Utgard) GPUs. These GPUs are present in several Replicant supported devices such as Galaxy S2, S3, S3 4G, Note and Note 2. 
157
158
Lima aims to full GLES support but it is still in development. However the "current implementation status":https://gitlab.freedesktop.org/lima/mesa/issues/39#note_79193 already allows the hardware acceleration of several tasks. GPU-based hardware acceleration is faster and less power hungry than software rendering, both by several orders of magnitude. It would allow Replicant devices to run applications with a performance close to that of non-free devices.
159 167 dl lud
160
*Hardware requirements* : A computer that is able to build Replicant. A Replicant device with a Mali-4xx GPU that can run mainline Linux (e.g. Galaxy S3 or Note 2).
161
162
*Difficulty*: Medium
163
164
*Requirements/Prerequisites*: "See with Lima project":https://gitlab.freedesktop.org/lima/web/wikis/home#build-and-install
165 1 Denis 'GNUtoo' Carikli
166 212 dl lud
*Expected outcomes*: Lima driver being used for GLES rendering on a supported device.
167
168 234 dl lud
|_. Step |_. man-hours |
169
| Rebase "Lima's Linux kernel DRM driver":https://gitlab.freedesktop.org/lima/linux on top of "forkbomb's Midas on Mainline kernel":https://blog.forkwhiletrue.me/pages/midas-mainline/. |>. 80 |
170
| Replace mainline Mesa for "Lima's Mesa":https://gitlab.freedesktop.org/lima/mesa (with their driver).  |>. 16 |
171
| Build and test thoroughly with "synthetic":https://source.android.com/devices/graphics/testing and real applications. |>. 40 |
172
| Create a fallback mechanism that uses the software renderer for GLES functions not yet implemented in Lima. |>. 100 |
173 222 dl lud
|_. TOTAL |_>. 236 |
174 252 Denis 'GNUtoo' Carikli
175 243 dl lud
h3. Software Bill of Materials
176
177
* "Replicant 9":https://redmine.replicant.us/projects/replicant/wiki/Porting_Replicant_to_Android_9
178
* "Mesa":https://www.mesa3d.org/intro.html (in particular: "Gallium llvmpipe driver":https://www.mesa3d.org/llvmpipe.html)
179
* "gbm_gralloc":https://osdn.net/projects/android-x86/scm/git/external-gbm_gralloc/summary
180
* "drm-hwcomposer":https://gitlab.freedesktop.org/drm-hwcomposer/drm-hwcomposer
181
* "Linux kernel":https://www.kernel.org/ (in particular: drm/exynos driver and "vGEM driver":https://www.phoronix.com/scan.php?page=news_item&px=DRM-vGEM-Mesa-Software)
182
* "SwiftShader":https://swiftshader.googlesource.com/SwiftShader
183
* "Ne10 library":https://github.com/projectNe10/Ne10
184
* "Neon Intrinsics":https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics
185
* "Lima":https://gitlab.freedesktop.org/lima
186 252 Denis 'GNUtoo' Carikli
187 222 dl lud
h3. "Graphics acceleration on Replicant" nlnet Grant application
188
189
|_. Project name | Graphics acceleration on Replicant |
190
|_. Website / wiki | https://redmine.replicant.us/projects/replicant/wiki/Tasks_funding#Graphics-acceleration |
191
192
Abstract: Can you explain the whole project and its expected outcome(s) in 1200 characters
193
<pre>
194
Replicant is a fully free software Android distribution which is approved by the
195
FSF. All supported devices on Replicant currently lack a free software driver
196
for their GPU. As such, OpenGL ES (GLES) rendering must be done on the CPU
197
through software rendering (SR).
198 223 dl lud
199 222 dl lud
Replicant's current renderer is both incomplete and slow. It causes essential
200
apps like web browsers to crash due to lack of GLES 2.0, and many other
201
apps run too slow to be usable.
202
203
This project aims to fix this by complementing Android's 9 graphics stack.
204
Adding a few missing components will created of a fully-free, fast and compliant
205
graphics stack.
206
207
First we will write a gralloc (graphics memory allocator) tailored for SR that
208
is compatible with drm-hwcomposer (a libre implementation of Android's Hardware
209
Composer HAL). This gralloc enables drm-hwcomposer to work with SurfaceFlinger
210
and SwiftShader, creating a stack capable of GLES 2.0 on the CPU of all Replicant
211
devices.
212
213
Afterwards we will integrate and optimize Mesa's llvmpipe SR, which offers better
214
community support than SwiftShader. As last step we will add support for the
215
Lima driver, which will bring an even faster GPU-backed GLES to at least 5
216
devices.
217
</pre> 
218
219
|_. Have you been involved with projects or organizations relevant to this project before?
220
And if so, can you tell us a bit about your contributions? | SEE TEMPLATE |
221
222
|_. Requested Amount (Between 5000 and 50000 Euros) | 50000 Euros |
223
|_. Does the project have other funding sources, both past and present? | SEE TEMPLATE |
224
225 1 Denis 'GNUtoo' Carikli
Explain what the requested budget will be used for? 
226 223 dl lud
<pre>
227 1 Denis 'GNUtoo' Carikli
The budget will only be used to fund this project through contract work.
228 223 dl lud
229
We estimate that this project should take 868 man-hours to reach full completion,
230
with 632 man-hours being enough to reach all software rendering goals, leaving only
231
the GPU rendering to be done. A detailed run-down of this estimate is available at
232
https://redmine.replicant.us/projects/replicant/wiki/Tasks_funding#Graphics-acceleration
233
234
So far we have a team of two people interested on working on this project (the
235
two authors and submitters of this application). Both can commit to the project
236
on a part-time regime (17.5 hours per week), which means that the project should
237
be fully completed in about 6 months.
238
239
We will make sure that everybody has a chance to apply for doing contract work.
240
If we take the cost of a freelance developer in the USA (75 to 150 USD
241
per hour) as a basis, to enable people living in Europe and the USA
242
to apply, we can fund between 380 and 760 man-hours with the 50000 EUR budget.
243
This should be enough to cover all work on software rendering plus the initial
244
work on GPU rendering.
245
246
As happens on all software projects, getting a precise time/effort evaluation is
247
a difficult endeavour, specially when dealing with a project that is heavy on
248
research such as this one.
249
250
If the software rendering goals are not reached when the 50000 EUR budget runs
251
out, or if the Replicant project deems it necessary to have GPU rendering, it
252
will use its existing funds to pay for contract work if no volunteers are found
253
to finish the project.
254
255
The Replicant project will also make sure that the people working on this project
256
have the necessary hardware to do it, for instance by shipping or reimbursing the
257 222 dl lud
purchase of a compatible smartphone with the Replicant project funds.
258
</pre>
259
260
Compare your own project with existing or historical efforts.
261 224 dl lud
<pre>
262
Past Replicant versions have relied on patches to the Android framework to make
263
software rendering work. These patches were quite specific for Replicant and
264
had no use elsewhere. This made them unfit for upstreaming or sharing with any
265 222 dl lud
other project.
266 224 dl lud
267
Android's Project Treble new graphics stack allows us to follow a different
268
approach this time. Instead of patching the Android framework, we will
269
implement one of the well defined Android HALs (Hardware Abstraction Layer):
270
the gralloc HAL. The end result will be a software library that can prove to be
271
useful on several projects besides Replicant (e.g. Android-x86 project) and
272
thus fit for upstreaming.
273
274
275
Furthermore, past Replicant versions relied on Google's software renderers
276
(ligAGL and libpixelflinger) for OpenGL ES support. As quite a few other
277
Google's open-source projects, these two had no community behind them and got
278
stalled as soon as Google deprecated them.
279
280
This time will we take a different approach. Although our first graphics stack
281
will rely on Google's SwiftShader renderer, we will then move our efforts into
282
Mesa. Mesa is a big community project, with hundreds of active contributors and
283
great community support. It includes the llvmpipe software renderer along with
284
new drivers in development for GPUs present on current and future Replicant
285 222 dl lud
devices. Mesa should provide a stable and maintained platform for years to come.
286
</pre>
287
288
What are significant technical challenges you expect to solve during the project, if any?
289 225 dl lud
<pre>
290
We expect to solve significant technical challenges during this project:
291
1. Implementation of the first Android gralloc library compatible with software
292
rendering.
293
2. Development of free-software benchmarks for OpenGL ES on Android, used to test
294
our optimizations to llvmpipe.
295
3. Optimization of llvmpipe by at least one order of magnitude.
296
4. Running an exynos based smartphone with fully free-software GPU graphics
297 222 dl lud
acceleration.
298
</pre>
299 229 dl lud
300
Describe the ecosystem of the project, and how you will engage with relevant actors and promote the outcomes?
301
<pre>
302
This project will re-use code from several projects such as Android,
303
drm-hwcomposer, Mesa and Lima driver. Whenever possible we will foster
304
collaboration with these projects and submit our changes upstream.
305
306
The Replicant project contributors and the FSF will supervise
307
contractors to do the work.
308
309
A blog post will announce that the Replicant project
310
has got some funding for this specific task, and that it is
311
looking for a contractor to work on it. This is to make sure
312
that everyone has equal chances in the application process.
313
314
Then the most suited contractor will be selected. Only contractors
315
that already have worked on similar tasks as part of free and open
316
source software projects will be chosen. This way we can look at
317
their existing contributions and make sure that they are able to
318
do the task before engaging with them.
319
320
The Replicant project will also make sure that the contractor has
321
or gets the hardware required to work on the task, before starting
322 1 Denis 'GNUtoo' Carikli
to work on it.
323 229 dl lud
</pre>
324 222 dl lud
325 167 dl lud
|_. Attachments | SEE TEMPLATE |