Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: removed community meeting from readme #2822

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

fra98
Copy link
Member

@fra98 fra98 commented Nov 21, 2024

Description

This PR removes from the readme file the community meeting paragraph.

@adamjensenbot
Copy link
Collaborator

Hi @fra98. Thanks for your PR!

I am @adamjensenbot.
You can interact with me issuing a slash command in the first line of a comment.
Currently, I understand the following commands:

  • /rebase: Rebase this PR onto the master branch (You can add the option test=true to launch the tests
    when the rebase operation is completed)
  • /merge: Merge this PR into the master branch
  • /build Build Liqo components
  • /test Launch the E2E and Unit tests
  • /hold, /unhold Add/remove the hold label to prevent merging with /merge

Make sure this PR appears in the liqo changelog, adding one of the following labels:

  • kind/breaking: 💥 Breaking Change
  • kind/feature: 🚀 New Feature
  • kind/bug: 🐛 Bug Fix
  • kind/cleanup: 🧹 Code Refactoring
  • kind/docs: 📝 Documentation

@frisso
Copy link
Member

frisso commented Nov 21, 2024

@fra98 I agree to modify this file, because a community meeting once a week is an overkill.
However, I would not remove it at all, as the community should be reinforced, not killed.
For example, this project schedules a "demo day" (which looks a sort of community meeting" once a month: https://www.edgee.cloud/demo-day
I think this is something we should consider, creating an event every month or so.

@fra98
Copy link
Member Author

fra98 commented Nov 26, 2024

@fra98 I agree to modify this file, because a community meeting once a week is an overkill. However, I would not remove it at all, as the community should be reinforced, not killed. For example, this project schedules a "demo day" (which looks a sort of community meeting" once a month: edgee.cloud/demo-day I think this is something we should consider, creating an event every month or so.

@frisso I think the once-a-month meeting is a good idea and we should evaluate it in case. Regarding this PR, we thought to remove it from the readme for now to not give false information to possible attendees. Once we have a more clear idea of what to do we can re-introduce it.

@frisso
Copy link
Member

frisso commented Dec 2, 2024

@fra98 I would suggest to rephrase this way:

🔔 Community Meeting
Liqo holds periodic community meetings to discuss directions and options with the community. Please refer to the Liqo Slack workspace to see the date/time of the next meeting.

@fra98 fra98 force-pushed the frt/remove-community-meeting branch from 580c089 to d01aa55 Compare December 2, 2024 11:54
@fra98 fra98 requested a review from frisso December 2, 2024 11:54
@fra98
Copy link
Member Author

fra98 commented Dec 2, 2024

/rebase test=true

@fra98
Copy link
Member Author

fra98 commented Dec 2, 2024

/merge

@adamjensenbot adamjensenbot added the merge-requested Request bot merging (automatically managed) label Dec 2, 2024
@adamjensenbot adamjensenbot merged commit 983e9a9 into liqotech:master Dec 2, 2024
13 checks passed
@adamjensenbot adamjensenbot removed the merge-requested Request bot merging (automatically managed) label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants