Skip to content
This repository has been archived by the owner on Nov 5, 2021. It is now read-only.

Soundcheck: What We Need to Get Started #2

Open
keywordnew opened this issue Jul 29, 2018 · 7 comments
Open

Soundcheck: What We Need to Get Started #2

keywordnew opened this issue Jul 29, 2018 · 7 comments

Comments

@keywordnew
Copy link
Contributor

keywordnew commented Jul 29, 2018

This initiative is the product of a discussion at the Spring 2018 Collab Summit.

I'm not exactly sure what to put in an issue. The discussion referenced collaborating with the Badges and Mentorship initiatives. But I'm not convinced this initiative is yet in a place where it can begin doing that.

So this is a soundcheck. To get the conversation on what we need to get started.

@bnb
Copy link
Contributor

bnb commented Sep 5, 2018

@patriciarealini probably has the most context on this – a few things that I can think of:

  • An explicit call for individuals who want to work on this would probably be helpful. Not sure what scoping we want to put on that, but there likely should be some.
  • Node.js project Code of Conduct file (see this example)
  • A CONTRIBUTING.md file that reflects guidelines for and paths to contributing to the project.
  • Adding the project to the list of Community Committee Strategic Initiatives

@Tiriel
Copy link

Tiriel commented Sep 5, 2018

Hey!

Sorry for the long silence on the matter. There are indeed a few things that are or were needed to get this started.

I'm not sure, I may be mistaken, but I think I remember the intent was to have a basic README fleshed out and explaining what this is for, before actually adding the Outreach Initiative to the Strategic Initiatives for the CommComm. Or maybe it was just "waiting for the CollabSummit to be over", not really sure anymore.

Anyway, for my part, I'm not sure it's necessary anymore to wait since pretty much everything can benefit from the participation of the many. Maybe an issue giving a bit of context and with a "help needed" label can be proper and help someone get on board the project, if it's ok for everyone?

@keywordnew
Copy link
Contributor Author

keywordnew commented Sep 18, 2018

To add another point to the above, this Initiative should give people who answer a call to action the resources they will need to successfully drive the Outreach Initiative.

For example, I believe the Moderation team received training funded by the Foundation. That was a helpful and a concrete indication of support.

It could look like too early a stage to suggest this. But having that resource waiting when people show up will build on any momentum created by the early work.

@codeekage
Copy link

Do we start working around this and have It discussed in the next CommComm meeting? @patriciarealini @bnb

@SMotaal
Copy link

SMotaal commented Sep 19, 2018

Can I recommend a having casual discussion in Vancouver, involving interested people. Which ironically means we need a bit of outreach about outreach 😉

@Tiriel
Copy link

Tiriel commented Sep 19, 2018

@SMotaal That's a pretty good idea!

Please do, but please make sure those that are not here can also follow and if possible participate! (I'd really like to see this really started at last, and I doubt I'm the only one)

@Tiriel
Copy link

Tiriel commented Feb 19, 2019

Hey there!

As I'm picking up steam on things I missed lately, could someone please tell me if there has been some discussions on the topic in Vancouver, and if so make small feedback?

I'm working on augmenting a bit the README and opening an issue for a call for help, so I'd like to be sure nothing has been actually started that I would disrupt.

@Tiriel Tiriel mentioned this issue Feb 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants