blob: 7e6604a2ee8311719565badb0ab0904ef15124e7 (
plain)
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
|
CY24: Migrate glibc to CTI services
===================================
In 2024 the goal is to migrate the glibc project to use CTI services.
The community feedback was collected from July to August 2023.
The `GNU Maintainers for the glibc project
<https://sourceware.org/glibc/wiki/MAINTAINERS#Project_stewards_.28GNU_package_maintainers.29>`_
were asked to make a decision on switching to the services provided by
CTI and currently the following support has been tallied:
* Ryan Arnold - Yay
* Paul Eggert - Nay
* Jakub Jelinek - Abstain
* Maxim Kuvyrkov - Yay
* Joseph Myers - Yay
* Carlos O'Donell - Yay
* Alexandre Oliva - Nay
* Andreas Schwab - No statement
As of 2024-02-28 feedback from the stewards was being incorporated into
this document to provide assurances that FOSS would be used to provide
services and that there was a checking mechanism in place for services
to remain FOSS.
Next steps:
* Revisit discussion with Paul Eggert and attain resolution in March 2024
to move forward.
Posted originally here: https://inbox.sourceware.org/libc-alpha/45e98807-908f-0968-b6fe-5dbb0af265b1@redhat.com/
The following is the suggested list of services to be migrated (with notes):
* Mailing lists
* Support public-inbox for mailing list archives.
* Use of public-inbox means archives can be cloned and copied.
* Use of LF IT Subspace mailing list services (mlmmj, postfix).
* bug database
* Consider starting fresh in new Bugzilla 5.0.4+ instance and freeze old product.
* glibc component in sourceware instance marked "Not open for new bugs."
* No easy way to clone this but we can discuss options.
* Isolate bugzilla from other services.
* git
* Migrate to gitolite
* Community manages access via gitolite keys.
* Minimize all access to sources and isolate from other processes.
* Minimal server side web hooks where required.
* Isolate git service from other services.
* Stop supporting svn/cvs and provide tarball dumps.
* wiki
* Migrate to git-based documentation with existing content copied over.
* Suggest rst/Sphinx or similar to existing discussions for GCC docs.
* Sphinx with themes can provide a lot of flexibility for display.
* Isolate wiki service from other services.
* patch management
* Continue patchwork usage and maintenance of isolated instance
* Required for community driven pre-commit CI
* LF IT hosting patchwork instance with community hosting bots.
* Isolate patchwork from other services.
* Website
* Provide a simple static site.
* Isolate web hosting from other services.
* Meeting
* Already migrated away from proprietary solutions.
* Continue to use LF IT BBB instance for glibc meetings including weekly patch review.
* Isolate BBB from other services.
The current list of glibc services were put together as part of the
CTI TAC `glibc service enumeration <./enum>`_.
-----------------
* :ref:`genindex`
* :ref:`search`
|
