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

Final submission for #112 #120

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
73 changes: 0 additions & 73 deletions CODE_OF_CONDUCT.md

This file was deleted.

98 changes: 2 additions & 96 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,97 +1,3 @@
![Hackathon](docs/hackathon_banner.png)
Welcome to the submission repository for the Colony Hackathon.
https://github.com/mduske/colonyHackathon

You can read more about the Colony Network and the colonyJS library on the [Docs site](https://joincolony.github.io/colonyjs/docs-overview/).

## Gitter

To meet potential team members, chat about projects, or get help with your code and the ColonyJS library, head over to the [the colonyHackathon Gitter](https://gitter.im/ColonyHackathon/Lobby).


# Submission Guidelines

Participating in the hackathon is as easy as contributing to an open source project on GitHub. Exactly so, because you will register your project by creating an issue in this repository, and submit it by creating a pull request.

Here’s how it works:

## The Submission Process

### 1) Create an issue
Your first step is to create an issue in the `colonyHackathon` repository. This issue acts as a "soft" registration for the hackathon, and can help you to coordinate your ideas with other participants. An issue is a good place to talk openly about your project ideas with others before you decide on its exact scope.

Use your issue to talk with collaborators, brainstorm, and organize. Check out the other issues to see if there are participants who want to work on the same things.

Members of the colony team will be able to point other participants to your issue (if it looks like they can help), help you with technical questions, or just offer support :)

Issue events will also be pulled into the Gitter feed [Gitter](https://gitter.im/ColonyHackathon/Lobby) which is a better place for more general discussion and chatting.

### 2) Build with Colony
Work on your project as you like. How you work is up to you; We recommend creating a new GitHub repo for your team. Remember to only begin working on your project after the hackathon begins on June 5th!

Use the issue you created in step 1 to let others know where your project lives. You might want discuss any technical challenges or attract additional teammembers.

Wherever you work, remember that your project should include an **Open Source License** of [some form](https://opensource.org/licenses), and should be accessible to everyone after the submission deadline.

### 3) Fork and PR
When you feel ready to submit, create a new fork of the colonyHackathon repo, and add your project as a markdown file inside `colonyHackathon/submissions/`.

You can use `submissions/exampleProject.md` as a template if you like.

Be sure that your project's folder links to the repo you've been working in, and contains any other supporting materials that you want evaluated by judges (such as links to a pitch deck or demo video).

Once ready, submit via a new [pull request](https://github.com/JoinColony/colonyHackathon/pulls).

*Opening a Pull Request establishes your project as an "official" submission*

You can open a PR before the submission deadline and continue to work, but all materials must be finalized *before* the end of the hackathon. Any commits to your project submission after the deadline will not be considered.

We'd also recommend referencing the issue you created in step 1 [using keywords](https://help.github.com/articles/closing-issues-using-keywords/) in your PR.

**Submit your pull request before the submission deadline: _June 24, 23:59 GMT_**

### 4) Congratulate your team (and yourself) on a job well-done
Whether or not you get a prize, you deserve to be proud of your work. Thanks for participating in the hackathon!


## Dates

**June 5th**
Registration begins

**June 24th**
Submission deadline

**June 25th**
Judging begins

**June 29th**
Winners Announced


## Judges and Scoring

Submissions will be graded across the following equally-weighted criteria:

1. Functionality
2. Creativity
3. Difficulty
4. Design

Info about our super-awesome judges panel can be found on [the hackathon website](https://colony.io/hackathon).

## Prizes

**Grand Prize:**
10,000 DAI

**2nd Prize:**
5,000 DAI

**3rd Prize:**
2,000 DAI

Runners up:

3 winners: 1,000 DAI

10 winners: 500 DAI
fixes #112
1 change: 1 addition & 0 deletions colonyHackathon
Submodule colonyHackathon added at a4bfe4
26 changes: 26 additions & 0 deletions src/__tests__/index.test.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
const createColony = require('../create_colony');
const createTask = require('../create_task');

describe('Starter project', () => {
test('Example logs successful results', async () => {
jest.spyOn(console, 'log');

const colonyClient = await createColony();
await createTask(colonyClient);

const logs = console.log.mock.calls.map(args => args[0]);

const expected = [
expect.stringContaining('Token address'),
expect.stringContaining('Colony ID'),
expect.stringContaining('Colony address'),
expect.stringContaining('Meta Colony address'),
expect.stringContaining('Specification hash'),
expect.objectContaining({
cancelled: false
}),
];

expect(logs).toEqual(expect.arrayContaining(expected));
}, 20000);
});
Loading