All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC Creation of a meta-telephony repository
Date: Fri, 11 Nov 2011 11:37:41 +0100	[thread overview]
Message-ID: <j9ittl$sf4$1@dough.gmane.org> (raw)
In-Reply-To: <1321006234.21488.35.camel@phil-desktop>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 11-11-11 11:10, Phil Blundell schreef:
> On Fri, 2011-11-11 at 10:25 +0100, Florian Boor wrote:
>> 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 :-/
> 
> Well, indeed.  Also, in the particular case at hand, it seems that the 
> board has already made a policy decision about community-maintained 
> layers being appropriate for hosting on oe.org.  I'm not sure that it is
>  within the TSC's remit to obstruct the implementation of that policy by
>  insisting on some sort of extra approval process every time someone
> wants to create such a layer.
> 
> The other thing that seems faintly absurd in this particular instance is
>  that nobody has raised any actual objection to the creation of the layer
>  in principle and, aside from noting that we don't wish the admin team to
>  be overworked, nor has anybody suggested any reasons why it shouldn't be
>  hosted on oe.org.  So, on that basis, and absent any reason to believe 
> that this layer would produce a crippling administrative workload, it 
> isn't obvious what rational basis the TSC would have for deciding to 
> oppose its creation.

Have you asked the TSC? My point was that you should ask before going ahead.
I can't speak for the TSC, but I wouldn't expect any troubles on that front,
but you do need to ask first.

In the past the TSC has expressed their suprise at git repos popping up on
oe.org with their knowledge.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFOvPr1MkyGM64RGpERAk5TAJ4z69GzWmjV6p9LCZv/HkDzgL4VlACdEuPh
rJ1ZwBNpUSyu5Foca7mJbIw=
=XQNE
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-11-11 10:44 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
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 [this message]
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='j9ittl$sf4$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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.