Agenda for Dev Chat 1/25/2012

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Last week was more of an old school group status check and less of a new-process meeting (my bad, I had a time conflictconflict A conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved.). Let’s try to get back to the stuff we said we would start doing.

First we’ll review past meeting to-dos and make sure everything is done that is supposed to be (or see if there’s anything that is supposed to be done by now but isn’t).
Look at draft project schedule, edit as needed and approve. http://wpdevel.wordpress.com/version-3-4-project-schedule/
Check in with each team to ID state (just finished scoping, already developing, or tested and commit-ready patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. posted) and plug into schedule based on state + ux needs
Review each team’s planned scope/timing for 1st cycle
Assign days to each team for putting up weekly status posts on this blogblog (versus network, site) (and add authors to site if needed)
Choose ‘office hours’ for each team to be in this channel and meet to chat re progress and/or chat with community members who are working on related tickets and have questions or need patch review
See if there are any new sub-teams we can form to get cracking on more feature dev
ID to-dos for each team member for next week
Ticketticket Created for both bug reports and feature development on the bug tracker. discussion: people not on an assigned team who have posted a patch on a ticket can ask for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team to check it and give feedback
Ongoing discussions re feature dev

#3-4, #agenda

Welcome!

Communication

Share this: