
\summary{2015}{3}{10}


\agendaitem{Infra team staffing issues}
\index{project!infrastructure}

References:
\begin{itemize}
\item agenda request: \agoref{gentoo-project}{2ccbe9e7dcbbe2320835ea440f4cac1e}
\item related -project mail: 
\agoref{gentoo-project}{2c8d8c149db1d5cfad877e6a355ff83b}
\end{itemize}

A proposal was made to make a few developers who are providing external
services into official infra team members so the services could possibly be
officially hosted.

Council response: Developers who are interested in helping or joining the infra 
team should contact them directly and if they have issues should elevate things 
to comrel or the council as necessary.


\agendaitem{Reducing/removing stable tree for some potentially lagging arches}
\index{stabilization!lagging arches}\index{arch!alpha}\index{arch!sparc}
\index{arch!ia64}\index{arch!ppc}\index{arch!ppc64}

References:
\begin{itemize}
\item agenda request: 
\agoref{gentoo-project}{d899dd93be2f93b85f65f47c54087806}
\item related -dev mail: 
\agoref{gentoo-dev}{a76eda0997a21e14d6a548e04590191b}
\end{itemize}

Some arches always appear to hold back stabilization and keywording efforts.
In particular alpha, sparc, ia64, ppc and ppc64 were mentioned.

Council response: Dropping excess packages from minor arches was discussed 
(i.e.  focusing more effort on keeping the core system set stable) but the 
majority of discussion was passed back to the lists so arch teams can 
contribute more information and ideas.


\agendaitem{Flagging packages that can be stabilized for all arches at the same 
time}
\index{stabilization}\index{ALLARCHES}

References:
\begin{itemize}
\item agenda request: 
\agoref{gentoo-project}{49389c3c62faaa11ffdeb07d42ceaf6d}
\item related -dev mail: 
\agoref{gentoo-dev}{aed760e7431f6d5ec7518be4d5b75c84}
\end{itemize}

Easily allow arch teams to handle and stabilize non-arch packages (icons,
theming, etc) across all arches.
Example solutions given include adding a new bugzilla keyword such as
"STABLEREQALL" or using a key set in a package's metadata.xml.

\vote{The council voted to add the STABLEREQALL keyword to bugzilla which will 
allow the first arch that stabilizes a package to also stabilize the remaining,
previous stable arches for the package.}{
Aye: dilfridge, williamh, radhermit, prometheanfire, rich0
Abstain: dberkholz, ulm}


\agendaitem{Combining various keyring related USE flags into one global}
\index{use flag!gnome-keyring}
\index{use flag!libsecret}
\index{use flag!wallet}

References:
\begin{itemize}
\item 
agenda request: 
\agoref{gentoo-project}{b26796b26c6fbcfbcd3240bf85a2a67f}
\item
related -dev mail: 
\agoref{gentoo-dev}{5c127aed355ee19d15ac38e114097f74}
\end{itemize}

Implementation specific USE flags (e.g. gnome-keyring, libsecret, wallet, etc)
force users to know about and enable each one. Perhaps instead use a global
"keyring" USE flag that controls keyring support.

Council response: Deferred to mailing lists and related projects or teams.


\agendaitem{Bugs assigned to Council}

\bug{503382}: No changes here.
