OE Github repositories

OE Github repositories

[Paul Eggleton]

Hi folks,

Could whoever has admin access for the OpenEmbedded repositories on github 
please do two things:

1) Stop having both "oe-core" and "openembedded-core" repositories - the 
latter is four months out-of-date. I'd suggest if we want to be consistent 
with our openembedded.org repos we should keep the "openembedded-core" 
repository and make it so it is kept up-to-date.

2) Rename the "meta-oe" repository to "meta-openembedded", since meta-oe the 
layer is distinct from meta-openembedded the repository, and again this would 
be consistent with the primary repository naming.

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: OE Github repositories

[Koen Kooi]

Op 28 apr. 2014, om 12:10 heeft Paul Eggleton <paul.eggleton@linux.intel.com> het volgende geschreven:

> Hi folks,
> 
> Could whoever has admin access for the OpenEmbedded repositories on github 
> please do two things:
> 
> 1) Stop having both "oe-core" and "openembedded-core" repositories - the 
> latter is four months out-of-date. I'd suggest if we want to be consistent 
> with our openembedded.org repos we should keep the "openembedded-core" 
> repository and make it so it is kept up-to-date.
> 
> 2) Rename the "meta-oe" repository to "meta-openembedded", since meta-oe the 
> layer is distinct from meta-openembedded the repository, and again this would 
> be consistent with the primary repository naming.

Keep in mind that renaming/removing 'oe-core' and 'meta-oe' will breaks things which use those repos to pull from by default. Which the oe.org git server has improved a lot, it still can't beat githubs CDN.

Re: OE Github repositories

[Paul Eggleton]

On Monday 28 April 2014 12:43:58 Koen Kooi wrote:
> Op 28 apr. 2014, om 12:10 heeft Paul Eggleton 
<paul.eggleton@linux.intel.com> het volgende geschreven:
> > Hi folks,
> > 
> > Could whoever has admin access for the OpenEmbedded repositories on github
> > please do two things:
> > 
> > 1) Stop having both "oe-core" and "openembedded-core" repositories - the
> > latter is four months out-of-date. I'd suggest if we want to be consistent
> > with our openembedded.org repos we should keep the "openembedded-core"
> > repository and make it so it is kept up-to-date.
> > 
> > 2) Rename the "meta-oe" repository to "meta-openembedded", since meta-oe
> > the layer is distinct from meta-openembedded the repository, and again
> > this would be consistent with the primary repository naming.
> 
> Keep in mind that renaming/removing 'oe-core' and 'meta-oe' will breaks
> things which use those repos to pull from by default. Which the oe.org git
> server has improved a lot, it still can't beat githubs CDN.

OK then, how about this instead:

1) Ensure the "openembedded-core" repository is kept up-to-date

2) Add a "meta-openembedded" repository and ensure it is kept up-to-date

3) Add a warning to the description for the contracted name repositories that 
the fully-named repositories should be used instead, so we can eventually drop 
them

4) Change documentation / scripts to match #3

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: OE Github repositories

[Koen Kooi]

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

Paul Eggleton schreef op 28-04-14 13:08:
> On Monday 28 April 2014 12:43:58 Koen Kooi wrote:
>> Op 28 apr. 2014, om 12:10 heeft Paul Eggleton
> <paul.eggleton@linux.intel.com> het volgende
> geschreven:
>>> Hi folks,
>>> 
>>> Could whoever has admin access for the OpenEmbedded repositories on
>>> github please do two things:
>>> 
>>> 1) Stop having both "oe-core" and "openembedded-core" repositories -
>>> the latter is four months out-of-date. I'd suggest if we want to be
>>> consistent with our openembedded.org repos we should keep the
>>> "openembedded-core" repository and make it so it is kept up-to-date.
>>> 
>>> 2) Rename the "meta-oe" repository to "meta-openembedded", since
>>> meta-oe the layer is distinct from meta-openembedded the repository,
>>> and again this would be consistent with the primary repository
>>> naming.
>> 
>> Keep in mind that renaming/removing 'oe-core' and 'meta-oe' will
>> breaks things which use those repos to pull from by default. Which the
>> oe.org git server has improved a lot, it still can't beat githubs CDN.
> 
> OK then, how about this instead:
> 
> 1) Ensure the "openembedded-core" repository is kept up-to-date
> 
> 2) Add a "meta-openembedded" repository and ensure it is kept up-to-date
> 
> 3) Add a warning to the description for the contracted name repositories
> that the fully-named repositories should be used instead, so we can
> eventually drop them
> 
> 4) Change documentation / scripts to match #3

Sounds like a good plan to me!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFTXk1mMkyGM64RGpERAn8NAJ49r8TimCZIouIBM45jseXqA3xUCACdGPsh
jb5olKQRlsskP9x4vlmEIms=
=FqlW
-----END PGP SIGNATURE-----

Re: OE Github repositories

[Paul Eggleton]

On Monday 28 April 2014 14:45:26 Koen Kooi wrote:
> Paul Eggleton schreef op 28-04-14 13:08:
> > OK then, how about this instead:
> > 
> > 1) Ensure the "openembedded-core" repository is kept up-to-date
> > 
> > 2) Add a "meta-openembedded" repository and ensure it is kept up-to-date
> > 
> > 3) Add a warning to the description for the contracted name repositories
> > that the fully-named repositories should be used instead, so we can
> > eventually drop them
> > 
> > 4) Change documentation / scripts to match #3
> 
> Sounds like a good plan to me!

OK, so who will do this then (whoever has access)?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [oe] OE Github repositories

[Phil Blundell]

On Fri, 2014-05-16 at 11:51 +0100, Paul Eggleton wrote:
> On Monday 28 April 2014 14:45:26 Koen Kooi wrote:
> > Paul Eggleton schreef op 28-04-14 13:08:
> > > OK then, how about this instead:
> > > 
> > > 1) Ensure the "openembedded-core" repository is kept up-to-date
> > > 
> > > 2) Add a "meta-openembedded" repository and ensure it is kept up-to-date
> > > 
> > > 3) Add a warning to the description for the contracted name repositories
> > > that the fully-named repositories should be used instead, so we can
> > > eventually drop them
> > > 
> > > 4) Change documentation / scripts to match #3
> > 
> > Sounds like a good plan to me!
> 
> OK, so who will do this then (whoever has access)?

I can do it if you like.

p.

Re: [oe] OE Github repositories

[Philip Balister]

On 05/16/2014 06:52 AM, Phil Blundell wrote:
> On Fri, 2014-05-16 at 11:51 +0100, Paul Eggleton wrote:
>> On Monday 28 April 2014 14:45:26 Koen Kooi wrote:
>>> Paul Eggleton schreef op 28-04-14 13:08:
>>>> OK then, how about this instead:
>>>>
>>>> 1) Ensure the "openembedded-core" repository is kept up-to-date
>>>>
>>>> 2) Add a "meta-openembedded" repository and ensure it is kept up-to-date
>>>>
>>>> 3) Add a warning to the description for the contracted name repositories
>>>> that the fully-named repositories should be used instead, so we can
>>>> eventually drop them
>>>>
>>>> 4) Change documentation / scripts to match #3
>>>
>>> Sounds like a good plan to me!
>>
>> OK, so who will do this then (whoever has access)?
> 
> I can do it if you like.

Thanks for taking care of this.

Philip

> 
> p.
> 
> 

Re: OE Github repositories

[Phil Blundell]

On Fri, May 16, 2014 at 11:51:06AM +0100, Paul Eggleton wrote:
> On Monday 28 April 2014 14:45:26 Koen Kooi wrote:
> > Paul Eggleton schreef op 28-04-14 13:08:
> > > OK then, how about this instead:
> > > 
> > > 1) Ensure the "openembedded-core" repository is kept up-to-date
> > > 
> > > 2) Add a "meta-openembedded" repository and ensure it is kept up-to-date
> > > 
> > > 3) Add a warning to the description for the contracted name repositories
> > > that the fully-named repositories should be used instead, so we can
> > > eventually drop them
> > > 
> > > 4) Change documentation / scripts to match #3
> > 
> > Sounds like a good plan to me!
> 
> OK, so who will do this then (whoever has access)?

[Cc list trimmed due to non-member posting constraints on oe-devel.]

I've done #1, #2 and #3.  I didn't know what scripts you were referring to
in #4 so I haven't taken any action on that.

p.

Re: OE Github repositories

[Paul Eggleton]

On Sunday 18 May 2014 21:01:18 Phil Blundell wrote:
> On Fri, May 16, 2014 at 11:51:06AM +0100, Paul Eggleton wrote:
> > On Monday 28 April 2014 14:45:26 Koen Kooi wrote:
> > > Paul Eggleton schreef op 28-04-14 13:08:
> > > > OK then, how about this instead:
> > > > 
> > > > 1) Ensure the "openembedded-core" repository is kept up-to-date
> > > > 
> > > > 2) Add a "meta-openembedded" repository and ensure it is kept
> > > > up-to-date
> > > > 
> > > > 3) Add a warning to the description for the contracted name
> > > > repositories
> > > > that the fully-named repositories should be used instead, so we can
> > > > eventually drop them
> > > > 
> > > > 4) Change documentation / scripts to match #3
> > > 
> > > Sounds like a good plan to me!
> > 
> > OK, so who will do this then (whoever has access)?
> 
> [Cc list trimmed due to non-member posting constraints on oe-devel.]
> 
> I've done #1, #2 and #3.  I didn't know what scripts you were referring to
> in #4 so I haven't taken any action on that.

OK, they're spread around a bit so I think others can take care of #4. Thanks!

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre