Open agarwal opened 11 years ago
Chris00
commented
11 years ago I think it would be nice for individual meetings to be listed but I share your concern about maitainability. Maybe this page could be generated from webpages or RSS flux (+ some CSV file)?
amirmc
commented
11 years ago By 'Meeting' do you mean the more formal gatherings like the Consortium or conferences? Is this meant to be a historical list or do you envisage upcoming events also being visible? (I ask because this may affect reverse chronology).
I think meetups should have a place on the site, though not necessarily mixed with the larger conferences/meetings. It can be maintainable if there's simply a feed to pull data from (e.g see Group Calendar Feeds at http://www.meetup.com/meetup_api/feeds/). Things could be setup in such a way that if a user group wants their events added, they submit a pull request with a link to the feed. That might also deal with the problem of inactive groups (no upcoming events, no display).
Links worth looking at (re: event feeds) http://talks.cam.ac.uk - I've used this a lot and it's useful for automatically aggregating lists (e.g http://www.neuroscience.cam.ac.uk/talks/ is made up of over 30 different lists). It's open-source. http://www.mashical.com - Used this too (for aggregating my calendars into one 'free/busy' feed)
In general feeds should be in ical form (rss would update on every edit).
Hope that helps.
agarwal
commented
11 years ago On Wed, Jan 16, 2013 at 12:52 PM, Amir Chaudhry notifications@github.comwrote:
By 'Meeting' do you mean the more formal gatherings like the Consortium or conferences?
I was thinking all kinds of meetings, but then the issue is how to organize and maintain such a list. Your links help. Thanks.
Is this meant to be a historical list or do you envisage upcoming events
also being visible? (I ask because this may affect reverse chronology).
Both past and future meetings could be listed. I think reverse chronological order makes sense. How do you think it's affected?
amirmc
commented
11 years ago Both past and future meetings could be listed. I think reverse chronological order makes sense. How do you think it's affected?
Reverse chronology makes sense more as an archive/history view or when there is only ever one 'upcoming' event at the top of the list. Forward chronological view makes more sense as a feed of upcoming stuff, where past events are of no further concern. Both are perfectly valid depending on the aims but mixing them up on the same page is awkward to read.
The Neuroscience list I posted earlier [1] is forward chronology. People just want to see what interesting events may be happening in the next couple of weeks (and if you scroll down you'll see a bunch of "Title to be confirmed" - imagine this list being in reverse order :) No-one expects to come back and see links to video/slides etc.
The OCaml.org Meeting page at the moment is reverse chronology (with fewer items) but each item also has more links within it to slides/video etc. It's more static and trying to act as more of a resource.
I've no idea how many OCaml events are out there or what you'd like to include but I wanted to pose the question. Note: I'm not saying you have to pick one! Just keep both groups separate as they serve different needs.
Does that help explain?
agarwal
commented
11 years ago Got it. Thanks. So maybe we'll have two sections: Upcoming and Past, with Upcoming meetings in chronological order and Past meetings in reverse (although switching the order on the same page might also be weird, but with appropriate formatting it might work).
On Wed, Jan 16, 2013 at 3:11 PM, Amir Chaudhry notifications@github.comwrote:
Both past and future meetings could be listed. I think reverse chronological order makes sense. How do you think it's affected?
Reverse chronology makes sense more as an archive/history view or when there is only ever one 'upcoming' event at the top of the list. Forward chronological view makes more sense as a feed of upcoming stuff, where past events are of no further concern. Both are perfectly valid depending on the aims but mixing them up on the same page is awkward to read.
- Examples -
The Neuroscience list I posted earlier [1] is forward chronology. People just want to see what interesting events may be happing in the next couple of weeks (and if you scroll down you'll see a bunch of "Title to be confirmed" - imagine this list being in reverse order :) No-one expects to come back and see links to video/slides etc.
The OCaml.org Meeting page at the moment is reverse chronology (with fewer items) but each item also has more links within it to slides/video etc. It's more static and trying to act as more of a resource.
I've no idea how many OCaml events are out there or what you'd like to include but I wanted to pose the question. Note: I'm not saying you have to pick one! Just keep both groups separate as they serve different needs.
Does that help explain?
[1] http://www.neuroscience.cam.ac.uk/talks/
— Reply to this email directly or view it on GitHubhttps://github.com/ocaml/ocaml.org/issues/96#issuecomment-12337466.
amirmc
commented
11 years ago Cool. For the past meetings, I'd only keep a page the most important/big ones. Things like OUD, the consortium meeting and there may be a couple of others I'm not yet aware of. If you really want to allow folks to see a list of all past events, then I'd suggest letting it be something they explicitly click through to from the upcoming page i.e not otherwise linked from anywhere (see [1] where there's a small link that says "{x} talks in the archive...")
amirmc
commented
11 years ago Relevant to #113
Let's remove the regional sub-divisions and list all meetings in reverse chronological order. Every meeting should have: full name of meeting, optionally an abbreviation in parentheses, date(s), city/country, organization hosting/organizing the meeting. The meeting name should be linked to the page for that meeting if there is one.
I'm unsure if individual meetings being held by user groups should all be listed here. It's probably good marketing to do so for now, but I suspect this will be unmaintainable in the long run.