From: Florian Boor <florian.boor@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC Creation of a meta-telephony repository
Date: Fri, 11 Nov 2011 10:25:15 +0100 [thread overview]
Message-ID: <4EBCE9FB.9030002@kernelconcepts.de> (raw)
In-Reply-To: <j9iooh$q1p$1@dough.gmane.org>
Hi,
Am 11.11.2011 10:09, schrieb Koen Kooi:
>> I don't recall any general requirement that one needs to seek permission
>> from the TSC before acting on what seems like essentially a minor
>> operational matter. When did this become the policy?
>
> Ever since the TSC has been formed. You never noticed it since the second
> TSC was so shockingly passive.
the job of the TSC is sketched in the TSC Charter like this:
"To govern access to all technical aspects of OpenEmbedded, this includes
official git trees, openembedded-devel mailing list, bug trackers, QA systems,
and others as the TSC sees fit."
In this context my interpretation would be that the TSC grants permissions for
write access to the Git tree but nothing more. And further control related to
the responsible use of Git is not defined and IMHO never was. Phil has the
required permissions to create a layer, so why he would have to ask?
If there are really members out there who interpret this sentence as "you have
to ask the TSC for everything related to use of the Git server" we need to
discuss the charter again. If we do not make this more clear it won't take long
and someone steps up claiming that the TSC would have to accept any single
commit :-/
Greetings
Florian
--
The dream of yesterday Florian Boor
is the hope of today Tel: +49 271-771091-15
and the reality of tomorrow. Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de
http://www.kernelconcepts.de/en
next prev parent reply other threads:[~2011-11-11 9:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 15:49 RFC Creation of a meta-telephony repository Holger Freyther
2011-11-10 16:11 ` Philip Balister
2011-11-10 16:19 ` Paul Eggleton
2011-11-10 17:21 ` Phil Blundell
2011-11-10 20:22 ` Koen Kooi
2011-11-10 20:29 ` Florian Boor
2011-11-11 9:10 ` Koen Kooi
2011-11-10 21:07 ` Phil Blundell
2011-11-11 9:09 ` Koen Kooi
2011-11-11 9:25 ` Florian Boor [this message]
2011-11-11 9:38 ` Koen Kooi
2011-11-11 9:56 ` Florian Boor
2011-11-11 10:10 ` Phil Blundell
2011-11-11 10:37 ` Koen Kooi
2011-11-11 18:06 ` Denis 'GNUtoo' Carikli
-- strict thread matches above, loose matches on Subject: below --
2011-11-10 14:58 Holger Freyther
2011-11-10 15:00 ` Philip Balister
2011-11-10 15:16 ` Paul Eggleton
2011-11-10 15:16 ` Martin Jansa
2011-11-10 16:35 ` Koen Kooi
2011-11-10 18:57 ` Denys Dmytriyenko
2011-11-10 20:25 ` Koen Kooi
2011-11-10 21:01 ` Denys Dmytriyenko
2011-11-11 9:44 ` Holger Freyther
2011-11-11 10:45 ` Koen Kooi
2011-11-11 12:54 ` Holger Freyther
2011-11-11 13:02 ` Phil Blundell
2011-11-11 13:08 ` Paul Eggleton
2011-11-10 20:27 ` Florian Boor
2011-11-23 20:58 ` Khem Raj
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=4EBCE9FB.9030002@kernelconcepts.de \
--to=florian.boor@kernelconcepts.de \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.