Looking for feedback: Updates to GitHub issue templates and labels

Summary: In an effort to streamline the team’s GitHub repo, the Next steps for GitHub updates project is looking to reduce the number of GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ issue templates in the repo from 9 to 5. The project is also looking for input as the current list of 119 labels is reassessed and reduced. Please leave your feedback on the proposed changes by October 17th (Tuesday).

Please review the new list of GitHub issue templates

In an effort to streamline the team’s GitHub repo, the Next steps for GitHub updates project has identified a need to reduce the number of GitHub issue templates. The expected benefits from this change include:

  • Less confusion for contributors creating new issues.
  • Less redundancy during topic vetting. (Currently, Subject Matter Experts (SMEs) must vet the same topic for multiple content types.) 
  • Reduction in quantity and complexity of automations that will get set up.
  • Preparation for the consolidation of content types, as proposed in Looking for Feedback: Learn Website Information Architecture.

Below is a table listing the current 9 issue templates, and the 5 proposed templates they’ll correspond to. Each of the new templates have already been created and can be previewed from https://github.com/WordPress/Learn/issues/new/choose. (Scroll to the bottom of the list, and you’ll see these new templates prefaced with “_do-not-use_”.) Please leave any questions, suggestions, or other comments about these templates below.

Current issue templatesProposed issue templates
Bug Report Template
Content Feedback
Feedback
Topic IdeaContent Development (general)
Lesson Plan Template
Tutorial Template
Online Workshop Template
Course Template
Content Development (for Faculty)
Content Translation TemplateContent Translation
Meeting Agenda TemplateMeeting Agenda

Some points to note in these changes:

  • All feedback pertaining to Learn WordPress, regardless of whether it is regarding the website itself or the content, will be submitted in one issue. Automation similar to what the Docs team has will be set up, allowing any contributor (regardless of GitHub access) to triage and send these to their respective projects where they’ll be actioned on.
  • The current “Topic Idea” template will be renamed to clarify this is actually the issue content creators should use when creating content. These issues will be highlighted to SMEs to be prioritized in their topic vetting process.
  • Faculty who will immediately create content themselves may skip the vetting process. The four content templates the repo currently have are designed for this process, but weren’t labeled as such, and were therefore confusing general contributors. These will be consolidated into a single template marked “for faculty”. Automation similar to what the Docs team has will be set up, allowing Faculty to call the respective development checklist for their content type with a command.

Help us review the current list of GitHub labels

The project has exported the current list of GitHub labels into this Google Spreadsheet. We’re looking for Training Team contributors with experience in labeling issues in the team’s repo to help us document the purpose of each label.

Once completed, the project will:

  • Reassess labels based on their current use.
    • Similar labels may be consolidated.
    • Labels may be renamed for clarity.
    • Some project-specific labels may be replaced with custom fields.
  • Document the purpose of each label in the handbook.
    • Documentation will also include how new labels should be added and which labels are used in automation and, therefore, should not be modified.

Thank you for your feedback!

We’re looking for feedback on the proposed changes to issue templates and documentation regarding the repo’s current list of labels, by October 17th (Tuesday).


@webtechpooja and @jominney were co-authors of this post. Thanks also go to @yuli-yang for exporting the list of GitHub labels for the project!

#feedback, #github

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

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

Recap of August 4, 2015 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 recap of last meeting
  2. Recap of Slides Meeting
  3. Lesson plans status and questions
  4. Testing status and questions
  5. Status of abandoned plans
    1. Notify @bethsoderberg or @abuango of lesson plans missing from spreadsheet or status of lesson plans assigned to you. Current lesson plans out reviewed by @abuango and confirmations sought.
    2. Discussion to be announced later on what lesson plans could be connected together to conduct workshops.
  6. 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. Contributor Days onboarding
  7. Lesson Plan continuity with WordPress updates
    1. When do we start tracking?
      1. Concern about lesson plans not approved but being initially tested matching up with the current version of what instructors and students may be using
    2. How and who will do the updating of content?
    3. Review @juliekuehl’s request for content audit plugin.  Further discussion at August 18th meeting.
  8. Alternate weekly discussions between Slides and Content Audit

#content-audit, #contributor-days, #feedback, #procedures, #slides

Meeting Recap – September 9 2014

This week @courtneydawn had to leave at the last minute and foolishly wisely left me in charge of the meeting. Henceforth I shall refer to myself in the 3rd person, just to make writing this post extra awkward. 🙂

  • Template Hierarchy: @coachbirgit has had trouble getting to this, but will be able to devote some time to it next week
  • Intro to CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site.: @jerrysarcastic has added the quiz, sample XML import file, and made a few edits, and @meaganhanes has also edited the module. This is now READY TO TEST but @jerrysarcastic will not be able to pick it up until October. To keep things moving along, anyone is welcome to do a test run at their local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. and offer feedback on how things went.
  • Widgeted Spaces @bethsoderberg created a stub for this new module in progress, yay! \o/
  • Post Formats: @courane01 reports that she is close to done with this module, but has run into a small issue where “post format video code interferes with the post format chat code, resulting in [the] sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. on the chat layout not being where they should.” and is working to resolve this issue before finalizing.

Opening up Testing to Meetups

Some time was spent talking about ways of letting local WordPress Meetups know that there are modules available for testing as a way to jump start this part of finalizing our curricula for these workshops. One thought that needs to be followed up on is possible connecting with Meetups that are on the Foundation Meetup account.

You can read all the fascinating details in the logs and anything if you would like to add anything, the comment form awaits!

#feedback