IMO: have the samples inside the Airavata repo. Have the gateway samples in their own repos. Because it might take up a life of its own. ex: the PHP client might go on to become a full blown gateway.
as Marlon mentioned, if that’s the case it would be better to have them in separate repos to restrict committership. On Apr 29, 2014, at 9:52 AM, Marlon Pierce <[email protected]> wrote: > Would we want to have the option to restrict committership to a specific > repo? > > Marlon > > On 4/29/14 12:32 PM, Suresh Marru wrote: >> For reference, please see what other projects are doing - >> https://git-wip-us.apache.org/repos/asf >> >> Projects like cloudstack, cordova, couchdb jclouds and others pretty much >> add a new repo for lots of components. Other projects choose to have one >> repo for everything. >> >> I am not yet weighing one option over other and soliciting everyone’s input. >> >> Suresh >> >> On Apr 29, 2014, at 12:27 PM, Suresh Marru <[email protected]> wrote: >> >>> Hi All, >>> >>> Since the transition to git was uneventful and seems to work well, I want >>> to resurrect the discussion of a code repos. >>> >>> To demonstrate Airavata we will need reference implementations of API. >>> Previous web implementations are all over the place. Can we discuss what is >>> the good place to consolidate these examples and indeed release them >>> periodically? >>> >>> Two options to consider: >>> >>> * Have these web implementations as a module within main trunk and release >>> them along with Airavata. >>> * Create a separate repo and have a separate release cycle. >>> >>> Any opinions? >>> >>> Suresh >>> >
