[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Aerogear-dev] /example repo

I would have to say the cons outweigh the pros on this. Not only would including them all together pretty much kill the ability to deploy to OpenShift, eventually as there are many examples added, the overhead to download everything would be ridiculous … especially if someone is only interested in one particular example.

What if we keep examples in their own repos and devise a naming convention (something like example-* so the cordova one would be aerogear/example-kitchensink-cordova) and direct people to the organization page where all of the repos are listed or we could even add a page to the wiki where we could better organize, group and link the examples in a way that is easy to understand.


On Mar 26, 2012, at 7:26 AM, Jay Balunas wrote:

> Hi Guys.
> I wanted to discuss the idea of having an example repo for aerogear.  
> Pros:
> - Avoids one example, one repo explosion 
> - Easier for new user to grok the repos, and the examples in one plase
> - We can provide instructions for inclusion in it, again easier for people to start with.
> Cons:
> - Adds some overhead initially, and for each example
> - Somethings like phonegap build and openshift expect apps to the root of the repo
> - Not all build systems work the same
>  - Might need mutiiple /example repo's by type?
> Thoughts?  BTW - this is related to AEROGEAR-6 where Qmx is making a TorqueBox example.
> -Jay
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev redhat com
> https://www.redhat.com/mailman/listinfo/aerogear-dev

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]