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

Create a FOSS-Responders Discourse #13

Closed
nuritzi opened this issue Mar 18, 2020 · 10 comments
Closed

Create a FOSS-Responders Discourse #13

nuritzi opened this issue Mar 18, 2020 · 10 comments

Comments

@nuritzi
Copy link
Contributor

nuritzi commented Mar 18, 2020

As part of the FOSS-Responders initiative, it'd be great to set up a Discourse instance.

We can then use this to post meeting notes for those interested in following our progress, and it can be a place where the community goes to support each other.

It looks like Discourse offers free hosting for Open Source projects. We should look into getting a free hosted instance set up.

@nuritzi has experience setting up groups within Discourse once we set it up . We are seeking someone to help set up the instance.

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 18, 2020

Adding some notes from @eriolfox on the Open Collective #crisis-working-group Slack that we can post once we have the discourse set up. I wasn't sure where to jot them down, so adding them here for now.

Pro-bono design resources

  • Open Source Design - For OSS design contributions you can ask for that here.
  • Virtual Design Sprint Organises design sprints remotely
  • Hague Hacks - Does in person design thinking for humanitarian crisis and links with OSS projects to make them 'exist'
  • OpenIDEO - does funded challenges more to do with humanitarian stuff:
  • Open Design - A project to create accessible processes for designers to collaborate and contribute to open source software:

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 18, 2020

Michael Downey offered to help with Discourse on the foundations@ list. I'm in contact with him and we'll update this issue if we're able to move things forward together.

@DuaneOBrien
Copy link
Member

Recommend transferring this issue to https://github.com/foss-responders/about/ so that we can keep this repo focused on Website issues.

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 20, 2020

@DuaneOBrien sure, do you know how to do that? Can we just move it, or do we have to close and re-open?

Thanks for the suggestion!

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 23, 2020

Per @downeymj: (foss-responders/about#7 (comment))

I am going to send off a couple referals to experts I know who have volunteered at the Discourse community call for volunteers for pandemic related activities. Will be sending them emails and copying @nuritzi today.

Once the website is set up through the Discourse.org hosting free trial, I'll then send an email intro to the Discourse team to ask them about their hosting offer. @nuritzi will send me an email once that's done with the chosen URL so I can point the team to the correct account/site.

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 24, 2020

Here are my notes from my meeting with @downeymj on Friday. Michael, please feel free to clarify if I missed anything!

2020-03-20 Notes | Michael <> Nuritzi

Timeframe

  • Plan for supporting the FOSS community through this initiative for 18 months (based on current WHO predictions)

There may be similar types of groups popping up, so we might want to keep in mind merging efforts with someone else eventually. Merging Discourse is pretty easy. It's a good investment. Pretty flexible, can keep it simple, and if you want different kinds of programs, then those can grow organically.

Structuring Discourse

Start conservatively. Have a free-for-all conversation area, and do specific outreach. Have a category called cancelled events. Have people start topics for each event. Have a template for people to fill out. People can follow up with specific questions or comments.

Can turn a topic into a wiki post. The first post in the topic can become a wiki style page that people can edit. For example, it can hold a list of which events are cancelled.

Things we want in our discourse instance / possible categories

  • General - a free-for-all conversation area
  • FOSS Matchmaking - People can volunteer a specific skill or thing, each in a separate thread (e.g. designers can volunteer like how community managers did in the discourse call for community managers thread thread)
  • Resources - a place where people can post resources they've found helpful (e.g. see this list we've started to compile)
  • Cancellations - a list of FOSS event cancellations
  • Funding Q&A - a space for people to ask about how to get resources. Provide an FAQ about how to access resources.
  • Stories -- we want to collect stories about how we are helping the community in order to fundraise
  • International -- this might be good to set up for some of the major languages, and add more subcategories if there's a critical mass of conversations in that language.

Process Integration

Internal program management discussions could happen in Discourse. Operations on GitHub, general public on Discourse. All requests might start convo in Discourse, and track status in GitHub.

Language Support

  • OSS contributions are mostly happening in English, although there's an exception of that in China.
  • There's a great plugin for auto-translations. Can do real-time translations. Re-rendering of the page.
  • If people are posting questions in other languages -- maybe have an international category. You can create an international top category and sub-categories for difference languages. Have a moderator for each of those. Make sure you write Francais, not French, for example. Make sure category description is in that native language.

What do we need to get started?

  • URL for discourse set up. @RichardLitt can you help us set up community.fossresponders.com?
  • Short list of volunteers that are content moderators.
  • Logos -- can update that later if needed.
  • Content blurbs. Topic descriptions and all that.

Other Considerations

  • Make sure that folks' questions are answered in a timely way.
  • Stoke conversation and ask questions of people.
  • Update meeting notes. Have working groups post things there to engage the community.

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 24, 2020

@downeymj just an FYI that I'm going to wait until tomorrow to see if we can get the URL sorted before we start. Plus, tomorrow I'll be speaking with one of the people you connected me to, so can get his input too before I start creating things.

Will send you the link to the discourse instance asap once it's set up!

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 24, 2020

@downeymj: Richard just helped us set up the URL (Thanks, @RichardLitt!), so we now have the instance running on: https://community.fossresponders.com/

I haven't done much customization yet, so it's not quite ready to "launch" aka be linked to from the website. Michael - are you able to ping the Discourse people about its free trial status now, or would you prefer to wait?

I'll update this thread with any changes to the discourse instance and will make it clear when I think it's reached the MVP stage and is ready to launch.

@nuritzi
Copy link
Contributor Author

nuritzi commented Mar 25, 2020

Just an update: thanks to Tobias, the Discourse instance is in much better shape and pretty close to being ready to launch more publicly. We've started to request feedback on the current categories.

Next, I want to talk to some of the people from the working group about processes/workflow/tools, as Yaw suggested.

We're moving along quickly -- thanks again to everyone involved so far!

@RichardLitt
Copy link
Member

I believe that this can be closed. Thank you, @nuritzi for driving this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants