Redirect governance resources to super project#13
Conversation
|
@jmertic , would this type of restructure for governance documents in sub-module repos of OpenMoonRay satisfy ASWF GitHub Best Practices Guidelines? Alternatively, we'll need to maintain sync on all these files across the 20+ repositories. |
|
Hey - my biggest feedback is referring to the project as 'MoonRay' and not 'OpenMoonRay'. Not sure if the mentions are just oversights or something else. |
|
Yeah, it is a common confusion. You are right that "MoonRay" is the official project name according to the charter, but the GitHub org and repository name for the repo that hosts the governance documentation being referred to is "OpenMoonRay/openmoonray": https://github.com/OpenMoonRay/openmoonray I suppose to be overly explicit, what do you think of something like:
|
|
@matthewlow-dwa That would be good - thanks. It's important to be super clear that the project name is "MoonRay"; the use of "https://github.com/openmoonray" is just because "https://github.com/omoonray" was already taken ( same deal for the domain ). |
Signed-off-by: Matthew Low <Matthew.Low@dreamworks.com>
9d5bbf9 to
9326a82
Compare
Sounds good. Updated. |
Prototype restructure of sub-module governance documents. Once approved, can be applied to other sub-module repos as well.
README.mdto refer users to main OpenMoonRay super project governance documentsLICENSECODE_OF_CONDUCT.mdandCONTRIBUTING.mdas special files GitHub understands and integrates, but removes content and refers readers to main OpenMoonRay super project filesMAINTAINERS.md, which can be maintained in the main OpenMoonRay super projectcharter.md,icla.md, andccla.md