Training Team 20 December 2018 Update

Slack Log

The Training Team held a video meeting to discuss the goals for the team in 2019.

There were several new contributors in attendance so we reviewed the team’s mission and how the team works before beginning.

2018 Team Goals

We reviewed the goals we had set for 2018, which included:

1. Re-create team handbook
2. Move lesson plans 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/
3. Restructure make.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//training
4. Fix broken images
5. Update lesson plans for 4.8-4.9/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/
6. Make workshop recommendations
7. AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) workshop

2018 Team Accomplishments

We had accomplished several of those goals and a few more this past year. A quick summary includes:

1. Re-create team handbook (expected by the end of the year)

2. Move lesson plans to GitHub

3. Restructure make.wordpress.org/training

4. Fix broken images (perhaps not all are fixed, but moving to GitHub addressed the problem)

5. Make workshop recommendations

plus

6. On-boarding improvements including a PDF and videos

7. Team management on 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. and in Waffle.io

8. Creation of the https://wptrainingteam.github.io/ page

9. Work towards the relaunch of the learn.wordpress.org site including collaboration with the #design, #marketing, and #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. teams.

Goals that we didn’t quite accomplish include:

1. Update lesson plans for Gutenberg

2. Accessibility workshop

2019 Team Goals

So turning towards setting goals for 2019, there was discussion about needing more contributor on-boarding videos on our YouTube channel (thanks @fahim!), and @courtneyengle suggested we make plans now for maintaining our lesson plans such as tagging them in GitHub with things such as WordPress version and whether there are screenshots.

We also talked about some specific lesson plans that we would like to develop in the new year such as a focus on Gutenberg and accessibility and lesson plans about plugins.

The team is excited about launching the learn.wordpress.org site in 2019 and the possibilities that will bring! We should have a complete list of team goals available on our Trello board soon.

Next meeting 3 January 2019 at 1930 UTC.

Training Team Update – 10 May 2018

Meeeting held at 19:30 UTC in the #training 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/. channel

https://wordpress.slack.com/archives/C02RW657Q/p1525980606000637

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/. materials

The Marketing team helped us out and created an on boarding PDF that we can use as a “handout” (paper or electronic) during Contributor Days to help them get started with all the accounts that are needed to participate. That led to creating a list of more comprehensive information that can help new people get started with the team. While built to help for Contributor Days, it’s going to be useful for anyone who wants to join the team.

Slides – Shower

Just a reiteration that Shower (Show-er https://github.com/wptrainingteam/shower) has replaced Reveal.js as the team’s solution for slides. There’s still a bit of testing to be done to finalize exactly how the file structure will work. Once that is determined videos and documentation on how to add slides to lesson plans will be created.

Learn site

The next step in getting 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/ site moving forward is to create a TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket and ask for assistance from the #meta, #design, and #marketing teams. It is expected to take months to work through that process.

Team survey

With many new faces on the team it was requested that folks complete a survey to gather information regarding their skills and interests and how they want to get involved with contributing.

Trello board update – slight change to workflow

A new list has been added to 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. board representing a new step in the workflow. The “Lesson Plans Needing Instructional Review” step has been added after drafting and before copyediting to represent a QA step for instructional quality and consistency.

Lesson plans needing volunteers (see the “User Plans Ready for Drafting” list in Trello

Just a reminder that there are several lesson plans in need of writing that are available for people to work on.

Open announcements / discussion

Next week’s meeting will be 30 minutes earlier, as an experiment, so 19:00 UTC in the #training Slack channel

Meta Team Update: November 7, 2013

Over the last week:

  • Devhub work is still ongoing, slowly. The docs team is working to get a better grip on the handbooks so we can bring them over. Outside of that, @krogsgard is working on themes for the code reference and the handbooks.
  • Mockups for the Docs Issue Tracker are up for feedback. Planning to compile that feedback and give it back to @karmatosed so she can wrap up the design phase and we can start on implementations.
  • GSoC profiles are still pending, but getting close to being wrapped up.

For the coming week:

  • Devhub: Hope to have a better grasp on the handbooks and a theme built for the code reference.
  • Docs Issue Tracker: Compile feedback and get final designs ready for development.
  • GSoC Profile Integration: Pending any problems, hopefully most of this work will be live.

 

#meta

Meta Team Update: November 1, 2013

Been a while since the last 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 update (sorry!). Here are some things that’ve happened:

And here’s what’s upcoming:

  • More devhub work. We’re hoping to get handbooks live in the next couple of weeks, but that’s dependent on the designs mostly.
  • Docs Issue Tracker mockups on Monday for feedback from the Docs team.
  • GSoC Profiles integration into profiles.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/. Target is to have some of it live next week and the rest not long after.
  • I’ve started work on a spec for profiles and intend to post it piecemeal (per team) in the next week or two. We intend this to be one of the next projects to start on.

Otherwise, I’ll do better about posting weekly on Thursdays (oh, is it Friday already?).

#meta

Meta Team Update: September 12

A few things currently in progress, but no major news to report. Here’s where we’re at for various projects:

  • make.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/: A spec is almost ready to be published. Meanwhile, work continues. We’re bringing in @krogsgard to help with on the development side.
  • developer.wordpress.org (devhub): Weekly meetings are starting next week. Some design work has been done for the handbooks, though more remains. We still need developers interested in contributing to the code reference to pop in and own some tickets. The 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 developer handbook needs an editor to push it forward.
  • Documentation Issue Tracker: I posted a spec for an issue tracker yesterday and would love some feedback on it. Next up will be creating some basic designs for it. If you’re an interested designer, let us know.

Outside of that, there’s also work being done to integrate @merty’s GSoC profile improvements, which should be done soon.

There are still pending questions for the plugin, support, and accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) teams, as mentioned last week.

#meta

Meta Team Update: September 5

There wasn’t much to report last week, so I didn’t do an update. Over the past two weeks, we did quite a bit of triage of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets. The list of 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. tickets in the core trac is now down to 19 open tickets, with a few that need to be migrated still and a few that will end their lives on in core trac.

Beyond that, work is continuing on both developer.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/ and the make.wordpress.org homepage, with some development done on each.

On the dev.wp.org front, the code reference is in alpha mode now, courtesy @nacin (e.g., wp_insert_post()), and will need more development and design work going forward. I’ve filed a number of tickets based on @nacin‘s list of “what’s next” so we can move forward. All of those items need help (code so far is viewable here). Meanwhile, designs are being drawn up by @saracannon for the main developer.wordpress.org homepage as well as the handbooks.

For the make.wordpress.org homepage, some work was started between @jenmylo, @georgestephanis, and @otto42 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. Birmingham two weekends ago. We’re still working on getting a specification up for comment, but that should come soon.

Outside of those things, the following meta tickets need feedback from the following teams. Note that some already have comments, but could always use more discussion at team meetings:

In general, we recommend teams follow their related components. For example, the support team should follow tickets filed in the Support Forums component. The plugin team should follow tickets filed in the Plugins Directory component. Let me know if I can help you find tickets for your team.

#meta

Meta Team Update: August 22

Thanks to a design from @melchoyce, code from @iandunn, and review and deployment from @otto42, we shipped a new global footer! There’s a few bugs to fix with it. If you notice anything (other than the display issues on the make P2s), file a meta trac ticket and let us know.

That’s not all, we also re-launched jobs.wordpress.net, with a brand new design courtesy @melchoyce, development and deployment from @coffee2code, and a brand new moderation duo, @mercime and @chriswiegman. Our new moderation duo will be pushing the site forward with proposed changes and design improvements where needed (like making the site responsive). If there are things you’re interested in helping with or issues you see, file a ticket or let them know.

Speaking of our new jobs.wordpress.net duo, we’ve officially added them to our 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 and posted a page listing team members. There might be people left off (I’m still new!), just let me know and I’ll add them.

As a smaller team, we don’t have regular meetings, but a number of us met this week to do some ticket triage and agreed to keep our current two team reps for this next period. I’ll be team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. with @otto42 as my backup.

During our ticket triage, we went through about half of the open WordPress.org tickets on the core trac, closing a number of them and migrating others over to the meta tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. There’s a few tickets that need follow up from me, but we hope to get that number down to 0 in the not-too-distant future, with all our tickets on the meta trac.

For this coming week: work on developer.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/ is progressing, a spec for make.wordpress.org should be live, work on make.wordpress.org will be starting up, and we’ll probably do some more ticket triage.

Outstanding issues:

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 team: We need feedback on improving the plugin dev FAQ. Do you want to publish that more broadly?

#meta

Meta Team Update: August 15

The improved footer received review and needs a few changes before going live. Some tickets were also filed to clean up some of our CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site..

I also posted the project queue this week and worked with @siobhan to publish a developer.wordpress.org spec. Comments on both are greatly appreciated. The queue will be incorporating the wordcamp.org projects in the not-too-distant future too.

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 team: We need feedback on improving the plugin dev FAQ. Should that be published more broadly?

#meta

Meta Team Update: August 8

Not much to report this week.

The improved global footer is on the way courtesy @iandunn (patch in the ticket) and should be live by next week’s update. Additionally, we have a volunteer to work on making wordpress.org responsive. Others interested should gather in that ticket and start work. Most of the CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. should be 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. and ready to be worked on.

Finally, the project queue is coming along and should actually be ready next week.

#meta

Meta Team Update: August 1

The 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/. saw quite a few new tickets filed in the 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/ (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.) trac. Some of them were fixed, but because large parts of wordpress.org aren’t 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., there wasn’t much help by way of patches; most work was done by @otto42 and @coffee2code. During the contributor day, @devinreams also added a list of the many things our team is responsible for to the homepage of trac.

As we start using our tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. instance more, we’ll need help from other teams on specific tasks. This week we identified a couple design changes needed for our associated sites. One of them was completed (see below)! The needs-ui keyword will show what changes we’ll need, as seen in this query.

There was also a proposal for a new global footer across wordpress.org that was planned out by @devinreams and myself, mocked up by @melchoyce, approved by @matt, and is now in the hands of @iandunn for implementation.

This week, we also started a new IRC channel (#wordpress-meta) as a place for community to come chat about all things wordpress.org. It might not get used much now, but as our team grows, hopefully it’ll help.

For this coming week, I’m hoping to update the project queue on our meta 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 provide a better tool for tracking current projects.

#meta