15 Comments

  1. guavaworks

    Thanks Sarah! What a trainwreck the GHangout was. Email matt@wordimpress.com if you want to join the Slack Channel and our GitHub Repo which is now just for putting in issues for discussion is hosted here – https://github.com/royboy789/helium – the name is temporary

    Report

  2. netweb

    I’d be happy to listen to the pros and cons of reviving BackPress, fundamentally as one of the bbPress team who hasn’t delved very deep at all into the code base of bbPress 1.x, reviving BackPress or not I think this would be a fun exercise for me personally…

    My big complaint here is how and where this discussion is taking place, first it started on Facebook, I’m not joining Facebook so I can talk about BackPress, then a Google hangout limiting participation, and now an “AdvancedWP Slack” instance where I must be invited to by an administrator to talk about BackPress, again this isn’t going to happen.

    BackPress is an open source project and I’d like to see this discussion in the open and publicly available to anyone who would like to contribute to this discussion.

    Report

    • guavaworks

      No one else gave us the time of day for open channel slack like on WP core, the Facebook conversation kind of blew up – but there is a public GH repo – https://github.com/royboy789/helium

      Report

    • guavaworks

      I’m open to other channels of communication / discussion. The Hangout was totally my fault, but even if it was public, there is a max amount of users on Hangout at a time, which I think is 10 or so. We are going to make it an “ON Air” Hangouts next time so at least it will be publicly viewable by anyone, and recorded. I will have to limit who gets invited so contributors who want to talk / discuss can do that.

      We talked about an IRC channel too, but that was thrown out pretty quickly.

      Report

    • Andreas Nurbo

      Cant demand to much at this stage. Its just starting we’ll see how it goes with where and how discussions takes place.

      Report

  3. Mike Schinkel (@mikeschinkel)

    @guavaworks – I would be interested in accessing the Slack channel…

    Report

    • guavaworks

      send an email to matt (at) wordimpress (dot) com and just ask for an invite tot he slack account, and join the #backpress channel.

      Report

  4. Mike Schinkel (@mikeschinkel)

    @guavaworks – Another possibly better option than Slack would be to use Gitter.im since it has chat rooms that tie to Git repos.

    Report

    • guavaworks

      We have created a glitter, but are using it specifically for when we have our hangouts. I won’t be paying attention to it TOO much and prefer everyone join the slack channel. I figure if you can wait for an invite, it means you are willing to give good feedback, I don’t need random trolls and spammers.

      https://gitter.im/royboy789/helium

      Report

    • guavaworks

      Glittler created. We will be using it for mainly hangout session chats, and prefer if you really want to commit and be part of the core conversation, to wait for an invite after emailing Matt.
      gitter . im / royboy789 / helium

      Report

  5. Pete Shaw

    Whilst back press is a great idea. This makes no sense as a standalone project. Really core itself should look to back press itself. WordPress desperately needs to be modularized.
    Wp core should choose a release (say 4.6) and as part of that release make itself properly modular and stick to being modular for all future releases. However if that doesn’t happen there is no point trying to to do this as the backpress guys will constantly have to play catch up.

    Report

    • Andrew Nacin

      I agree with you. A lot of effort put directly into the REST API and into core itself make things better for everyone, including those who want what BackPress tried to promise (and never delivered on).

      Report

  6. Paul

    I rolled my eyes at the reactions from the core devs to the BackPress revival. You know, the universe doesn’t revolve around you.

    Report

  7. Andreas Nurbo

    This post title is a bit missleading. If it had said; “… rocky reception from people affiliated or part of Core development” it would have more truth to it. There are alot of discussions going on with the project. Whatever comes out of the discussions about Core and how it could be improved, the discussions themselves are very enlightening and informative for those interested in development and best practices.

    Report

  8. Ray

    I actually think there should be a FrontPress, instead of a BackPress.

    Here’s an example of such a project:
    https://github.com/jgrossi/corcel

    What I mean by that is all WordPress files do not need to be loaded on the frontend to display some data, like they currently are.

    Things like the WP REST API would make perfect sense for this. Currently, the WP REST API is built out as a WP plugin, so you will require all the bloat that comes with loading WordPress in order to receive and respond to API requests.

    Report

Comments are closed.

%d bloggers like this: