Recap for Training Team Meeting June 13, 2019

Attendance: @juliekuehl, @jessecowens, @man4toman, @chetan200891, @Janet357, @iwritten, @aurooba

Slack timestamp

Learn siteLearn site The Training Team publishes its completed lesson plans at https://learn.wordpress.org/ which is often referred to as the "Learn" site. update

@chetan200891 is waiting on some stuff from the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team.

@man4toman created his first PR for review and an issue for the footer file that needs reviewing

@jessecowens has a working version of the markdown importer but is working on getting it recognize the JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. format, perhaps some folks at WCEU can help with that – potentially the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ team.

@aurooba put together a README file for the Learn site beta repo to help if anyone else wants to jump in and contribute. She also has a PR almost ready for the workshop template, which should be ready for submission by Sunday.

As we’ve started to build out the Learn site, @juliekuehl identified some issues that have come up in the design – things that should be checkboxes are radio buttons, etc. We have to try and figure out how to make things happen in the Make environment without the use of additional plugins.

WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

@jessecowens will be the acting lead at WCEU for the Training team, the rest of the team can join remotely.

Contributor Day is on Thursday 20 June from 8:30-17:00 German time (UTC +2) which is Central European Summer Time

Four lesson plans have been set aside for those contributors to focus on for the workshop Best Practices for WordPress Friendly Layout. Issues have been created for all of them, so they should be ready for people to address them. We’re hoping to get the workshop to an instructional review status by the end of WCEU.

@iwritten will do some research and printout Blooms.

@juliekuehl created a ZenHub workspace (you’ll need to log in with your GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ account to see the workspace) set up specifically for Contributor Day with all the issues that can be addressed during that day.

@juliekuehl is working on drafting a blog post up on P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. to help folks prepare to contribute to our team, and @jessecowens will review it.

There will be an assigned table (or a whole room) at WCEU Contributor Day for the Training team

Upcoming team meetings

As a reminder, due to WCEU there will be no regular weekly team meeting next week.

The following week @juliekuehl will be on vacation and @jessecowens will lead the meeting with a WCEU recap and update on everything

Open announcements/discussion

@juliekuehl noted that while we’ve been focused on WCEU, other things have been moving forward too. Instructional reviews. Updates to the style guide. Lesson plan pull requests.

Action Items

#contributor-days, #workshops

Recap for Training Team Meeting June 6, 2019

Attendance: @juliekuehl, @jessecowens, @iwritten, @man4toman, @kartiks16, @mukesh27, @aurooba, @viitorcloudvc, @chetan200891, @lisa

Slack timestamp

Learn siteLearn site The Training Team publishes its completed lesson plans at https://learn.wordpress.org/ which is often referred to as the "Learn" site. update

@chetan200891 merged several pull requests that added the following new templates to the Learn site betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. theme:

If anyone else wants to help out with the development of the Learn site, there are clear issues with help wanted labels in the Learn site GitHub repository that you can ask to be assigned to.

@aurooba has a pull request almost ready to publish that will add a README file to the repository that shows potential contributors how to set up a local installation so they can properly contribute to the theme.

@juliekuehl: It’s going to be great to have a beta site to show to contributors at WCEU. It will help them understand how their work fits in.

@aurooba wants to discuss the transition to SCSS from CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. the next time @chetan200891 is available during the meeting as well – it will help with modularity and collaboration.

@chetan200891 is planning on adding responsive styling to the templates soon, it doesn’t currently exist. Also brought up the issue of lack of authentication fields on the Submit Lesson Idea page, and recommended that either the submitter be required to include their WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ username or email, or both.

@juliekuehl also suggested we add an area for objectives and recommended @chetan200891 go ahead and add these fields to the template.

@jessecowens has been working on the markdown importer implementation and the Custom Post Types code but would love help from anyone who’d like to assist.

Currently, @jessecowens is trying to get the manifest.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. script perfected reliably for the markdown importer implementation.

Slides Style Guide update

@Janet357 made some comments on the TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. card

@juliekuehl added some information to the Slides Style Guide page in the handbook and @jessecowens is planning on getting a video up today possibly.

WCEU Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

The folks from the Calgary Contributor Day came up with a great list of workshops based on the ideas in this post (workshops are detailed in the comments), so the next step is to decide on a workshop to focus on as a team and tackle that during WCEU Contributor Day.

@jessecowens and the communications team came up with the following snippet for the day:

The training team has identified several workshops– series of lesson plans for a specific audience/learning outcome– and we’ll be doing a “Sprint” to complete one of them. The workshop we’ll be working on, Best Practices for WordPress-Friendly Layout includes the lesson plans Introduction to CSS, Web Fonts, Using the Theme CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., and Using Child Themes.

Everyone agreed that this is a good workshop to start with and as work begins on it, more lessons will probably need to be identified and created.

Once WCEU Contributor Day happens, we can set priorities for other workshops based on the experience and feedback from WCEU.

ZenHub now has the ability to break out other workspaces and this can be useful to narrow focus and not overwhelm people as they begin to contribute.

@juliekuehl: I’m going to work on making more digestible versions [of ZenHub Workspaces] that people can use to look for issues that they can work on. Which also means that there’s a ton of issues that could be added to lesson plans

screenshot of the workspace for WCEU Contributor Day

@jessecowens recommended making issues in these 4 plans to manage Contributor Day more easily.

Documentation will need to be created on how to get set up and use ZenHub if we want to use it during Contributor Day. @aurooba volunteered to kickstart the ZenHub documentation if someone (@juliekuehl volunteered) takes her through it once.

@juliekuehl: So right now there are only two “Workspaces” – the big, ugly master one and one called “Contributor Day” which is in preparation for WCEU. I can imagine adding a “New Contributors” workspace and then labeling the issues with the skills required to complete them.

Upcoming team meetings

@juliekuehl: WCEU is two weeks away and we will not have a meeting that week. So that would be 20 June. But we will meet next week (13 June) and be back again the week after WCEU (27 June)

Lesson plan assignments and updates

The WP-CLI lesson plan has been added to the team’s reposrepos The Training Team uses GitHub for working copies of lesson plans. You can find them at https://github.com/wptrainingteam. and is looking great!

#contributor-days, #handbook, #workshops

Recap for Training Team Meeting May 30, 2019

Attendance: @juliekuehl, @man4toman, @iwritten, @chetan200891, @aurooba, @Janet357, @viitorcloudvc, @jessecowens, @kartiks16, @iwritten

Slack timestamp

Learn SiteLearn site The Training Team publishes its completed lesson plans at https://learn.wordpress.org/ which is often referred to as the "Learn" site. Update

@chetan200891 worked on the Custom Metadata for the learn site, which can be found here.

Everyone’s comments and feedback are encouraged. For those contributors, who would like edit access, please reach out to @chetan200891.

Getting Started Info / Handbook Update

@juliekuehl made significant progress on cleaning up and streamlining the Getting Started info in the Training Handbook to make it leaner and clearer.

@iwritten went through it today to learn and found it very helpful, so that’s good feedback!

The new glossary tool is activated on the Training Team blog, if there are other definitions anyone wants to suggest, please let @juliekuehl or another team member know!

@aurooba shared the open source plugin link for anyone who may want to take advantage of the feature.

@juliekuehl: I believe that the Handbook could still use some work around our actual workflow processes, but with the Learn site still in development some of those may be changing which is why we haven’t documented those just yet.

@jessecowens noted that there should be more videos and a lot of people concurred.

The move to ZenHub from Waffle.io for GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ project management also impacts the workflow, and there are a lot of new features that can be taken advantage of. This will also need to be documented.

Style Guide update

@janet357 worked on the Style Guide and made good progress! The more comments and feedback on Handbook Information the better!

Workshop focus / Calgary Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

Reference: https://make.wordpress.org/training/2019/05/25/a-small-shift-in-focus/ (and the comments!)

The Calgary Contributor Day contributions included brainstorming and fleshing out outlines for 8 potential workshops targeting different audiences that the Training team could work on.

@juliekuehl noted a lot of lesson plans that were included are in various stages of development and completeness.

@Janet357 mentioned that the next is step is to decide which workshop to start on and list the lesson plans to be used. These become top priority.

@juliekuehl: So, what I’d like the team to do at this point is to think about those suggestions and make comments as to whether or not they think they are the right ones or if there are others that should be included. Then I’d like us to get down to the specifics of choosing a workshop to begin with and decide which lesson plans would be a part of it and build those out. Then we could move on to the next workshop. Basically do sprints to get a workshop built out.

@aurooba volunteered to create TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. cards for each workshop that has been suggested after she’s given access. @juliekuehl will also make an “Other Workshop Ideas” Trello card.

Everyone should comment on the Trello card for the workshop they feel can be one of the first ones to work on.

WCEU Contributor Day

If everything can be put in place in time for WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe, the aim is to do a couple sprints on workshops to get them fleshed out and completed. Beginner workshops will take precedence and will likely be the first few to be fleshed out and completed.

@juliekuehl and @jessecowens were thinking if it’s possible to also do a sprint on the learn.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ there too with the help of another team.

@aurooba suggested that the tasks left for the website be added to GitHub. @juliekuehl will go through and create issues (in the repository https://github.com/wptrainingteam/learn-theme-beta) for all the tasks noted in the Trello card (https://trello.com/c/HgCQ6Jlp). @chetan200891 also felt that getting help from a different team would be helpful!

Lesson plan assignments and updates

A repository was created for the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ lesson plan that @tristup created, now it just needs to be submitted using a PR request by @tristup to https://github.com/wptrainingteam/wp-cli.

There have been a few pull requests. Some of these still need to be reviewed and a few more have come in since the last queue clean out.

The team focus is coming back to including lesson plans, and the plan is to focus intensely on them after WordCamp Europe.

Open announcements/discussion

@chetan200891 shared GitPod, which is an online IDE for Github, that is easy and fast to use. You can work directly on Repo. Edit, Preview and Submit PR. It’s free for open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. projects! He made a video on how to work using it: https://www.youtube.com/watch?v=xmCEyyzctbk.

@juliekuehl mentioned that this may become the recommended way to work on lesson plans for the Training team and contributors. She’ll add the video to the Getting Started section in the Training Handbook.

Action Items

Tasks without a specific person assigned are for anyone who’d like to contribute.

  • Provide comments and feedback on Custom Metadata doc.
  • Provide comments and feedback on Style Guide and Handbook.
  • Suggestions and feedback on which workshops to focus on, on this post.
  • @aurooba: create Trello cards for each workshop that has been suggested
  • @juliekuehl: Make an “Other Workshop Ideas” Trello card.
  • Comment on workshop Trello cards to indicate which one you think should be prioritized
  • @juliekuehl: Create issues for tasks left for Learn site in GitHub
  • @tristup: submit lesson plan to WP-CLI lesson plan repository
  • @juliekuehl: add this video to the Handbook
  • There are some lesson plan PRs to review still

#contributor-days, #feedback, #handbook, #workshops

Notes on January 3, 2019 Meeting

Slack Log (Requires SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. login to view. Set one up if you don’t have a Slack account)

Welcome and Meeting Outline

  1. Handbook Updates
    1. Revising the Style Guide
      1. Examples displayed should be relevant to GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ formatting
      2. Slides style guide wasn’t functional as the slide display tool was discontinued. Suggest moving to https://pages.github.com/ . 
      3. @juliekuehl will update this page.
    2. Add tasks for semi-annual handbook updates to our team TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board.
      1. 2 weeks before time changes begin, communicate about if the meeting moves times.
      2. Update a few places on the handbook displaying meeting times
      3. Update annual team goals
  2. Videos
    1. @jessecowens has been working on editing the atom video with some updates. He expects both the atom video and the one on slides to be complete by end of January
  3. Learn.WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/
    1. The Design Team is still working on re-doing the design based on the recommendations of the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team.
  4. Lesson Plans
    1. Regrouping about what lesson plans are in process next week to get more ready for the relaunch of the Learn siteLearn site The Training Team publishes its completed lesson plans at https://learn.wordpress.org/ which is often referred to as the "Learn" site.
    2. Possibly conduct a video meeting to brainstorm regrouping on lesson plans.
    3. Work with Kids Camps for workshop plans
    4. Repo Maintenance Labels for tagging lesson plans
      1. @courane01 will brainstorm ideas this week to be reviewed next week (January 10) and finalized on January 17.
      2. These will be part of the lesson plan submission process
    5. Meeting Wrap Up and Next Meeting Next meeting on 10 Jan 2019

#handbook, #slides, #videos

Notes on December 20, 2018 Meeting

Slack Log (Requires SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. login to view. Set one up if you don’t have a Slack account)

  1. Welcome and Meeting Outline
    1. @juliekuehl Welcomed everyone to the meeting and reviewed how the #Training team operates for the new comers and also touched on the outcome of 2018 and the projects accomplished. Julie also outlined the purpose of the meeting and asked about the goals for 2019.
    2. Link to the 2019 Goals post
    3. Suggestion for more videos on our YouTube channel from @fahim.
    4. @courtneyengle suggests:
      TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. & categorize lesson plans by versions, themes, etc. in GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ (digging back to the old Content Audit idea)
      • Purpose statement about videos on Youtube (target audience is those contributing to and accessing materials from the training team, not the end user to be trained)
      • Write guidelines for plugins created by an agency
      • On-boarding buddies
  2. @juliekuehl mentioned that the lesson plans follow BloomBloom's Taxonomy Bloom's Taxonomy is a way of writing lesson plan objectives using specific words so that the objectives can be measured. See https://make.wordpress.org/training/handbook/guidelines/blooms-taxonomy/ for more details.’s TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. (more info) and that there are needs for translating videos from WordPress.tv into lesson outlines.
  3. How to Contribute
    1. Look up projects on Trello.
    2. Review style guides available on our getting started page
    3. GitHub issues are listed out in Waffle.io 
  4. Comments about GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg//5.0 and WCUS
    1. Suggestion on lesson for using 5.0 / differences between old editor and new editor.
    2. Newcomers to WordPress would not need lesson on legacy WordPress.
    3. @fahim links to Health Check Plugin
    4. @courtneyengle How to create a post lesson plan idea – reuse Comparing Classic Editor and Gutenberg for the tasks in creating a lesson plan. Create same plan using both modes.
  5. Meeting Wrap Up and Next Meeting
    1. Next meeting on 3 Jan 2019 and resuming the usual weekly schedule after that.

Recap of August 2, 2017 Meeting

@aimeegc is working on the content flow audit process and is working to have something by the end of September.

@conradhallauthor has completed the first stage of content inventory and will now begin to identify the state of each piece with the help of @coachwp and incorporate testing feedback

@bethsoderberg and @melindahelt will take a look at SupportFlow and see what needs to happen there.

@coachwp reminded us about https://docs.google.com/spreadsheets/d/1PPb9Y9eXhdZXS7QJYCcWXzyMZRVVoVDLXrEbYyTHfnY/edit#gid=0 which will be helpful to the inventory that @conradhallauthor is working on

@aimeegc mentioned in regards to processing lesson plan testing feedback (Google Spreadsheet) “This may or may not be helpful, but the name for what we’re starting to veer into is actually a whole thing called Program Evaluation (taking feedback, results, questions, etc, and making sense of it to determine whether something is working well or not, as well as turning all that data and results into actionable next steps) so it was smart to have a person working on this only, and we may want to come back to that once we have a content flow to discuss. Just stating it for the record at this point. There are people who devote their career solely to this part of what we’re endeavoring to do”

@bethsoderberg brought up a topic from our last video call that we determined that folks are not actually using our lesson plans as a script when delivering the lessons. People are not reading them word for word (which we agreed is a good thing!)

We will not be ditching the current lesson plans, but would like to brainstorm, over the long run, what format we want our lessons to have.

Once we determine a format, we will reformulate one or two plans and test those, in order to confirm the new format. THEN we may work on refactoring existing plans to fit the new, tested format.

We discussed an outline format, similar to something that could be converted to slides by the instructor.

We also discussed the original assumption that instructors didn’t already know everything (and didn’t need to) in order to pick up a lesson plan and teach it.

@aaimeeg shared a sample lesson plan format: https://docs.google.com/document/d/1JDgl8BJ9c7Q2moaUkyG075RD5wlX0Yb0xsEZlME4aYI/edit

@aimeegc shared the following from WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. for Publishers:

A lot of what I heard was about the frustration that WordPress developers aren’t ramped up enough for the kinds of developer positions open (in Publishing, but I bet this is true elsewhere), and it would be great to channel people’s desire to learn and get good at WordPress specific to goals and industry. WordPress developing is context-specific, so it would be great to see more support or direction being applied to what people want to do with what they’re learning about WordPress.

I’m not entirely sure how that should fit into our scope as it currently exists, but if our goal is to provide official training and skill building to become professional wordpress developers, through helping teachers of WordPress teach others, then it might be worthwhile to entertain how we might consider this need from our wider WordPress community

@bethsoderberg mentioned that this could potentially be addressed in the future workshop plans rather than individual lesson plans themselves.

Recap of August 8, 2017 meeting

1. Content flow and process (see Aimee’s post on this for quick reference)

  • Talked about item 1 and 4 in the post first
  • Item 1:
    • David’s share—copyediting a lesson used to be what group meant by “content flow.” Content flow is slightly bigger now to include the idea generating and pitching of lessons, then testing lessons and getting/using that feedback
  • Item 4:
    • Beth: general consensus on what the process should be or is, but implementation is where we’re getting stuck. Different people come and go, and they interpret the process differently. This creates inconsistency and confusion around what is most recent and up to date and the final choice
    • Scott and Melissa: Yes. We need to just state what is, and include that as a handbook page to clarify how to implement/improve documentation
    • Julie: we need to lock down a process to be THE process. We suffer from the open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. collective action inertia. The process can serve as a president/decision maker
  • Item 3:
    • Have tried all the ways to manage/own steps
    • From what I am hearing, this is closely intertwined with volunteer management and expectations in open source community
    • Content management and documentation closely linked
  • Clues to track down existing information to help with getting this endeavor to have a definitive process underway:
    • TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the make.wordpress.com/marketing team uses for example: https://trello.com/b/8UGHVBu8/wp-marketing. board won’t work, but may have most up to date information/data
      • Consider GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/—then:
        • wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ = handbook only
        • wordpress.org = lessons
        • Github = in between
      • Copywriting plugins to manage who is managing steps is a nixed idea
      • Constrained by Make site (its reorganization disoriented many). Anything else we use must be free and open source
    • Five buckets make the top level flow
      • Vetting ideas
      • Create lesson plans + edit
      • Test
      • Combine into workshops (curricula)
      • Maintenance
      • Onboarding/Welcome wagon/who writes a lesson plan and how?

2. Inventory of what we have

  • A bit of clarifying Q&A around observations so far
    • Theme lessons are not necessarily how to develop themes that meet WP standards, they are meant to teach people how to use themes
    • WP handbook versus our team—don’t match, but we’re teaching to a simplified bar
    • To include or not include pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party lessons—there is a moratorium on them so maybe put them to the side for now
  • Observation on lack of clarity around learner levels and lack of connection to pre-requisite knowledge assets
  • Style guide says to write a script (dialogue) for the lesson plan instead of the information to cover — conversation around script v. no script
    • Verdict: we are not about scripted lessons—if you do not know what you’re doing (yet), don’t teach it!
  • Conrad suggests another section in the lesson plan template on prerequisites for the teacher as well as the learner

3. Team goals

  • Not covered today

4. Next steps

  • Conrad will continue with preliminary inventory. Should be done by Monday next week (14). Next stage is an estimated further 3 weeks
  • Aimee will continue to move forward with content flow work. Will also need to take time because of client deadlines and speaking at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. for Publishers next week
  • Other next steps rest of group can be working on:
    • How lesson plans are structured, reformulated
    • What are our goals around a usable lesson plan? (Based on experiences and insights from testing)

 

Recap for May 22, 2017 Meeting

Slack Log (Requires SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. login to view. Set one up if you don’t have a Slack account)

Special Announcement

@chanthaboune will be stepping away from the team as she’s been asked to lead a second team at work. Very special thanks to @chanthaboune for the spirit, insights, support, and contributions to this team. We appreciate everything you’ve done and will miss you (but will see you soon!).

We will need a new backup for @bethsoderberg moving forward.

Lesson Plan Updates

  • @jenwill is working on Enqueuing Scripts and Styles after a productive conversation in the Slack channel over the last week or so where the team decided to keep this plan simple, with room to expand into other plans as necessary later.
  • @donkiely is working on an updated version of the Child Themes lesson plan and it needs one more round of feedback before it heads into copyediting. Everyone is encouraged to take a look and leave their feedback in Slack.
  • We are not able to audit the lesson plans for the 4.8 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. until our issue with images not showing up in our lesson plans is fixed. We’ve submitted a ticket with systems and are waiting for a response.

Copyediting Updates

  • @mike_piercy is going through and making edits for grammar, punctuation, etc.
  • Some of the image issues were fixed last week, but not all.

Testing Updates

  • @chanthaboune tried to do a 101 workshop with the beginner lesson plans last weekend but it didn’t work out for totally unpredictable reasons.
  • @chanthaboune reports that Hack the Hood is going to use some of the theme lessons and will implement them in their summer boot camp.
  • @mikepiercy asked about database syncing in workshop settings. We had a productive conversation about how hard this is to do and outlined a few different options. You can read the whole thing at this time stamp.

Recap of April 25, 2017 Meeting

@coachwp took the lead on this meeting in @chanthaboune‘s absence, welcoming some new and returning attendees.

Lesson Plan Updates

@jenwill mentioned that she may soon be looking for feedback on the progress of the Enqueuing Scripts and Styles Lesson Plan she’s working on.

No other updates on new/assigned Lesson Plans.

 

@donkiely asked if there was any update on why the images are returning 404 errors. No-one on the meeting had any additional information and agreed to wait for an update from @chanthaboune.

@coffee2code later responded with an update: Images have to be restored and a request sits with Systems to look into it.

Copyediting Updates

@mike_piercy noticed some grammatical errors on some pages and @juliekuehl granted access edit to update.

@awakekat noticed some editing required on the Child-Theme quiz questions. @donkiely confirmed that this was marked as needing revision.

Q&A and Announcements

@juliekuehl asked if anyone knew if there was anything happening at Summit regarding Training. No-one on the meeting knew and @coachwp reverts this question back to @chanthaboune

Recap of April 18, 2017 Meeting

Lesson Plan Updates

Per @chanthaboune, these are lesson plans started but may need taking over:

  • Theme Internationalization
  • Enqueueing Scripts
  • Basic Theme Config
  • Speaker Lesson Plans
  • Finding and Using Theme Documentation
  • Theme Documentation

@donkiely gave an update on the Enqueuing Scripts and Styles lesson plan

@jenwill offered to take on completing the Enqueuing Scripts and Styles lesson plan. Yay!

@donkiely updated on his lesson plan reviews.

  • Conditional Tags – good shape, although uses theme files from Twenty Fourteen. Worth it to update those?
  • Custom Post Types – I just copyedited that in January, so it’s still good
  • CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.: Taglines – did some light copyediting, but couldn’t finish since images are broken

@chanthaboune will give @donkiely access to the spreadsheet to directly update (and expanded all the rows so that he knows just how much work he’s gotten himself into!)
Led to a quick discussion about the missing images in P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.. @chanthaboune will pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” Scott-not-@coachwp about it.

The Style Guide is updated with the “built using” item in the Teacher Notes section.

Copyediting Updates

@mike_piercy is getting into copyediting and had some questions about navigation (the Next/Previous buttons that go to parent sections, not the next lesson plan; looks like the links are broken) and Online Tutorials.

@donkiely slacked off this week

Training Updates

@coachwp had some feedback about training the Dashboard lesson plan. Went very well, and it doesn’t need any changes. Next week he’ll be doing some training on themes.

Q&A and Announcements

@chanthaboune said that the WordPress Foundation intends to do some CMS agnostic, Open SourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. trainings this year in non-US locations. The plan is to use the lesson plans we’ve created for that, so we should probably take a look at those and see that they are all up to date/ready for use. @mike_piercy offered to help with the use of non-US English.

@jenwill pointed out that there are some contradictory times listed for the weekly Tuesday meeting. @chanthaboune is on it.