Skip to content
This repository has been archived by the owner on Jun 10, 2019. It is now read-only.

Unconf - Decentralized Unconference Planner #17

Closed
salis opened this issue May 21, 2017 · 1 comment · Fixed by #173
Closed

Unconf - Decentralized Unconference Planner #17

salis opened this issue May 21, 2017 · 1 comment · Fixed by #173

Comments

@salis
Copy link

salis commented May 21, 2017

Status Hackathon Submission

Type: DApp + Bot
Github Repo: https://github.com/BlockchainLabsNZ/Unconf-DApp

Description:
A way to gather a community to plan an Unconference with a few smart contracts providing a lightweight governance model.

Why:

  1. Because the Unconference format aligns very well with the decentralized Blockchain philosophy.
  2. Because Status.im enables the group chat collaboration and location discovery to bring this DApp to life
  3. Because BlockchainLabs.nz and Blockchain.org.nz are planning a Blockchain Unconference later this year ;)

What:
At a minimum someone should be able to create an Unconference event with a location & date for it to be discoverable in Status.im. People should be able to register (free or paid) and be added to a group chat for collaboration. People should be able to suggest topics they would like to share, and then let others upvote the suggestions.

Team Members:

Preferred Name: Paul
Github Handle: @salis
Slack Username: @salis
Twitter Handle: @paulsalis

Preferred Name: Klaus
Github Handle: @Janther
Slack Username: @Janther
Twitter Handle: @KlausHott

Preferred Name: Isaac
Github Handle: @IsaacPayne
Slack Username: @Isaac2

@commiteth
Copy link

commiteth commented May 30, 2017

Balance: 0.0000
Contract address: 0x629fe72d5fbdf51a8c8a2d64f03fe134a08d620f
Network: Mainnet
Status: pending maintainer confirmation
Winner: Janther

benmorrow added a commit that referenced this issue Jun 11, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants