Skip to:
Content
Pages
Categories
Search
Top
Bottom

Want to help accelerate the release of BuddyPress 1.3?

  • Avatar of Jeff Sayre
    Jeff Sayre
    Participant

    @jeffsayre

    With BuddyPress 1.2.5.1 hot off the press, we turn our eyes to the next big release — BuddyPress 1.3. But to make this happen, we need the continued help of the community.

    Currently, there are 10 listed bugs assigned to BP 1.2.6 and 155 bugs assigned directly to BP 1.3. Whereas not all of these may turn out to be true bugs, they do need to be investigated. Some of the reported bug tickets include patches that need testing, others are bugs that need to be confirmed or denied, and those that are confirmed but without patches need patches. Here is a link to the bugs ordered by version.

    http://trac.buddypress.org/query?status=accepted&status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&type=defect

    What You Can Do

    1. 1. If you are a developer, look through the above list and take one, two, or ten of the bug tickets, investigate the cause, and offer a patch.
    2. 2. If you are not a developer, you can still help out by testing those tickets that have patches or confirming reported bugs that currently do not have patches.
    3. 3. Report suspected bugs in Trac. First, post in the forums to try to get confirmation that it is a bug. The more relevant information added to a bug ticket, the easier it can be to track down the root cause of the bug. So, please include a link to any support-forum threads on the bug issue.

    NOTE: To add comments and patches to a Trac ticket, you first must log into the Trac system. Everyone with a BuddyPress account can do so easily. Just use the same log in credentials as you do on BuddyPress.org

    Roadmap

    You can also help accelerate the development and release of BuddyPress 1.3 by taking on one of the Roadmap enhancements — in other words, new features, or refactored existing features that are not bugs. Feel free to not only tackle any of the 1.3 Roadmap features, but also any of the 1.4 features as well. If you don’t know which current Roadmap features are in the works, just post here. For instance, I took on the challenge of coding a comprehensive Privacy Component for BuddyPress almost a year ago. With BP 1.2.5 out, I’m just about ready to release it. My goal is to have it make it into BP 1.3 — ahead of the BP 1.4 Roadmap deadline.

    As always, your help in making BuddyPress a stronger, more user-, developer-, and designer-friendly product is appreciated.

    Edited: 6 July 2010 by author

Viewing 21 replies - 1 through 21 (of 21 total)
  • Avatar of Jeff Sayre
    Jeff Sayre
    Participant

    @jeffsayre

    Bump

    Avatar of Pisanojm
    Pisanojm
    Participant

    @pisanojm

    Hi Jeff,

    I’m new to BP, but have been trying to get a handle on some of this and am starting to participate in the TRAC system after confirming on BP.. Truth is it’s a little intimidating to use the TRAC system…

    Avatar of Jeff Sayre
    Jeff Sayre
    Participant

    @jeffsayre

    @pisanojm

    It can be intimidating using Trac. But, don’t worry. You will not break anything. There are people who monitor Trac very closely (@DJPaul, for instance), keeping it in good order, correcting any issues.

    You will become more confident in participating in the bug tracking system over time. Thank you for your contributions.

    Avatar of paulhastings0
    paulhastings0
    Participant

    @paulhastings0

    @pisanojm One of the tools that I love to use with Trac is Jing. It’s free too (which is like… a +10 for brownie points). It helps a ton just to be able to show people visually in real-time what the issue is.

    http://www.jingproject.com/

    Avatar of Pisanojm
    Pisanojm
    Participant

    @pisanojm

    I’ve been posting some of the picts as I go along here… currently using Faststone capture… jing is very cool though…

    Avatar of abcde666
    abcde666
    Participant

    @erich73

    great initiative, Jeff.

    I myself have reported about 293 defects, enhancements and suggestions into the TRAC-reporting-system during the last year and a lot has been fixed and changed so far.

    So where are all the intelligent coders who are capable of moving BuddyPress to the next level ?

    Only by improving the core-code of BuddyPress, all of you coders, freelancers and designers will make money in the long-term.
    Do not take the short-term-view, step out of your tunnel-vision and take the long-term-approach !

    Well, I guess you remember what the short-term-view did to e.g. the financial industry ?

    http://trac.buddypress.org/search?q=erich73

    Avatar of Hugo
    Hugo
    Moderator

    @hnla

    Another very good SC plugin(free) is Fireshot for Firefox.

    @erich73

    The intelligent coders are all here, waiting and willing, posts such as this are the clarion calls to stir everyone to action, and after the recent posts discussing the state of play the core dev team and mods are attempting to ensure the project is put on an even firmer footing.

    In terms of BP as a project and production application I think it’s worth remembering ( I certainly have to remind myself ) that BP is a relatively young project – WP took quite a few years before it settled into a mature app – As for looking to the long term I think that this is addressed in the NextGenAPI which is a necessary next step and one that looks to take BP forward.

    Avatar of abcde666
    abcde666
    Participant

    @erich73

    @hnla

    not sure what the coders (I am definitely not talking about the BP-Core-Developers, but rather the “Coding-Community”) are waiting for ?
    The Core-Developers did a great job and are a bit exhausted for the moment, which is very understandable and acceptable.

    Now is the time for the Coding-Community to move ahead and a matter of TEAM-building into small teams who take on features they want to improve or develop.

    Avatar of Hugo
    Hugo
    Moderator

    @hnla

    @erich73 very true, it’s been requested before and again now for all and any willing and capable members to start to run through that body of Trac tickets for 1.3, the more experienced might be able to provide fixes or even just set things off on the right track anything like that helps the core team, after that testing is one of the huge burdens that falls on any developer, the more we help in testing fixes the more time the core devs will have. I think that time is the biggest enemy for many of us which is why the more that can muck in the better. Ultimately the speed at which versions are released and the quality of those releases will be down to the wider community, if no one helps out then things will come together but a heck of a lot slower.

    This next point is purely a personal feeling but I think it wouldn’t hurt to see a general slow down on plugin writing or feature extending in favour of a little more focus on the core app, but I realise it’s not really practical to expect plugin development to take a back seat and that there are plugins in development that people are crying out for :)

    Avatar of Boone Gorges
    Boone Gorges
    Keymaster

    @boonebgorges

    @hnla You raise an interesting point about plugin development vs core development. Speaking from the point of view of someone who makes a living off of WP and BP-related development, I can note that it’s often quite easy to justify the development of plugin-type functionality for a client. The client’s job needs a specific type of functionality not available in, or appropriate for, the core of BP, so it makes sense for them to pay to have it developed as an add-on. From there it generally takes just a bit of extrapolation and cleanup to turn that add-on into something that can be released as a plugin in the WP repo. (If you’re really lucky, like I am, you have paying clients who actually *encourage* these cleanup and extrapolating steps in plugin development.)

    It’s a bit harder to bill for core-type development, since so much of core development involves extensive bug testing on a wide variety of different server and software configurations – something that isn’t really required for a specific client project.

    Still, this all makes me think about Andy’s awesome post from last year, “Give a Little”: http://apeatling.wordpress.com/2009/09/25/give-a-little/. Now that I’m starting to catch up from my month-long break from BP (honeymoon ftw), I personally am going to start devoting more time to the core project, which I understand broadly as this buddypress.org community as well as the ongoing core development on trac.buddypress.org.

    Avatar of Hugo
    Hugo
    Moderator

    @hnla

    @boonebgorges Your point about plugin development is exactly why I felt a little reticent in expressing my feelings. Plugin development is part of the intrinsic nature of WP and it’s sibling/child modules (I still have a problem refering to BP as a plugin , it’s nearly a standalone app?) and to ask any developers to shift focus from that to the core app is a difficult one. Obviously billing for core development is next to impossible and we all know that – if we’re honest developers – we don’t bill clients for the testing of work or for cross browser conformance or for implementing 17 different image galleries because we want to find a new cool one for clients site etc.

    All that none withstanding I do have this impression that there is a lot of plugin development and that this development slightly fractures the strong focus that BP might need?

    I also still feel that many plugins – your ‘Invite Anyone’ is a prime example – should really be core modules or extensions much as we have BP ‘Components Setup’ as these plugins enhance and improve part of the core that already exists or add components that one might expect to be core in a social network app.

    I would like to see, perhaps?, something along the lines of a Trac milestone when a pretty stable BP is reached (1.4?) that sets out a process for identifying and bringing in certain plugins to the core , but this is probably something better discussed in a dev chat and is looking quite far forward; I also see an issue where the author has put substantial time and effort into development of the plugin and would hope there was some means of recompense given that the plugin would effectively cease to exist as downloadable and donateable

    I’d probably dedicate more time to trac patches if I knew or had a better understanding what/where/how and being on the same page/vision for the project. Probably why I stick to plugins, I have a better control over what I think works vs what the collective maybe thinking. (plus i don’t look like a doof since i’m a Java junky vs php guy :P ) And what @boonebgorges mentioned – 99% of the plugins I created came from a specific client request – I just like to recycle back to the community.

    ( just to get on the fun, i sent in a patch today :P http://trac.buddypress.org/ticket/2517 )

    Avatar of paulhastings0
    paulhastings0
    Participant

    @paulhastings0

    @nuprn1 @boonebgorges Btw, thanks for releasing your client plugins back to the community. The 2 of you combined probably account for 30% of the most recently updated plugins. Thanks.

    Avatar of Hugo
    Hugo
    Moderator

    @hnla

    @nuprn1 Might have been for fun but good patch nonetheless, essential bit of security supplying original password and seen in so many apps

    Avatar of Paul Gibbs
    Paul Gibbs
    Keymaster

    @djpaul

    Trunk not being merged with 1.2 branch is holding back a few patches from me

    Avatar of Jeff Sayre
    Jeff Sayre
    Participant

    @jeffsayre

    I agree we need to get trunk synced with branch, and work toward keeping it the bleeding-edge version once again.

    Avatar of Jeff Sayre
    Jeff Sayre
    Participant

    @jeffsayre

    Update on reported, possible bugs.

    For BP 1.2.6, there are currently 20 reported, possible defects.

    For BP 1.3, there are currently 154 reported, possible defects.

    Please read the first post in this thread to learn how you can help accelerate the process of getting BP 1.3 ready for release.

    Avatar of intimez
    intimez
    Participant

    @intimez

    @jeffsayre Ticket #2521 I do not see this problem and see settings menu for both wpms and wp.

    Avatar of Jeff Sayre
    Jeff Sayre
    Participant

    @jeffsayre

    @intimez

    Which versions of BP and WP are you running?

    Avatar of intimez
    intimez
    Participant

    @intimez

    @jeffsayre

    I tried both wp3+bp1.2.5.2 and wp3ms+bp1.2.5.2

    Avatar of Jeff Sayre
    Jeff Sayre
    Participant

    @jeffsayre

    @intimez

    Interesting. Okay, I had this issue with BP 1.2.5, 1.2.5.1, and 1.2.5.2 on WPMS 2.9.2 and WPMS 3.0. I just saw a note from @nuprn1 on that Trac ticket that he did not have this issue specific issue but a related one that the suggested patch fixed.

Viewing 21 replies - 1 through 21 (of 21 total)

You must be logged in to reply to this topic.