I have no particular objections to the term "client", so I would be ok with
guacamole/
guacamole-client/
guacamole-server/
or even
guacamole/
client/
server/
for reduced redundancy.
Of the two, I think the second would appeal to me a bit more, since
guacamole/guacamole-* does seem a bit unnecessary.
James
On Thu, Feb 11, 2016 at 3:29 PM, Mike Jumper <[email protected]>
wrote:
> Hello All,
>
> Now that the project has been accepted into the Apache incubator, we
> need to go about importing the source into Apache-hosted version
> control. For us, this means the previously-separate "guacamole-client"
> and "guacamole-server" repositories need to be combined into one.
>
> It is possible to combine multiple repositories while preserving
> history. I did this before with "guacamole-server" back when libguac,
> guacd, and libguac-client-* were all separate projects. We can filter
> the history such that everything is preserved. The question is how to
> arrange the repository itself.
>
> The obvious simple choice would be to keep the naming as-is and just
> use simple subdirectories of the root:
>
> guacamole/
> guacamole-client/
> guacamole-server/
>
> ...but I'm not sure that's best, nor do I want to unilaterally assume
> that's best.
>
> Any suggestions? Is guacamole/guacamole-* too redundant? Is now the
> time to ditch "guacamole-client" as too confusing and find a better
> name for that half of the stack?
>
> All ideas are welcome.
>
> Thanks,
>
> - Mike
>
