search

alg / hack_night

Hack Night planning application
5 stars 0 forks source link

Hack night definition #4

Open alg opened 13 years ago

alg commented 13 years ago

Here's one interesting topic for discussion. As opposed to having a centralized HN declaration by some admin, what if we let users tell when they want to meet and where, invite other people, change location etc...

We may want to have the concept of Venue where people willing to host a hack night declare how many slots they have and when is the time they want to hold the event. Others may, or may not join it. As well, as they can decide to go completely separate and meet in a different place. Or, for instance, if two venues decide to host an event at the same time, groups may join either one of them.

That being said, what if:

Some use cases:

  1. I know I will be working on something Friday evening at 6pm at Celentano Pizzeria. I create a HN event for that and invite Ivan and Alex to join me. Event appears on my calendar and if they join me, on their too.
  2. Office owner wants to promote his company and decides to host an event on Thursday night. He creates a HN from 6:30pm to 9pm with free beer and pizza. Everyone gets a notification about this new event (since it's global and for no one in particular). Interested parties join until there are available spots. As I join, the event is added to my calendar.
iosadchiy commented 13 years ago

Agree! this is what I imaging v.2.0 should be!

1) We've already experienced difficulties defining time for the next HN. People should be able to meet when they can or prefer 2) Hosting a HN should not be limited to a single office owner. There are good places out there to try.

BTW, what happened to "New design" feature?

On Tue, May 31, 2011 at 9:20 PM, alg < reply@reply.github.com>wrote:

Here's one interesting topic for discussion. As opposed to having a centralized HN declaration by some admin, what if we let users tell when they want to meet and where, invite other people, change location etc...

We may want to have the concept of Venue where people willing to host a hack night declare how many slots they have and when is the time they want to hold the event. Others may, or may not join it. As well, as they can decide to go completely separate and meet in a different place. Or, for instance, if two venues decide to host an event at the same time, groups may join either one of them.

That being said, what if:

  • we had a Venue with associated title and location
  • each Venue can have a representative, who decides on the number of slots and the time of the next possible event
  • people may register HNs themselves for venues w/o reps (cafe's for example)
  • people could join HNs and could invite others to join them
  • HN can be private
  • reps can create a targeted HN in their Venue and invite others just like anyone else can create HNs in unrepresented Vs

Some use cases:

  1. I know I will be working on something Friday evening at 6pm at Celentano Pizzeria. I create a HN event for that and invite Ivan and Alex to join me. Event appears on my calendar and if they join me, on their too.
  2. Office owner wants to promote his company and decides to host an event on Thursday night. He creates a HN from 6:30pm to 9pm with free beer and pizza. Everyone gets a notification about this new event (since it's global and for no one in particular). Interested parties join until there are available spots. As I join, the event is added to my calendar.

Reply to this email directly or view it on GitHub: https://github.com/alg/hack_night/issues/4

alg commented 13 years ago

There's a fluid layout and header / subheader stories that cover that. So I figured I'll just cleanup. ;)

On Jun 1, 2011, at 10:18 , tepoga wrote:

Agree! this is what I imaging v.2.0 should be!

1) We've already experienced difficulties defining time for the next HN. People should be able to meet when they can or prefer 2) Hosting a HN should not be limited to a single office owner. There are good places out there to try.

BTW, what happened to "New design" feature?

On Tue, May 31, 2011 at 9:20 PM, alg < reply@reply.github.com>wrote:

Here's one interesting topic for discussion. As opposed to having a centralized HN declaration by some admin, what if we let users tell when they want to meet and where, invite other people, change location etc...

We may want to have the concept of Venue where people willing to host a hack night declare how many slots they have and when is the time they want to hold the event. Others may, or may not join it. As well, as they can decide to go completely separate and meet in a different place. Or, for instance, if two venues decide to host an event at the same time, groups may join either one of them.

That being said, what if:

  • we had a Venue with associated title and location
  • each Venue can have a representative, who decides on the number of slots and the time of the next possible event
  • people may register HNs themselves for venues w/o reps (cafe's for example)
  • people could join HNs and could invite others to join them
  • HN can be private
  • reps can create a targeted HN in their Venue and invite others just like anyone else can create HNs in unrepresented Vs

Some use cases:

  1. I know I will be working on something Friday evening at 6pm at Celentano Pizzeria. I create a HN event for that and invite Ivan and Alex to join me. Event appears on my calendar and if they join me, on their too.
  2. Office owner wants to promote his company and decides to host an event on Thursday night. He creates a HN from 6:30pm to 9pm with free beer and pizza. Everyone gets a notification about this new event (since it's global and for no one in particular). Interested parties join until there are available spots. As I join, the event is added to my calendar.

Reply to this email directly or view it on GitHub: https://github.com/alg/hack_night/issues/4

Reply to this email directly or view it on GitHub: https://github.com/alg/hack_night/issues/4#comment_1272611