-
Notifications
You must be signed in to change notification settings - Fork 87
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
Meeting Agenda May 2, 2024 #2407
Comments
@lada7042 Could you raise the following point in tomorrow's meeting please? 🙏 I’ve received notice from the Sensei LMS plugin team that they will no longer be able to provide the following two features that were discussed at WordCamp US in summer 2023. For context, these were features #training had requested as part of our content type consolidation efforts around the site relaunch happening this year.
Based on this information, I'd like to discuss next steps with the team.
|
@lada7042 We could add this item to the agenda, as an FYI: Project updates - Learning Pathways Guides program We currently have a couple of folks still waiting to be matched with a guide, but no guides are available. What are some ways we could attract more guides, ideally in a variety of time zones? A general call for new guides already went out a few weeks ago in the cc @bsanevans |
Hey @lada7042 I'm interested as a Meeting note taker for May 23rd. |
Thank you @Zeelthakkar1207 |
Issue is closed Meeting Recap |
Training Team meetings start at 00:00 UTC weekly on Thursdays. Anyone is welcome to contribute to the meeting by commenting in Slack threads during the meeting and throughout the following days. Meeting notes will be published by the following Tuesday to also incorporate these asynchronous conversations.
This week’s meeting will be hosted by @lada7042 .
1. News
1. Meeting Note Takers
2. Looking for feedback
Based on this information, I'd like to discuss next steps with the team.
-- Regarding feature 1, I think we’ll will want to work with #meta to still create this feature as part of the site redesign. But this should probably be done with as minimal custom development as possible to reduce future maintenance overhead.
-- Feature 2 is something I propose we reassess and consider alternatives for. Technically, I think Learning Pathways could still be launched without this.
The lesson page is getting a makeover too. Learn Design (post by Joen)
I am updating the wording in the Training team contributor badge reviewing section to make it more clear and add a link to the review template. I noticed under copyediting/reviewing there is wording "You should successfully move pieces of content from the “Review in Progress” stage to the “Published or closed” stage in Github."
--Do we want the reviewers to publish or close an issue?
--Is it the author's responsibility to publish or close an issue?
-- Thoughts? Should the wording be removed?
3. Looking for volunteers
We currently have a couple of folks still waiting to be matched with a guide, but no guides are available. What are some ways we could attract more guides, ideally in a variety of time zones? A general call for new guides already went out a few weeks ago in the #training channel, but no one stepped forward, so other ideas are very welcome.
4. Updates from last week's dev-squad triage session
5. Other news
2. Come and Contribute
highlight- Validated feedback awaiting fix
Content ready for review
Feedback awaiting validation
Topics awaiting vetting
Good first issues for developers
Validated feedback awaiting fix
3. Contribution Acknowledgement
4. Project updates
5. Faculty Updates ( DID LAST MEETING)
6. Open Discussions
If you have topics you’d like discussed in the meeting, please leave them as a comment on this issue.
You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.
The text was updated successfully, but these errors were encountered: