-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Website #4
Comments
I have hivecommons.org (currently just redirects 1hive.org) but if we want to have a portal that is focused specifically on the license we can use that (I think a good idea as I think the audience may get distracted by all the DAO stuff on 1hive.org) |
Yeah that sounds great. Do you think we can get the basic high level stuff drafted this afternoon so that we could have a simple website/landing-page by the end of the weekend? |
My thinking is that we should divert contributors to 1hive, and keep the hivecommons site focused on documentation for users. I'm thinking that the eventually the compliance registry/portal would actually be hosted there as well as general information about the license and mission. |
I tend to think that we should have a FAQ for core concepts rather than a wiki. (much easier to maintain and more conducive to linking out for most of the explanation). |
I don't know what you're saying here. I was saying that we need to create a high level overview and explanation of what the HCL is (as outlined in #2) and put that on the internet on a webpage. That way people who interested (users) can learn about and engage with the HCL project. Then we can start integrate the HCL Registry portal lik we talked bout last week in the ideas repo Issue and on Keybase. This repo was created to start that process (website, docs/faq, and then React UI and contracts for an HCL registry). What are you saying when you refer to contributors and users? |
Sorry should have been more clear, my understanding is that issue is to discuss creating a web portal for people to learn about the HCL. From an audience perspective we have a couple of people/personas to think about:
It makes sense for us to provide information for these users on the site, as well as also host the compliance registry itself there. We also may have people who are interested in contributing to the project directly (they might be lawyers, they might be devs that can help build out the registry itself). For these people I think we should direct them to 1hive (rather than having a seperate set of contributor guidelines, and project pages/documentation). So the distinction is essentially that registry is a 1hive development project and contributors onboarding and dev documentation live there. The hivecommon.org site hosts the actual registry itself and associated user documentation including FAQs about the license. Does that make more sense? |
Awesome. Yeah that makes total sense. 100% in agreement |
The portal for people to learn about and interact with all things HCL related
The text was updated successfully, but these errors were encountered: