Fork Observatory for RCOS?

[daviddoria]

Rather than have an RCOS branch of Observatory, should we fork it and call it RCOSObservatory? This would allow the issues on RCOSObservatory to be content related, whereas the issues on Observator would be backend related.

[colinsullivan]

Typically, when forking a repository the name of it isn't changed. I do think it would be useful to have a separate repository for the RCOS version of the site, however. The way to do this would be to create an RCOS "organization" on github. Then fork the repo into this organization, and it will then live at RCOS/Observatory instead of NateStedman/Observatory.

[mskmoorthy]

I tend to agree - This is splitting hairs -

[daviddoria]

Colin, sounds good, run it by Nate and go for it.

Moorthy, agree with what? I didn't see Colin say anything about this being a trivial addition? I think the Observatory issues are too cluttered with content issues, but that there should definitely be a place for both.

[mskmoorthy]

I did not say it is trivial - We have to make sure till we get this observatory going - Observatory may have a life on its own. Your email to Eric about previous dashboard did not go off well. I do not want that to happen again