Revise README for Cloud Native Belgium meetups#3
Conversation
Updated the README to clarify the organization and roles of meetup groups in Belgium.
evrardjp
left a comment
evrardjp
left a comment
There was a problem hiding this comment.
A typo, but also it looks like the term meetup is bothering you.
Would you mind clarifying?
| As the Cloud Native ecosystem continues to grow, multiple meetup groups have emerged across Belgium, each organizing local events and initiatives. To reduce confusion and create synergies, we decided to collaborate across these groups and centralize shared resources, communication, and community efforts under Cloud Native Belgium. | ||
|
|
||
| To reduce confusion and create synergies, we decided to collaborate across these groups and centralize shared resources, communication, and community efforts under Cloud Native Belgium. | ||
| We are currently organized through two different channels, each with respecitive organisers. |
| * The [Cloud Native Belgium](https://www.meetup.com/cloudnative-belgium/) meetups on meetup.com. | ||
| * The Official [CNCF Cloud Native Brussels](https://community.cncf.io/cloud-native-brussels/) meetups. | ||
| * The [CNCF Brussels Community events](https://community.cncf.io/cloud-native-brussels/). | ||
| * The [Cloud Native Belgium meetups](https://www.meetup.com/cloudnative-belgium/). |
There was a problem hiding this comment.
I don't really like this phrasing, maybe we can reiterate.
I kinda like the fact it's clear you were the previous Kubernetes Belgium group on meetup.com.
By removing the mention of meetup.com, you remove that intent.
The problem mostly comes from the fact that "a meetup" is not only something from "meetup.com". I blame meetup.com trying to appropriate the term meetup for non-native english speakers :D
(We usually call the CNCF events "CNCF meetups").
Can we think of a better wording here?
There was a problem hiding this comment.
Yes I agree with your reasoning
| If you wish to help organise the official meetup, it's all happening in the [cncf-events repo](https://github.com/CloudNativeBelgium/cncf-events). | ||
| If you wish to help organise on the meetup.com group, please have a look at [the meetup.com-events repo](https://github.com/CloudNativeBelgium/meetup.com-events) | ||
| If you wish to help organise an official CNCF event, it's all happening in the [cncf-events repo](https://github.com/CloudNativeBelgium/cncf-events). | ||
| If you wish to help organise a meetup, please have a look at [the meetup.com-events repo](https://github.com/CloudNativeBelgium/meetup.com-events) |
There was a problem hiding this comment.
again, same thing for line 26. I do partially prefer your line 25, that's more clear that it's CNCF. Maybe something in between?
There was a problem hiding this comment.
I'm wondering if we should just reword this section to not focus on "help organize meetups/events" but all kinds of contributions e.g. help design the logo and what not. And then we can simplify it to links to the "contribution" page of the respective repositories and then each group can explain there the process to help them
| | [Mauro Morales](http://github.com/mauromorales) | CNCF Community organizer | Ghent | | ||
| | [Christopher Peeters](https://github.com/cpeetersburg) | CNCF Community organizer | Brussels | | ||
| | [Jean-Philippe Evrard](https://github.com/evrardjp) | CNCF Community organizer | Vilvoorde | | ||
|
|
There was a problem hiding this comment.
Why the split?
I thought it was great to unite people a bit more!
Could you edit the table instead?
There was a problem hiding this comment.
same here, how about on this page we just say who are the "representatives" of each group who are working together between the two communities, and then link to the repo to have the details of who forms that community
|
|
||
| | Name | Role | City | | ||
| | ---- | ---- | ---- | | ||
| | [Pieter Lewyllie](https://github.com/plewyllie) | Meetup.com organizer | Brussels | |
| If you wish to help organise an official CNCF event, it's all happening in the [cncf-events repo](https://github.com/CloudNativeBelgium/cncf-events). | ||
| If you wish to help organise a meetup, please have a look at [the meetup.com-events repo](https://github.com/CloudNativeBelgium/meetup.com-events) |
There was a problem hiding this comment.
What about this?
If you wish to help organise an official CNCF meetup, it's all happening in the [cncf-events repo](https://github.com/CloudNativeBelgium/cncf-events).
If you wish to help organise an official meetup.com meetup, please have a look at [the meetup.com-events repo](https://github.com/CloudNativeBelgium/meetup.com-events)
There was a problem hiding this comment.
I would not say bothering, I played around how we could make it clear what is a CNCF event, and what is a Meetup.com
|
@EvelienSchellekens could you have a looksie please? Thank you :) |
mauromorales
left a comment
mauromorales
left a comment
There was a problem hiding this comment.
I left a bigger comment on the slack channel and I'm just putting it here too for transparency:
I think what we’re missing is a neutral discovery layer. Just a place that helps people find what already exists.
My suggestion would be to use the .github repo purely as that neutral layer: a simple index of all Cloud Native communities in Belgium that want to be listed there, with a short description of what each one is and a link to their own repo or website.
Each community would keep full autonomy over its own repo, branding, and how it presents itself. The .github org wouldn’t speak for anyone, it would just help people navigate the ecosystem without getting confused.
If there are wording or positioning questions, we handle them transparently in issues/PRs so both sides can see and agree on what’s written.
Long-term, I also think a small shared website that mirrors this structure would really help with discoverability. A few people have told me they tried to look us up and couldn’t find anything. Having one neutral entry point would fix that, and it also gives us a very practical way to collaborate across teams without stepping on anyone’s identity.
One nice side effect of having this neutral layer is that it doesn’t prevent overlap. If at some point people want to be involved in more than one group, or if we want to run something together (like a website, venue contacts, sponsors, etc.), we can just do that in shared repos under the github org without affecting anyone’s independence. But none of that is required, it just gives us a place to collaborate when it makes sense.
Another thing the umbrella could be useful for, over time, is setting some very lightweight baseline expectations for anything that wants to be listed there, for example having a README, some basic governance info, and a way to know whether a group is active or not. Not as a barrier to entry, but just so that when someone lands on the page, they don’t have to guess what’s real, who runs it, or whether it’s still alive. We don’t have to decide any of that now, it’s just something the umbrella makes possible if we later agree it’s helpful.
3 participants
Updated the README to clarify the organization and roles of meetup groups in Belgium.