Closed cvan closed 8 years ago
Yep. That's the naming I had in mind also.
I assume we want to keep all these in MozVR for now, yes?
MozVR/aframe
MozVR/aframe-core
and not a new org?
aframe/aframe
aframe/core
That's what I was thinking. Are there tradeoffs that you can think of with that approach?
That's what I was thinking. Are there tradeoffs that you can think of with that approach?
it'd be nice if we had like
aframe/boilerplate
aframe/debug-toolbar
aframe/landscapes
if those were in the MozVR org, they'd have to be
MozVR/aframe-boilerplate
MozVR/aframe-debug-toolbar
MozVR/aframe-landscapes
I kind of like the simplicity of per-project teams à la https://github.com/Polymer/ and https://github.com/hapijs and what @dmarcos had going with https://github.com/vr-components/
I like the having one org per project. One project / one team / one org. It makes a clear separation and less likely to step on other peoples toes.
Also, when we start having outside contributors, we'd have to be careful to give them access to only aframe repos not other MozVR repos.
WFM
unfortunately, someone already has https://github.com/aframe and http://aframe.github.io/
'github.com/mozvr/aframe' it is
To
aframe
? Probably need to renamevr-markup
to likeaframe-core
or something.Also see MozVR/vr-markup#238.
/cc @jcarpenter