Post items as replies to suggest agenda …

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.

Jane Wells 10:14 pm on July 15, 2009

MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tables, per DD32 last week.
Denis de Bernardy 10:14 pm on July 15, 2009

So, RT last week: the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. tables stuff.
Denis de Bernardy 10:16 pm on July 15, 2009

Possibly re-discuss committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. workflow with rboren (and ideally matt) around. I think the key points were made today, though.
- Jane Wells 4:09 pm on July 22, 2009
  
  Ryan won’t be at today’s meeting due to a family emergency. Let’s hold this until next week.
Pingback: Contribute To The Meeting Agenda
banago 1:48 pm on July 21, 2009

I have several suggestions – am I still in time?
- Jane Wells 9:03 pm on July 22, 2009
  
  Agenda already up when this comment posted, can add to next week.
Matt 2:22 pm on July 22, 2009

Discuss change in time for meeting as per results of whenisgood.net
- Jane Wells 9:03 pm on July 22, 2009
  
  Already on agenda, above. 🙂
Mark Jaquith 3:45 pm on July 22, 2009

Discuss closure of 2.0.x branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch".—I want to write a post on the .org blogblog (versus network, site) officially announcing it and touching on some of the reasons why the branch was difficult to support in the last couple of years (mostly because the time period was so long that it made it impossible to keep up with security changes that weren’t just tweaks, but total rethinks of the way we handle certain stuff).

Explain my high level idea for reworking capabilities/roles and discuss potential shortcomings.
- Jane Wells 4:10 pm on July 22, 2009
  
  Sounds good.
- Denis de Bernardy 5:28 pm on July 22, 2009
  
  I thought it was dropped from Debian already?
  - Mark Jaquith 6:16 pm on July 22, 2009
    
    We started the 2.0 LTS branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". before it went into Debian, IIRC. The two things weren’t completely linked. Debian involvement was a royal pain in the butt and had no upsides that I could see (as much as it pains me to say that about my favorite distro).
    
    The main problem was that the security changes going into trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision. were so huge and interconnected with other stuff that merging them into 2.0 was a daunting task, because it wouldn’t just be adapting a 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., but writing completely new code to solve the problem in a way that didn’t depend on all the new stuff available in trunk. It got to the point that we had to say “this minor security issuesecurity issue A security issue is a type of bug that can affect the security of WordPress installations. Specifically, it is a report of a bug that you have found in the WordPress core code, and that you have determined can be used to gain some level of access to a site running WordPress that you should not have. is just not solvable in the 2.0 branch without disruptive changes” and once enough of those piled up, it seemed like a lost cause.
    
    Five years is an eternity in this space—it was an unrealistic goal from the outset.

Comments are closed.

Welcome!

Communication

Share this: