Welcome to buddypress.org Ninjas
In the June 30, 2010 BP dev chat http://bpdevel.wordpress.com/2010/06/30/summary-of-june-30th-dev-chat/, it was decided that a small group would form to address some of the ongoing issues with the buddypress.org website. I’ll be leading the effort.
Anyone who is interested in playing a role in this process should join the group. In this thread, I’d like to work out how things will work. Here’s what I know so far:
– There have been numerous discussions on this site and elsewhere about the current state of buddypress.org. @r-a-y, @gigalinux, and @lph2005 have been working on a whiteboard that assembles some of these threads and organizes them by severity/priority. You can view the list here: http://123.writeboard.com/7555930eb348e12b5 (password is cake)
– @apeatling is working on getting me access to the buddypress.org environment. Once I have that access, I can act as the implementer of fixes. That said, I don’t want or need to be the only people fixing things. Many of the fixes on the list – especially feature requests – can and should be developed independently. If there’s something on the list that you’re particularly interested in coding, please start a thread in this group.
A few other thoughts:
* The purpose of this group is NOT to discuss the BuddyPress software more generally – ONLY its implementation as the software that runs this site, http://buddypress.org. If you want to discuss the BuddyPress software and its development, there are many places to do so: BuddyPress Trac, the BuddyPress Development Updates blog, the forums, #buddypress-dev and #buddypress on irc.freenode.net.
* The purpose of this group is not to complain. (May I suggest that you start your own blog ? ) The purpose is to find bugs and develop solutions for them, as well as to discuss/develop new features or UX/IA directions for buddypress.org.
Let’s get cracking!
- The topic ‘Welcome to buddypress.org Ninjas’ is closed to new replies.