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

Introduce 'Source code availability' section #3

Merged
merged 3 commits into from
Sep 6, 2017
Merged

Introduce 'Source code availability' section #3

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c838b06
Introduce 'Source code availability' section
Sep 6, 2017
7b9e3bd
Language
Sep 6, 2017
dda4e47
s/may/will/
Sep 6, 2017
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
13 changes: 12 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,18 @@ The code (and any other produced artifacts) will belong to the participants. How

In the interest of keeping things level, we’re only allowing to incorporate free/libre open source software that’s publicly available before the competition begins. We don’t have any issues with people using popular software packages, but we’d like to avoid that teams bring a whole project along when others couldn’t have done the same. If you have a non-trivial codebase you’d like to use on your hack, make sure it is publicly available under [an OSI approved license](https://opensource.org/licenses) and unencumbered by any IP restrictions before the competition begins. This way everybody starts equally as far from the finish line.

At the beginning of the fair, we’ll make a public fork of your repo. This ensures that we’ll have a copy that we can make available to everyone and that we can preserve it for posterity.

#### Source code availability

In order to assure that all code is available to everyone, participants should
use the GitHub repository provided by the organization. Nuking the repository
and force pushes will be disabled. This ensures that we’ll have a copy that we
can make available to everyone and that we can preserve it for posterity.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe: "and that we can preserve for posterity."


Not using the repository **may disqualify their entire team** from winning any
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"will disqualify"

prizes. If any team has a problem with this setup they must convene promptly
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Double space.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe: "If a team has any problem"

with the organization as soon as possible, to find a way to avoid
disqualification.

#### Hosting

Expand Down