[katello-devel] Codebase Split-up

[David Davis]

Also, the team is a lot different now. I wasn't here for the original discussion but I'd vote we split it up. Like Jay said, I think scanning stuff like git history would be easier if the code was separated into distinct repos.

David

----- Original Message -----
> From: "Eric D Helms" <ericdhelms at gmail.com>
> To: "Cliff Perry" <cperry at redhat.com>
> Cc: "katello-devel" <Katello-devel at redhat.com>
> Sent: Friday, April 5, 2013 1:59:19 PM
> Subject: Re: [katello-devel] Codebase Split-up
> 
> 
> 
> 
> On Fri, Apr 5, 2013 at 1:52 PM, Cliff Perry < cperry at redhat.com > wrote:
> 
> 
> 
> On 05/04/13 18:36, Eric D Helms wrote:
> 
> 
> The idea of splitting our codebase up into more logical repositories has
> come about again as we head towards our 1.3 release. This is a topic
> that we have broached in the past, see
> https://www.redhat.com/ archives/katello-devel/2012- August/msg00243.html
> 
> The potential places for splitting out repos:
> 
> cli/
> agent/
> certs-tools/
> katello-configure/
> katello-utils/
> selinux/
> repos/
> src/ (a.k.a Katello)
> 
> The direct benefits I see:
> 
> - Travis can run smaller focused test suites and run faster (mostly for
> the CLI (python based) and the Web App (ruby based))
> - Clearer distinction about where a particular chunk of code lives (e.g.
> configuration lives with katello-configure)
> - Cleaner distinction between the application itself and the tooling
> that surrounds it
> 
> So, I'll ask, *why* are you posting this thread. What is your motivation for
> bring this topic up again. I suspect it is, your feeling that the 3 above
> items will benefit you or the team/project.
> 
> This was brought up by a few team members during our planning for the sprint
> (who were not me) and since I tried to push for this way back when, I took
> it on as a task to get the ball rolling since it is a story for current
> sprint.
> 
> 
> 
> What has changed since last time, that makes you feel the time is right to
> re-propose this?
> - otherwise folks will re-hash the same discussion you pointed too.
> 
> Circumstance has placed us in a situation where if we were ever going to do
> it, now would be the best time, where as previously there was associated
> overhead due to the place the project was in.
> 
> 
> 
> Cliff
> 
> 
> 
> 
> 
> Please add comments, concerns, justifications for or against as well as
> ideas on how we'd tackle parts like packaging.
> 
> 
> -Eric
> 
> 
> ______________________________ _________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/ mailman/listinfo/katello-devel
> 
> 
> 
> --
> Clifford Perry
> Manager, Satellite Engineering
> Red Hat, Inc.
> http://www.redhat.com/
> RHCA / RHCE# 805007680128201
> 
> 
> ______________________________ _________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/ mailman/listinfo/katello-devel
> 
> 
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel