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

📞 LoopBack Maintainers Call 🚀 #4

Open
bajtos opened this issue Apr 2, 2020 · 43 comments
Open

📞 LoopBack Maintainers Call 🚀 #4

bajtos opened this issue Apr 2, 2020 · 43 comments
Assignees
Labels
video-call 📞 Issues discussing regular or ad-hoc video-call meetings

Comments

@bajtos
Copy link
Member

bajtos commented Apr 2, 2020

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.

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 [email protected]. We'll do our best to find a solution that works for everybody.

@bajtos bajtos added the video-call 📞 Issues discussing regular or ad-hoc video-call meetings label Apr 2, 2020
@bajtos bajtos self-assigned this Apr 2, 2020
@bajtos

This comment has been minimized.

@bajtos bajtos changed the title 📞 LoopBack Maintainers Calls 🚀 📞 LoopBack Maintainers Call 🚀 Apr 2, 2020
@bajtos
Copy link
Member Author

bajtos commented Apr 2, 2020

There was a slight glitch in my webex setup, please ignore my previous comment. Here is the correct information for joining the call.

Thursday 2020-04-23

@dhmlau
Copy link
Member

dhmlau commented Apr 2, 2020

Just a thought. For agenda item #2, perhaps everyone shares what they are working on currently instead?

@frbuceta

This comment has been minimized.

@dhmlau

This comment has been minimized.

@frbuceta

This comment has been minimized.

@dhmlau

This comment has been minimized.

@bajtos

This comment has been minimized.

@bajtos

This comment has been minimized.

@bajtos
Copy link
Member Author

bajtos commented Apr 24, 2020

Thursday 2020-05-21

@bajtos

This comment has been minimized.

@bajtos
Copy link
Member Author

bajtos commented May 25, 2020

Thursday 2020-06-18

@bajtos
Copy link
Member Author

bajtos commented Jun 19, 2020

Thursday 2020-07-16

@bajtos

This comment has been minimized.

@bajtos
Copy link
Member Author

bajtos commented Jul 24, 2020

Thursday 2020-08-13

@bajtos
Copy link
Member Author

bajtos commented Aug 31, 2020

Thursday 2020-09-10

@bajtos

This comment has been minimized.

@bajtos

This comment has been minimized.

@bajtos
Copy link
Member Author

bajtos commented Nov 2, 2020

Thursday 2020-11-05

@bajtos

This comment has been minimized.

@bajtos
Copy link
Member Author

bajtos commented Nov 30, 2020

Thursday 2020-12-03

@bajtos

This comment has been minimized.

@bajtos
Copy link
Member Author

bajtos commented Jan 18, 2021

Thursday 2021-01-21

@bajtos

This comment has been minimized.

@bajtos
Copy link
Member Author

bajtos commented Feb 15, 2021

Thursday 2021-02-18

@bajtos

This comment has been minimized.

@hacksparrow
Copy link

hacksparrow commented Mar 16, 2021

Thursday 2021-03-18

@hacksparrow

This comment was marked as duplicate.

@hacksparrow
Copy link

Thursday 2021-04-15

@hacksparrow
Copy link

hacksparrow commented Jun 8, 2021

Thursday 2021-06-10

@hacksparrow
Copy link

hacksparrow commented Jul 8, 2021

Thursday 2021-07-08

@hacksparrow
Copy link

hacksparrow commented Aug 12, 2021

Thursday 2021-08-12

@hacksparrow
Copy link

hacksparrow commented Sep 8, 2021

Thursday 2021-09-09

@hacksparrow
Copy link

hacksparrow commented Oct 14, 2021

Thursday 2021-10-14

@hacksparrow
Copy link

hacksparrow commented Nov 8, 2021

Thursday 2021-11-11

@achrinza
Copy link
Member

achrinza commented Dec 8, 2021

Thursday 2021-12-09

@achrinza
Copy link
Member

achrinza commented Jan 12, 2022

Thursday 2022-01-13

@achrinza
Copy link
Member

achrinza commented Feb 9, 2022

Wednesday 2022-02-09

@achrinza
Copy link
Member

achrinza commented Feb 27, 2022

Wednesday 2022-03-09

@bajtos bajtos removed their assignment Apr 5, 2022
@achrinza achrinza self-assigned this Apr 12, 2022
@achrinza
Copy link
Member

achrinza commented Apr 12, 2022

Wednesday 2022-04-13

@achrinza
Copy link
Member

achrinza commented Apr 29, 2022

Wednesday 2022-05-11

@achrinza
Copy link
Member

achrinza commented Feb 6, 2023

Wednesday 2023-02-14

@achrinza
Copy link
Member

achrinza commented Nov 3, 2023

Wednesday 2023-11-14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
video-call 📞 Issues discussing regular or ad-hoc video-call meetings
Projects
None yet
Development

No branches or pull requests

5 participants