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.

Sign up for GitHub

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

fixing small typos in README.md #883

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fixing small typos in README.md #883

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,29 +26,29 @@ We have 3 categories:
- _Gallery_, contains interactive exhibits, installations, games, stalls designed for 1:1 self driven experience and emergent activities. Often these experiences or activities are not scheduled time blocks but take place over the day or weekend allowing access and interaction at any time. The Gallery can provide context for upcoming sessions, and finished prototypes from sessions for that relevant Space.


We are here to help in case you get stuck or need help at anytime. Don't worry -- you can't break anything!
We are here to help in case you get stuck or need help at any time. Don't worry -- you can't break anything!

## Important note

All session submissions must come through the official [Call for Proposals form](https://mozillafestival.org/proposals) on the MozFest website. Do *not* manually add a new ticket here as it will not integrate with the rest of our systems.

## Github Etiquette

Please be advised that if you create a user name and comment on issues, your comments will be public. We will not publish anyone's personal information, and we ask you to respect this in your comments. People who are submitting a session are putting themselves out there and we are invested in ensuring they have a good experience with us, regardless whether their session is accepted or not.
Please be advised that if you create a username and comment on issues, your comments will be public. We will not publish anyone's personal information, and we ask you to respect this in your comments. People who are submitting a session are putting themselves out there and we are invested in ensuring they have a good experience with us, regardless whether their session is accepted or not.

Please be aware that many people are using Github for the first time, so be patient and offer to help if you see someone in need.

## Participation Guidelines
MozFest respects [Mozilla's community participation guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/), which cover our behaviour as participants, facilitators, space wranglers, staff, volunteers, vendors, and anyone else involved in making MozFest possible. Please report unnacceptable behaviour to [email protected].
MozFest respects [Mozilla's community participation guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/), which cover our behavior as participants, facilitators, space wranglers, staff, volunteers, vendors, and anyone else involved in making MozFest possible. Please report unacceptable behavior to [email protected].

## Licensing
MozFest session descriptions are owned by their respective submitters, but any content created by Mozilla is available under a [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) license.

## Why we use Github Issues for MozFest

This is our third year of using Github to manage, review and curate sessions for MozFest. This tool allows us to better collaborate and coordinate across the program, as well as provide a record for how the program came together.
This is our third year of using Github to manage, review and curate sessions for MozFest. This tool allows us to better collaborate and coordinate across the program, as well as provide a record of how the program came together.

## Improving this process

Ideas? Let us know: [email protected].