Archives

Jen 6:04 pm on June 20, 2014
Tags: ,   

Team Meetup at WCSF (More)

Hi again! We’re working on making sure we have enough room blocks to make sure all the contributors who are coming in October can get a decent rate (or have a room provided by us if needed). Some of you replied to my post from last week and filled in the survey so I’d know you were planning to come, but some haven’t. Additionally, some people did the survey and marked themselves as team members of teams they’re not actually involved with, so I need your help! 🙂

I just want to make sure we count everyone so we can try to put you at the same hotel to make the 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. part easier (though I know most people on this team are also heavily involved in other teams, so we’ll figure that once we have a solid tally of who’s planning to come at all).

If you didn’t read the post before, the plan for the event is:
Sat/Sun — WCSF conference
Monday — community summit
Tues/Wed — team meetups (team being together to talk issues, make plans, work together, etc)

The people who identified themselves as active members of the docs team in the survey are: @jerrysarcastic, @drewapicture, @trishasalas, @topher1kenobe, @hanni, @kpdesign, @nicolealleyinteractivecom, @davidjlaietta, @jazzs3quence, @sewmyheadon, @siobhan, @otto42 (all authors on this team blog), as well as:
Cousett Hoover, Benjamin Hansen, John Blackbourn, Ed Caissie, and Russell Fair.

Is this an accurate list? @kpdesign, can you let me know if these folks are all active with the docs team, and also tell me if there’s anyone missing that you think should be there from the team? Comment here, email me, hit me in irc, whatever’s easiest.

Any docs folks not listed above who are active on the team and want to come to the team meetup should fill out the survey so I can have you on the list as we start deciding which hotels to put each team in. We’ll be spread out among 4 or 5 hotels, so I want to be sure we can keep the teams together.

And just a reminder that we have a travel assistance program this year to help contributors who don’t work for a wp-based company and can’t cover travel costs on their own. Apply for travel assistance by June 30 Applications for travel assistance are now closed. If you need help, contact @jenmylo.

Thanks!

#meetup, #wcsf2014

Kim Parsell 1:19 pm on March 16, 2014
Tags:   

Docs Chat: Mar. 13, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: Work continues on fixing parser-related issues. @samuelsidler said volunteers are still needed to help with the handbook theme. If you would like to work on the project, leave a comment on this post, or come to the weekly IRC chat on Tuesdays at 16:00 UTC.

2. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.: There are some big changes, and a new direction, for both the team and the project. The new co-leads are @trishasalas and @Clorith. @jazzs3quence will still be involved in the project in a supportive role. Their weekly meeting on 3/10/2014 was used to discuss the Feature PluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. Meeting, and the feedback @jazzs3quence received regarding the current implementation of 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. They also began laying the groundwork for the new direction the project will take. If you would like to be part of the effort, please attend the weekly IRC chat on Mondays at 18:30 UTC.

3. Handbooks: @sewmyheadon and @hanni met on Wednesday to discuss the current status of the handbooks. @philiparthurmoore has made progress on the Theme Developer Handbook intro. @sewmyheadon still needs to review it.

4. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Style Guide: The team discussed a post that proposed a community-written (and maintained) style guide for WordPress Core to follow. The consensus was that WordPress has its own voice, and there are places where that voice could probably be refined a bit. A WordPress Core style guide could be written, but it would be a canonical reference rather than a community-driven guide.

5. New 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/ Profiles: @jenmylo reached out to the team reps a few weeks ago about identifying people in each team to get badges on the new profiles that are being worked on. At some point they hope that the process may be automated, but for now, the profile badges will be manually added. I have already provided a preliminary list of names of team members.

6. In-House Mentorship Program: @DrewAPicture and I talked to @jenmylo and @andreamiddleton about the program 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. Phoenix in January. They hope to kick off the one-month ‘contributor onramp’ within the coming month. The team discussed what the requirements are, what tasks we could have someone work on for the one-month contributor onramp, and possible mentors.

7. Group Chats Calendar for WordPress Project: @GaryJ brought up the idea in IRC for a group chats calendar that people could subscribe to. @siobhan said this would be a project for 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, if a decision was made to implement one. Concern was expressed that, without a maintainer, the calendar could end up with incorrect information listed. The consensus was that the chat times listed 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. for each of the Make blogs should be sufficient for now.

#chat-recap

Kim Parsell 6:14 am on March 1, 2014
Tags:   

Docs Chat: Feb. 27, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: @Rarst is working on fixing parser-related issues. @nlarnold1 is working on resolving issues with the handbook theme. (2/26/2014 team meeting summary)

2. Docs Issue Tracker: @otto42 unveiled the alpha version of the issue tracker earlier this week. The Docs team is providing feedback, and work continues to implement those suggestions.

3. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.: @jazzs3quence said there were some minor UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. fixes merged in this past week, and work continues on refactoring the overview. Current needs are writers to assist with tooltip creation, and people to test the plugin, and provide feedback. (2/24/2014 team meeting summary)

4. Docs Project Landing Pages: The landing pages are now complete for all four projects: Codex, Devhub, Handbooks, and Inline Docs.

5. Handbooks: Good progress was made on 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. The new outline is finished, and @hanni and @blobaugh completed migrating the existing content into the new structure. @sewmyheadon and @philiparthurmoore will be working together to get the intro completed for the Theme Developer Handbook, and begin work on the new outline. (2/27/2014 team meeting summary)

6. Contributor Events: There are two contributor events happening this weekend: the Monthly Docs Sprint at the Seattle WordPress 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. group, and the WP Contributor Day in the UK. Both events are on Saturday, March 1. If you aren’t located near either event, you can join in via the #wordpress-sfd IRC channel, and participate virtually.

#chat-recap

hanni 1:04 pm on February 27, 2014
Tags: ,   

Handbooks Chat: 27th Feb

Present: @blobaugh, @caseydriscoll, @hanni, @NikV @philiparthurmoore,and @sams.

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

The revised outline proposal was finalised last week by @blobaugh and @hanni, who are this week working on getting the content copied over from the “old” to new structure. If you take a look at the handbook you’ll see this is well underway, and we’re hoping to complete the merge in-time for the sprint.

A backup was taken of all content prior to starting this, so as to be able to “revert” in case of disaster, and also to allow the restoration the proper metadata for each and every contributors to each section when appropriate.

The structure can be seen here: https://docs.google.com/spreadsheet/ccc?key=0Ak0ISjkNpXRIdHRVSDlFOWlBakYwRnNJZV9rbDIyOHc&usp=sharing#gid=0

The first section is very much in draft form, and is intended to be written by a couple of folks going through the process of writing their own plugin (including @hanni), so no-one should be alarmed by the apparently bizarre state at present.

Note: until we’ve ported the numbers etc. we’ll not replace the link in either the spiffy new nav or 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., so as not to confuse. This also motivates us to get it finished in time for this weekend’s Docs Sprint. Whilst the sprint is based in Seattle, everyone is welcome to participate, wherever they are.

Admin-wise, @blobaugh is leaving for a trip to Uganda on the 5th March, and will return on the 21st. As such, Ben is eager to get things in tip-top shape prior to his departure.

During @blobaugh‘s trip, @hanni will be the point of contact for the Plugin Developer Handbook.

2. Theme Developer Handbook

Due to travel, Theme Developer Handbook Editor @sewmyheadon was unable to make this week’s meeting, so @hanni attempted to fill his shoes for the day.

@philiparthurmoore kindly joined to help kick-off the effort to integrate some of the fantastic themeshaper.net content. As per previous recent handbook discussions, focus for the Theme Developer Handbook is very much on stage (i).

To this end, over the next couple of weeks @philiparthurmore will be working on an initial one page summary distilling the themeshaper content down to the basics of getting from zero to your first theme, upon which we can then expand as necessary.

He’ll have an outline ready for the Docs Sprint on March 1st, such that any folks present can see where things are going and lend a hand if they so desire.

If anyone else is interested in helping with this, please do leave a comment here or 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.” Philip, Eric, or myself.

Thanks again everyone!

#handbook-chat, #handbooks

Samuel Wood (Otto) 9:57 pm on February 25, 2014
Tags:   

Docs issue tracker

Okay, so the preliminary version of the Docs Issue Tracker is up. Here’s a quick rundown on how it works.

Note: I fully expect it to be slightly buggy at first. 🙂

The issue list can be seen at https://make.wordpress.org/docs/issues/ . You will need to be logged in and also an editor on this make-site to do anything useful here. The dropdown menu on the right is the action menu. You can “accept” an issue, “close” an issue, or “reopen” a closed issue. Again, preliminary, this can be expanded later if needed.

Issue submission can be done at https://make.wordpress.org/docs/issue/submit/ . You will need to be logged in, and when you visit this page, it will force you to do so if you’re not already.

However, it will be the case that we link to this page from other places on the WordPress.org website. I put a link on my Codex page so you can see how this works: https://codex.wordpress.org/User:Otto42

When you click to that submit form from somewhere else, it auto-grabs where you linked here from, and fills in the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org of the problem. There is some sanity and safety checking here, so it won’t work for all links from everywhere. Also note that the link to /issue/submit should always be httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information., because of referer restrictions when going from https sites to non-https sites. Based on the URL, the location information on the ticket is filled in and so forth.

I know it’s not quite the prettiest. Sorry. HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites./CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. suggestions are welcome. Also, pagination is there, just not displayed until there’s more issues. Currently it’s the default of ten per page, I’ll increase that eventually.

Things missing:

  • Stats
  • Re-ordering by status
  • Probably some other stuff

Again, this is a starting point. Things can be added to it, as needed.

Also, please don’t add “test” issues. I’ll do the testing. If you have real issues, feel free to add those. 🙂

#issue-tracker

Kim Parsell 11:59 am on February 22, 2014
Tags:   

Docs Chat: Feb. 20, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: Progress continues. Most of the template work for the code reference is done for the moment. @Rarst now has commit access to the parser repo, and will be working on changes needed for parsing the inline docs. @nlarnold1 is working on resolving issues with the handbook theme.

2. Docs Issue Tracker: @samuelsidler said we should have an initial version soon.

3. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.: Per @jazzs3quence, @brainfork will be working on redoing the help overviews due to a display issue. Work continues on adding tooltips. Version 0.6 was released Thursday – please test and provide feedback to the team. (2/17/2014 team meeting summary)

4. Docs Project Landing Pages: Landing pages were created for the Codex, DevHub, and Handbooks projects. The Code Reference falls under DevHub, and will be included there. @siobhan will be adding information to the DevHub landing page, and @hanni will be populating the Handbooks landing page.

I’ll be pulling together a to-do list of outstanding Codex tasks to include in the Codex section. We also need to look at putting together a list of Codex updates needed for the 3.9 release in mid-April.

5. Handbooks: @hanni posted the detailed plans for the Handbooks project this week.

There is now a weekly IRC chat for the Handbooks team – Thursday at 1:00 UTC (5pm PST, 6pm MST, 8pm EST on Wednesday) in #wordpress-sfd. The team held their first meeting on 2/19/2014.

@blobaugh is the new editor of 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, and is working with @hanni on a revised outline. There are also several new contributors eager to get started writing.

@sewmyheadon is the editor of the Theme Developer Handbook, and will be working with new contributors @philiparthurmoore and @nudge to move that handbook toward completion.

More contributors are needed for the Theme Developer Handbook, so if you are interested in helping, contact @sewmyheadon or @hanni via IRC, attend the weekly meeting on Wednesdays, or leave a comment on this post.

#chat-recap

hanni 12:13 am on February 21, 2014
Tags:   

Handbooks Chat: 19th Feb 2014

@sewmyheadon, @blobaugh, and, @hanni had our first checkin yesterday.

  1. Stated utility and purpose of the meetings: to support each other as far as possible, and ensure we’re all the right track with regards to the goals of the handbooks, focusing on incremental progress rather than becoming bogged down with concern over current timeline.
    @hanni’s purpose to allow each editor to focus on their handbook whilst watching for potential problems or unwanted divergences, reviewing diffs on an at least weekly basis and helping out with editing when and as she can.
  2. Agreed on the provisional contents the reference portion of 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 cut up by @blobaugh and @hanni).
  3. Started on new spreadsheet for the Plugin Developer Handbook to reflect structure update and porting of existing content (links forthcoming).
  4. @sewmyheadon will be meeting with @philiparthurmoore to integrate the ThemeShaper tutorials and restructure Theme Developer Handbook as needed over the next ten days or so.
  5. Welcomed new contributor @lorax who’ll be attending the docs chat today to get involved!

#handbook-chat

hanni 5:14 pm on February 18, 2014
Tags:   

Weekly Handbooks Check-in

It’s time to get back on the handbook bandwagon, folks!

We’re starting a weekly check-in meeting between those responsible for the progress of a number of the handbooks, @hanni (general helper), @sewmyheadon (editor of the Theme Developer Handbook), and @blobaugh (editor of 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), and anyone else who is both interested in the progress of the above, and wishes to find out more about getting involved.

The goal of this status meeting is to ensure that we’re keeping an eye on content coming in, making the requisite progress (here’s to getting back the momentum we lost!), doing all we can to support both current, and potential contributors. Most importantly, we want to keep the outlines of the handbooks on track to meet the common goals of outlining the process to build both a theme and plugin for those newer to the process, whilst also providing an appropriate level of reference for those familiar more familiar with theme and plugin development. More to come on this subject.

Please feel free to join, it’ll be in #wordpress-sfd at 5PM Pacific, every Wednesday. Open to all!

#handbooks

Kim Parsell 4:46 am on February 15, 2014
Tags:   

Docs Chat: Feb. 13, 2014

Thank you to everyone who came. For anyone unable to attend, you can read the logs here.

The following is a summary of the topics that were discussed.

1. DevHub: There’s been a lot of activity on the 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/ 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. TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets this past week, primarily by @Rarst and @nlarnold1. Good progress is being made on the design change tickets.

2. Docs Issue Tracker: Per @samuelsidler, @Otto42 is still working on it, and making progress.

During our initial discussions about what we would like to see in the issue tracker, several things were mentioned that aren’t included in initial development. I’ll be working through those posts, gathering a list of those items and posting that list, most likely in a Meta Trac ticket. We can review the list after development is complete, and we’ve been using the tracker for awhile to see what items we may still want to add.

3. AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.: Per @jazzs3quence, the team has removed the use of title attributes from 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, based on @grahamarmfield‘s extensive 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) review of the plugin, and the fact that those attributes are being removed from coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Version 0.6 of the plugin has been released, incorporating those recommendations, and is available in the repo. Please download the plugin, test, and provide feedback to the team. (2/10/2014 team meeting summary)

4. Handbooks: @hanni provided an extensive update on the status of the handbooks, and the plans now being put in place to move the effort forward at a much faster pace. @hanni will be posting the details of these plans early next week.

We also discussed the status of handbooks being produced by the other teams. @netweb brought up a post on Make/Polyglots regarding their Handbook. If you are interested in helping write the Polyglots handbook, @samuelsidler will be posting on Make/Polyglots asking for volunteers.

5. First Steps for Docs Contributors: We received some very helpful feedback from the comments, and changes have been made to incorporate that feedback. If you have not had the chance to review it, please take the time to do so, and leave your feedback so we can get this completed. (original post | draft page)

6. Docs Project Landing Pages: I’ll be creating the landing pages for each of the listed projects this weekend so that each team can begin adding the information about their respective projects. The Inline Docs landing page is a good example to follow. We would like to have these completed by February 28th.

We would also like to thank our outgoing 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., @sewmyheadon, for all of his hard work. We look forward to your continued contributions. 🙂

#chat-recap

Eric Amundson 1:19 am on January 15, 2014
Tags:   

Docs Meetup Roundup – Jan 9, 2014

1. DevHub

Things are getting back in gear and progress is being made 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/.

2. Docs Issue Tracker

Still pending because of the Holidays, but Otto’s planning to work on it soon, if he’s not already.

3. Inline Docs

@DrewAPicture and @kimparsell will be working on inline docs 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. Phoenix.

4. Docs Meetups

Going back to once a month. Next meetup is Feb 1.

5. AH-O2

The Admin Help (AH-O2) project now has an AH-O2 plugin in the repo for testing.

Also @jazzsequence would like help figuring out the content portion of the Admin Help.

Join the AH-O2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. project:

6. Docs Project Landing Pages

We discussed having landing pages for each docs-related project in December and @siobhan posted about First Steps for Contributors.

Ideally, it would be nice to have make.wordpress.org/docs link to landing pages for each sub-project that each give an overview of the project and tell contributors all they need to know to get involved.

Full IRC logs

#chat-recap