From: galevsky@gmail.com
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] April Council meeting summary
Date: Fri, 13 Apr 2007 10:25:06 +0200 [thread overview]
Message-ID: <5d4c1ca80704130125h2bd2decbp266c0882aadcfc98@mail.gmail.com> (raw)
In-Reply-To: <200704121845.13563.vapier@gentoo.org>
Very good job.
2007/4/13, Mike Frysinger <vapier@gentoo.org>:
> here is a summary of this month's meeting. people seem to think that the CoC
> is set in stone now when in reality it is not ... feel free to hilite
> anything you feel wasnt addressed in the previous discussion or anything new
> you've thought of (i went through the previous threads and tried to distill
> out things that were missed, but i cant catch it all).
>
> CoC:
> - amne has been doing a good job putting the group together
> - ask proctors to address these two issues for next meeting:
> - add a "mission" statement
> - fix wording to have a positive spin
> sync Social Contract with Gentoo Foundation (external entities):
> - trustees will review the statement to clarify things and then
> we'll look again at syncing
> documentation for mail servers:
> - they are supposed to be finished in terms of content
> - wolf will look at getting them actually committed
> PMS:
> - current status looks good in getting issues resolved
> - should be up and running on Gentoo infra by next meeting
> - let the devs sort out the todo as the current work flow seems
> to be getting things done finally
> splitting gentoo-dev mailing lists:
> - no real favorable backing for this
> - people dont like -dev because of the crap, splitting the lists
> will just move the crap else where, not really solving anything
> - let proctors do their thing and if need be, review this again
> limiting of council powers:
> - doesnt seem to be real backing for this from dev community or
> the council itself
> - if a majority of developers are truly upset/disturbed by a
> council decision, it should show easily
> - if you dont like a council member, dont vote for them next time
> moving gentoo-core to public archives:
> - many people dislike this moving forward
> - use -dev over -core for most things
> - not going to happen at this time
> - look into getting a dev-only archive finally
> surveys:
> - robbat2 will look at getting user/dev surveys in place after the
> release of 2007.0
> - probably try and take fresh surveys after each bi-annual release
> from now on to see if we're meeting many of users' desires
> new metastructure proposal:
> - doesnt seem to address any of the problems it proposes to
> - a large majority of developers and users prefer the single tree
> development style that Gentoo has versus many smaller trees
>
> full log at the normal place:
> http://www.gentoo.org/proj/en/council/meeting-logs/20070412.txt
> -mike
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-04-13 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 22:45 [gentoo-dev] April Council meeting summary Mike Frysinger
2007-04-13 8:25 ` galevsky [this message]
2007-04-13 15:27 ` Ciaran McCreesh
2007-04-13 17:03 ` Ilya A. Volynets-Evenbakh
2007-04-14 6:36 ` [gentoo-dev] " Steve Long
[not found] ` <evod2s$d47$1@sea.gmane.org>
2007-04-13 17:11 ` Ciaran McCreesh
2007-04-13 17:20 ` Jakub Moc
2007-04-13 17:31 ` Ciaran McCreesh
2007-04-13 17:43 ` Jakub Moc
2007-04-13 17:59 ` Ciaran McCreesh
2007-04-13 17:50 ` Wernfried Haas
2007-04-14 6:34 ` [gentoo-dev] " Steve Long
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=5d4c1ca80704130125h2bd2decbp266c0882aadcfc98@mail.gmail.com \
--to=galevsky@gmail.com \
--cc=gentoo-dev@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