Proposed teams for 3.org
We have created more than a half-dozen teams for the 3.org initiative, based on various discussions, ideas, and proposals. As a general disclaimer, these may evolve over the next few days.
API 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, multisite admins, plugin developers, theme developers, and core contributors. Lead: Jane. Editors: Lisa Sabin-Wilson, Andrea Rennick, Doug Provencio, Aaron Jorbin, Andrew Nacin, and others TBA.
bbPress 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: Core Integration. Improve installer, upgrades, compatibility reports, api.wordpress.org. Lead: Ryan. Members: TBD..
UI 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:
i18n Projects. Improving the management of localized plugins, and also providing better tools for localized communities.
Plugin Directory: Stats. SVN notifications, improvements to Trac, 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.
Aaron D. Campbell, and 13 others are discussing. 
BrianLayman 8:10 pm on July 8, 2010 Permalink
Excellent! Sounds excitingT
scribu 8:10 pm on July 8, 2010 Permalink
The “bbPress as a plugin” might want to take a look at A bbPress alternative
Andrew Nacin 8:15 pm on July 8, 2010 Permalink
JJJ and PeteMall have been working on this for about as long as Justin has. They are taking different approaches, I think Justin is leveraging taxonomies and JJJ post types. I would love to see the efforts combined however, if everyone is interested. Ideally, it would end up a direct bbPress successor, versus an alternative.
scribu 8:31 pm on July 8, 2010 Permalink
Actually, he switched to post types too. Anyway, yeah, a combined effort would be a lot better.
Mike Schinkel 9:53 pm on July 8, 2010 Permalink
Yes, I tool would really like to see one effort rather than several.
Justin 4:01 am on July 9, 2010 Permalink
I tried to get involved months ago in the bbPress plugin project, but nothing really ever came of it, which is one reason why I’ve been doing my own thing.
Ideally, I’d move my efforts over to the bbPress plugin so we could all work together, but I’ve got project deadlines that I want to meet right now and don’t want to risk more delay (though I’m not sure where the bbPress plugin is at right now).
I do want to keep tabs on the bbPress plugin because I’d like for users to be able to easily switch from one to the other without a lot of hassle. If anyone wants to talk about how to best store data for the forums, don’t hesitate to shoot me an email. I’ll be happy to hear your thoughts.
John James Jacoby 7:38 pm on July 9, 2010 Permalink
Justin, would be happy to have your experience in on this. No reason to duplicate efforts. Let’s find time soon to pass some ideas back and forth? I know you have a deadline, where as ours is a little more relaxed (at the moment anyhow.)
http://bbpdevel.wordpress.com
mark. 8:27 pm on July 8, 2010 Permalink
JJJ/PeteMall, drop me a line if you’re in the market for any more hands on the bbPress team. That’s a project I’ve been interested in seeing happen for quite some time!
Sergey Biryukov 8:27 pm on July 8, 2010 Permalink
I’d like to work on the i18 projects.
Mo Jangda 8:29 pm on July 8, 2010 Permalink
I’m interested in helping; possibly either the Community, Core Integration, or bbPress groups (since their numbers seem low) — though I’m really open to anything.
filosofo 8:30 pm on July 8, 2010 Permalink
I had mentioned interest in this when I volunteered to help, so if this team can get off the ground I’d like to participate.
dremeda 9:24 pm on July 8, 2010 Permalink
Let the fun begin
kevinjohngallagher 8:37 am on July 9, 2010 Permalink
Is there any chance we can not call the wordpress forum plugin the “bbPress plugin”?
We have bbPress0.9 and bbPress1.0 (both incompatible, both only reffered to as bbPress), BuddyPress, the bbPress plugin for for BuddyPress (also incompatible with bbPress0.9 & bbPress1.0) and now the bbPress plugin (incompatible with both versions of bbPress and the bbPress plugin for BuddyPress).
That is 4 pieces of software, all unique, all incompatible and all using the same name.
Gautam 9:22 am on July 9, 2010 Permalink
That’s nice! I’d like to be in the bbPress team if possible – I’ve been contributing to the project for some months now.
Aaron D. Campbell 9:17 pm on July 9, 2010 Permalink
I was on vacation for the last two weeks, so I missed out on a lot of this, but I’d be happy to help with either “Plugin Directory: Core Integration” or “Plugin Directory: Stats” when they get started. If those don’t end up happening, I don’t mind helping with something else.
Milan 10:24 pm on July 9, 2010 Permalink
I think that this should be done in Plugin Directory: Core Integration since most of it is related to description of that team. There is already tool (GlotPress), we just need to connect it with plugin repository.
Though someone could help Nikolay on GlotPress development.
bbPress – as a Plugin! « bbPress Development Updates 11:57 am on July 15, 2010 Permalink
[...] – as a Plugin! Andrew Nacin announced over on WPDevel that Pete Mall and John James Jacoby will be diving head first into bbPress plugin development soon [...]
Few More Thoughts On The WordPress.org Redesign — Mark McWilliams 11:54 pm on July 24, 2010 Permalink
[...] starters the development teams going to work on the redesign have been announced, and while I probably couldn’t help fully, I’m sitting on the [...]