Hadrian, Alex, I withdraw my -1 vote in the light of the discussion.
Richard. Sent from my Android phone On 27 Nov 2015 5:42 pm, "Hadrian Zbarcea" <[email protected]> wrote: > Richard, > > I suspect your -1 reflects a misunderstanding of the proposal and the > [discuss] thread brought some clarification. Are you staying at -1? > > Hadrian > > > On 11/26/2015 06:09 AM, Richard Downer wrote: > >> * brooklyn - all files in the root (no subdirs) >>> >> >> -1 >> >> The files in the root are: >> >> LICENSE >> NOTICE >> README.md >> .gitignore >> .gitattribues >> pom.xml >> >> All of these except pom.xml would also be present in every *other* >> repository, with minor modifications. This repo is not pulling its >> weight. >> >> * brooklyn-dist >>> usage/all >>> usage/dist >>> usage/scripts >>> usage/downstream-parent >>> usage/archetypes >>> >> >> My recommendation: drop `brooklyn-dist` and put all of this stuff into >> `brooklyn`. >> >> I'm with Mike on this one; 6 repositories - now 7 if there's a new one >> for the Go CLI - risks overcomplicating things (and not just for >> newcomers). >> >> A top-level project for the distribution and odds and ends, plus >> projects for "server", "web UI", "CLI" and "docs" is IMO acceptable - >> to most observers it's a logical split and people would know where >> they need to work. I'd accept "library" on the basis that we're trying >> to obsolete it by having a catalog of pure-YAML blueprints, but I >> suspect that it is going to hang around for quite a long time. >> >> Richard. >> >>
