The Make Marketing team is currently inactive. Work on the WordPress Showcase remains open to contributions, and marketing amplification requests can be made via 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 by the repository owner. https://github.com/. For those with marketing talents, we currently recommend connecting with the Community team to promote WordPress events or with one of the many other Make teams. For any other ideas or discussions unrelated to these contributing areas, you can use the GitHub discussion area or Make Slack.
Marketing Team Contributor Day Recap from #WCABQ
The marketing team participated in WordCamp Albuquerque’s Contributor Day on Sunday 1/21/2018. The main focus for the camp was working on “Navigating TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. guide for new people core.trac.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/.”
Team members present: @mcdwayne, @Kitty, @angela, @heatherm
Trac Quick Start Guide
The main focus for the camp was working on “Navigating Trac guide for new people core.trac.wordpress.org.”
@mcdwayne and @Kitty took on the task of turning @flixos90’s presentation of beginning use of Trac into a Google Doc.
Meanwhile @angela attended the ‘getting started as a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributor’ session and took notes of the general overview she received for Trac.
@Kitty worked out an outline for a new user guide, including minimum criteria for the intended guide user, which was discussed in depth by the rest of the team over lunch resulting in this document.
After debating the merits and disadvantages of a single doc for both outline and draft vs using a second dedicated doc for the drafting of the guide itself, only to find ourselves equally divided on preferred approach. We flipped a coin and went with the 2 document approach.
It was a very good day.