blob: cbd8895ec73e1ca61aae9c256988c1be5d3d3094 (
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
|
\summary{2016}{1}{10}
\agendaitem{Further discussion on GLEP 67}
References:
\begin{itemize}
\item \glep{67}
\item \wgoref{User:MGorny/GLEP:67}
\item \agoref{gentoo-project}{637270936c9f07e3bd2f10ee45264a42}
\end{itemize}
Michał Górny reported on the progress regarding \glep{67}. He has cleaned
the spec to make it more informative and updated the reference implementation
section for the most common software in use.
Nearly all herds have been merged into existing or new projects, or have been
abandoned.
Automated generation of projects.xml is already active on Gentoo Infrastructure.
A short discussion about the mapping between projects and subprojects has
happened. It has been agreed on not definitely specifying the mapping being 1:n
or m:n in the GLEP right now.
The general consensus was that m:n mapping resembles the reality best and
missing support of that map style in tools like mediawiki is not sufficient
to nail the connectivity to 1:n.
\vote{Approval of GLEP 67 with wording from \wgoref{User:MGorny/GLEP:67} as of
08:14, 10 January 2016}{Approved unanimously.}
\vote{The final deadline for the herds -> project migration is
to be the 24th January 2016. All remaining herds will be dropped after that and
the remaining packages will be assigned to maintainer-needed.}{Approved
unanimously.}
\agendaitem{Banning of EAPI 0 \& 3 for new ebuilds}
\index{EAPI!0}\index{EAPI!3}\index{EAPI!1}
References:
\begin{itemize}
\item \agoref{gentoo-project}{bc0a1b7498c389bdbb0b0d52feb43391}
\item \agoref{gentoo-dev}{6904e810caedf66d889458e6fd1cc552}
\end{itemize}
The Council voted on banning EAPI 0 \& 3 for new ebuilds and EAPI updates
in existing ebuilds. After some discussion an exception was made allowing
the security team and only the security team to do minor patching using
those EAPI levels. The decision was made unanimously.
Further the Council decided unanimously to amend the ban of EAPI
1 \& 2 made in the Council meeting 2014-03-11. To this effect, the
exception of updating EAPI=0 ebuilds to EAPI=1 is dropped.
\agendaitem{Bugs with council involvement}
\index{news items!format 1.1}
\begin{itemize}
\item
The Council briefly discussed \bug{503382} again. Ulm had written the
final missing summary. The bug is fixed now.
\item
The Council briefly discussed \bug{569914} and \bug{571490}. Dilfridge is
working on the logs.
\item
The Council voted on the NEWS item format 1.1, \bug{568068}. Format 1.1 allows
EAPI=5 style package dependency specification. Rich0 questioned the amount
of discussion with the community, but the general consensus was that the
public transparency for the size of the change has been enough. The Council
unanimously approved the new format.
\end{itemize}
\agendaitem{Open floor}
A short information exchange about the presence of Gentoo Linux at the 2016
FOSDEM has happened but further discussion has been moved to \#gentoo-fosdem
\@ freenode.
|
GitWeb