summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndreas K. Hüttel <dilfridge@gentoo.org>2017-02-22 23:12:00 +0100
committerAndreas K. Hüttel <dilfridge@gentoo.org>2017-02-22 23:12:00 +0100
commit5d6a017bc2a8380f306988a1a21136d425dd8ca0 (patch)
tree1007cebf19b8d1e4d26f4847f99200c7efd3132c /decisions/summary-20160214.tex
parentAdd Feb 2017 log (diff)
downloadcouncil-5d6a017bc2a8380f306988a1a21136d425dd8ca0.tar.gz
council-5d6a017bc2a8380f306988a1a21136d425dd8ca0.tar.bz2
council-5d6a017bc2a8380f306988a1a21136d425dd8ca0.zip
Continue the index experiment
Diffstat (limited to 'decisions/summary-20160214.tex')
-rw-r--r--decisions/summary-20160214.tex97
1 files changed, 97 insertions, 0 deletions
diff --git a/decisions/summary-20160214.tex b/decisions/summary-20160214.tex
new file mode 100644
index 0000000..f239cb1
--- /dev/null
+++ b/decisions/summary-20160214.tex
@@ -0,0 +1,97 @@
+\section{14 February 2016}
+
+\subsection{Options for new XML validation language}\index{XML validation}
+
+References:
+\begin{itemize}
+\item \agoref{gentoo-project}{3ebf4ccf0d4f27d6240888a3100d0d58}
+\item \agoref{gentoo-project}{fa05f5319ef4255d3e3fe34da79a2534}
+\end{itemize}
+
+The situation of what would be the best option to choose wasn't completely
+clear to the council and the proposing party wasn't present.
+
+Any further decision have been postponed until better metrics are available.
+
+\begin{itemize}
+\item Which are Gentoo's requirements for an xml validation language?
+\item Can both options provide the necessary capabilities?
+\item What are the pros and cons specific for our requirements?
+\item What are the advantages over our current system? Specifically what cannot
+ be done currently?
+\item Which tools are impacted when switching from DTD to an alternative?
+\end{itemize}
+
+Michał Górny volunteered to do some research on the output of all three
+validators.
+
+\subsection{Discuss situation of libressl support maintenance}\index{LibreSSL}
+
+Reference: \agoref{gentoo-project}{dc5406af670aebc050362fcbd8cd528e}
+
+The libressl situation sums up as following:
+\begin{itemize}
+\item main maintainer is currently inactive
+\item no team is present for libressl in Gentoo
+\item 1/2 of the tree has libressl support implemented
+\item a quite solid \href{https://github.com/gentoo/libressl/wiki/Transition-plan}{transition
+plan} is in place
+\end{itemize}
+
+The council shortly touched various topics around the introduction of
+libressl into the Gentoo ecosystem, but concluded that a project team
+is needed, to which questions and concerns can be directed.
+
+Some question which arise and should be answered by the project comprise
+\begin{itemize}
+\item Finish the work or remove it again?
+\item Does it make sense to introduce a second highly security relevant library
+ to the tree?
+\item Who adds the necessary code to the packages, the libressl team directly, or
+ via patch and bugs, or just the maintainers?
+\item Who is maintaining the libressl support in the packages, the libressl project
+ or the individual maintainers?
+\item What happens in case of API divergence between libressl and openssl? Who
+ maintains the necessary patches?
+\end{itemize}
+
+\subsection{Automatic bug assignments}\index{Bug assignment}\index{Bug wrangling}
+
+Reference: \agoref{gentoo-project}{00e02ff494857599633e2bbc30520ca3}
+
+The general preference of the council is positive towards automatic bug
+assignments. But so far no working solution has been proposed. At this
+point the Council sees no reason for any decision to be made itself.
+The community or the bug wrangling project should draft an implementation.
+
+
+\subsection{The usage of use() in global scope violates PMS}\index{use()}\index{PMS}\index{Dynamic SLOT}
+
+Reference: \agoref{gentoo-project}{69ed522b3b53de90e616267a77441012}
+
+The council members unanimously request all global usage of use() violating
+PMS (\verb+https://projects.gentoo.org/pms/6/pms.html#x1-650007.1\verb+) to be fixed
+until the March 2016 council meeting. After that members of the QA are
+asked to fix remaining ebuilds/eclasses.
+
+This decision renders the proposed solution for dynamic SLOTs (\bug{174407}) impossible.
+This topic was deferred to a later meeting to give time for an alternative solution to be found.
+
+\subsection{Bugs with council involvement}
+
+\begin{itemize}
+\item \bug{569914}:
+dilfridge is kindly to be asked to provide the missing council meeting logs
+and summary for the 20150727 meeting
+\item \bug{568068}:
+ulm volunteered to prepare an updated \glep{42} for the next meeting.
+The only open question is if the new news item format should include a
+Display-If-Visible header.
+\end{itemize}
+
+\subsection{Open floor}
+
+--
+
+
+