Skip to content
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

Closed
8 of 11 tasks
Eeems opened this issue Sep 7, 2020 · 15 comments
Closed
8 of 11 tasks

Announce the repo #15

Eeems opened this issue Sep 7, 2020 · 15 comments
Labels
documentation Improvements or additions to the documentation and to workflows

Comments

@Eeems
Copy link
Member

Eeems commented Sep 7, 2020

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":

@Eeems Eeems changed the title Rollout repo to communit Rollout repo to community Sep 7, 2020
@matteodelabre matteodelabre added documentation Improvements or additions to the documentation and to workflows pending Further information is requested and removed pending Further information is requested labels Sep 7, 2020
@matteodelabre

This comment has been minimized.

@Eeems

This comment has been minimized.

@raisjn
Copy link
Contributor

raisjn commented Sep 10, 2020

In terms of announcing, I'd be happy to:

  • work on web pages and package listing
  • post an announcement to reddit (since i've been talking on reddit about wanting package manager + app store for about a month)

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.

@Eeems
Copy link
Member Author

Eeems commented Sep 10, 2020

I think we'd want to hit that milestone before announcing on Facebook.

@Eeems

This comment has been minimized.

@Eeems Eeems added this to the Community Rollout milestone Sep 23, 2020
@matteodelabre
Copy link
Member

Can this issue be merged in the milestone https://github.com/toltec-dev/toltec/milestone/1?

@Eeems
Copy link
Member Author

Eeems commented Sep 23, 2020

There are a couple items in the list that don't have separate issues, so I think it deserves to stay open.

@matteodelabre
Copy link
Member

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.

@matteodelabre matteodelabre changed the title Rollout repo to community Announce the repo Sep 23, 2020
@Eeems
Copy link
Member Author

Eeems commented Oct 14, 2020

Should we also create a code of conduct?

@raisjn
Copy link
Contributor

raisjn commented Oct 19, 2020

Should we also create a code of conduct?

is there a standard one we can use?

@Eeems
Copy link
Member Author

Eeems commented Oct 19, 2020

I believe there is a template.

@Eeems
Copy link
Member Author

Eeems commented Oct 22, 2020

To follow up on this, iirc, when adding the CoC to oxide it gave me two templates to pick from.

@Eeems
Copy link
Member Author

Eeems commented Dec 16, 2021

We should probably make some progress on the actual announcement of this?

@Eeems
Copy link
Member Author

Eeems commented Mar 15, 2023

Should we close this? I'd say we are actually already announced.

@raisjn
Copy link
Contributor

raisjn commented Mar 17, 2023

yeah, let's close

@Eeems Eeems closed this as completed Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to the documentation and to workflows
Projects
None yet
Development

No branches or pull requests

3 participants