[katello-devel] Proposal: Breaking up Codebase

[Bryan Kearney]

On 08/06/2012 08:01 AM, Chris Alfonso wrote:
> On 03/08/12 21:58 -0400, Eric Helms wrote:
>> Prior to using Github for source control management, the project had
>> one logical repository available that made sense for keeping the
>> various components of Katello contained within.  As the project has
>> grown, and as our community efforts increase I propose we break out
>> code base elements from our mainline repository for the following
>> reasons:
>>
>> 1) Reduces the overall size of the project repository.
>> 2) Provides smaller, logical components that users and developers can
>> work from and on.  This makes it easier for the community to
>> contribute as they can work on components that are important to them,
>> that they are more comfortable working on and are smaller (a.k.a less
>> imposing due to size).
>> 3) Decreases "tag-mania" on the mainline repository and lets the tags
>> and the packages they are associated with live on their own.  Provides
>> direct connection between package and repository (e.g. katello-cli.rpm
>> is derived from katello-cli git repository)
>> 4) Some components just have no logical reason to be contained within
>> the same repository.  (e.g. I don't need the CLI code to run and work
>> on Katello)
>> 5) The Github Organization concept with multiple repositories makes it
>> easy to manage multiple applications and pull requests associated with
>> each.
>>
>>
>> Components I currently see that could be stand-alone repositories:
>>
>> cli/
>> agent/
>> certs-tools/
>> puppet/
>> repos/
>> src/ (a.k.a Katello)
>>
>>
>> To quote Jordan: DISCUSS
>>


If we decide to break up, I would suggest delaying until after 1.1. 
First, it will not add any nutty risk tot he release and second, it will 
allow us to stabilize the community  builds before we switch things up 
again.
-- bk