Proposed teams for

We have created more than a half-dozen teams for the initiative, based on various discussions, ideas, and proposals. As a general disclaimer, these may evolve over the next few days.

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. Reference. This team will build a comprehesive API reference based on inline documentation, and integrated closely with the handbooks. Lead: Nacin. Members: duck_, koopersmith, jorbin, mikeschinkel, benbalter.

Handbooks. This team will edit a series of handbooks, with the ultimate goal of one each for users, multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site admins, 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 Plugin Directory or can be cost-based plugin from a third-party developers, theme developers, and core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. Lead: Jane. Editors: Lisa Sabin-Wilson, Andrea Rennick, Doug Provencio, Aaron Jorbin, Andrew Nacin, and others TBA.

bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. as a Plugin. This team will concentrate on creating a bbPress plugin for WordPress. Lead: JJJ. Member: PeteMall.

We’re going to create a few teams to focus on the plugins directory. These teams may overlap and in some instances work together, but it is important to primarily work in small teams with manageable, defined scope. More about our general goals in this blog post.

Plugin Directory: Support and Management. Develop tools enabling plugin authors to better support their plugins, and for better administrative management. Lead: Mark Jaquith. Members: beaulebens, Dougal, WDS-Brad, Glenn Ansley.

Plugin Directory: Community. Improve user interaction with the directory, such as user reviews, adoption, comments. Lead: Peter. Members: filosofo, Dan Cole, Brian Layman, Michael Torbert.

Plugin Directory: CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Integration. Improve installer, upgrades, compatibility reports, 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. Lead: Ryan. Members: TBD..

UIUI User interface Working Group: Will assist other teams. Lead: Jane. Members: JohnONolan, TECannon, Dremeda, MT, Kevin Conboy.

We have identified two additional projects that would need teams to proceed:

i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. Projects. Improving the management of localized plugins, and also providing better tools for localized communities.

Plugin Directory: Stats. SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. notifications, improvements to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., better stats for plugin developers (and aggregate, public download stats).

Quick hits for what’s not on here and why. Ideas forum: It’s a GSoC project by Justin Shreve. Themes directory: We hope lessons learned in the plugins directory projects can be carried over to the themes directory. Forums: We believe the plugins directory and the bbPress projects will offer incremental improvements to the forums. Codex: See API reference and handbooks. Profiles: We’ve realized without studying this well and developing a solid direction, a profiles project could flop. We’re going to go ahead with these projects and discuss profiles in the near future. Site content and design: We’ll get there.

If you’re not on here, we’re sorry. We either omitted you accidentally, or weren’t sure what you want to commit to, or didn’t know enough about you to offer you an assignment. Please let us know where you’d like to be involved in the comments (links to your website, portfolio, etc would be useful). Just note that some of these teams are already pretty much at their maximum, as we want to them to be agile pirate/ninja teams. But we don’t want to leave anyone out who wants to enlist their skills and feels they can contribute.