DEI Handbook Update: Etherpad content moved to Github

Hi everyone,

The Etherpad content was successfully migrated to our Github Repo DEI Handbook New contents on Etherpad will not be added to the repo since it will require a manual versioning comparison.

You can see the full website here

If you want to update or add a new content:

  • Create a new branch
  • Do your magic adding the content
  • Open a PR to the main branch

Suggestion of things to discuss on the next meeting:

  • Should we use another theme for the handbook? Some references here: https://sphinx-themes.org/
  • Where should we put the Table of Content? Shoudl we keep it at the “Landscape” page?
  • Is the page organization good? I tried to split it into three main topics, but feedbacks are always welcomed! :slight_smile:
  • We should use another place to assign the topics of interest or who is working on what. Maybe Google Docs?

For any questions, please let me know! :slight_smile:

2 Likes

This is awesome, thanks @glauesppen :tada:

Personally, I really like the one we currently have—it’s simple and easy to use.

+1 to keep it at the “Landscape” page

looks great :clap:

Since we are using GitHub, I’m in favor of using GitHub issues for this. We can create new issues for different topics, assign people to the issues they want to work on, and it might be easier to check for updates or provide feedback.

1 Like

Thank you for the responses!

Using the github issues seems very intelligent. Let’s do it. What do you think @Anita_Ihuman ?

1 Like

This is awesome; thanks a lot, @glauesppen, for taking this up.

  • I agree with Jona that we maintain the theme we are currently using.

  • Yes, I think we would need to put up the table of content once it is refined.

  • I like the idea of splitting it into key topics, but if we eventually organise the table of content and have it up, we can use that to improve on it as well.

  • We did not use Google Docs at first because it was not very inclusive for some people, so Etherpad was more accessible. I think we should create issues of sections that are still under development and then assign them to different individuals. That way, when someone indicates interest in an issue, they can use whatever collaborator material they want to expand on the section they selected.