diff options
authorAndreas K. Hüttel <>2017-03-12 21:18:58 +0100
committerAndreas K. Hüttel <>2017-03-12 21:19:38 +0100
commit878c327c7c670b87d5af8887e469dbe4254676fb (patch)
treed904bf0c077d8dd47fc167144c5114153858f3cd /decisions/summary-20151025.tex
parentAdd mar 2017 log (diff)
Add 2015/10 to index. Completes 2015/16 council term.
Diffstat (limited to 'decisions/summary-20151025.tex')
1 files changed, 80 insertions, 0 deletions
diff --git a/decisions/summary-20151025.tex b/decisions/summary-20151025.tex
new file mode 100644
index 0000000..488a18f
--- /dev/null
+++ b/decisions/summary-20151025.tex
@@ -0,0 +1,80 @@
+\agendaitem{Projects, herds, etc.}
+\index{herds}\index{project identification}\index{metadata.xml}
+A lengthy discussion on the merits of deprecating herds and on how to
+precisely do that resulted. The suggestion to use GUIDs for project
+identification was dismissed as slightly impractical, even though they
+provide for a near-unlimited number of projects.
+\vote{A: The concept of "herds" is abandoned, and the usage of the term
+deprecated. As a replacement, a package may be maintained by a
+7 yes, unanimous}
+\vote{B: do we want
+\item "$<$project$>$bla$<$/project$>$" or
+\item "$<$maintainer$><$project$>$bla$<$/project$><$/maintainer$>$" or
+\item "$<$maintainer type="project"$>$bla$<$/maintainer$>$" or
+\item "$<$maintainer$><$email$>$$<$/email$><$/maintainer$>$" ?
+3x a, 2x c, 2x d}
+This led to a discussion on the meaning of the vote outcome, and it
+was decided to re-formulate the question into several votes.
+\vote{C: New $<$project$>$ tag, or add something to existing $<$maintainer$>$
+4x project and 3x maintainer}
+\vote{D: what goes into the $<$project$>$ tag? a project shortname or an
+e-mail address?}{
+4x shortname, 1x e-mail, 2x abstain}
+\vote{E: do we want a 1:1 mapping of a new e-mail address to the
+project shortname?}{
+4 yes, 2 no}
+\vote{F: define the project shortname on the wiki project page, and
+expect that any project is *also* reachable as}{
+4 yes, 2 abstain}
+After these decisions several council members stated that things were
+going the wrong way and that they would like to change their votes for
+earlier decisions, thereby making latter decisions obsolete. As a
+consequence, it was suggested to scrap the just-made decisions again
+and request a GLEP on the issue.
+\vote{All votes today from vote B on are anulled. The council recommends
+that the details on herds to projects transition should be worked out
+in a GLEP.}{
+6 yes, 1 abstain}
+\agendaitem{Open bugs with council participation}
+\bug{503382}: Ulm stated that the 20131210 summary has been written and submitted,
+and minor corrections were suggested.
+\agendaitem{Open floor}
+No issues were brought up.