[sakai2-tcc] code review process/software

Seth Theriault slt at columbia.edu
Fri Jun 28 07:12:39 PDT 2013


On Fri, Jun 28, 2013 at 10:03 AM, Neal Caidin <neal.caidin at apereo.org> wrote:
> I am the contact for our hosting provider Wush.net . It seems like Wush might also be able to help us with
> this too. I imagine I would be a logical contact for Atlassian. Probably good to have at least two backups
> for every service. Not good to have a single point of failure.

Isn't our real problem with Crucible that our codebase is "too big"
for Atlassian to handle on their hosted infrastructure? I seem to
remember Matt Jones talking about this at the Apereo Infrastructure
meeting/discussion and elsewhere in San Diego.

> I remember something about a hosting provider that Apereo Ja-Sig folks thought were full of awesomeness
> that can host these kinds of systems too. I've been happy with Wush, but if Infrastructure decides to
> consolidate providers, then the timing/cost considerations should tie in with that (provided there is a
> reaonable timeline?).

Jasig's hosting provider for Atlassian stuff is, I believe, the same
group that handles Atlassian's hosted service and their reputation is
stellar (just ask Eric Dalquist). Consolidation of back-end
infrastructure -- especially the hosting of Atlassian instances -- is
squarely on the future agenda, but no one is rushing.

Perhaps we should get some clarification/more detail from Matt and
others before we run out and redo all of this again. It needs to be a
coordinated and informed effort.

Seth


More information about the sakai2-tcc mailing list