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

Meetup page redesign for OSS days #79

Open
zainab-ali opened this issue Dec 2, 2020 · 0 comments
Open

Meetup page redesign for OSS days #79

zainab-ali opened this issue Dec 2, 2020 · 0 comments
Labels

Comments

@zainab-ali
Copy link
Collaborator

Open Source days are very different to meetups for talks.

  • They’re focused around GitHub projects and issues
  • They have far more speakers (project maintainers)
  • There are multiple groups happening at once, so our current agenda isn’t useful
  • They aren’t recorded. This means they aren’t as valuable in our past events listing.

The title and explanation

Thus far we’ve assumed that we only give talks, so don’t have a space for a title. We need a title to distinguish an OSS day from conventional talks.

The day also needs a brief explaination of how it works. We could repurpose the ‘welcome’ section for this, placing it at the top and getting rid of the host’s profile.

Agenda

Our agenda should list break times and group times. We could use a generic agenda, without mentioning specific projects.

| 14:00 | local_cafe | Chat |
| 14:15 | local_cafe | Introduce the projects |
| 14:30 | build | Round 1 of coding |
| 15:45 | local_cafe | Break |
| 16:15 | build | Round 2 of coding |
| 17:15 | local_cafe | Closing discussion |

Where ‘build’ and ‘local_cafe’ are material icons corresponding to Blackboard Collaborate and Spatial Chat. Clicking on the icon should take the attendee to the corresponding virtual space.

Project lists

The project list is currently too large to easily scroll through. We could experiment with:

  • having a condensed list at the top and more detailed projects below
  • having a drawer per project
  • having anchors to projects. This may be worthwhile for talks too.

Project details

All projects have a few things in common:

  • a GitHub repository
  • a contributor guide, or instructions
  • a list of issues

We could pull the issues list from GitHub, searching for the specific repository, and have an ’issues’ tab.
Some projects are manned by the same speaker. In this case, we don’t necessarily want to duplicate the speaker profile.

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

No branches or pull requests

1 participant