Update: Seeing as this hardly led to a wail of anguish from plugin authors I’m gonna can it… maybe it’ll be back next year in another form, we’ll see. Apologies to anyone this has inconvenienced.
The response to the plugin contest this year has been pretty low.
We’ve only had 5 submissions – only *one* of which has any real specific relation to MU / BuddyPress – and that’s been with a big extension.
Not to mention that there hasn’t been a single extra sponsor come forward :(
Anyway, not being one to try to flog a dead horse I’m thinking that we should probably cancel it this year and think about how / if it could be done next year.
Whadda people reckon?





Wow. Personally speaking, I was trying to clean up some last minute bugs before I submitted something this week. But if the response over is very low (especially single digits), maybe it would be best to cancel it and bring it back next year maybe with an earlier announcement might best overall for the community/contest? Maybe people are still getting the hang of BuddyPress 1.1/WPMU 2.8.x?
I’m thinking that it needs re-formatting / re-purposing… am very sorry to you guys who have put in the effort but like a said, beating inanimate quadrupeds isn’t really my style ;)
Hi,
I wrote a few plugins for Buddypress. I just finished Buddypress chat. I would have entered it if I had even know about the contest. I think that was part of the problem here. Getting access to people who are writing plugins for Buddypress.
I think if you can solve that problem that might bring more interest from developers. As from a sponsor effort, why would they join the endeavor? To me I think they’d join if you angled the contest to solving a novel problem. Then finding these sponsors…well I’d have no idea.
Perhaps I’d try the sites using buddypress on buddypress.org for a sponsor list and buddypress developers on the same site.
I’ll be writing more plugins so I do hope you bring this back:)
Thanks,
Dave
Hi David,
Thanks for the feedback / ideas – I’m leaning more and more towards this being a bit of a waste of time though.
It is a pity, but completely understandable. Maybe there are not that many developers still working with WordPress MU.
That’s too bad, because I know plug-in contest tend to generate some great functionality. I know that developing plug-ins from scratch is too time consuming to do myself, but I have some good ideas for them.
Perhaps an alternative, would be to find people willing to throw some cash at a really good plug-in, and then offer to pay developers who use their time to write them. Essentially become a clearing house for plug-in development.
So, what’s the scoop? Are you canning it or not? If not, I have other plugins to submit. If you are, I won’t bother….
I think it’s canned:
http://twitter.com/wpmuorg/status/5189735269
Sorry I couldn’t contribute this time around, James. The timing didn’t work for me this year. During last year’s contest I had a luxurious couple weeks free time in late August to immerse in the poetry of the code.
“To every thing there is a season, …”
Hi James,
Sorry to hear about this.
I just came here after long time to submit our buddypress component as an entry for competition. Sad to see things didn’t work out the way you expected but I am really grateful to you for this initiative as it helped me complete our first big open source project on time.
Link: http://www.wpveda.com/buddypress-kaltura-media-component/
Thanks,
-Rahul
Timing was also the issue for me. Now my would-be entries are finally finished:
Revisionary
Enables Pending Revisions and Scheduled Revisions to published posts/pages.
http://wordpress.org/extend/plugins/revisionary/
Role Scoper (major update with full MU support, sitewide user groups)
description: http://wordpress.org/extend/plugins/role-scoper/
RC download: http://downloads.wordpress.org/plugin/role-scoper.1.1.RC1.zip
In both plugins, every functionality option can be configured for either sitewide or blog-specific setting.