loopbackio / loopbackio/loopback-governance
📞 LoopBack Maintainers Call 🚀
@achrinza is already working on this.
Since Apr 12, 2022.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
_In #3, we arranged the first video-call for LoopBack maintainers. The call was well received, we will repeat the meeting every four weeks._
Our regular Maintainers Call provide a space where the maintainers from the community can connect with the core team from IBM, get to know each other, share the plans & visions and discuss any topics that are more efficiently resolved by talking together.
## General agenda
1. Ice breakers to to help participants get to know each other.
2. High-level overview of project status and the near-term roadmap of the core team, presented by @dhmlau.
3. Cool demos. Do you have anything interesting you would like to discuss or demo? Come and show us! Anything from a rough idea to a fully working feature qualifies, the goal is to spread the word and get (early) feedback.
4. Discussion. Let's go around the room, one person at a time, and talk about what you are working on (or planning to), what obstacles you are facing and where you need help, or anything else you want to discuss with other maintainers.
_This is just a basic structure, the agenda can be adapted for each call. We also expect it to evolve over time, based on the experience and your feedback._
## Legal disclaimers
- The calls are recorded and published on YouTube, to allow everybody in the community to watch it in their own time (including maintainers that could not join live).
- By joining the call, you are giving us consent to publishing the recording on YouTube in the channel [StrongLoop by IBM](https://www.youtube.com/channel/UCR8LLOxVNwSEWLMqoZzQNXw).
_We are sensitive about your privacy. Please do let us know if you are not comfortable with this arrangement, either in a public GitHub comment or by sending me an email to [mbajtos@cz.ibm.com](mailto:mbajtos@cz.ibm.com). We'll do our best to find a solution that works for everybody._
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.