Make WordPress Core

Opened 6 years ago

Closed 6 years ago

#12185 closed enhancement (invalid)

Switch Code to BackPress?

Reported by: Gautam Gupta Owned by:
Milestone: Priority: low
Severity: normal Version:
Component: General Keywords: backpress 2nd-opinion
Focuses: Cc:


BackPress and WordPress files share most of the code. It would be a good idea to switch to BackPress.

If BackPress is integrated into WordPress, bbPress and other Press(es) would also seemlessly integrate into each others.

Just my two cents.

Change History (3)

comment:1 @beaulebens6 years ago

  • Keywords 2nd-opinion added
  • Priority changed from normal to low
  • Type changed from task (blessed) to enhancement

Open for discussion, but probably not going to happen immediately. There's quite a lot of code in BackPress that's *not* used in WordPress, so if anything I'd suggest that it might make sense to shuffle code in WP into a single directory if it also exists in BackPress, then at some point down the line, we could potentially just replace that directory with an svn:external to BackPress.

Also, the "blessed" task type should generally only be set by a core developer to confirm that something is bumped for specific inclusion.

comment:2 @Gautam Gupta6 years ago

  • Cc gautam.2011@… added

comment:3 @nacin6 years ago

  • Milestone 3.1 deleted
  • Resolution set to invalid
  • Status changed from new to closed

I would imagine this is going to happen over time with various aspects of the code, just as it occurred with WP_Scripts.

I don't think we need this ticket open and sitting here to see that through though. Closing as invalid for now in that case.

Regarding seamless integration, at this point, most items in the Press family run or will run through WordPress in some form. BuddyPress is a plugin, bbPress is to become a plugin, MU is merged, BackPress uses significant amounts of WP code.

Note: See TracTickets for help on using tickets.