I’d like this week’s dev chat to be…

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.
Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.
Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Erlend 5:20 pm on March 7, 2011

Definitely happy to see this topic — actually considering my recent comment at wordpress.tv the timing is uncanny 😉

Was it just 2 months later than planned though? As I recall, the end-of-2010 deadline was itself a postponement of an even earlier date. I guess that was also a result of 3.0 being delayed, but that just makes it an integral part of this discussion.

http://replay.waybackmachine.org/20100527203256/https://wordpress.org/about/roadmap/
- Jane Wells 5:28 pm on March 7, 2011
  
  Nope. It wasn’t a postponement of an earlier date at all. We decided to take two months off to focus on wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ community infrastructure (the cycle we were calling 3.org), and that just didn’t have a place on the roadmap, so the roadmap was out of date, that’s all.
  - Erlend 5:36 pm on March 7, 2011
    
    Oh right! My bad. Yeah I remember those two months, it was a very welcome move, and a bunch got done 🙂
Malcjohn 7:48 pm on March 7, 2011

Hi, what abou to make a banner, which says to help to WP community. Maybe we shall also think about how to make developers glad (money…………..VIP section) to make patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for us.

By the Way : Glad to see you here back
Erlend 7:53 pm on March 7, 2011

Agreed, I made a couple suggestions along those lines back in the “What should 2011 hold ..” post – see “Acknowledge contributions”.

Though, I think this is a somewhat different topic. Developer appraisal is quite s separate issue from “what can 3.2 learn from the 3.1 release cycle”.
- Malcjohn 8:24 pm on March 7, 2011
  
  of course you are right, BUT : if we want to change somethink ( read: “what can 3.2 learn from the 3.1 release cycle” ) we have to start to think what we already had made wrong.
  
  Examples are :
  1.Forget to write a roadmap with dates. Same like Blizzard does.
  2.Pay people, or don’t, if they finish their work or not. Exception for @Nacin a @scribu + some others
  
  +
  +
  +
  - Erlend 8:51 pm on March 7, 2011
    
    There are several reasons why Blizzard doesn’t publicize/use a roadmap, but hardly any of them apply to WordPress. Blizzard and WordPress (or Blizzard and Automattic for that matter) are largely dissimilar.
    
    Structurally speaking, WordPress is very similar to Ubuntu, which has got an exceptionally steady release cycle that has no doubt been in their favor.
    
    A successful release cycle is more about meeting expectations than it is about getting tons of stuff done. If you promise too many things, you trap yourself in a release cycle that’s based on work that needs to be done on time. If you promise only a few things, you’ll have a much higher chance of delivering on your promise, and you’ll probably get to surprise your users with a handful of bonus additions that made it in in time for release.
  - Matt 8:46 am on March 8, 2011
    
    Very well put.
  - Erlend 1:58 pm on March 11, 2011
    
    Thanks, I think. See, here’s an inherent problem of WordPress threaded comments:
    To not make a mess of threads (in this case we seem to have also reached the limit of threading) I usually reply in the same way, that is in this case, reply to Malcjohn in order to make my comment appear directly below yours. I’d like to think you meant to reply to me, however my e-mail notification said you were replying to Malcjohn.
    
    There logic of the commenting system is a tad flawed. Figured I might as well point that out here since the example use case is right under our noses.
arena 11:33 pm on March 7, 2011

3.2 > PHP5 > WordPress Object Oriented code

will help for sure !

Comments are closed.

Welcome!

Communication

Share this: