Title: Goals for 2017
Author: Josepha
Published: January 3, 2017

---

 [  ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
10:28 pm _on_ January 3, 2017     
Tags: [goals ( 5 )](https://make.wordpress.org/training/tag/goals/)

# Goals for 2017

In 2016 we had a pretty clear goal set out for us. We haven’t had any discussions
about goals for 2017, though, so now is the time!

Does anyone have something they would like to see from or for the team this year?
Put your thoughts in the comments below and we’ll prioritize everything in the coming
weeks!

[#goals](https://make.wordpress.org/training/tag/goals/)

### Share this:

 * [  Threads ](https://make.wordpress.org/training/2017/01/03/goals-for-2017/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/training/2017/01/03/goals-for-2017/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/training/2017/01/03/goals-for-2017/?share=bluesky)
 * [  Facebook ](https://make.wordpress.org/training/2017/01/03/goals-for-2017/?share=facebook)
 * [  X ](https://make.wordpress.org/training/2017/01/03/goals-for-2017/?share=x)
 * [  LinkedIn ](https://make.wordpress.org/training/2017/01/03/goals-for-2017/?share=linkedin)

 * [Login to Reply](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2017%2F01%2F03%2Fgoals-for-2017%2F%23respond&locale=en_US)

 1.  Pingback: [Team Updates — WordPress](https://make.wordpress.org/updates/2017/01/06/training-team-updates-for-january-6-2016/)
 2.  ![](https://secure.gravatar.com/avatar/19aaaab5b8bd4e69e658865958076e39950c4162f5f884ef9bcda3bed3f8e010?
     s=32&d=mm&r=g)
 3.   [bethsoderberg](https://profiles.wordpress.org/bethsoderberg/)  2:37 pm _on_ 
     January 6, 2017
 4.  Aggregating the comments from this week’s meeting and elsewhere so they are attached
     to this post!
 5.  From our 1/3 meeting:
      @juliekuehl would love to see a content audit/edit flow
     solution finalized @bethsoderberg would love to get copyediting back on track @
     chanthaboune and @bethsoderberg would like ot see proper handbook @chanthaboune
     suggests that we all find groups in our local community who would benefit from
     these lessons
 6.  From @wpaleks: [https://make.wordpress.org/training/2017/01/05/hi-and-happy-new-year-to-all-team/](https://make.wordpress.org/training/2017/01/05/hi-and-happy-new-year-to-all-team/)
 7.   * ![](https://secure.gravatar.com/avatar/113970402caff1fe19232f4325219fd415b3f23aebd6ef59710f1abafbe4bbe6?
        s=32&d=mm&r=g)
      *  [estes.chris](https://profiles.wordpress.org/esteschris/)  2:12 pm _on_ January
        11, 2017
      * I too would like to see a content flow solution, preferably with an overview
        dashboard. I think we spend much of our weekly meeting on items that would 
        be automatically tracked if we had one. It could also help during major updates
        to WP if we had a ‘needs update’ checkbox rather making a list or guessing 
        based on what we know about each new release.
      * My big dream would be cohesiveness running through each section so that LPs
        could be used in logical blocks without any abruptness moving from one to the
        other. And I know the resources for that are not available right now.
 8.  ![](https://secure.gravatar.com/avatar/ef9d69890797099d4cf9277e83c067770497440a012fad4694ce8e0fec834fe3?
     s=32&d=mm&r=g)
 9.   [skarjune](https://profiles.wordpress.org/skarjune/)  1:47 am _on_ February 1,
     2017
 10. These goals were presented at the 1/31/2017 meeting for a
      Discussion of Yearly
     Goals: 1. Content flow solution 2. More solid copyediting process (ties into 1)
     3. Proper handbook (ties to 1 + 2) 4. Outreach to local groups 5. An 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
 11. As [@juliekuehl](https://profiles.wordpress.org/juliekuehl/) & [@esteschris](https://profiles.wordpress.org/esteschris/)
     have commented, I agree that Goal 1 is critical and supports other goals. While
     we’ve had good tracking in Google Sheets, and most feel that it’s necessary but
     cumbersome to navigate and maintain.
      Moving tracking to 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.](https://trello.com/b/8UGHVBu8/wp-marketing)
     might offer a streamlined interface, and it’s a nice overall project management
     tool, but it’s not an editorial workflow tool and does not integrate with the 
     editing process, which is an objective we want to meet. The option of integrating
     Edit Flow is basically an “Eat your own dogfood” solution, and if we are not able
     to implement that at 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/](https://wordpress.org/),
     we need to understand the issue.

### Leave a Reply 󠀁[Cancel reply](https://make.wordpress.org/training/2017/01/03/goals-for-2017/?output_format=md#respond)󠁿

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Ftraining%2F2017%2F01%2F03%2Fgoals-for-2017%2F&locale=en_US)
to post a comment.

This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/)

# Post navigation

[← Recap of January 3, 2017 Meeting](https://make.wordpress.org/training/2017/01/03/recap-of-january-3-2017-meeting/)

[Hi and Happy New Year to all team… →](https://make.wordpress.org/training/2017/01/05/hi-and-happy-new-year-to-all-team/)