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

Jump to bottom

Decide data model for cryptoparty list #32

Open
danohu opened this issue Nov 13, 2014 · 1 comment
Open

Decide data model for cryptoparty list #32

danohu opened this issue Nov 13, 2014 · 1 comment

Comments

@danohu
Copy link
Contributor

danohu commented Nov 13, 2014

No coding required -- this is a planning/UI/community question

The info we currently collect/store doesn't seem to capture either the info currently usually added to the wiki, or the most useful info.

We should work out what info to include in the form/listing.

Current form has:

  • event name
  • time and date
  • additional info URL
  • street address
  • your email address

Compare to https://www.cryptoparty.in, where:

  • most events don't have a name

many/most events do have:

  • venue (somewhat distinct from address, I think)
  • directions (again, slightly different from address -- e.g. nearby public transport, where to park, which room number)
  • end time as well as start time
  • topics which will be covered
  • organizer (e.g. sponsoring organization)
  • what to bring / preparation expected
  • target audience
  • and some free-text description
  • registration required

We probably shouldn't include all these in the template, but do want some of them.
danohu added a commit to danohu/cryptoparty.in that referenced this issue Nov 13, 2014
@danohu
Atom feed
5186a97 
see bug cryptoparty#26

Still needs us to:

 - link to the feed from the rest of the site (both human-readable and for autodiscovery)
 - work out the ordering. most-recently-added seems most useful, but requires us to collect that info
 - decide the content of the feed items -- cf. issue cryptoparty#32

Also: this is Atom only, not RSS -- but I think one feed format is enough?
@danohu danohu mentioned this issue Nov 13, 2014
Closed
danohu added a commit to danohu/cryptoparty.in that referenced this issue Nov 22, 2014
@danohu
Atom feed
5591efb 
see bug cryptoparty#26

Still needs us to:

 - link to the feed from the rest of the site (both human-readable and for autodiscovery)
 - work out the ordering. most-recently-added seems most useful, but requires us to collect that info
 - decide the content of the feed items -- cf. issue cryptoparty#32

Also: this is Atom only, not RSS -- but I think one feed format is enough?
danohu added a commit that referenced this issue Nov 22, 2014
@danohu
Atom feed
12e41f1 
see bug #26

Still needs us to:

 - link to the feed from the rest of the site (both human-readable and for autodiscovery)
 - work out the ordering. most-recently-added seems most useful, but requires us to collect that info
 - decide the content of the feed items -- cf. issue #32

Also: this is Atom only, not RSS -- but I think one feed format is enough?
@waaaaargh
Copy link

I would opt for keeping as little Info as possible on the calendar. IMO this app should not be the canonical address for managing cryptoparty information and announcements but a geographically and temporally indexed pointer to wherever the organizing community is comfortable with hosting their information.

This also drastically reduces the time needed to just add an entry to the calendar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@danohu @waaaaargh