\summary{2008}{3}{13}



\agendaitem{Document of being an active developer}
\index{developer certificate}

No updates


\agendaitem{Slacker arches}
\index{arches!slacking}

2 months ago:
vapier will work on rich0's suggestion and repost it for 
discussion on -dev ML

Updates:
vapier said he was going to work on it this weekend.


\agendaitem{GLEP 46: Allow upstream tags in metadata.xml}

Reference: \glep{46}

Last month: Caveat on approval about allowed protocols

Updates: No updates; no authors present


\agendaitem{EAPI 0}
\index{EAPI!0}

Last month: Halcy0n was working on it

Updates:
	Ciaran has been contributing and has committed quite a few 
		things. Halcy0n hopes to work on it in the next couple of weeks. 
		He informed us that Ciaran said when he finishes the environment 
		tables, EAPI=0 is probably a week of solid work from having a 
		draft for review.

		Halcy0n wasn't around when the topic came up, so the above info 
		was from after the meeting.


\agendaitem{Google Summer of Code}
\index{GSoC}

Should Gentoo devs be allowed to participate?

GNOME's policy is that they favor people who haven't contributed 
	before, but they will accept great projects from contributors.

Decision: Council members will become additional SoC admins, and 
	will serve as tiebreaker votes if they aren't actively participating 
	in SoC project selection.

Decision: Gentoo SoC admins will decide whether non-contributors 
	should be favored over contributors.



\agendaitem{Package maintainers}
\index{proxy-maintainers}

Decision: We'll promote proxy-maintainers more -- GMN, website, etc.



\agendaitem{amd64 arch team and big bug list}
\index{arches!slacking}\index{arch!amd64}

	kingtaco (mike) said it's hard to keep people interested in 
	keywording.

	Anyone interested has had permission to keyword and stabilize 
	non-system packages since 2007.1 (see -core email from kingtaco with 
	subject "AMD64 keywording").


\agendaitem{Open floor}
\index{council!meeting!required attendees}

	A list of required attendees would be useful. dberkholz will start 
	creating the agenda along with this list in advance of the meeting.
	Posting the agenda on a google calendar, along with other stuff, 
	could help. flameeyes is starting to work with the PR team on this.