Automatically populate website with new Community Calls

[spier]

Title

Automatically populate website with new Community Calls

Purpose & Details

Our Community Calls created new InnerSource-related content for anybody interested on a regular cadence.

Let's make it as easy as possible for interested people to find out:

• which Community Calls have taken place recently
• which Community Calls are up next, and when
• which additional material is there to see about the Community Calls (e.g. Infographics that we post to twitter already)

Acceptance Criteria

TBD

Help Needed / Blockers

None

[spier]

We discussed in Slack how to get the event details for the Communtiy Calls from eventbrite automatically, so that we don't have to update our website manually all the time.

Here the options discussed. However our best bet is probably to search a bit further if somebody else has already done something similar to this, which is rather likely 😄

eventbrite checkout widgets

One can apparently embed multiple eventbrite checkout widgets.
Drawbacks:

• We would still have to make a manual change on our website, whenever we post a new event on eventbrite
• Not sure how pretty it would be
• I don't know how this widget looks like once an event has passed.

eventbrite API

It's probably also possible to retrieve this data through the API:
https://www.eventbrite.de/platform/docs/events

[clcoffey]

Hi Sebastian, I am just checking in to see what the status of this issue is. Are you still working on it? Do you need any help?

[spier]

No, I am not working on this any more.
We can close it if you like.

[spier]

We do show the Community Calls on our Events page (https://innersourcecommons.org/events/) already.
However we create all of them manually.

So this issue is actually more about doing this automatically.
Will rename the issue accordingly.

[rrrutledge]

Is this realistically going to happen? How much time do we spend on the manual process between @OliveCannon @CiaraFlanagan and Andrea?

[yuhattor]

implemented

[rrrutledge]

Where and how was this implemented?

[yuhattor]

this one:)
InnerSourceCommons/innersourcecommons.org#1021

[spier]

Sounds like there was a misunderstanding of the goal of this issue.

This issue was about automatically pulling the data from eventbrite into our isc.org website. See comment above.

However Russ had asked whether trying to automate this is even worthwhile. i.e. how much work/time does it cost us to do this manually?

One other bit that we might fix as a side-effect of this automation:

Make sure that the community calls that we show as upcoming (i.e. in the future) are really in the future.
e.g. right now we are still showing the community call by Guilherme on May 13th as the next upcoming community call.

These issues are consequences of our website being static, which does have many other advantages. However we might be able to use a combination of GitHub Actions and the eventbrite API to pull data from eventbrite and generate/update the required markdown files on our side (or the other way around!).