-
Notifications
You must be signed in to change notification settings - Fork 60
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
Announce the repo #15
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
In terms of announcing, I'd be happy to:
my ideal is that when we announce, we should have a single script they run to get opkg+toltec+nao+a launcher, then at that point they have enough UI to start installing packages directly from the tablet. it's fine if we can't hit this for the first announcement, though since we will probably target power users first. |
I think we'd want to hit that milestone before announcing on Facebook. |
This comment has been minimized.
This comment has been minimized.
Can this issue be merged in the milestone https://github.com/toltec-dev/toltec/milestone/1? |
There are a couple items in the list that don't have separate issues, so I think it deserves to stay open. |
Indeed. AFAICT, the remaining tasks are all related to actually making the announcement, so this issue should be the last one closed in the milestone. |
Should we also create a code of conduct? |
is there a standard one we can use? |
I believe there is a template. |
To follow up on this, iirc, when adding the CoC to oxide it gave me two templates to pick from. |
We should probably make some progress on the actual announcement of this? |
Should we close this? I'd say we are actually already announced. |
yeah, let's close |
From what I can tell, we should probably do a proper rollout of this to the larger community. Here is what I think we need to do first before we can "announce":
After that we should probably do the following to "announce":
The text was updated successfully, but these errors were encountered: