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

Re: [Aerogear-dev] /example repo



I would say if we are going to just rely on the AeroGear org page on github, then example-<tech>-<name> for ease of finding examples. If we build a wiki page, then I would vote <tech>-<name>-example.

Kris
On Mar 26, 2012, at 9:44 AM, Douglas Campos wrote:

>>> 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.
> Ok, I'm sold
> 
>>> 
>>> 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.
>> 
>> If we don't have an /example repo - I agree we'll need some convention for naming. 
> +1
> 
> -- qmx
> 
> _______________________________________________
> 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]