cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Weber <>
Subject Re: github organisation cloudstack
Date Wed, 16 Mar 2016 08:13:42 GMT
On Tue, Mar 15, 2016 at 11:07 PM, Daan Hoogland <>

> devs,
> There is a github organisation called cloudstack, to which we have more
> control then to the apache/cloudstack repo on github. We need to decide as
> community what to do with it.
> What are we going to do in this new organisation?

How about we test out different ways of improving our CI/other automation
tasks, without the 'pressure' we have with the official repos?
I.e. there is no pressure to get things merged, just test things out.

> Will we let/ask Schuberg Philis to put cosmic in there?

No offence, but why would we do that? Cosmic != CloudStack. They already
have what looks like a healthy github organization.
If they want to help improve the CloudStack organization then fine, but
lets not mix Cosmic into this.

> Will be ask/let Will to run upr to it (so we don't depend on the
> foundation)?

I don't see why not, let Will, SB, SBP, Accelerite (I have no clue how to
spell it right yet), or whoever wants to, do automated testing on it.
We need to figure out how we should grant access in a systematic way, but
as Will explained in a different thread -- the permissions needed are
non-intrusive and imho we should be generous handing them out to whoever
wants/needs, and revert that grant if necessary

> How will we sink it from/to apache or the apache github organisation?

I guess we still need to commit things to git-wip.a.o to keep doing commits
the apache way, that would keep the ASF github fork in sync.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message