Agenda for July 18, 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.

The agenda for today’s weekly project meeting:

Affirm deadlines and scope. Check in on the proposed feature scope for 3.5.
Teams. Form an initial set of feature development teams. This is about establishing responsibility for each feature, focusing ourselves on our goals, and making sure we have enough volunteers across the various projects. You don’t need to be at this meeting to “join” a team, nor do you need to be on a team to contribute.
APIs. Discuss potential platform and APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. improvements, particularly those that tie into the proposed features. (For example, ImageMagick support would be a great pitch, given changes to image handling.) XML-RPC and other perennial improvements should also be discussed.
Unit tests. What’s changed, and what our goals should be.

#3-5, #agenda, #dev-chat

Welcome!

Communication

Share this: