Updates from Paul Gibbs Toggle Comment Threads | Keyboard Shortcuts

  • Paul Gibbs 8:50 am on May 22, 2013 Permalink | Reply
    Tags:   

    It’s Wednesday! It’s also 14 days before feature development ends for BuddyPress 1.8, so let’s recap where we’re all at!

     

    • Paul Gibbs 9:17 am on May 22, 2013 Permalink | Reply

      Automatic download of language translations

      • Everything looking good.
      • Planning to commit after work today.

    • Tammie Lister 9:43 am on May 22, 2013 Permalink | Reply

      Refresh UI plugin:

      • Made the table of contents to new content and also removed ones we weren’t using.
      • Did few small patch tidies.

      This week: Considering removing all inner-box shadows, focus elements and also border/form styling. These are more radical moves but would mean it’s easier for light / dark themes. Have to see impact so may not decide to keep in.

      Template pack:
      Whilst some progress has been made this week it became aware that some ground work needed doing in order to allow anyone a chance to contribute. As a result this project I’m not sure will be ready for the 1.8 feature dev end. I’m ok with this myself, as we all knew it may stretch over 2 releases – it’s a lot of work.

      I think one of the worst things we could do is rush things in 14 days just to reach a deadline. However, I want to keep the pace because if we’re done 1 week into new dev cycle we then have the luxury of user testing, refinement and time. I think that’s a better approach to release this with time – if we’re doing this it needs to be good.

      • I created a template based on the good work Turtleshell did so we can now use that to load. It’s on Github:https://github.com/karmatosed/buddypress-templatepack
      • I started a Google document for standards / format we are going to use for template pack. To give focus this is currently being reviewed by @hnla before I’ll put it up with open access to all to see. This hopefully will be today.

      Core question: Do we want a ticket per template section or have those on Github as issues? I want to assign each to a person so we can keep conversations relevant to the template and track things easier. I’d like to use trac but don’t want to clutter it if that’s not suitable.

      This week: Plan on creating and assigning templates to those who want to get involved. When you do volunteer just do for one template at a time. We don’t have to have everything assigned all at once.

    • Blazej 9:03 am on May 24, 2013 Permalink | Reply

      We have added missing Polish translations – now 100% is in. But we don’t know how to aprove them – cen you help? It would e nice to have them in BP 1.8

    • Ronel 7:36 am on June 11, 2013 Permalink | Reply

      HI Paul,

      These all good fantastic!
      Any chance you could slip in an update for the Welcome Pack email templates? Would love to be able to customise the sign up email for my website redesign launching in 2 weeks.

      Let me know!

      Thanks for all the hard work, and for keeping this plugin free! :)

  • Paul Gibbs 5:56 pm on May 15, 2013 Permalink | Reply
    Tags:   

    Wednesday updates! How’s your BuddyPress gone this week, feature leads?

     

  • Paul Gibbs 8:56 am on May 1, 2013 Permalink | Reply
    Tags:   

    Let’s try something new; each Wednesday, would people leading on a headline feature for 1.8 please publish a brief progress update to the weekly update post.

    Doesn’t matter when on Wednesday, as long as it’s still Wednesday wherever you are :)

    I’m hoping this will increase visibility of things that are in development, as it’s hard for someone not going to the dev chats or reading the IRC logs to find out the current status of a particular feature, and in turn help us keep 1.8 on schedule.

    I’ll post mine later to kick things off!

     

    • Tammie Lister 9:06 am on May 1, 2013 Permalink | Reply

      I’m going to split it into the 2 tasks so it’s easier to follow:

      UI Refresh:

      So far the plugin has dealt with the following areas: font fixes, removed gradients, removed border radius

      New template pack:

      The current plan is to get more people involved now and start looking at who wants to do what.
      Ideally this week wireframes should be the focus to keep to schedule.

      • hnla 6:27 pm on May 1, 2013 Permalink | Reply

        Can I make a suggestion for consideration? with things like this ui-refresh plugin and my experimental playing around with members templates re-factoring to use bp_nav_menu() files on my github that we could perhaps move these to the buddypress-themers github that we used for the Status theme as somewhere to maintain bits like this and where we can easily add people as necessary?

        • Tammie Lister 6:48 pm on May 1, 2013 Permalink

          Hmm not convinced on that one. It assumes everyone will be doing every project – this won’t be the case at all. A github home should also only be temporary. Lets not and lets keep things separate for now – it could get over confusing otherwise fast.

    • Boone B. Gorges 11:22 am on May 1, 2013 Permalink | Reply

      The meta_query parameter has been introduced for the bp_has_groups() and bp_has_activities() family of functions. See http://buddypress.trac.wordpress.org/ticket/4591, http://buddypress.trac.wordpress.org/ticket/3521, http://buddypress.trac.wordpress.org/changeset/6948, http://buddypress.trac.wordpress.org/changeset/6950

      Trisha mentioned that she was working on group member queries: http://buddypress.trac.wordpress.org/ticket/4482

      Next on my list is to tackle BP_Group_Extension improvements. http://buddypress.trac.wordpress.org/ticket/4955

      • trishasalas 6:35 pm on May 8, 2013 Permalink | Reply

        I got sidetracked with client work but have made some progress with the ‘how’ of it.

        My biggest hurdle is wading through the BuddyPress code itself since it is somewhat unfamiliar to me. I have a file I put together but it is just a conglomeration of all the parts I `think` might work. I still need to go through them and test and narrow it down after adding my sql to it.

        I’m not sure if it is even ‘post-worthy’ at this point but I don’t mind posting if only to get some direction. I’m trying to keep in mind that everyone is busy and do my learning on my time :)

    • Paul Gibbs 12:20 pm on May 1, 2013 Permalink | Reply

      For the auto language downloads, I wrote a patch for GlotPress to add LAST-MODIFIED headers to the .mo export, which was committed. Waiting for the change to be deployed to translate.wordpress.org:

      http://glotpress.trac.wordpress.org/ticket/236
      http://glotpress.trac.wordpress.org/changeset/751

      I am working on the BuddyPress changes and hope to have a patch up for review next week before I do some travelling.

    • Ray 6:21 pm on May 1, 2013 Permalink | Reply

      Didn’t do anything for template hierarchy this week.

      Looking to refresh the patch in https://buddypress.trac.wordpress.org/ticket/3741 before next dev chat.

      Will also try to implement JJJ’s idea of hierarchy for the wrapper template as well.

    • John James Jacoby 5:06 pm on May 2, 2013 Permalink | Reply

      Rewrite Rules Update:

      • Started writing the backwards compatibility layer to make rewrite rules and tags out of the existing bp_nav and bp_options_nav arrays.
      • Started creating functions to encapsulate and simplify adding “screens” and their associated “actions” ala register_post_type() so we can use them in core to start, and third party plugins later.
      • May not have a proof of concept for a week or more, based on availability.

  • Paul Gibbs 11:23 am on April 11, 2013 Permalink | Reply
    Tags:   

    Unfortunately, BuddyPress’ application to be a mentoring organisation for GSoC 2013 was rejected. We’d like to thank everyone who helped put together the application and ideas pages, and those who volunteered to be a mentor. However, WordPress got in!

    If those people would still like to mentor a WordPress project, or you’re a student and you’d like to work on a BuddyPress project, then I’d encourage you to applying as a mentoring or student to the WordPress project. Check out make/core for details.

     

    • http://www.facebook.com/ 6:58 am on June 19, 2013 Permalink | Reply

      A traumatic experience with dental work, usually occurring
      as a child, can cause repercussions that make it genuinely stressful and anxiety-inducing to submit to dental work.
      Stitches placed during surgery will either dissolve or be removed by the oral surgeon.

      The ability to share patient health information between primary care
      physicians and dentists is allowing that beneficial communication to make a difference in diagnosis, patient care, and treatments available.

  • Paul Gibbs 7:10 pm on March 29, 2013 Permalink | Reply
    Tags:   

    The GSoC Mentoring Organisation deadline passed 10 minutes ago… and BuddyPress did submit on time :) We find out on April 8th 17:00 UTC if we’ve been accepted into GSoC or not.

    Big thanks to everyone for helping to pull together the various bits of paperwork; special shoutouts to @karmatosed and @mercime who put in long hours!

     

  • Paul Gibbs 9:07 am on March 28, 2013 Permalink | Reply
    Tags: , rc   

    @johnjamesjacoby released BuddyPress 1.7 RC1 yesterday: blog post

    What does this mean? 1.7′s pretty close to being released :) You can help by:

    • Testing your site with the upgrade
    • If you are a developer or a theme author, test your things against 1.7
    • Report any bugs or broken plugins to https://buddypress.trac.wordpress.org
    • Polyglots can help finish up the pending translations for 1.7 on translate.wordpress.org (we’re now in string freeze)
     

    • Andre 12:33 pm on March 31, 2013 Permalink | Reply

      Is there a BuddyPress Beta Plugin so we can test the upgrade process also?

  • Paul Gibbs 4:23 pm on March 24, 2013 Permalink | Reply
    Tags:   

    This year, BuddyPress is going to apply for GSoC 2013. In previous years, we’ve tagged along under the WordPress application, but we’re going it alone this time! I’m taking care of the application, but I need the community’s help in building the list of project ideas, and finding potential mentors.

    I’ve borrowed a bunch of text for this post from Jen’s WP Core post :)

    Potential Mentors

    If you want to volunteer to be a mentor, you need to be good enough with WP + BP coding that you generally don’t need oversight to get it right, and have enough time to be available to your student for feedback and code review (at least once per week).

    The time commitment can be anywhere from one hour to ten hours per week, depending on how far along your student’s project is, and what there is for you to review; an hour or two a week is typical.

    You get an awesome GSoC tshirt at the end! I’ve directly approach a bunch of qualified people already, so if I’ve spoken to you, no need to post again here. But if you want to be a mentor, leave a comment on this post with a short/one-paragraph bio about yourself, what kinds of projects you are interested in/qualified to mentor, and links to your website, wordpress.org profile, and twitter account.

    Project Ideas

    The more project ideas the better. There’s no shortage of good BuddyPress project ideas, but these all need to be written up. The Project Ideas list is the most important part of our application. The projects must be code, though, not design or documentation, etc.

    List your project ideas in a comment on this post. Please give it a title, and a short one-paragraph description. If there’s a ticket or relevant thread somewhere, link to it.

    BP GSoC Meeting

    On Monday 25th at 19:00 UTC, we have a quick meeting on IRC to review progress with our GSoC application, and to discuss anything else GSoC-related.

     

    • mercime 8:12 pm on March 24, 2013 Permalink | Reply

      Idea #1 – EnGrande Privacy & Moderation Component

      xprofiles already in core. Messaging, Friendships, Groups, Blogs, etc. Jeff Sayre started something cool with http://wordpress.org/extend/plugins/bp-privacy/

      Idea #2 – Extended Membership Levels and Registration

      Allow set up of different types/levels of membership e.g. Student, Teacher and have a registration form with different xprofile fields listed in registration and profiles depending on the different types/levels

    • Paul Gibbs 8:57 pm on March 24, 2013 Permalink | Reply

      Idea – Media albums

      Use the WP media gallery to let people create albums of pictures (that they’d upload), and pull in external media sources, e.g. youtube, etc.

      Idea – Tie Private Messaging and Activity Streams and Commenting and Forums together

      A BP site with Messaging, Activity, and Forums activated offers a lot of different ways of allowing people to communicate. Why aren’t these joined up? Envisage a super activity stream which more resembles a Twitter stream, but when you reply to a link to a blog post, the reply is actually added as a comment.

      We’d need a more powerful sorting system for results, as interesting results would need to surface to the top. Relevant discussion on hackernews.

      Idea – Expand Relationship Types

      The only current way of mapping user relationships is a one-to-one (“friend”) mapping. Expand to allow many-to-one (“followers”) and metadata to classify the type of relationship (“colleagues”, “partner”, etc).

    • modemlooper 4:08 pm on March 25, 2013 Permalink | Reply

      #1 Import / export site data

      Allow site admins to transfer data from one BP site to another.

      #2 front end custom post type creation

      Allow admins to create a custom post type and then serve a creation dialog for users in the front end. Similar to how activity is now but not limit it

      • Paul Gibbs 4:33 pm on March 25, 2013 Permalink | Reply

        Need some more information on your second idea; what’s the end goal look like? What are these post types used for?

        • modemlooper 3:22 am on March 26, 2013 Permalink

          The activity could be transferred to something like how you can create custom components. Instead of just having activity, create BP content types that can be extended.

          So, a developer could create plugins that add new BP content types that users can create on the front end.

    • Paul Gibbs 7:36 pm on March 25, 2013 Permalink | Reply

      Here’s some suggestions from someone who emailed me:

      1) WebRTC chat for buddypress similar to drucall that is for drupal?

      http://www.drucall.org/
      http://danielpocock.com/announcing-drucall-webrtc-for-drupal

      2) 2) ostatus integration there is already a plugin available:

      http://wordpress.org/extend/plugins/ostatus-for-wordpress/
      https://github.com/pfefferle/ostatus-for-wordpress

      3) owncloud integration?
      owncloud.org

      4) aggregate stream from all my social networks and display them in a list or grid view
      rss + tumblr + linkedin + facebook + twitter + google plus in one a bit like:

      bebop or buddystream – wordpress.org/extend/plugins/bebop/ – https://github.com/lncd/bebop – http://wordpress.org/extend/plugins/buddystream/
      wpmu.org/introducing-buddystream-a-social-network-synchronization-plugin-for-buddypress/

    • imath 8:45 pm on March 25, 2013 Permalink | Reply

      #1 It would be interesting to have the ability to share activities that are only viewable by friends, or group of friends as Paul suggested when saying “metadata to classify the type of relationship (“colleagues”, “partner”, etc).”

      #2 A guided “tour” / help for new users that can be customized by the admin to help users discover all the active areas.

      #3 An Admin UI to organize the positioning of the different element of each component page and eventually add some custom content

    • mercime 9:38 pm on March 25, 2013 Permalink | Reply

      Suggested ideas from BuddyPress Forums, some of which could be incorporated into Privacy, Moderation, or on its own like Spam prevention http://buddypress.org/support/topic/calling-for-buddypress-project-ideas-for-gsoc-2013/

    • Tammie Lister 9:56 am on March 26, 2013 Permalink | Reply

      #1 : Statistics Dashboard (a more useful dashboard) : A dashboard which could be the default page for BuddyPress and shows statistics from your site. Likely areas would be groups, activity, members. There would be graphs/charts to show these and the ability to also drill down further.
      https://www.evernote.com/shard/s3/sh/ddb7cb0c-3d96-48fd-945d-cbc94cf44599/3821b0e8a6499d32c3986c7c4c91a1ef explains this idea in a sketch.

      #2 : Scrapbook : A way to share site wide and external links as a collaborative resource. Would be nice if able to be video, images along with text links.

      #3 : Naughty step : A way to assign roles to users that limit what they can do on the site as a form of policing. This is a different take on privacy as works per user / roles and would be useful to limit site wide access and also functionality as a penalty for bad behaviour. It would also be customisable to create whatever roles admin wants.

    • Tammie Lister 10:01 am on March 26, 2013 Permalink | Reply

      #4 : Start Zone : A useful way to introduce users to your community. When you login for the first time a starting zone will appear where you can learn about the community (videos, content) and also some FAQ. This could also expand to include contextual help and be a ‘one stop’ help package.

      #5 : Nag Notifications : Timed and action based messages. You can set a message to prompt you to update your profile fields, reset passwords – anything you can do on the site. You can change the frequency and how many nags can appear at one time (probably best only have one though as default for sanity).

      #6 : Human Captcha : A site wide (all forms) human captcha that has configurable questions and configurable look.

  • Paul Gibbs 8:04 pm on March 20, 2013 Permalink | Reply
    Tags: ,   

    We’re planning an quick dev meeting for Monday 25th at 19:00 UTC to review our GSOC application & ideas progress.

    We can move around with the time/date if it will make it possible for more people to attend, but I don’t want to move it beyond Tuesday at the latest. Ideally, any would-be mentors will be at the meeting to contribute. We’ll reach out to people to confirm we’ve accepted them as mentors before this meeting.

     

  • Paul Gibbs 8:46 pm on March 16, 2013 Permalink | Reply
    Tags: ,   

    Agenda for next dev chat (Wed, same time and place as usual).

    • RC
    • GSOC
     

    • Paul Gibbs 2:54 pm on March 17, 2013 Permalink | Reply

      Here’s some more info on GSOC. I spent time with @jenmylo at WCATL this weekend going over what needs to happen.

      1) We need to complete an application; I am happy to be responsible for this.

      2) And we need to build a great ideas page, which is perhaps the most important part of the process.

      3) We need to move fast and build a quality application. The WP Core application is going to make reference to ours; a new project needs an existing mentoring organisation to vouch for them.

      4) We need to confirm people appropriate to be mentors.

      **We have 2 weeks with a hard deadline**. Relevant timeline:

      March 18: 19:00 UTC

      • Mentoring organizations can begin submitting applications to Google.

      March 29: 19:00 UTC

      • Mentoring organization application deadline.

      April 8: 19:00 UTC

      • List of accepted mentoring organizations published on the Google Summer of Code 2013 site.

      Via http://www.google-melange.com/gsoc/events/google/gsoc2013

      ACTIONS

      EDIT: no Idea Wrangler volunteered, so we’ll all have to pitch in to get it done.

    • Paul Gibbs 7:18 pm on March 18, 2013 Permalink | Reply

      GSOC 2013 mentoring organisation applications are now open:

      http://google-opensource.blogspot.com/2013/03/mentoring-organization-applications-now.html

  • Paul Gibbs 9:56 pm on February 24, 2013 Permalink | Reply
    Tags:   

    As always, this week’s dev chat is Wednesday at the normal time of 19:00 UTC.

    We’ll be talking about the beta, and reviewing any outstanding tickets for 1.7.

     

← Older posts

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel
Follow

Get every new post delivered to your Inbox.

Join 331 other followers

%d bloggers like this: