This is a draft document that covers what our policy is for creating sub-domains of hyperledger.org (such as wiki.hyperledger.org or grid.hyperledger.org).
...
- Project sub-domains: There are a few open questions about this that the TSC may have thoughts about:
- When is it appropriate for a project to have a sub-domain? For example, is it tied in to additional support for reaching graduated status or not?.
- How is the project site hosted and does the TSC and/or Hyperledger staff have access to edit and update the site and get analytics?
- How is the site branded and designed? Do we want there to be some consistency across project sites so it is easy for people to navigate multiple project sites?
- Language sub-domains: Staff will set this up when a new language is added to the site
- Services sub-domains: Staff will set this up when a new tool is added to the community
- One-off sub-domains: The TSC may have some thoughts on criteria for this – perhaps the criteria should be about the sub-domain needing to relate to an officially sanctioned community activity?
Process for requesting a Sub-Domain
If someone is interested in a sub-domain, they can reach out to the Community Architects alias.