Restructure index page to link to individual pages by mauromorales · Pull Request #4 · CloudNativeBelgium/.github

mauromorales · 2026-01-14T12:32:41Z

supersedes #3

evrardjp

I am not against that, but it needs further clarification.

evrardjp · 2026-01-19T07:36:17Z

profile/README.md

+## Individuals

-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.
+Including individuals is a core part of the organization. We recognize speakers, organizers, contributors, and other active community members even if they are not part of a listed group. Individuals who are not affiliated with a specific community are encouraged to participate and can serve as neutral chairs.


I am not sure to fully grasp your meaning and intent here.

This impacts the rest of the review btw.

it would be nice to have people who are not affiliated to any of the groups but who still want to be part of the umbrella organization. that way if there's any scenario where there needs to be an objective vote, they can do it

After further thinking, I can come up with a counter proposal.

Focus on individuals. This maps EXACTLY to your text, not exactly with your explanation here.

Each individual maintain their "profile" through issues. In there, they ASK to be owner/member of a group. First member asking for ownership of group gets access to the group without requesting further details. Next ones we ask for existing members for approval.

Owners of a group are representative their own content. So it means they can update our pages by doing PRs. Simple.

This means it's very simple: people post their personal updates into github. We update the content. Or they do update it through PR. Simple, isn't it enough?

This would be similar to "group auto-registration".

profile/README.md

evrardjp · 2026-01-19T07:38:29Z

profile/README.md

+## Listing Format & Status

-## Contribute
+Required fields for groups: name, short description, status, link, and a contact channel.


Should we add a check date now that we check for activity ?

as in, last time we checked them? or how?

profile/README.md

evrardjp · 2026-01-19T07:43:12Z

GOVERNANCE.md

+- Maintainers: reviewers who merge changes and keep the index current in this org. Maintainers are added by consensus of existing maintainers.
+- Neutral chairs: individuals who facilitate coordination across groups without representing any single group.
+
+### Group Roles (each community)


That assumes or force a community to adhere your wording and your way of doing.

Wouldn't contact persons be enough for discovery layer?

At the same time, if we do that, we'll lose some of the added value of a ranking inside each community, should they decide to have one.

yup good point ... not sure

evrardjp · 2026-01-19T08:14:39Z

GOVERNANCE.md

+
+## Shared Resources
+
+- Shared repos are opt-in and only created when multiple groups agree to collaborate.


" when two or more groups"? It would prevent the use of the term multiple, which could be ambiguous. Imagine the conversation about Multiple = majority...

@copilot can you implement the suggestion?

.github/ISSUE_TEMPLATE/listing-request.md

evrardjp · 2026-01-19T08:17:14Z

.github/ISSUE_TEMPLATE/listing-request.md

+## Type
+- [ ] Group
+- [ ] Individual
+- [ ] Update to existing listing


Shouldn't changes be atomic ? What did you mean here ?

What I meant is that "everything is an update". Hence you only need two lines: updates to groups or updates to individual members.

yeah i guess it was to distinguish creation vs update, but maybe that's not necessary, I'll remove

@copilot can you remove this line?

evrardjp · 2026-01-19T08:17:43Z

.github/PULL_REQUEST_TEMPLATE.md

+- 
+
+## Checklist
+- [ ] Listing fields are complete and neutral


I did not get this yet. But it's because I skimmed the PR.

@evrardjp basically no missing fields in the application and that they are neutral in the sense of, no description like "We are the best cloud native group in belgium" :P

@copilot reword while keeping intent. Avoid "Listing" "complete" (be more explicit).

Copilot · 2026-01-22T17:47:36Z

@mauromorales I've opened a new pull request, #5, to work on those changes. Once the pull request is ready, I'll request review from you.

Copilot · 2026-01-22T17:48:47Z

@mauromorales I've opened a new pull request, #6, to work on those changes. Once the pull request is ready, I'll request review from you.

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Copilot · 2026-01-22T17:58:08Z

@mauromorales I've opened a new pull request, #7, to work on those changes. Once the pull request is ready, I'll request review from you.

Copilot · 2026-01-22T17:59:28Z

@mauromorales I've opened a new pull request, #8, to work on those changes. Once the pull request is ready, I'll request review from you.

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Add governance prerequisite checklist to listing request template

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Remove "Update to existing listing" option from issue template

Clarify shared resource requirement in governance

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

…r-one Add GitHub issues to contact channels list

profile/README.md

evrardjp

I have a tendency to overthink this.
I don't want us to do back and forth on it.

I am FINE with what you are proposing. I am just suggesting something even simpler. I can write the code after this one if you wish. Or we do it directly.

18 commits for this is a bit exagerated already...

In other words:
Please read what I suggested, tell me what you think, then merge if you don't want a change OR tell me what you think and I will update this.

evrardjp · 2026-01-26T12:43:50Z

profile/README.md

+## Individuals

-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.
+Including individuals is a core part of the organization. We recognize speakers, organizers, contributors, and other active community members even if they are not part of a listed group. Individuals who are not affiliated with a specific community are encouraged to participate and can serve as neutral chairs.


After further thinking, I can come up with a counter proposal.

Focus on individuals. This maps EXACTLY to your text, not exactly with your explanation here.

Each individual maintain their "profile" through issues. In there, they ASK to be owner/member of a group. First member asking for ownership of group gets access to the group without requesting further details. Next ones we ask for existing members for approval.

Owners of a group are representative their own content. So it means they can update our pages by doing PRs. Simple.

This means it's very simple: people post their personal updates into github. We update the content. Or they do update it through PR. Simple, isn't it enough?

This would be similar to "group auto-registration".

evrardjp · 2026-01-26T12:46:42Z

profile/README.md

+## Listing Format & Status

-## Contribute
+Required fields for groups: name, short description, status, link, and a contact channel.


evrardjp · 2026-01-26T12:47:23Z

profile/README.md

-	📍 **Venue partners** – Help us find cozy spaces across Belgium to gather and connect.
-	🤝 **Volunteers** – Whether it’s logistics or promotion, every helping hand makes a difference.
+Open an issue using the listing request template and we'll take it from there. See `CONTRIBUTING.md` for required fields.



Based on previous review message, we would add here "How do you add a new group?"

mauromorales added 4 commits January 14, 2026 13:31

restructure index page to link to individual pages

2c8af6e

add governance

13b3bab

add contributing, templates and update profile

078efc6

update readme

7d01498

mauromorales self-assigned this Jan 14, 2026

mauromorales requested a review from evrardjp January 14, 2026 18:48

mauromorales marked this pull request as ready for review January 14, 2026 18:49

evrardjp reviewed Jan 19, 2026

View reviewed changes

Initial plan

0992cd9

Copilot AI mentioned this pull request Jan 22, 2026

Add governance prerequisite checklist to listing request template #5

Merged

Initial plan

025dd61

Copilot AI mentioned this pull request Jan 22, 2026

Remove "Update to existing listing" option from issue template #6

Merged

Copilot AI and others added 3 commits January 22, 2026 17:49

Add governance prerequisite checklist to listing request template

0fd70de

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Remove 'Update to existing listing' option from listing request template

ad1cbdf

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Initial plan

3e344d5

Copilot AI mentioned this pull request Jan 22, 2026

Simplify contact section to only use GitHub issues #7

Merged

Initial plan

6bc3e1e

Copilot AI mentioned this pull request Jan 22, 2026

Clarify shared resource requirement in governance #8

Merged

Copilot AI and others added 7 commits January 22, 2026 17:59

Update contact section to list channels including GitHub issues

70bac20

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Merge pull request #5 from CloudNativeBelgium/copilot/sub-pr-4

67034b1

Add governance prerequisite checklist to listing request template

Replace 'multiple groups' with 'two or more groups' for clarity

504f27e

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Merge pull request #6 from CloudNativeBelgium/copilot/sub-pr-4-again

7abd6d5

Remove "Update to existing listing" option from issue template

Merge pull request #8 from CloudNativeBelgium/copilot/sub-pr-4-yet-again

3da6b28

Clarify shared resource requirement in governance

Simplify contact section to only GitHub issues

0fc9cb8

Co-authored-by: mauromorales <433958+mauromorales@users.noreply.github.com>

Merge pull request #7 from CloudNativeBelgium/copilot/sub-pr-4-anothe…

b9ae3cd

…r-one Add GitHub issues to contact channels list

mauromorales commented Jan 22, 2026

View reviewed changes

profile/README.md Outdated Show resolved Hide resolved

Apply suggestion from @mauromorales

199e288

mauromorales requested a review from evrardjp January 22, 2026 18:29

evrardjp approved these changes Jan 26, 2026

View reviewed changes


		## Shared Resources

		- Shared repos are opt-in and only created when multiple groups agree to collaborate.

Conversation

mauromorales commented Jan 14, 2026

Uh oh!

evrardjp left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI commented Jan 22, 2026

Uh oh!

Copilot AI commented Jan 22, 2026

Uh oh!

Copilot AI commented Jan 22, 2026

Uh oh!

Copilot AI commented Jan 22, 2026

Uh oh!

Uh oh!

evrardjp left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

evrardjp left a comment •

edited

Loading