File: 01_the-debian-project.po

package info (click to toggle)
debian-handbook 10.20200619
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 135,632 kB
  • sloc: xml: 29,579; sh: 227; makefile: 62; perl: 54
file content (1536 lines) | stat: -rw-r--r-- 109,326 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
#
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2020-05-17 17:54+0200\n"
"PO-Revision-Date: 2019-09-05 14:51+0000\n"
"Last-Translator: rayray61 <laladodo000@gmail.com>\n"
"Language-Team: Turkish <https://hosted.weblate.org/projects/debian-handbook/01_the-debian-project/tr/>\n"
"Language: tr-TR\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n != 1;\n"
"X-Generator: Weblate 3.9-dev\n"

msgid "Objective"
msgstr "Amaç"

msgid "Means"
msgstr "Anlamına gelir"

msgid "Operation"
msgstr "Işlem"

msgid "Volunteer"
msgstr "Gönüllü"

msgid "The Debian Project"
msgstr "Debian Projesi"

msgid "Before diving right into the technology, let us have a look at what the Debian Project is, its objectives, its means, and its operations."
msgstr "Teknolojiye doğrudan dalmadan önce, Debian Projesinin ne olduğuna, amaçlarına, araçlarına ve faaliyetlerine bir göz atalım."

msgid "What Is Debian?"
msgstr "Debian Nedir?"

msgid "<primary>association</primary>"
msgstr "<primary> dernek</primary>"

msgid "<emphasis>CULTURE</emphasis> Origin of the Debian name"
msgstr "<emphasis>KÜLTÜR</emphasis> Debian adının kökeni"

msgid "Look no further: Debian is not an acronym. This name is, in reality, a contraction of two first names: that of Ian Murdock, and his girlfriend at the time, Debra. Debra + Ian = Debian."
msgstr "Başka yere bakmayın: Debian bir kısaltma değildir. Bu isim, gerçekte, iki ilk ismin daraltılmasıdır: Ian Murdock ve o zamanki kız arkadaşı Debra. Debra + Ian = Debian."

#, fuzzy
msgid "Debian is a GNU/Linux distribution. We will discuss what a distribution is in further detail in <xref linkend=\"sect.role-of-distributions\" />, but for now, we will simply state that it is a complete operating system, including software and systems for installation and management, all based on the Linux kernel and free software (especially those from the GNU project)."
msgstr "Debian bir GNU/Linux dağıtımıdır. Bir dağılımın ne olduğunu <xref linkend=\"sect.role-of-distributions\" />'da daha ayrıntılı olarak tartışacağız, ancak şimdilik, kurulum ve yönetim için yazılım ve sistemler de dahil olmak üzere tam bir işletim sistemi olduğunu belirteceğiz. Linux çekirdeği ve özgür yazılım (özellikle GNU projesinden olanlar)."

#, fuzzy
msgid "When he created Debian, in 1993, under the leadership of the FSF, Ian Murdock had clear objectives, which he expressed in the <emphasis>Debian Manifesto</emphasis>. The free operating system that he sought would have to have two principal features. First, quality: Debian would be developed with the greatest care, to be worthy of the Linux kernel. It would also be a non-commercial distribution, sufficiently credible to compete with major commercial distributions. This double ambition would, in his eyes, only be achieved by opening the Debian development process just like that of Linux and the GNU project. Thus, peer review would continuously improve the product."
msgstr "1993'te FSF'nin önderliğinde Debian'ı kurduğunda, Ian Murdock'un <emphasis>Debian Manifestosu</emphasis>'nde ifade ettiği net hedefleri vardı. Aradığı ücretsiz işletim sisteminin iki temel özelliği vardı. İlk olarak, kalite: Debian linux çekirdeğine layık olmak için, büyük bir özenle geliştirilecekti. Aynı zamanda ticari olmayan bir dağıtım, yeterince büyük ticari dağıtımlar ile rekabet güvenilir olacaktır. Bu çifte hırs, onun gözünde, sadece Linux ve GNU projesi gibi Debian geliştirme sürecini açarak elde edilebilir. Böylece, akran incelemesi sürekli ürün geliştirmek olacaktır."

msgid "<emphasis>CULTURE</emphasis> GNU, the project of the FSF"
msgstr "<emphasis>KÜLTÜR</emphasis> GNU, FSF'nin projesi"

#, fuzzy
msgid "<primary>GNU</primary>"
msgstr "<primary>GNU</primary>"

msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgstr "<primary>GNU</primary> <secondary> Unix Değil </secondary>"

#, fuzzy
msgid "The GNU project is a range of free software developed, or sponsored, by the Free Software Foundation (FSF), originated by its iconic leader, Dr. Richard M. Stallman. GNU is a recursive acronym, standing for “GNU is Not Unix”."
msgstr "GNU projesi, Özgür Yazılım Vakfı (FSF) tarafından, ikonik lideri Dr. Richard M. Stallman'ın geliştirdiği veya sponsor olduğu bir dizi ücretsiz yazılımdır. GNU “GNU Unix değil” anlamına gelen özyinelemeli bir kısaltmadır."

msgid "<emphasis>CULTURE</emphasis> Richard Stallman"
msgstr "<emphasis>KÜLTÜR</emphasis> Richard Stallman"

msgid "<primary>Stallman, Richard</primary>"
msgstr "<primary>Stallman, Richard</primary>"

msgid "<primary>RMS</primary>"
msgstr "<primary>RMS</primary>"

#, fuzzy
msgid "<acronym>FSF</acronym>'s founder and author of the GPL license, Richard M. Stallman (often referred to by his initials, RMS) is a charismatic leader of the Free Software movement. Due to his uncompromising positions, he is not unanimously admired, but his non-technical contributions to Free Software (in particular, the legal and philosophical) are respected by everybody."
msgstr "<acronym>FSF</acronym> kurucusu ve GPL lisans yazarı Richard M. Stallman (genellikle onun baş harfleri, RMS ile anılır) Özgür Yazılım hareketinin karizmatik bir lideridir. Uzlaşmaz tutumu nedeniyle oybirliğiyle takdir edilmese de Özgür Yazılım'a (özellikle hukuki ve felsefi düzeyde) yaptığı teknik olmayan katkılara herkes saygı duyuyor."

msgid "A Multi-Platform Operating System"
msgstr "Çok Platformlu İşletim Sistemi"

msgid "<primary>meta-distribution</primary>"
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> Ian Murdock's journey"
msgstr ""

msgid "<primary>Ian Murdock</primary>"
msgstr ""

msgid "<primary>Murdock, Ian</primary>"
msgstr ""

msgid "<primary>Progeny</primary>"
msgstr ""

msgid "Ian Murdock, founder of the Debian project, was its first leader, from 1993 to 1996. After passing the baton to Bruce Perens, Ian took a less public role. He returned to working behind the scenes of the free software community, creating the Progeny company, with the intention of marketing a distribution derived from Debian. This venture was, sadly, a commercial failure, and development was abandoned. The company, after several years of scraping by, simply as a service provider, eventually filed for bankruptcy in April of 2007. Of the various projects initiated by Progeny, only <emphasis>discover</emphasis> still remains. It is an automatic hardware detection tool."
msgstr ""

msgid "Ian Murdock died on 28 December 2015 in San Francisco after a series of worrying tweets where he reported having been assaulted by police. In July 2016 it was announced that his death had been ruled a suicide."
msgstr ""

msgid "Debian, remaining true to its initial principles, has had so much success that, today, it has reached a tremendous size. Currently there are 10 hardware architectures officially supported and also other kernels like FreeBSD (although the FreeBSD-based ports are not part of the set of officially supported architectures). Furthermore, with more than 28,000 source packages, the available software can meet almost any need that one could have, whether at home or in the enterprise."
msgstr ""

msgid "The sheer size of the distribution can be inconvenient: it is really unreasonable to distribute 16 DVD-ROMs to install a complete version on a standard PC… This is why Debian is increasingly considered as a “meta-distribution”, from which one extracts more specific distributions intended for a particular public: Debian Science for scientific use, Debian Edu for education and pedagogical use in an academic environment, Debian Med for medical applications, Debian Jr. for young children, etc. A more complete list of the subprojects can be found in <xref linkend=\"sect.sub-projects\" />, dedicated to that purpose."
msgstr ""

msgid "These partial views of Debian are organized in a well-defined framework, thus guaranteeing hassle-free compatibility between the various “sub-distributions”. All of them follow the general planning for release of new versions. And since they build on the same foundations, they can be easily extended, completed, and personalized with applications available in the Debian repositories."
msgstr ""

msgid "<primary>subproject</primary>"
msgstr ""

msgid "All the Debian tools operate in this direction: <command>debian-cd</command> has for a long time now allowed the creation of a set of CD-ROMs containing only a pre-selected set of packages; <command>debian-installer</command> is also a modular installer, easily adapted to special needs. <command>APT</command> will install packages from various origins, while guaranteeing the overall consistency of the system."
msgstr ""

msgid "<emphasis>TOOL</emphasis> Creating a Debian CD-ROM"
msgstr ""

msgid "<primary><command>debian-cd</command></primary>"
msgstr ""

#, fuzzy
#| msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-cd@lists.debian.org</email></secondary>"
msgstr "<primary>GNU</primary> <secondary> Unix Değil </secondary>"

msgid "<command>debian-cd</command> creates ISO images of installation media (CD, DVD, Blu-Ray, etc.) ready for use. Any matter regarding this software is discussed (in English) on the <email>debian-cd@lists.debian.org</email> mailing list. The team is led by Steve McIntyre who is handling official Debian ISO builds."
msgstr ""

msgid "<emphasis>BACK TO BASICS</emphasis> To each computer, its architecture"
msgstr ""

msgid "The term “architecture” indicates a type of computer (the most known include Mac or PC). Each architecture is differentiated primarily according to its processor, usually incompatible with other processors. These differences in hardware involve varying means of operation, thus requiring that software be compiled specifically for each architecture."
msgstr ""

msgid "<primary>architecture</primary>"
msgstr ""

msgid "<primary>processor</primary>"
msgstr ""

msgid "Most software available in Debian is written in portable programming languages: the same source code can be compiled for various architectures. In effect, an executable binary, always compiled for a specific architecture, will not usually function on any of the other architectures."
msgstr ""

msgid "Remember that each program is created by writing source code; this source code is a text file composed of instructions in a given programming language. Before you can use the software, it is necessary to compile the source code, which means transforming the code into a binary (a series of machine instructions executable by the processor). Each programming language has a specific compiler to execute this operation (for example, <command>gcc</command> for the C programming language)."
msgstr ""

msgid "<primary>source</primary><secondary>code</secondary>"
msgstr ""

msgid "<primary>binary code</primary>"
msgstr ""

msgid "<primary>compilation</primary>"
msgstr ""

msgid "<primary>compiler</primary>"
msgstr ""

msgid "<emphasis>TOOL</emphasis> Installer"
msgstr ""

msgid "<primary><command>debian-installer</command></primary>"
msgstr ""

#, fuzzy
#| msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-boot@lists.debian.org</email></secondary>"
msgstr "<primary>GNU</primary> <secondary> Unix Değil </secondary>"

msgid "<command>debian-installer</command> is the name of the Debian installation program. Its modular design allows it to be used in a broad range of installation scenarios. The development work is coordinated on the <email>debian-boot@lists.debian.org</email> mailing list under the direction of Cyril Brulebois."
msgstr ""

msgid "The Quality of Free Software"
msgstr ""

msgid "Debian follows all of the principles of Free Software, and its new versions are not released until they are ready. Developers do not work upon a set schedule and don't have to rush to meet an arbitrary deadline. People frequently complain of the long time between Debian's stable releases, but this caution ensures that Debian's legendary reliability is met: long months of testing are indeed necessary for the full distribution to receive the “stable” label."
msgstr ""

msgid "Debian will not compromise on quality: all known critical bugs on key packages are resolved in any new version, even if this requires the initially forecast release date to be pushed back. Optional packages whose critical bugs are not fixed, and thus do not meet the quality requirements, are simply dropped from the stable release."
msgstr ""

msgid "The Legal Framework: A Non-Profit Organization"
msgstr ""

msgid "Legally speaking, Debian is a project managed by an American not-for-profit, volunteer association. The project has around a thousand <emphasis>Debian developers</emphasis>, but brings together a far greater number of contributors (translators, bug reporters, artists, casual developers, etc.)."
msgstr ""

msgid "To carry its mission to fruition, Debian has a large infrastructure, with many servers connected across the Internet, offered and hosted by many sponsors."
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> Behind Debian, the SPI association, and local branches"
msgstr ""

msgid "<primary>SPI</primary>"
msgstr ""

msgid "<primary>Debian France</primary>"
msgstr ""

msgid "<primary>Software in the Public Interest</primary>"
msgstr ""

msgid "Debian doesn't own any server in its own name, since it is only a project within the <emphasis>Software in the Public Interest</emphasis> (<acronym>SPI</acronym>) association, which manages the hardware and financial aspects (donations, purchase of hardware, etc.). Although it was initially created specifically for the Debian project, this association now hosts other free software projects, especially the PostgreSQL database, Freedesktop.org (project for standardization of various parts of modern graphical desktop environments, such as GNOME and KDE Plasma), and the LibreOffice office suite. <ulink type=\"block\" url=\"https://www.spi-inc.org/\" />"
msgstr ""

msgid "In addition to SPI, various local associations collaborate closely with Debian in order to generate funds for Debian, without centralizing everything in the USA: they are known as “Trusted Organizations” in the Debian jargon. This setup avoids prohibitive international transfer costs, and fits well with the decentralized nature of the project."
msgstr ""

msgid "Do not hesitate to join your local association and support the project! <ulink type=\"block\" url=\"https://wiki.debian.org/Teams/Auditor/Organizations\" /> <ulink type=\"block\" url=\"https://france.debian.net/\" /> <ulink type=\"block\" url=\"https://debian.ch/\" />"
msgstr ""

msgid "The Foundation Documents"
msgstr ""

msgid "<primary>Foundation Documents</primary>"
msgstr ""

msgid "A few years after its initial launch, Debian formalized the principles that it should follow as a free software project. This deliberately activist decision allows orderly and peaceful growth by ensuring that all members progress in the same direction. To become a Debian developer, any candidate must confirm and prove their support and adherence to the principles established in the project's Foundation Documents."
msgstr ""

msgid "The development process is constantly debated, but these Foundation Documents are widely and consensually supported, thus rarely change. The Debian constitution also offers other guarantees for their stability: a three-quarter qualified majority is required to approve any amendment."
msgstr ""

msgid "The Commitment towards Users"
msgstr ""

msgid "<primary>social contract</primary>"
msgstr ""

msgid "<primary>contract, social</primary>"
msgstr ""

msgid "The project also has a “social contract”. What place does such a text have in a project only intended for the development of an operating system? It is quite simple: Debian works for its users, and thus, by extension, for society. This contract summarizes the commitments that the project undertakes. Let us study them in greater detail:"
msgstr ""

msgid "Debian will remain 100% free."
msgstr ""

msgid "This is Rule No. 1. Debian is and will remain composed entirely and exclusively of free software. Additionally, all software development within the Debian project, itself, will be free."
msgstr ""

msgid "<emphasis>PERSPECTIVE</emphasis> Beyond software"
msgstr ""

msgid "The first version of the Debian Social Contract said “Debian Will Remain 100% Free <emphasis>Software</emphasis>”. The disappearance of this last word (with the ratification of Version 1.1 of the contract in April of 2004) indicates the will to achieve freedom, not only in software, but also in the documentation and any other element that Debian wishes to provide within its operating system."
msgstr ""

msgid "This change, which was only intended as editorial, has, in reality, had numerous consequences, especially with the removal of some problematic documentation. Furthermore, the increasing use of firmware in drivers poses problems: many are non-free, yet they are necessary for proper operation of the corresponding hardware."
msgstr ""

msgid "We will give back to the free software community."
msgstr ""

msgid "Any improvement contributed by the Debian project to a work integrated in the distribution is sent back to the author of the work (called “upstream”). In general, Debian will cooperate with the community rather than work in isolation."
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> Upstream author, or Debian developer?"
msgstr ""

msgid "<primary>upstream author</primary>"
msgstr ""

msgid "<primary>author, upstream</primary>"
msgstr ""

msgid "<primary>upstream</primary>"
msgstr ""

msgid "The term “upstream author” means the author(s)/developer(s) of a work, those who write and develop it. On the other hand, a “Debian developer” uses an existing work to make it into a Debian package (the term “Debian maintainer” is better suited)."
msgstr ""

msgid "In practice, there can be overlaps between both roles: the Debian maintainer may write a patch, which benefits all users of the work. In general, Debian encourages those in charge of a package in Debian to get involved in “upstream” development as well (they become, then, contributors, without being confined to the role of simple users of a program)."
msgstr ""

msgid "We will not hide problems."
msgstr ""

msgid "Debian is not perfect, and, there will be new problems to fix every day. Debian will keep its entire bug report database open for public view at all times. Reports that people file on-line will promptly become visible to others."
msgstr ""

msgid "Our priorities are our users and free software."
msgstr ""

msgid "This commitment is more difficult to define. Debian imposes, thus, a bias when a decision must be made, and will discard an easy solution for the developers that will jeopardize the user experience, opting for a more elegant solution, even if it is more difficult to implement. This means to take into account, as a priority, the interests of the users and free software."
msgstr ""

msgid "Works that do not meet our free software standards."
msgstr ""

msgid "Debian accepts and understands that users may want to use some non-free programs. That is why the project allows usage of parts of its infrastructure to distribute Debian packages of non-free software that can safely be redistributed."
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> For or against the non-free section?"
msgstr ""

msgid "<primary>non-free</primary>"
msgstr ""

msgid "<primary>section</primary><secondary>non-free</secondary>"
msgstr ""

msgid "The commitment to maintain a structure to accommodate non-free software (i.e. the “non-free” section, see the sidebar <xref linkend=\"sidebar.sections\" />) is frequently a subject of debate within the Debian community."
msgstr ""

msgid "Detractors argue that it turns people away from free software equivalents, and contradicts the principle of serving only the free software cause. Supporters flatly state that most of the non-free packages are “nearly free”, and held back by only one or two annoying restrictions (the most common being the prohibition against commercial usage of the software). By distributing these works in the non-free branch, we indirectly explain to the author that their creation would be better known and more widely used if they could be included in the main section. They are, thus, politely invited to alter their license to serve this purpose."
msgstr ""

msgid "After a first and unfruitful attempt in 2004, the complete removal of the non-free section is unlikely to return to the agenda, especially since it contains many useful documents that were moved simply because they did not meet the new requirements for the main section. This is especially the case for certain software documentation files issued by the GNU project (in particular, Emacs and Make)."
msgstr ""

msgid "The continued existence of the non-free section is a source of occasional friction with the Free Software Foundation, and is the main reason it refuses to officially recommend Debian as an operating system."
msgstr ""

msgid "The Debian Free Software Guidelines"
msgstr ""

msgid "<primary>free software principles</primary>"
msgstr ""

msgid "<primary>DFSG</primary>"
msgstr ""

msgid "<primary>Debian Free Software Guidelines</primary>"
msgstr ""

msgid "<primary>free</primary><secondary>software</secondary>"
msgstr ""

msgid "This reference document defines which software is “free enough” to be included in Debian. If a program's license is in accordance with these principles, it can be included in the main section; on the contrary, and provided that free distribution is permitted, it may be found in the non-free section. The non-free section is not officially part of Debian; it is an added service provided to users."
msgstr ""

msgid "More than a selection criteria for Debian, this text has become an authority on the subject of free software, and has served as the basis for the “Open Source Definition”. Historically, it is therefore one of the first formal definitions of the concept of “free software”."
msgstr ""

msgid "The GNU General Public License, the BSD License, and the Artistic License are examples of traditional free licenses that follow the 9 points mentioned in this text. Below you will find the text as it is published on the Debian website. <ulink type=\"block\" url=\"https://www.debian.org/social_contract#guidelines\" />"
msgstr ""

msgid "Free redistribution."
msgstr ""

msgid "The license of a Debian component may not restrict any party from selling or giving away the software as a component of an aggregate software distribution containing programs from several different sources. The license may not require a royalty or other fee for such sale."
msgstr ""

msgid "Source code."
msgstr ""

msgid "The program must include source code, and must allow distribution in source code as well as compiled form."
msgstr ""

msgid "Derived works."
msgstr ""

msgid "The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software."
msgstr ""

msgid "Integrity of the author's source code."
msgstr ""

msgid "The license may restrict source code from being distributed in modified form <emphasis>only</emphasis> if the license allows the distribution of “patch files” with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software (<emphasis>This is a compromise. The Debian group encourages all authors not to restrict any files, source or binary, from being modified</emphasis>)."
msgstr ""

msgid "No discrimination against persons or groups."
msgstr ""

msgid "The license must not discriminate against any person or group of persons."
msgstr ""

msgid "No discrimination against fields of endeavor."
msgstr ""

msgid "The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research."
msgstr ""

msgid "Distribution of license."
msgstr ""

msgid "The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties."
msgstr ""

msgid "License must not be specific to Debian."
msgstr ""

msgid "The rights attached to the program must not depend on the program being part of a Debian system. If the program is extracted from Debian and used or distributed without Debian but otherwise within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the Debian system."
msgstr ""

msgid "License must not contaminate other software."
msgstr ""

msgid "The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be free software."
msgstr ""

msgid "<emphasis>BACK TO BASICS</emphasis> Copyleft"
msgstr ""

msgid "<primary>copyleft</primary>"
msgstr ""

msgid "<primary>copyrights</primary>"
msgstr ""

msgid "Copyleft is a principle that consists in using copyrights to guarantee the freedom of a work and its derivatives, rather than restrict the rights of uses, as is the case with proprietary software. It is, also, a play of words on the term “copyright”. Richard Stallman discovered the idea when a friend of his, fond of puns, wrote on an envelope addressed to him: “copyleft: all rights reversed”. Copyleft imposes preservation of all initial liberties upon distribution of an original or modified version of a work (usually a program). It is, thus, not possible to distribute a program as proprietary software if it is derived from code from a copyleft released program."
msgstr ""

msgid "The most well-known family of copyleft licenses is, of course, the GNU General Public License (<acronym>GPL</acronym>) and its derivatives, the GNU Lesser General Public License (<acronym>LGPL</acronym>), and the GNU Free Documentation License (<acronym>GFDL</acronym>). Sadly, the copyleft licenses are generally incompatible with each other. Consequently, it is best to use only one of them."
msgstr ""

msgid "Example licenses"
msgstr ""

msgid "The “GPL”, “BSD”, and “Artistic” licenses are examples of licenses that we consider “free”."
msgstr ""

msgid "<emphasis>BACK TO BASICS</emphasis> Free licenses"
msgstr ""

msgid "<primary>license</primary><secondary>BSD</secondary>"
msgstr ""

msgid "<primary>BSD license</primary>"
msgstr ""

msgid "<primary>license</primary><secondary>GPL</secondary>"
msgstr ""

msgid "<primary>GPL</primary>"
msgstr ""

msgid "<primary>GNU</primary><secondary>General Public License</secondary>"
msgstr ""

msgid "<primary>General Public License</primary>"
msgstr ""

msgid "<primary>license</primary><secondary>artistic</secondary>"
msgstr ""

msgid "<primary>artistic license</primary>"
msgstr ""

msgid "The GNU GPL, the BSD license, and the Artistic License all comply with the Debian Free Software Guidelines, even though they are very different."
msgstr ""

msgid "The GNU GPL, used and promoted by the FSF (Free Software Foundation), is the most common. Its main feature is that it also applies to any derived work that is redistributed: a program incorporating or using GPL code can only be distributed according to its terms. It prohibits, thus, any reuse in a proprietary application. This poses serious problems for the reuse of GPL code in free software incompatible with this license. As such, it is sometimes impossible to link a program published under another free software license with a library distributed under the GPL. On the other hand, this license is very solid in American law: FSF lawyers have participated in the drafting thereof, and have often forced violators to reach an amicable agreement with the FSF without going to court. <ulink type=\"block\" url=\"https://www.gnu.org/copyleft/gpl.html\" />"
msgstr ""

msgid "The BSD license is the least restrictive: everything is permitted, including use of modified BSD code in a proprietary application. <ulink type=\"block\" url=\"https://www.opensource.org/licenses/bsd-license.php\" />"
msgstr ""

msgid "Finally, the Artistic License reaches a compromise between these two others: integration of code in a proprietary application is permitted, but any modification must be published. <ulink type=\"block\" url=\"https://www.opensource.org/licenses/artistic-license-2.0.php\" />"
msgstr ""

msgid "The complete text of these licenses is available in <filename>/usr/share/common-licenses/</filename> on any Debian system (in case of BSD the newer 3-Clause License)."
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> Bruce Perens, a controversial leader"
msgstr ""

msgid "<primary>Bruce Perens</primary>"
msgstr ""

msgid "<primary>Perens, Bruce</primary>"
msgstr ""

msgid "<primary>Open Source</primary>"
msgstr ""

msgid "Bruce Perens was the second leader of the Debian project, just after Ian Murdock. He was very controversial in his dynamic and authoritarian methods. He, nevertheless, remains an important contributor to Debian, to whom Debian is especially indebted for the editing of the famous “Debian Free Software Guidelines” (DFSG), an original idea of Ean Schuessler. Subsequently, Bruce would derive from it the famous “Open Source Definition”, removing all references to Debian from it. <ulink type=\"block\" url=\"https://opensource.org/\" />"
msgstr ""

msgid "His departure from the project was quite emotional, but Bruce has remained strongly attached to Debian, since he continues to promote this distribution in political and economic spheres. He still sporadically appears on the e-mail lists to give his advice and present his latest initiatives in favor of Debian."
msgstr ""

msgid "<primary>codename</primary>"
msgstr ""

msgid "<primary>name</primary><secondary>codename</secondary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Rex</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Buzz</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Bo</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Hamm</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Slink</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Potato</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Woody</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Sarge</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Etch</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Lenny</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Squeeze</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Wheezy</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Jessie</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Stretch</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Buster</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Bullseye</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Bookworm</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Sid</emphasis></primary>"
msgstr ""

msgid "<primary>Toy Story</primary>"
msgstr ""

msgid "<primary>Pixar</primary>"
msgstr ""

msgid "Last anecdotal point, it was Bruce who was responsible for inspiring the different “codenames” for Debian versions (1.1 — <emphasis role=\"distribution\">Rex</emphasis>, 1.2 — <emphasis role=\"distribution\">Buzz</emphasis>, 1.3 — <emphasis role=\"distribution\">Bo</emphasis>, 2.0 — <emphasis role=\"distribution\">Hamm</emphasis>, 2.1 — <emphasis role=\"distribution\">Slink</emphasis>, 2.2 — <emphasis role=\"distribution\">Potato</emphasis>, 3.0 — <emphasis role=\"distribution\">Woody</emphasis>, 3.1 — <emphasis role=\"distribution\">Sarge</emphasis>, 4.0 — <emphasis role=\"distribution\">Etch</emphasis>, 5.0 — <emphasis role=\"distribution\">Lenny</emphasis>, 6.0 — <emphasis role=\"distribution\">Squeeze</emphasis>, 7 — <emphasis role=\"distribution\">Wheezy</emphasis>, 8 — <emphasis role=\"distribution\">Jessie</emphasis>, 9 — <emphasis role=\"distribution\">Stretch</emphasis>, 10 — <emphasis role=\"distribution\">Buster</emphasis>, 11 (not released yet) — <emphasis role=\"distribution\">Bullseye</emphasis>, 12 (not released yet) — <emphasis role=\"distribution\">Bookworm</emphasis>, <emphasis role=\"distribution\">Unstable</emphasis> — <emphasis role=\"distribution\">Sid</emphasis>). They are taken from the names of characters in the Toy Story movie. This animated film entirely composed of computer graphics was produced by Pixar Studios, with whom Bruce was employed at the time that he led the Debian project. The name “Sid” holds particular status, since it will eternally be associated with the <emphasis role=\"distribution\">Unstable</emphasis> branch. In the film, this character was the neighbor's child who always broke toys — so beware of getting too close to <emphasis role=\"distribution\">Unstable</emphasis>. Otherwise, <emphasis role=\"distribution\">Sid</emphasis> is also an acronym for “Still In Development”."
msgstr ""

msgid "The Inner Workings of the Debian Project"
msgstr ""

msgid "<primary>operations, internal</primary>"
msgstr ""

msgid "<primary>organization, internal</primary>"
msgstr ""

msgid "The abundant end results produced by the Debian project derive simultaneously from the work on the infrastructure performed by experienced Debian developers, from the individual or collective work of developers on Debian packages, and from user feedback."
msgstr ""

msgid "The Debian Developers"
msgstr ""

msgid "<primary>developers</primary><secondary>Debian developers</secondary>"
msgstr ""

msgid "Debian developers have various responsibilities, and as official project members, they have great influence on the direction the project takes. A Debian developer is generally responsible for at least one package, but according to their available time and desire, they are free to become involved in numerous teams, thus acquiring more responsibilities within the project. <ulink type=\"block\" url=\"https://www.debian.org/devel/people\" /> <ulink type=\"block\" url=\"https://www.debian.org/intro/organization\" /> <ulink type=\"block\" url=\"https://wiki.debian.org/Teams\" />"
msgstr ""

msgid "<emphasis>TOOL</emphasis> Developer's database"
msgstr ""

msgid "<primary>developers</primary><secondary>developer's database</secondary>"
msgstr ""

msgid "<primary>database</primary><secondary>developer's database</secondary>"
msgstr ""

msgid "Debian has a database including all developers registered with the project, and their relevant information (address, telephone, geographical coordinates such as longitude and latitude, etc.). Some of the information (first and last name, country, username within the project, IRC username, GnuPG key, etc.) is public and available on the Web. <ulink type=\"block\" url=\"https://db.debian.org/\" />"
msgstr ""

msgid "The geographical coordinates allow the creation of a map locating all of the developers around the globe. Debian is truly an international project: its developers can be found on all continents, although the majority are in “Western countries”."
msgstr ""

msgid "World-wide distribution of Debian developers"
msgstr ""

msgid "<primary>world-wide distribution</primary>"
msgstr ""

msgid "Package maintenance is a relatively regimented activity, very documented or even regulated. It must, in effect, comply with all the standards established by the <emphasis>Debian Policy</emphasis>. Fortunately, there are many tools that facilitate the maintainer's work. The developer can, thus, focus on the specifics of their package and on more complex tasks, such as squashing bugs. <ulink type=\"block\" url=\"https://www.debian.org/doc/debian-policy/\" />"
msgstr ""

msgid "<emphasis>BACK TO BASICS</emphasis> Package maintenance, the developer's work"
msgstr ""

msgid "<primary>maintenance</primary><secondary>package maintenance</secondary>"
msgstr ""

msgid "<primary>package</primary><secondary>maintenance</secondary>"
msgstr ""

msgid "Maintaining a package entails, first, “packaging” a program. Specifically, this means to define the means of installation so that, once installed, this program will operate and comply with the rules which the Debian project sets for itself. The result of this operation is saved in a <filename>.deb</filename> file. Effective installation of the program will then require nothing more than extraction of this compressed archive and execution of some pre-installation or post-installation scripts contained therein."
msgstr ""

msgid "After this initial phase, the maintenance cycle truly begins: preparing updates to follow the latest version of the Debian Policy, fixing bugs reported by users, and including new “upstream” versions of the program which naturally continues to develop simultaneously. For instance, at the time of the initial packaging, the program was at version 1.2.3. After some months of development, the original authors release a new stable version, numbered 1.4.0. At this point, the Debian maintainer should update the package, so that users can benefit from its latest stable version."
msgstr ""

msgid "<primary>Debian Policy</primary>"
msgstr ""

msgid "<primary>policy</primary>"
msgstr ""

msgid "The Policy, an essential element of the Debian Project, establishes the norms ensuring both the quality of the packages and perfect interoperability of the distribution. Thanks to this Policy, Debian remains consistent despite its gigantic size. This Policy is not fixed in stone, but continuously evolves thanks to proposals formulated on the <email>debian-policy@lists.debian.org</email> mailing list. Amendments that are agreed upon by all interested parties are accepted and applied to the text by a small group of maintainers who have no editorial responsibility (they only include the modifications agreed upon by the Debian developers that are members of the above-mentioned list). You can read current amendment proposals on the bug tracking system: <ulink type=\"block\" url=\"https://bugs.debian.org/debian-policy\" />"
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> Policy editorial process"
msgstr ""

#, fuzzy
#| msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-policy@lists.debian.org</email></secondary>"
msgstr "<primary>GNU</primary> <secondary> Unix Değil </secondary>"

msgid "Anyone can propose an amendment to the Debian Policy just by submitting a bug report with a severity level of “wishlist” against the <emphasis role=\"pkg\">debian-policy</emphasis> package. The process that then starts is documented in <ulink url=\"https://www.debian.org/doc/debian-policy/ap-process.html\" />: if it is acknowledged that the problem revealed must be resolved by creating a new rule in the Debian Policy, a discussion begins on the <email>debian-policy@lists.debian.org</email> mailing list until consensus is reached and a proposal issued. Someone then drafts a desired amendment and submits it for approval (in the form of a patch to review). As soon as two other developers approve the fact that the proposed amendment reflects the consensus reached in the previous discussion (they “second” it), the proposal can be included in the official document by one of the <emphasis role=\"pkg\">debian-policy</emphasis> package maintainers. If the process fails at one of these steps, the maintainers close the bug, classifying the proposal as rejected."
msgstr ""

msgid "<emphasis>DEBIAN POLICY</emphasis> The documentation"
msgstr ""

msgid "<primary>documentation</primary><secondary>location</secondary>"
msgstr ""

msgid "<primary>location of the documentation</primary>"
msgstr ""

msgid "<primary><filename>/usr/share/doc/</filename></primary>"
msgstr ""

msgid "<primary><filename>README.Debian</filename></primary>"
msgstr ""

msgid "<primary><filename>NEWS.Debian.gz</filename></primary>"
msgstr ""

msgid "Documentation for each package is stored in <filename>/usr/share/doc/<replaceable>package</replaceable>/</filename>. This directory often contains a <filename>README.Debian</filename> file describing the Debian specific adjustments made by the package maintainer. It is, thus, wise to read this file prior to any configuration, in order to benefit from their experience. We also find a <filename>changelog.Debian.gz</filename> file describing the changes made from one version to the next by the Debian maintainer. This is not to be confused with the <filename>changelog.gz</filename> file (or equivalent), which describes the changes made by the upstream developers. The <filename>copyright</filename> file includes information about the authors and the license covering the software. Finally, we may also find a file named <filename>NEWS.Debian.gz</filename>, which allows the Debian developer to communicate important information regarding updates; if <emphasis>apt-listchanges</emphasis> is installed, then these messages are automatically displayed. All other files are specific to the software in question. We especially would like to point out the <filename>examples</filename> sub-directory, which frequently contains examples of configuration files."
msgstr ""

msgid "The Policy provides considerable cover of the technical aspects of packaging. The size of the project also raises organizational problems; these are dealt with by the Debian Constitution, which establishes a structure and means for decision making. In other words, a formal governance system."
msgstr ""

msgid "<primary>constitution</primary>"
msgstr ""

msgid "<primary>Debian Project Leader</primary>"
msgstr ""

msgid "<primary>DPL</primary>"
msgstr ""

msgid "<primary>leader</primary><secondary>role</secondary>"
msgstr ""

msgid "<primary>leader</primary><secondary>election</secondary>"
msgstr ""

msgid "This constitution defines a certain number of roles and positions, plus responsibilities and authorities for each. It is particularly worth noting that Debian developers always have ultimate decision making authority by a vote of general resolution, wherein a qualified majority of three quarters (75%) of votes is required for significant alterations to be made (such as those with an impact on the Foundation Documents). However, developers annually elect a “leader” to represent them in meetings, and ensure internal coordination between varying teams. This election is always a period of intense discussions. This leader's role is not formally defined by any document: candidates for this post usually propose their own definition of the position. In practice, the leader's roles include serving as a representative to the media, coordinating between “internal” teams, and providing overall guidance to the project, within which the developers can relate: the views of the DPL are implicitly approved by the majority of project members."
msgstr ""

msgid "Specifically, the leader has real authority; their vote resolves tie votes; they can make any decision which is not already under the authority of someone else and can delegate part of their responsibilities."
msgstr ""

msgid "<primary>Jackson, Ian</primary>"
msgstr ""

msgid "<primary>Akkerman, Wichert</primary>"
msgstr ""

msgid "<primary>Collins, Ben</primary>"
msgstr ""

msgid "<primary>Garbee, Bdale</primary>"
msgstr ""

msgid "<primary>Michlmayr, Martin</primary>"
msgstr ""

msgid "<primary>Robinson, Branden</primary>"
msgstr ""

msgid "<primary>Towns, Anthony</primary>"
msgstr ""

msgid "<primary>Hocevar, Sam</primary>"
msgstr ""

msgid "<primary>McIntyre, Steve</primary>"
msgstr ""

msgid "<primary>Zacchiroli, Stefano</primary>"
msgstr ""

msgid "<primary>Nussbaum, Lucas</primary>"
msgstr ""

#, fuzzy
#| msgid "<primary>RMS</primary>"
msgid "<primary>Dogguy, Mehdi</primary>"
msgstr "<primary>RMS</primary>"

#, fuzzy
#| msgid "<primary>Stallman, Richard</primary>"
msgid "<primary>Lamb, Chris</primary>"
msgstr "<primary>Stallman, Richard</primary>"

#, fuzzy
#| msgid "<primary>Stallman, Richard</primary>"
msgid "<primary>Hartman, Sam</primary>"
msgstr "<primary>Stallman, Richard</primary>"

msgid "Since its inception, the project has been successively led by Ian Murdock, Bruce Perens, Ian Jackson, Wichert Akkerman, Ben Collins, Bdale Garbee, Martin Michlmayr, Branden Robinson, Anthony Towns, Sam Hocevar, Steve McIntyre, Stefano Zacchiroli, Lucas Nussbaum, Mehdi Dogguy, Chris Lamb and Sam Hartman."
msgstr ""

msgid "<primary>technical committee</primary>"
msgstr ""

msgid "The constitution also defines a “technical committee”. This committee's essential role is to decide on technical matters when the developers involved have not reached an agreement between themselves. Otherwise, this committee plays an advisory role for any developer who fails to make a decision for which they are responsible. It is important to note that they only get involved when invited to do so by one of the parties in question."
msgstr ""

msgid "<primary>the project secretary</primary>"
msgstr ""

msgid "Finally, the constitution defines the position of “project secretary”, who is in charge of the organization of votes related to the various elections and general resolutions."
msgstr ""

msgid "The “general resolution” procedure is fully detailed in the constitution, from the initial discussion period to the final counting of votes. The most interesting aspect of that process is that when it comes to an actual vote, developers have to rank the different ballot options between them and the winner is selected with a <ulink url=\"https://en.wikipedia.org/wiki/Condorcet_method\">Condorcet method</ulink> (more specifically, the Schulze method). For further details see: <ulink type=\"block\" url=\"https://www.debian.org/devel/constitution\" />"
msgstr ""

msgid "<primary>general resolution</primary>"
msgstr ""

msgid "<primary>vote</primary>"
msgstr ""

msgid "<emphasis>CULTURE</emphasis> Flamewar, the discussion that catches fire"
msgstr ""

msgid "<primary>flamewar</primary>"
msgstr ""

msgid "<primary>heated debate</primary>"
msgstr ""

msgid "A “flamewar” is an exceedingly impassioned debate, which frequently ends up with people attacking each other once all reasonable argumentation has been exhausted on both sides. Certain themes are more frequently subject to polemics than others (the choice of text editor, “do you prefer <command>vi</command> or <command>emacs</command>?”, is an old favorite). The matters often provoke very rapid e-mail exchanges due to the sheer number of people with an opinion on the matter (everyone) and the very personal nature of such questions."
msgstr ""

msgid "Nothing particularly useful generally comes from such discussions; the general recommendation is to stay out of such debates, and maybe rapidly skim through their content, since reading them in full would be too time-consuming."
msgstr ""

msgid "Even if this constitution establishes a semblance of democracy, the daily reality is quite different: Debian naturally follows the free software rules of the do-ocracy: the one who does things gets to decide how to do them. A lot of time can be wasted debating the respective merits of various ways to approach a problem; the chosen solution will be the first one that is both functional and satisfying… which will come out of the time that a competent person did put into it."
msgstr ""

msgid "This is the only way to earn one's stripes: do something useful and show that one has worked well. Many Debian “administrative” teams operate by co-optation, preferring volunteers who have already effectively contributed and proved their competence. The public nature of the work of those teams makes it possible for new contributors to observe and start helping without any special privilege. This is why Debian is often described as a “meritocracy”."
msgstr ""

msgid "<emphasis>CULTURE</emphasis> Meritocracy, the reign of knowledge"
msgstr ""

msgid "<primary>meritocracy</primary>"
msgstr ""

msgid "Meritocracy is a form of government in which authority is exercised by those with the greatest merit. For Debian, merit is a measure of competence, which is, itself, assessed by observation of past actions by one or more others within the project (Stefano Zacchiroli, a former project leader, speaks of “do-ocracy”, meaning “power to those who get things done”). Their simple existence proves a certain level of competence; their achievements generally being free software, with available source code, which can easily be reviewed by peers to assess their quality."
msgstr ""

msgid "This effective operational method guarantees the quality of contributors in the “key” Debian teams. This method is by no means perfect and occasionally there are those who do not accept this way of operating. The selection of developers accepted in the teams may appear a bit arbitrary, or even unfair. Furthermore, not everybody has the same definition of the service expected from these teams. For some, it is unacceptable to have to wait eight days for inclusion of a new Debian package, while others will wait patiently for three weeks without a problem. As such, there are regular complaints from the disgruntled about the “quality of service” from some teams."
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> Integration of new maintainers"
msgstr ""

msgid "<primary>maintainer</primary><secondary>new maintainer</secondary>"
msgstr ""

msgid "The team in charge of admitting new developers is the most regularly criticized. One must acknowledge that, throughout the years, the Debian project has become more and more demanding of the developers that it will accept. Some people may see some injustice in that, but we must confess that what were only little challenges at the beginning have become much greater in a community of over 1,000 people, when it comes to ensuring the quality and integrity of everything that Debian produces for its users."
msgstr ""

msgid "<primary>DAM</primary>"
msgstr ""

msgid "<primary>Debian Account Managers</primary>"
msgstr ""

msgid "Furthermore, the acceptance procedure is concluded by review of the candidacy by a small team, the Debian Account Managers. These managers are, thus, particularly exposed to criticism, since they have final say in the inclusion or rejection of a volunteer within the Debian developers community. In practice, sometimes they must delay the acceptance of a person until they have learned more about the operations of the project. One can, of course, contribute to Debian before being accepted as an official developer, by being sponsored by current developers."
msgstr ""

msgid "The Active Role of Users"
msgstr ""

msgid "One might wonder if it is relevant to mention the users among those who work within the Debian project, but the answer is a definite yes: they play a critical role in the project. Far from being “passive”, some users run development versions of Debian and regularly file bug reports to indicate problems. Others go even further and submit ideas for improvements, by filing a bug report with a severity level of “wishlist”, or even submit corrections to the source code, called “patches” (see <xref linkend=\"sect.patch\" />)."
msgstr ""

msgid "Reporting bugs"
msgstr ""

msgid "<primary>system</primary><secondary>Bug Tracking System</secondary>"
msgstr ""

msgid "<primary>BTS</primary>"
msgstr ""

msgid "<primary>Bug Tracking System</primary>"
msgstr ""

msgid "<primary><literal>bugs.debian.org</literal></primary>"
msgstr ""

msgid "The fundamental tool for submitting bugs in Debian is the Debian Bug Tracking System (Debian BTS), which is used by large parts of the project. The public part (the web interface) allows users to view all bugs reported, with the option to display a sorted list of bugs selected according to various criteria, such as: affected package, severity, status, address of the reporter, address of the maintainer in charge of it, tag, etc. It is also possible to browse the complete historical listing of all discussions regarding each of the bugs."
msgstr ""

msgid "Below the surface, the Debian BTS is e-mail based: all information that it stores comes from messages sent by the various persons involved. Any e-mail sent to <email>12345@bugs.debian.org</email> will, thus, be assigned to the history for bug number 12345. Authorized persons may “close” a bug by writing a message describing the reasons for the decision to close to <email>12345-done@bugs.debian.org</email> (a bug is closed when the indicated problem is resolved or no longer relevant). A new bug is reported by sending an e-mail to <email>submit@bugs.debian.org</email> according to a specific format which identifies the package in question. The address <email>control@bugs.debian.org</email> allows editing of all the “meta-information” related to a bug."
msgstr ""

msgid "The Debian BTS has other functional features, as well, such as the use of tags for labeling bugs. For more information, see <ulink type=\"block\" url=\"https://www.debian.org/Bugs/\" />"
msgstr ""

msgid "<emphasis>VOCABULARY</emphasis> Severity of a bug"
msgstr ""

msgid "<primary>severity</primary>"
msgstr ""

msgid "<primary>bug</primary><secondary>severity</secondary>"
msgstr ""

msgid "The severity of a bug formally assigns a degree of gravity to the reported problem. Effectively, not all bugs have the same importance; for instance, a typo in a manual page is not comparable to a security vulnerability in server software."
msgstr ""

msgid "Debian uses an extended scale to describe the severity of a bug. Each level is defined precisely in order to facilitate the selection thereof. <ulink type=\"block\" url=\"https://www.debian.org/Bugs/Developer#severities\" />"
msgstr ""

msgid "Users can also use the command line to send bug reports on a Debian package with the <command>reportbug</command> tool. It helps making sure the bug in question hasn't already been filed, thus preventing redundancy in the system. It reminds the user of the definitions of the severity levels, for the report to be as accurate as possible (the developer can always fine-tune these parameters later, if needed). It helps writing a complete bug report without the user needing to know the precise syntax, by writing it and allowing the user to edit it. This report will then be sent via an e-mail server (by default, a remote one run by Debian, but <command>reportbug</command> can also use a local server)."
msgstr ""

msgid "This tool first targets the development versions, which is where the bugs will be fixed. Effectively, changes are not welcome in a stable version of Debian, with very few exceptions for security updates or other important updates (if, for example, a package is not working at all). A correction of a minor bug in a Debian package must, thus, wait for the next stable version."
msgstr ""

msgid "Translation and documentation"
msgstr ""

#, fuzzy
#| msgid "<primary>association</primary>"
msgid "<primary>documentation</primary>"
msgstr "<primary> dernek</primary>"

#, fuzzy
#| msgid "<primary>association</primary>"
msgid "<primary>translation</primary>"
msgstr "<primary> dernek</primary>"

msgid "Additionally, numerous satisfied users of the service offered by Debian like to make a contribution of their own to the project. As not everyone has appropriate levels of expertise in programming, they may choose to assist with the translation and review of documentation. There are language-specific mailing lists to coordinate this work. <ulink type=\"block\" url=\"https://lists.debian.org/i18n.html\" /> <ulink type=\"block\" url=\"https://www.debian.org/international/\" />"
msgstr ""

msgid "<emphasis>BACK TO BASICS</emphasis> What are i18n and l10n?"
msgstr ""

msgid "<primary>internationalization</primary>"
msgstr ""

msgid "<primary>localization</primary>"
msgstr ""

msgid "<primary>i18n</primary>"
msgstr ""

msgid "<primary>l10n</primary>"
msgstr ""

msgid "“i18n” and “l10n” are the abbreviations for the words “internationalization” and “localization”, respectively, preserving the initial and last letter of each word, and the number of letters in the middle."
msgstr ""

msgid "To “internationalize” a program consists of modifying it so that it can be translated (localized). This involves partially rewriting a program initially written to work in one language in order to be able to open it to all languages."
msgstr ""

msgid "To “localize” a program consists of translating the original messages (frequently in English) to another language. For this, it must have already been internationalized."
msgstr ""

msgid "In summary, internationalization prepares the software for translation, which is then executed by localization."
msgstr ""

msgid "Sending fixes"
msgstr ""

msgid "<primary><command>patch</command></primary>"
msgstr ""

msgid "<primary>patch</primary>"
msgstr ""

msgid "<primary><command>diff</command></primary>"
msgstr ""

msgid "More advanced users might be able to provide a fix to a program by sending a patch."
msgstr ""

msgid "A patch is a file describing changes to be made to one or more reference files. Specifically, it will contain a list of lines to be removed or added to the code, as well as (sometimes) lines taken from the reference text, replacing the modifications in context (they allow identification of the placement of the changes if the line numbers have changed)."
msgstr ""

msgid "The tool used for applying the modifications given in such a file is simply called <command>patch</command>. The tool that creates it is called <command>diff</command>, and is used as follows:"
msgstr ""

msgid "<computeroutput>$ </computeroutput><userinput>diff -u file.old file.new &gt;file.patch</userinput>"
msgstr ""

msgid "The <filename>file.patch</filename> file contains the instructions for changing the content of <filename>file.old</filename> into <filename>file.new</filename>. We can send it to someone, who can then use it to recreate <filename>file.new</filename> from the two others, like this:"
msgstr ""

msgid "<computeroutput>$ </computeroutput><userinput>patch -p0 file.old &lt;file.patch</userinput>"
msgstr ""

msgid "The file, <filename>file.old</filename>, is now identical to <filename>file.new</filename>."
msgstr ""

msgid "In practice, most software is maintained in Git repositories and contributors are thus more likely to use <command>git</command> to retrieve the source code and propose changes. <command>git diff</command> will generate a file in the same format as what <command>diff -u</command> would do and <command>git apply</command> can do the same as <command>patch</command>."
msgstr ""

msgid "<emphasis>CULTURE</emphasis> Git"
msgstr ""

msgid "<primary>Git</primary>"
msgstr ""

msgid "<primary>configuration management</primary>"
msgstr ""

msgid "Git is a tool for collaborative work on multiple files, while maintaining a history of modifications. The files in question are generally text files, such as a program's source code. If several people work together on the same file, <command>git</command> can only merge the alterations made if they were made to different portions of the file. Otherwise, these “conflicts” must be resolved by hand."
msgstr ""

msgid "Git is a distributed system where each user has a repository with the complete history of changes. Central repositories are used to download the project (<command>git clone</command>) and to share the work done with others (<command>git push</command>). The repository can contain multiple versions of the files but only one version can be worked on at a given time: it is called the working copy (it can be changed to point to another version with <command>git checkout</command>). Git can show you the modifications made to the working copy (<command>git diff</command>), can stage changes for inclusion (<command>git add</command>)), and can create a new entry in the versions history (<command>git commit</command>). It can also update the working copy to include modifications made in parallel by other users (<command>git pull</command>), and can record a particular configuration in the history in order to be able to easily extract it later on (<command>git tag</command>)."
msgstr ""

msgid "Git makes it easy to handle multiple concurrent versions of a project in development without them interfering with each other. These versions are called <emphasis>branches</emphasis>. This metaphor of a tree is fairly accurate, since a program is initially developed on a common trunk. When a milestone has been reached (such as version 1.0), development continues on two branches: the development branch prepares the next major release, and the maintenance branch manages updates and fixes for version 1.0."
msgstr ""

msgid "<primary>Version Control System (VCS)</primary>"
msgstr ""

msgid "Git is, nowadays, the most popular version control system but it is not the only one. Historically, CVS (Concurrent Versions System) was the first widely used tool but its numerous limitations contributed to the appearance of more modern free alternatives. These include, especially, <command>subversion</command> (<command>svn</command>), <command>git</command>, <command>bazaar</command> (<command>bzr</command>), and <command>mercurial</command> (<command>hg</command>). <ulink type=\"block\" url=\"https://www.nongnu.org/cvs/\" /> <ulink type=\"block\" url=\"https://subversion.apache.org/\" /> <ulink type=\"block\" url=\"https://git-scm.com/\" /> <ulink type=\"block\" url=\"https://bazaar.canonical.com/\" /> <ulink type=\"block\" url=\"http://mercurial.selenic.com/\" />"
msgstr ""

msgid "<primary><command>subversion</command></primary>"
msgstr ""

msgid "<primary><command>svn</command></primary>"
msgstr ""

msgid "<primary><command>git</command></primary>"
msgstr ""

msgid "<primary><command>bzr</command></primary>"
msgstr ""

msgid "<primary><command>hg</command></primary>"
msgstr ""

msgid "<primary><command>mercurial</command></primary>"
msgstr ""

msgid "<primary><command>cvs</command></primary>"
msgstr ""

msgid "It is beyond the scope of this book to provide a detailed explanation about Git, for that you can refer to the <citetitle>Pro Git</citetitle> book. <ulink type=\"block\" url=\"https://git-scm.com/book/\" />"
msgstr ""

msgid "While the output of <command>git diff</command> is a file that can be shared with other developers, there are usually better ways to submit changes. If the developers prefer to get patches by email, they usually want patches generated with <command>git format-patch</command> so that they can be directly integrated in the repository with <command>git am</command>. This preserves commits meta-information and makes it possible to share multiple commits at once."
msgstr ""

msgid "This email-based workflow is still popular but it tends to be replaced by the usage of <emphasis>merge requests</emphasis> (or <emphasis>pull requests</emphasis>) whenever the software is hosted in a platform like Github or GitLab — and Debian is using GitLab on its <literal>salsa.debian.org</literal> server. On those systems, once you have created an account, you <emphasis>fork</emphasis> the repository, effectively creating a copy of the repository in your own account, and you can then clone that repository and push your own changes in it. From there, the web interface will suggest you to submit a merge request, notifying the developers of your changes, making it easy for them to review and accept your changes with a single click."
msgstr ""

msgid "Other ways of contributing"
msgstr ""

msgid "All of these contribution mechanisms are made more efficient by users' behavior. Far from being a collection of isolated persons, users are a true community within which numerous exchanges take place. We especially note the impressive activity on the user discussion mailing list, <email>debian-user@lists.debian.org</email> (<xref linkend=\"solving-problems\" /> discusses this in greater detail). <ulink type=\"block\" url=\"https://lists.debian.org/users.html\" />"
msgstr ""

msgid "Not only do users help themselves (and others) on technical issues that directly affect them, but they also discuss the best ways to contribute to the Debian project and help it move forward — discussions that frequently result in suggestions for improvements."
msgstr ""

#, fuzzy
#| msgid "<emphasis>CULTURE</emphasis> Richard Stallman"
msgid "<emphasis>TOOL</emphasis> how-can-i-help"
msgstr "<emphasis>KÜLTÜR</emphasis> Richard Stallman"

#, fuzzy
#| msgid "<primary>association</primary>"
msgid "<primary><command>how-can-i-help</command></primary>"
msgstr "<primary> dernek</primary>"

#, fuzzy
#| msgid "<primary>association</primary>"
msgid "<primary>orphaned packages</primary>"
msgstr "<primary> dernek</primary>"

#, fuzzy
msgid "<primary>“newcomer” bugs</primary>"
msgstr "<primary>GNU</primary>"

msgid "The <command>how-can-i-help</command> program lists opportunities for contributing to Debian packages that are installed locally. After each APT invocation, it shows ways to help, by highlighting bugs tagged “newcomer” (which are easy entry-points for new contributors) or orphaned packages that need a new maintainer. The program can be executed directly as well."
msgstr ""

msgid "Since Debian does not expend funds on any self-promoting marketing campaigns, its users play an essential role in its diffusion, ensuring its fame via word-of-mouth."
msgstr ""

msgid "This method works quite well, since Debian fans are found at all levels of the free software community: from install parties (workshops where seasoned users assist newcomers to install the system) organized by local <acronym>LUG</acronym>s or “Linux User Groups”, to association booths at large tech conventions dealing with Linux, etc."
msgstr ""

msgid "Volunteers make posters, brochures, stickers, and other useful promotional materials for the project, which they make available to everyone, and which Debian provides freely on its website and on its wiki: <ulink type=\"block\" url=\"https://www.debian.org/events/material\" />"
msgstr ""

msgid "Teams and Sub-Projects"
msgstr ""

msgid "Debian has been organized, right from the start, around the concept of source packages, each with its maintainer or group of maintainers. Many work teams have emerged over time, ensuring administration of the infrastructure, management of tasks not specific to any package in particular (quality assurance, Debian Policy, installer, etc.), with the latest series of teams growing up around sub-projects."
msgstr ""

msgid "Existing Debian Sub-Projects"
msgstr ""

msgid "To each their own Debian! A sub-project is a group of volunteers interested in adapting Debian to specific needs. Beyond the selection of a sub-group of programs intended for a particular domain (education, medicine, multimedia creation, etc.), sub-projects are also involved in improving existing packages, packaging missing software, adapting the installer, creating specific documentation, and more."
msgstr ""

msgid "<emphasis>VOCABULARY</emphasis> Sub-project and derivative distribution"
msgstr ""

msgid "<primary>derivative distribution</primary>"
msgstr ""

msgid "The development process for a derivative distribution consists in starting with a particular version of Debian and making a number of modifications to it. The infrastructure used for this work is completely external to the Debian project. There isn't necessarily a policy for contributing improvements. This difference explains how a derivative distribution may “diverge” from its origins, and why they have to regularly resynchronize with their source in order to benefit from improvements made upstream."
msgstr ""

msgid "On the other hand, a sub-project can not diverge, since all the work on it consists of directly improving Debian in order to adapt it to a specific goal."
msgstr ""

msgid "The most known distribution derived from Debian is, without a doubt, Ubuntu, but there are many. See <xref linkend=\"derivative-distributions\" /> to learn about their particularities and their positioning in relationship to Debian."
msgstr ""

msgid "Here is a small selection of current sub-projects:"
msgstr ""

msgid "Debian Jr., by Ben Armstrong, offering an appealing and easy to use Debian system for children;"
msgstr ""

msgid "Debian Edu, by Petter Reinholdtsen, focused on the creation of a specialized distribution for the academic world;"
msgstr ""

msgid "Debian Med, by Andreas Tille, dedicated to the medical field;"
msgstr ""

msgid "Debian Multimedia which deals with audio and multimedia work;"
msgstr ""

msgid "Debian GIS which takes care of Geographical Information Systems applications and users;"
msgstr ""

msgid "Debian Accessibility, improving Debian to match the requirements of people with disabilities;"
msgstr ""

msgid "Debian Science, finally, working on providing researchers and scientists a better experience using Debian."
msgstr ""

msgid "DebiChem, targeted at Chemistry, provides chemical suites and programs."
msgstr ""

msgid "The number of projects will most likely continue to grow with time and improved perception of the advantages of Debian sub-projects. Fully supported by the existing Debian infrastructure, they can, in effect, focus on work with real added value, without worrying about remaining synchronized with Debian, since they are developed within the project."
msgstr ""

msgid "Administrative Teams"
msgstr ""

msgid "Most administrative teams are relatively closed and recruit only by co-optation. The best means to become a part of one is to intelligently assist the current members, demonstrating that you have understood their objectives and methods of operation."
msgstr ""

msgid "The <emphasis>ftpmasters</emphasis> are in charge of the official archive of Debian packages. They maintain the program that receives packages sent by developers and automatically stores them, after some checks, on the reference server (<literal>ftp-master.debian.org</literal>)."
msgstr ""

msgid "They must also verify the licenses of all new packages, in order to ensure that Debian may distribute them, prior to including them in the corpus of existing packages. When a developer wishes to remove a package, they address this team through the bug tracking system and the <emphasis>ftp.debian.org</emphasis> “pseudo-package”."
msgstr ""

msgid "<primary>ftpmaster</primary>"
msgstr ""

msgid "<emphasis>VOCABULARY</emphasis> The pseudo-package, a monitoring tool"
msgstr ""

msgid "<primary>pseudo-package</primary>"
msgstr ""

msgid "The bug tracking system, initially designed to associate bug reports with a Debian package, has proved very practical to manage other matters: lists of problems to be resolved or tasks to manage without any link to a particular Debian package. The “pseudo-packages” allow, thus, certain teams to use the bug tracking system without associating a real package with their team. Everyone can, thus, report issues that needs to be dealt with. For instance, the BTS has a <emphasis>ftp.debian.org</emphasis> entry that is used to report and track problems on the official package archive or simply to request removal of a package. Likewise, the <emphasis>www.debian.org</emphasis> pseudo-package refers to errors on the Debian website, and <emphasis>lists.debian.org</emphasis> gathers all the problems concerning the mailing lists."
msgstr ""

msgid "<emphasis>TOOL</emphasis> GitLab, Git repository hosting and much more"
msgstr ""

#, fuzzy
#| msgid "<primary>Stallman, Richard</primary>"
msgid "<primary><literal>salsa.debian.org</literal></primary>"
msgstr "<primary>Stallman, Richard</primary>"

#, fuzzy
msgid "<primary>GitLab</primary>"
msgstr "<primary>GNU</primary>"

msgid "A GitLab instance, known as <literal>salsa.debian.org</literal>, is used by Debian to host the Git packaging repositories but this software offers much more than simple hosting and Debian contributors have been quick to leverage the continuous integration features (running tests, or even building packages, on each push). Debian contributors also benefit from a cleaner contribution workflow thanks the well understood merge request process (similar to GitHub's pull requests)."
msgstr ""

msgid "GitLab replaced FusionForge (which was running on a service known as <literal>alioth.debian.org</literal>) for collaborative package maintenance. This service is administered by Alexander Wirt, Bastian Blank and Jörg Jaspert. <ulink type=\"block\" url=\"https://salsa.debian.org/\" /> <ulink type=\"block\" url=\"https://wiki.debian.org/Salsa/Doc\" />"
msgstr ""

msgid "The <emphasis>Debian System Administrators</emphasis> (<acronym>DSA</acronym>) team (<email>debian-admin@lists.debian.org</email>), as one might expect, is responsible for system administration of the many servers used by the project. They ensure optimal functioning of all base services (DNS, Web, e-mail, shell, etc.), install software requested by Debian developers, and take all precautions in regards to security. <ulink type=\"block\" url=\"https://dsa.debian.org\" />"
msgstr ""

msgid "<primary><emphasis>debian-admin</emphasis></primary>"
msgstr ""

msgid "<primary>DSA (Debian System Administrators)</primary>"
msgstr ""

#, fuzzy
#| msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-admin@lists.debian.org</email></secondary>"
msgstr "<primary>GNU</primary> <secondary> Unix Değil </secondary>"

msgid "<emphasis>TOOL</emphasis> Debian Package Tracker"
msgstr ""

msgid "<primary>package tracking system</primary>"
msgstr ""

msgid "<primary>system</primary><secondary>package tracking system</secondary>"
msgstr ""

msgid "<primary>Debian Package Tracker</primary>"
msgstr ""

msgid "<primary>tracker</primary><secondary>Debian Package Tracker</secondary>"
msgstr ""

msgid "<primary>package</primary><secondary>Debian Package Tracker</secondary>"
msgstr ""

msgid "<primary>PTS</primary>"
msgstr ""

msgid "<primary>DDPO</primary>"
msgstr ""

msgid "<primary>Debian Developer's Packages Overview</primary>"
msgstr ""

msgid "This is one of Raphaël's creations. The basic idea is, for a given package, to centralize as much information as possible on a single page. Thus, one can quickly check the status of a program, identify tasks to be completed, and offer one's assistance. This is why this page gathers all bug statistics, available versions in each distribution, progress of a package in the <emphasis role=\"distribution\">Testing</emphasis> distribution, the status of translations of descriptions and debconf templates, the possible availability of a new upstream version, notices of noncompliance with the latest version of the Debian Policy, information on the maintainer, and any other information that said maintainer wishes to include. <ulink type=\"block\" url=\"https://tracker.debian.org/\" />"
msgstr ""

msgid "An e-mail subscription service completes this web interface. It automatically sends the following selected information to the list: bugs and related discussions, availability of a new version on the Debian servers, new translations available for proofreading, etc."
msgstr ""

msgid "Advanced users can, thus, follow all of this information closely and even contribute to the project, once they have got a good enough understanding of how it works."
msgstr ""

msgid "Another web interface, known as <emphasis>Debian Developer's Packages Overview</emphasis> (DDPO), provides each developer a synopsis of the status of all Debian packages placed under their charge. <ulink type=\"block\" url=\"https://qa.debian.org/developer.php\" />"
msgstr ""

msgid "These two websites are tools developed and managed by the group responsible for quality assurance within Debian (known as Debian QA)."
msgstr ""

msgid "<primary>assurance</primary><secondary>quality assurance</secondary>"
msgstr ""

msgid "<primary>quality</primary><secondary>assurance</secondary>"
msgstr ""

msgid "The <emphasis>listmasters</emphasis> administer the e-mail server that manages the mailing lists. They create new lists, handle bounces (delivery failure notices), and maintain spam filters (unsolicited bulk e-mail)."
msgstr ""

msgid "<primary>listmaster</primary>"
msgstr ""

msgid "<emphasis>CULTURE</emphasis> Traffic on the mailing lists: some figures"
msgstr ""

msgid "<primary>lists</primary><secondary>mailing lists</secondary>"
msgstr ""

msgid "<primary>mailing lists</primary>"
msgstr ""

msgid "The mailing lists are, without a doubt, the best testimony to activity on a project, since they keep track of everything that happens. The numbers (from May 2019) regarding our mailing lists speak for themselves: Debian hosts about 315 lists, totaling over 303,000 individual subscriptions. 227,000 e-mails are delivered every day."
msgstr ""

msgid "Each specific service has its own administration team, generally composed of volunteers who have installed it (and also frequently programmed the corresponding tools themselves). This is the case of the bug tracking system (BTS), the package tracker, <literal>salsa.debian.org</literal> (GitLab server, see sidebar <xref linkend=\"sidebar.gitlab\" />), the services available on <literal>qa.debian.org</literal>, <literal>lintian.debian.org</literal>, <literal>buildd.debian.org</literal>, <literal>cdimage.debian.org</literal>, etc."
msgstr ""

msgid "Development Teams, Transversal Teams"
msgstr ""

msgid "Unlike administrative teams, the development teams are rather widely open, even to outside contributors. Even if Debian does not have a vocation to create software, the project needs some specific programs to meet its goals. Of course, developed under a free software license, these tools make use of methods proven elsewhere in the free software world."
msgstr ""

msgid "Debian has developed little software of its own, but certain programs have assumed a starring role, and their fame has spread beyond the scope of the project. Good examples are <command>dpkg</command>, the Debian package management program (it is, in fact, an abbreviation of Debian PacKaGe, and generally pronounced as “dee-package”), and <command>apt</command>, a tool to automatically install any Debian package, and its dependencies, guaranteeing the consistency of the system after an upgrade (its name is an acronym for Advanced Package Tool). Their teams are, however, much smaller, since a rather high level of programming skill is required to gain an overall understanding of the operations of these types of programs."
msgstr ""

msgid "The most important team is probably that for the Debian installation program, <command>debian-installer</command>, which has accomplished a work of momentous proportions since its conception in 2001. Numerous contributors were needed, since it is difficult to write a single program able to install Debian on a dozen different architectures. Each one has its own mechanism for booting and its own bootloader. All of this work is coordinated on the <email>debian-boot@lists.debian.org</email> mailing list, under the direction of Cyril Brulebois. <ulink type=\"block\" url=\"https://www.debian.org/devel/debian-installer/\" /> <ulink type=\"block\" url=\"https://joeyh.name/blog/entry/d-i_retrospective/\" />"
msgstr ""

msgid "The (very small) <command>debian-cd</command> program team has an even more modest objective. Many “small” contributors are responsible for their architecture, since the main developer can not know all the subtleties, nor the exact way to start the installer from the CD-ROM."
msgstr ""

msgid "Many teams must collaborate with others in the activity of packaging: <email>debian-qa@lists.debian.org</email> tries, for example, to ensure quality at all levels of the Debian project. The <email>debian-policy@lists.debian.org</email> list develops Debian Policy according to proposals from all over the place. The teams in charge of each architecture (<email>debian-<replaceable>architecture</replaceable>@lists.debian.org</email>) compile all packages, adapting them to their particular architecture, if needed."
msgstr ""

#, fuzzy
#| msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-qa@lists.debian.org</email></secondary>"
msgstr "<primary>GNU</primary> <secondary> Unix Değil </secondary>"

msgid "<primary>mailing lists</primary><secondary><email>debian-<replaceable>architecture</replaceable>@lists.debian.org</email></secondary>"
msgstr ""

msgid "Other teams manage the most important packages in order to ensure maintenance without placing too heavy a load on a single pair of shoulders; this is the case with the C library and <email>debian-glibc@lists.debian.org</email>, the C compiler on the <email>debian-gcc@lists.debian.org</email> list, or Xorg on the <email>debian-x@lists.debian.org</email> (this group is also known as the X Strike Force)."
msgstr ""

msgid "Follow Debian News"
msgstr ""

msgid "As already mentioned, the Debian project evolves in a very distributed, very organic way. As a consequence, it may be difficult at times to stay in touch with what happens within the project without being overwhelmed with a never-ending flood of notifications."
msgstr ""

msgid "If you only want the most important news about Debian, you probably should subscribe to the <email>debian-announce@lists.debian.org</email> list. This is a very low-traffic list (around a dozen messages a year), and only gives the most important announcements, such as the availability of a new stable release, the election of a new Project Leader, or the yearly Debian Conference. <ulink type=\"block\" url=\"https://lists.debian.org/debian-announce/\" />"
msgstr ""

msgid "<primary>mailing lists</primary><secondary><email>debian-announce@lists.debian.org</email></secondary>"
msgstr ""

msgid "<primary>Debian Project News</primary>"
msgstr ""

msgid "More general (and regular) news about Debian are sent to the <email>debian-news@lists.debian.org</email> list. The traffic on this list is quite reasonable too (usually around a handful of messages a month), and it includes the semi-regular “Debian Project News”, which is a compilation of various small bits of information about what happens in the project. <ulink type=\"block\" url=\"https://lists.debian.org/debian-news/\" />"
msgstr ""

#, fuzzy
#| msgid "<primary>GNU</primary><secondary>is Not Unix</secondary>"
msgid "<primary>mailing lists</primary><secondary><email>debian-news@lists.debian.org</email></secondary>"
msgstr "<primary>GNU</primary> <secondary> Unix Değil </secondary>"

#, fuzzy
#| msgid "<emphasis>CULTURE</emphasis> Richard Stallman"
msgid "<emphasis>COMMUNITY</emphasis> The publicity team"
msgstr "<emphasis>KÜLTÜR</emphasis> Richard Stallman"

msgid "Debian's official communication channels are managed by volunteers of the Debian publicity team. They are delegates of the Debian Project Leader and moderate news and announcements posted there. Many other volunteers contribute to the team, for example, by writing content for “Debian Project News”, Debian's official blog (<ulink url=\"https://bits.debian.org\">bits.debian.org</ulink>) or the microblogging service (<ulink url=\"https://micronews.debian.org/\">micronews.debian.org</ulink>), which supplies social networking sites with microblogging content. <ulink type=\"block\" url=\"https://wiki.debian.org/Teams/Publicity\" />"
msgstr ""

msgid "For more information about the evolution of Debian and what is happening at some point in time in various teams, there is also the <email>debian-devel-announce@lists.debian.org</email> list. As its name implies, the announcements it carries will probably be more interesting to developers, but it also allows interested parties to keep an eye on what happens in more concrete terms than just when a stable version is released. While <email>debian-announce@lists.debian.org</email> gives news about the user-visible results, <email>debian-devel-announce@lists.debian.org</email> gives news about how these results are produced. As a side note, “d-d-a” (as it is sometimes referred to) is the only list that Debian developers must be subscribed to. <ulink type=\"block\" url=\"https://lists.debian.org/debian-devel-announce/\" />"
msgstr ""

msgid "<primary>mailing lists</primary><secondary><email>debian-devel-announce@lists.debian.org</email></secondary>"
msgstr ""

msgid "Debian's official blog (<ulink url=\"https://bits.debian.org\">bits.debian.org</ulink>) is also a good source of information. It conveys most of the interesting news that are published on the various mailing lists that we already covered and other important news contributed by community members. Since all Debian developers can contribute these news when they think they have something noteworthy to make public, Debian's blog gives a valuable insight while staying rather focused on the project as a whole."
msgstr ""

msgid "<primary>Planet Debian</primary>"
msgstr ""

msgid "A more informal source of information can also be found on Planet Debian, which aggregates articles posted by Debian contributors on their respective blogs. While the contents do not deal exclusively with Debian development, they provide a view into what is happening in the community and what its members are up to. <ulink type=\"block\" url=\"https://planet.debian.org/\" />"
msgstr ""

msgid "<primary>microblog</primary>"
msgstr ""

msgid "<primary>Identi.ca</primary>"
msgstr ""

msgid "<primary>Twitter</primary>"
msgstr ""

msgid "<primary>Facebook</primary>"
msgstr ""

msgid "<primary>social networks</primary>"
msgstr ""

msgid "<primary>network</primary><secondary>social networks</secondary>"
msgstr ""

msgid "The project is also well represented on social networks. Debian only has an official presence on Identi.ca (microblogging platform, powered by <emphasis>pump.io</emphasis>), but there are some accounts retransmitting the RSS feed from https://micronews.debian.org/ and many Debian contributors who are posting on non-official accounts. <ulink type=\"block\" url=\"https://identi.ca/debian\" /> <ulink type=\"block\" url=\"https://fosstodon.org/@debian\" /> <ulink type=\"block\" url=\"https://twitter.com/debian\" /> <ulink type=\"block\" url=\"https://www.facebook.com/debian\" /> <ulink type=\"block\" url=\"https://www.flickr.com/groups/debian\" /> <ulink type=\"block\" url=\"https://www.linkedin.com/company/debian\" />"
msgstr ""

msgid "The Role of Distributions"
msgstr ""

msgid "<primary>Linux distribution</primary><secondary>role</secondary>"
msgstr ""

msgid "A GNU/Linux distribution has two main objectives: install a free operating system on a computer (either with or without an existing system or systems), and provide a range of software covering all of the users' needs."
msgstr ""

msgid "The Installer: <command>debian-installer</command>"
msgstr ""

msgid "The <command>debian-installer</command>, designed to be extremely modular in order to be as generic as possible, targets the first objective. It covers a broad range of installation situations and in general, greatly facilitates the creation of a derivative installer corresponding to a particular case."
msgstr ""

msgid "This modularity, which also makes it very complex, may be daunting for the developers discovering this tool; but whether used in graphical or text mode, the user's experience is still similar. Great efforts have been made to reduce the number of questions asked at installation time, in particular thanks to the inclusion of automatic hardware detection software."
msgstr ""

msgid "It is interesting to note that distributions derived from Debian differ greatly on this aspect, and provide a more limited installer (often confined to the i386 or amd64 architectures), but more user-friendly for the uninitiated. On the other hand, they usually refrain from straying too far from package contents in order to benefit as much as possible from the vast range of software offered without causing compatibility problems."
msgstr ""

msgid "The Software Library"
msgstr ""

msgid "Quantitatively, Debian is undeniably the leader in this respect, with over 28,000 source packages. Qualitatively, Debian’s policy and long testing period prior to releasing a new stable version justify its reputation for stability and consistency. As far as availability, everything is available on-line through many mirrors worldwide, with updates pushed out every six hours."
msgstr ""

msgid "Many retailers sell DVD-ROMs on the Internet at a very low price (often at cost), the “images” for which are freely available for download. There is only one drawback: the low frequency of releases of new stable versions (their development sometimes takes more than two years), which delays the inclusion of new software."
msgstr ""

msgid "Most new free software programs quickly find their way into the development version which allows them to be installed. If this requires too many updates due to their dependencies, the program can also be recompiled for the stable version of Debian (see <xref linkend=\"debian-packaging\" /> for more information on this topic)."
msgstr ""

msgid "Lifecycle of a Release"
msgstr ""

msgid "<primary>lifecycle</primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Unstable</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Testing</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Stable</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Experimental</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Oldstable</emphasis></primary>"
msgstr ""

msgid "<primary><emphasis role=\"distribution\">Oldoldstable</emphasis></primary>"
msgstr ""

msgid "The project will simultaneously have three to six different versions of each program, named <emphasis role=\"distribution\">Experimental</emphasis>, <emphasis role=\"distribution\">Unstable</emphasis>, <emphasis role=\"distribution\">Testing</emphasis>, <emphasis role=\"distribution\">Stable</emphasis>, <emphasis role=\"distribution\">Oldstable</emphasis>, and even <emphasis role=\"distribution\">Oldoldstable</emphasis>. Each one corresponds to a different phase in development. For a good understanding, let us take a look at a program's journey, from its initial packaging to inclusion in a stable version of Debian."
msgstr ""

msgid "<emphasis>VOCABULARY</emphasis> Release"
msgstr ""

msgid "<primary>release</primary>"
msgstr ""

msgid "The term “release”, in the Debian project, indicates a particular version of a distribution (e.g., “unstable release” means “the unstable version”). It also indicates the public announcement of the launch of any new version (stable)."
msgstr ""

msgid "The <emphasis role=\"distribution\">Experimental</emphasis> Status"
msgstr ""

msgid "First let us take a look at the particular case of the <emphasis role=\"distribution\">Experimental</emphasis> distribution: this is a group of Debian packages corresponding to the software currently in development, and not necessarily completed, explaining its name. Not everything passes through this step; some developers add packages here in order to get feedback from more experienced (or braver) users."
msgstr ""

msgid "Otherwise, this distribution frequently houses important modifications to base packages, whose integration into <emphasis role=\"distribution\">Unstable</emphasis> with serious bugs would have critical repercussions. It is, thus, a completely isolated distribution, its packages never migrate to another version (except by direct, express intervention of the maintainer or the ftpmasters). It is also not self-contained: only a subset of the existing packages are present in <emphasis role=\"distribution\">Experimental</emphasis>, and it generally does not include the base system. This distribution is therefore mostly useful in combination with another, self-contained, distribution such as <emphasis role=\"distribution\">Unstable</emphasis>."
msgstr ""

msgid "The <emphasis role=\"distribution\">Unstable</emphasis> Status"
msgstr ""

msgid "Let us turn back to the case of a typical package. The maintainer creates an initial package, which they compile for the <emphasis role=\"distribution\">Unstable</emphasis> version and place on the <literal>ftp-master.debian.org</literal> server. This first event involves inspection and validation from the ftpmasters. The software is then available in the <emphasis role=\"distribution\">Unstable</emphasis> distribution, which is the “cutting edge” distribution chosen by users who are more concerned with having up-to-date packages than worried about serious bugs. They discover the program and then test it."
msgstr ""

msgid "If they encounter bugs, they report them to the package's maintainer. The maintainer then regularly prepares corrected versions, which they upload to the server."
msgstr ""

msgid "Every newly updated package is updated on all Debian mirrors around the world within six hours. The users then test the corrections and search for other problems resulting from the modifications. Several updates may then occur rapidly. During these times, autobuilder robots come into action. Most frequently, the maintainer has only one traditional PC and has compiled their package on the amd64 (or i386) architecture (or they opted for a source-only upload, thus without any precompiled package); the autobuilders take over and automatically compile versions for all the other architectures. Some compilations may fail; the maintainer will then receive a bug report indicating the problem, which is then to be corrected in the next versions. When the bug is discovered by a specialist for the architecture in question, the bug report may come with a patch ready to use."
msgstr ""

msgid "<primary>autobuilder</primary>"
msgstr ""

msgid "Compilation of a package by the autobuilders"
msgstr ""

msgid "<emphasis>QUICK LOOK</emphasis> <command>buildd</command>, the Debian package recompiler"
msgstr ""

msgid "<primary><command>buildd</command></primary>"
msgstr ""

msgid "<primary>build daemon</primary>"
msgstr ""

msgid "<emphasis>buildd</emphasis> is the abbreviation of “build daemon”. This program automatically recompiles new versions of Debian packages on the architectures on which it is hosted (cross-compilation is avoided as much as possible)."
msgstr ""

msgid "Thus, to produce binaries for the <literal>arm64</literal> architecture, the project has <literal>arm64</literal> machines available. The <emphasis>buildd</emphasis> program runs on them continuously and creates binary packages for <literal>arm64</literal> from source packages sent by Debian developers."
msgstr ""

msgid "This software is used on all the computers serving as autobuilders for Debian. By extension, the term <emphasis>buildd</emphasis> frequently is used to refer to these machines, which are generally reserved solely for this purpose."
msgstr ""

msgid "Migration to <emphasis role=\"distribution\">Testing</emphasis>"
msgstr ""

msgid "A bit later, the package will have matured; compiled on all the architectures, it will not have undergone recent modifications. It is then a candidate for inclusion in the <emphasis role=\"distribution\">Testing</emphasis> distribution — a group of <emphasis role=\"distribution\">Unstable</emphasis> packages chosen according to some quantifiable criteria. Every day a program automatically selects the packages to include in <emphasis role=\"distribution\">Testing</emphasis>, according to elements guaranteeing a certain level of quality:"
msgstr ""

msgid "lack of critical bugs, or, at least fewer than the version currently included in <emphasis role=\"distribution\">Testing</emphasis>;"
msgstr ""

msgid "at least 5 days spent in <emphasis role=\"distribution\">Unstable</emphasis>, which is usually sufficient time to find and report any serious problems (successfully passing the package's own test suite, if it has one, reduces that time);"
msgstr ""

msgid "successful compilation on all officially supported architectures;"
msgstr ""

msgid "dependencies that can be satisfied in <emphasis role=\"distribution\">Testing</emphasis>, or that can at least be moved there together with the package in question;"
msgstr ""

msgid "automatic quality tests of the package (<emphasis role=\"pkg\">autopkgtest</emphasis>) — if defined — don't show any regression."
msgstr ""

msgid "This system is clearly not infallible; critical bugs are regularly found in packages included in <emphasis role=\"distribution\">Testing</emphasis>. Still, it is generally effective, and <emphasis role=\"distribution\">Testing</emphasis> poses far fewer problems than <emphasis role=\"distribution\">Unstable</emphasis>, being for many, a good compromise between stability and novelty."
msgstr ""

msgid "<emphasis>NOTE</emphasis> Limitations of <emphasis role=\"distribution\">Testing</emphasis>"
msgstr ""

msgid "While very interesting in principle, <emphasis role=\"distribution\">Testing</emphasis> does have some practical problems: the tangle of cross-dependencies between packages is such that a package can rarely move there completely on its own. With packages all depending upon each other, it is sometimes necessary to migrate a large number of packages simultaneously, which is impossible when some are uploading updates regularly. On the other hand, the script identifying the families of related packages works hard to create them (this would be an NP-complete problem, for which, fortunately, we know some good heuristics). This is why we can manually interact with and guide this script by suggesting groups of packages, or imposing the inclusion of certain packages in a group, even if this temporarily breaks some dependencies. This functionality is accessible to the Release Managers and their assistants."
msgstr ""

msgid "Recall that an NP-complete problem is of an exponential algorithmic complexity according to the size of the data, here being the length of the code (the number of figures) and the elements involved. The only way to resolve it is frequently to examine all possible configurations, which could require enormous means. A heuristic is an approximate, but satisfying, solution."
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> The Release Manager"
msgstr ""

msgid "<primary>Release Manager</primary>"
msgstr ""

msgid "<primary>Stable Release Manager</primary>"
msgstr ""

msgid "Release Manager is an important title, associated with heavy responsibilities. The bearer of this title must, in effect, manage the release of a new, stable version of Debian, and define the process for development of <emphasis role=\"distribution\">Testing</emphasis> until it meets the quality criteria for <emphasis role=\"distribution\">Stable</emphasis>. They also define a tentative schedule (not always followed)."
msgstr ""

msgid "We also have Stable Release Managers, often abbreviated SRM, who manage and select updates for the current stable version of Debian. They systematically include security patches and examine all other proposals for inclusion, on a case by case basis, sent by Debian developers eager to update their package in the stable version."
msgstr ""

msgid "The Promotion from <emphasis role=\"distribution\">Testing</emphasis> to <emphasis role=\"distribution\">Stable</emphasis>"
msgstr ""

msgid "Let us suppose that our package is now included in <emphasis role=\"distribution\">Testing</emphasis>. As long as it has room for improvement, its maintainer must continue to improve it and restart the process from <emphasis role=\"distribution\">Unstable</emphasis> (but its later inclusion in <emphasis role=\"distribution\">Testing</emphasis> is generally faster: unless it changed significantly, all of its dependencies are already available). When it reaches perfection, the maintainer has completed their work. The next step is the inclusion in the <emphasis role=\"distribution\">Stable</emphasis> distribution, which is, in reality, a simple copy of <emphasis role=\"distribution\">Testing</emphasis> at a moment chosen by the Release Manager. Ideally, this decision is made when the installer is ready, and when no program in <emphasis role=\"distribution\">Testing</emphasis> has any known critical bugs."
msgstr ""

msgid "Since this moment never truly arrives, in practice, Debian must compromise: remove packages whose maintainer has failed to correct bugs on time, or agree to release a distribution with some bugs in the thousands of programs. The Release Manager will have previously announced a freeze period, during which each update to <emphasis role=\"distribution\">Testing</emphasis> must be approved. The goal here is to prevent any new version (and its new bugs), and to only approve updates fixing bugs."
msgstr ""

msgid "A package's path through the various Debian versions"
msgstr ""

msgid "<emphasis>VOCABULARY</emphasis> Freeze: the home straight"
msgstr ""

msgid "<primary>freeze</primary>"
msgstr ""

msgid "During the freeze period, development of the <emphasis role=\"distribution\">Testing</emphasis> distribution is blocked; no more automatic updates are allowed. Only the Release Managers are then authorized to change packages, according to their own criteria. The purpose is to prevent the appearance of new bugs by introducing new versions; only thoroughly examined updates are authorized when they correct significant bugs."
msgstr ""

msgid "After the release of a new stable version, the Stable Release Managers manage all further development (called “revisions”, ex: 7.1, 7.2, 7.3 for version 7). These updates systematically include all security patches. They will also include the most important corrections (the maintainer of a package must prove the gravity of the problem that they wish to correct in order to have their updates included)."
msgstr ""

msgid "At the end of the journey, our hypothetical package is now included in the stable distribution. This journey, not without its difficulties, explains the significant delays separating the Debian Stable releases. This contributes, over all, to its reputation for quality. Furthermore, the majority of users are satisfied using one of the three distributions simultaneously available. The system administrators, concerned above all about the stability of their servers, don't need the latest and greatest version of GNOME; they can choose Debian <emphasis role=\"distribution\">Stable</emphasis>, and they will be satisfied. End users, more interested in the latest versions of GNOME or KDE Plasma than in rock-solid stability, will find Debian <emphasis role=\"distribution\">Testing</emphasis> to be a good compromise between a lack of serious problems and relatively up-to-date software. Finally, developers and more experienced users may blaze the trail, testing all the latest developments in Debian <emphasis role=\"distribution\">Unstable</emphasis> right out of the gate, at the risk of suffering the headaches and bugs inherent in any new version of a program. To each their own Debian!"
msgstr ""

#, fuzzy
#| msgid "<emphasis>CULTURE</emphasis> Origin of the Debian name"
msgid "<emphasis>CULTURE</emphasis> GNOME and KDE Plasma, graphical desktop environments"
msgstr "<emphasis>KÜLTÜR</emphasis> Debian adının kökeni"

msgid "GNOME (GNU Network Object Model Environment) and Plasma by KDE (formerly known as K Desktop Environment) are the two most popular graphical desktop environments in the free software world, and will be presented in greater detail in <xref linkend=\"sect.graphical-desktops\" />."
msgstr ""

msgid "A desktop environment is a set of programs grouped together to allow easy management of the most common operations through a graphical interface. They generally include a file manager, office suite, web browser, e-mail program, multimedia accessories, etc. The most visible difference resides in the choice of the graphical library used: GNOME has chosen GTK+ (free software licensed under the LGPL), and the KDE community has selected Qt (a company-backed project, available nowadays both under the GPL and a commercial license). <ulink type=\"block\" url=\"https://www.gnome.org/\" /> <ulink type=\"block\" url=\"https://www.kde.org/\" />"
msgstr ""

msgid "Chronological path of a program packaged by Debian"
msgstr ""

msgid "The <emphasis role=\"distribution\">Oldstable</emphasis> and <emphasis role=\"distribution\">Oldoldstable</emphasis> Status"
msgstr ""

msgid "<primary>Long Term Support (LTS)</primary>"
msgstr ""

msgid "<primary>support</primary><secondary>Long Term Support (LTS)</secondary>"
msgstr ""

msgid "Each <emphasis role=\"distribution\">Stable</emphasis> release has an expected lifetime of about 5 years and given that releases tend to happen every 2 years, there can be up to 3 supported releases at a given point of time. When a new stable release happens, the former release becomes <emphasis role=\"distribution\">Oldstable</emphasis> and the one even before becomes <emphasis role=\"distribution\">Oldoldstable</emphasis>."
msgstr ""

msgid "This Long Term Support (LTS) of Debian releases is a recent initiative: individual contributors and companies joined forces to create the Debian LTS team. Older releases which are no longer supported by the Debian security team fall under the responsibility of this new team."
msgstr ""

msgid "The Debian security team handles security support in the current <emphasis role=\"distribution\">Stable</emphasis> release and also in the <emphasis role=\"distribution\">Oldstable</emphasis> release (but only for as long as is needed to ensure one year of overlap with the current stable release). This amounts roughly to three years of support for each release. The Debian LTS team handles the last (two) years of security support so that each releases benefits from at least 5 years of support and so that users can upgrade from version N to N+2, for example from Debian 8 \"Jessie\" to Debian 10 \"Buster\". <ulink type=\"block\" url=\"https://wiki.debian.org/LTS\" />"
msgstr ""

msgid "<emphasis>COMMUNITY</emphasis> Companies sponsoring the LTS effort"
msgstr ""

msgid "Long Term Support is a difficult commitment to make in Debian because volunteers tend to avoid the work that is not very fun. And providing security support for 5 years old software is — for many contributors — a lot less fun than packaging new upstream versions or developing new features."
msgstr ""

msgid "To bring this project to life, the project counted on the fact that long term support was particularly relevant for companies and that they would be willing to mutualize the cost of this security support."
msgstr ""

msgid "The project started in June 2014: some organizations allowed their employees to contribute part-time to Debian LTS while others preferred to sponsor the project with money so that Debian contributors get paid to do the work that they would not do for free. Most Debian contributors willing to be paid to work on LTS got together to create a clear sponsorship offer managed by Freexian (Raphaël Hertzog's company): <ulink type=\"block\" url=\"https://www.freexian.com/services/debian-lts.html\" />"
msgstr ""

msgid "In the Debian LTS team, the volunteers work on packages they care about while the paid contributors prioritize packages used by their sponsors."
msgstr ""

msgid "The project is always looking for new sponsors: What about your company? Can you let an employee work part-time on long term support? Can you allocate a small budget for security support? <ulink type=\"block\" url=\"https://wiki.debian.org/LTS/Funding\" />"
msgstr ""