-
Notifications
You must be signed in to change notification settings - Fork 14
Meeting Notes
Randy Hicks edited this page Oct 14, 2015
·
4 revisions
- hangout: Brett, Josiah, Randy
- Update core boilerplate with current functionality
- Do a quick transition don't get crazy refactoring yet, that will happen later
- The goal of this first pass is to translate to the new code format and get it running
- Create issues from each section from the Initial-Plugin-Structure wiki page
- https://github.com/brettshumaker/Staff-List-Plugin/wiki/Initial-Plugin-Structure
- Use issue tracker to assign sections to ourselves
- Using dev-master as root branch
- Use the issue number in your branch and git-hub will recognize that when merging
- Create issues for each section within the Initial Plugin Structure page
- Assign yourself one area to translate and assign the yourself the issue
- Use GitHub Flow for branching
- hangout: Brett, Josiah, Randy
- https://github.com/brettshumaker/Staff-List-Plugin/
- https://github.com/DevinVinson/WordPress-Plugin-Boilerplate/
- https://guides.github.com/introduction/flow/ (official)
- http://scottchacon.com/2011/08/31/github-flow.html (blog post)
- https://guides.github.com/activities/contributing-to-open-source/
- use github issues system to the project management part of the project
- tags, issues and milestones
- https://www.zenhub.io/
- https://github.com/waffleio/waffle.io/wiki/Recommended-Workflow-Using-Pull-Requests-&-Automatic-Work-Tracking
- Brett break apart the plugin at a high level into grouping for a re-write
- Randy and Josiah need to review the plugin well enough for Brett to walk us through
- Find a contribute md file, should be able to find an example on github
- Find a few locations for January meetup (randy)
- Find a day for the in-person (randy)
- Find a day for the hangout (randy)
- re-write the plugin from the boilter-plate above
- Nashville collaboration
- unit testing
- using compilers
- vagrant env
- fork & pull request for non-admin contributors