public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Anderson <gentoofan23@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: [gentoo-council] Council meeting summary for November 13, 2008
Date: Sat, 14 Feb 2009 18:35:30 -0500	[thread overview]
Message-ID: <20090214233530.GA4191@dodo.hsd1.nj.comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 268 bytes --]

The summary is attached. I've roughly based it off of Donnie's
work-in-progress summary with more information from the logs.

-- 
---------
Thomas Anderson
Gentoo Developer
/////////
Areas of responsibility:
AMD64, Secretary to the Gentoo Council
---------

[-- Attachment #2: councilsummary-20081113.txt --]
[-- Type: text/plain, Size: 1616 bytes --]

Roll call:
==========
dberkholz: 40 minutes lates, daylight savings time
Halcy0n: absent
Cardoe: here
dertobi123: here
lu_zero: here
Betelgeuse: here
jokey: absent, slacker

Topics:
=======

    No topics for the meeting were proposed.

Open Bugs:
==========

    Slacker Arches(bug 234706):
        
        Mark sent a proposal to gentoo-dev about this. No other discussion or
	decision.

    GLEP 55(.ebuild-$eapi extension, bug 234713):
        
        Conclusion:
            This bug has been RESO LATER'ed pending concrete need and
            consensus(GLEP 54 being the main one).

    Code of Conduct Update(Proctors no longer exist, bug 185572):
        
        Conclusion:
            Jorge(jmbsvicetto) will talk to other members of devrel about this
            bug.

    Extent of Code of Conduct enforcement(Banning people entirely from Gentoo,
    bug 234716):

        Conclusion:
            Userrel is responsible for establishing these policies. Since each
            developer is also a user at some point, these policies will apply
            to developers as well as users.

    GLEP 54(-scm package suffix. bug 234711):
    
        Conclusion:
            No decision. David Leverton commented that portage's current
            method for identifying 'live' ebuilds was hackish, as it depends
            on the list of inherited eclasses, which could change. Also, it
	    was pointed out that some ebuilds use scm eclasses to check out
	    specific revisions(mythtv). PROPERTIES=live was considered
            as another option.

             reply	other threads:[~2009-02-14 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14 23:35 Thomas Anderson [this message]
2009-02-15  4:46 ` [gentoo-council] Council meeting summary for November 13, 2008 Donnie Berkholz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090214233530.GA4191@dodo.hsd1.nj.comcast.net \
    --to=gentoofan23@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox