cloud-native-nordics / meetups Goto Github PK

cloud-native-* is redundant as a directory name, let's just have aarhus, copenhagen, helsinki, etc. as top-level dirs

While helping the Aalborg meetup group setup in this repo we talked about that it could create more clarity to move all auto generated in to a folder called "generated" or similar to indicate that these files should not be changed manually.
This would make it more clear that to setup a meetup group or add meetups should be done using meetup.yaml, companies.yaml, and speakers.yaml.

I had to go read the go code again to remember which files to edit and which not to.

That will tell the user how many "problems" there are with the data that we have.
Examples include, missing Github/Speaker's bureau information, no logo for a company, etc. etc.

This is related to #75
cc @kaspernissen @netumoliver @jepp2078

@kaspernissen and/or @Steiniche can you take this on? Thanks!

When cloning this warning is shown

Encountered 2 file(s) that should have been pointers, but weren't:
	aarhus/2019/cloud-native-aarhus-13/linkerd-2-introduction.pdf
	aarhus/2019/cloud-native-aarhus-13/nats.pdf

@kaspernissen something that happened recently?

like https://github.com/cloud-native-finland/meetups/blob/master/SPEAKER_GUIDE.md, but more about best practices how to run a meetup

Store a YAML file for every location that specifies everything needed, and generate docs based on that

...and an example/guide of how to split up the work items involved on different people.
@netumoliver will help with this.

Currently we have around 20 companies that have signed up.

As discussed with @jepp2078

Can we add Turku to the list of cities instead of having to select "other" and type the name in this form? 🙂

We have a meetup in Aarhus with multiple speakers, I would expect something like this to work:

    - startTime: 17:15
      endTime: 18:00
      title: The DevOps story, from Spar Nord Bank. A glimpse, of the success stories and detours we have experienced, during the past years
      speaker:
      - camillalarsen
      - rasmusroemer

Maybe it should be speakers which can be one or more. Would that make sense?

Change this:

type Presentation struct {
         ........
	Speaker   *Speaker `json:"speaker"`
}

to:

type Presentation struct {
         ........
	Speakers   []*Speaker `json:"speakers"`
}

@netumoliver can you help with this?

Should we share templates for our meetup slide decks?

This repo will have more info than just the presentations given at meetups; let's rename it to meetups

Move content from https://github.com/cloud-native-finland/meetups to here

Otherwise cloning will be super slow and inefficient in the end
cc @kaspernissen would this be ok?

In order to make sure the autogenerated content is correct for any PR (ref: #26), we should set up pre-merge CI checks.

Where and how to join the Slack channel

The current implementation of the Makefile outputs a linux binary to the host machine, which the rest of the make targets rely on.

This binary cannot be executed on e.g. a Mac.

Maybe we should wrap the binary in a container instead, making it portable between platforms?

When creating a new group, there are a number of things that are explained in the repos already, other things may not be as clear to new people joining the nordics with the aim of being a good citizen.

There is a clear definition of how to use the artwork stuff, maybe some clarity of whether it is expected to create a PR for the slide-background in order to have your background in that repo as well (once more people did that it might become obvious and it would be easy to switch backgrounds on slides if you wanted to change that according to the city - if that is thought of as being useful)

Other things may not be as clear e.g. that it is a good idea to create a private slack channel for the city e.g. "cloudnativeaarhus" or "cloudnativeaalborg", and create a private channel for each meetup involving e.g. external speakers, sponsors etc. e.g. "cloudnativeaarhus17" or "cloudnativeaalborg1", where the number is the meetup number. These are kept private in order to reduce the noise in the public part of slack.

Another valuable information would be to link to the page informing on the terms to be part of cncf meetup program.

Yet another valuable information could be how to start using the tools in this repo, what to add and where and what gets generated from the meetup API etc. - the thing that @luxas talked about in the hangout.

Maybe the #29 is somehow linked to portions of this?

I can keep adding things as I experience them, however if people think it would be useful to create a "Starting-your-own-town-CNCF-Meetup-group.md" file for that purpose, then that might be the best place to add that information.

Would be awesome if we could get some help with a "brand" id in terms of colors, slide decks, a custom logo etc.

Does anybody know someone who could be interested in helping us out with this?

Since we have multiple meetup groups in each country it would make sense to be able to differentiate which city a given sponsor, member or speaker has affiliation with in a given country.

The site is served over HTTPS but if the webpage tries to load a resource from a non-HTTP destination, the entire site is marked as insecure as we can no longer trust the contents served.

Here is an example of such a request. This is from https://cloudnativenordics.com/meetup-groups/Cloud-Native-Aarhus when you scroll past MHI Vestas Offshore Wind in the Speaker providers section.

The source of the non-HTTPS resource is here:

I would have provided a PR with the HTTPS scheme, but MHI Vestas does not serve the contents over HTTPS.

@dzolotusky can you help here? Please cc the other organizers here so we can add them to the gh org.
Let's collaborate with e.g. these meetups

• https://www.meetup.com/sthlm-k8s/
• https://www.meetup.com/Cloud-Native-Computing-Stockholm/
• https://www.meetup.com/Cloud-Native-Northern-Sweden/

I couldn't find Robert Winter who organizes the Northern Sweden meetup but I'll try to get in touch with him via email

Follow up from #26. Split /meetups.yaml into /speakers.yaml, /companies.yaml and /$city/meetups.yaml

Anyone that wants to take this on?