search

scalaspace / scalaspace.github.io

Scala Space website
14 stars 47 forks source link

Aggregate upcoming meetups into a list #7

Open propensive opened 9 years ago

propensive commented 9 years ago

It would be great to be able to integrate with meetup.com and fetch upcoming events from each of the groups, and display them in a list.

anicolaspp commented 8 years ago

I will take a look at the Meetup.com API to see how to do this.

rajmahendra commented 7 years ago

Two things here to consider

What we can do is like groups we can have a JSON or something and read from there. We can have some criteria of the event to be added here.

propensive commented 7 years ago

I think that any usergroup not using Meetup will just have to miss out. I don't like to force anyone to use a particular proprietary service, but the vast majority of people ARE using Meetup, so it makes sense at least to implement this first.

For getting the data, I have an idea for this... I'll try a couple of things first, then report back!

rajmahendra commented 7 years ago

Somehow run a schedule and generate a ugeveents.JSON (or something) and have a separate page for UG events. We can have one page for International Conference also. One entry for each conference. Or we have to rewrite scalaspeace in Play with backend

rajmahendra commented 7 years ago

@propensive I did a small hacking and got the following We can read each meetup iCal. We need some server side app to pull all this and expose service so ScalaJS can pull this and display.

propensive commented 7 years ago

Sounds great! That's roughly what I had in mind. :)

jarrodu commented 6 years ago

I would like to take another look at this. @rajmahendra are there any old branches around?

jarrodu commented 6 years ago

I have been able to get a snapshot of the data we need fromm the Meeetup API. The problem is that if we keep the site static then we hit Meetup's throttling.

It looks like we need one request per group. I can get this without hitting limits if I space out the requests by 200 milliseconds. I might be able to trim this down a bit.

The sad truth, though, is that there are a lot of dormant groups. If we filter the list down maybe it will be fast enough.

Another option is to cache the results and refresh the cache every hour or day. I like this idea but it would add to the complexity of our deployments.