Suggest Agenda Items for March 25th 2010…

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.

Denis de Bernardy 9:38 pm on March 23, 2010

I dunno if this will get considered in 3.0 at the end of the day, but I’d expect a lot of FUD if this gets checked in:

https://core.trac.wordpress.org/ticket/12672
- Denis de Bernardy 9:45 pm on March 23, 2010
  
  Following up and more generally speaking, I’d like to add the following item to the agenda: either we disable wp.org stats entirely in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., or we make the stats public.
  
  If they’re collected for the sake of WP.org, there’s absolutely no reason whatsoever to prevent anyone from accessing them.
  
  If they’re collected for the sake of Automattic, then they don’t belong in WP. Full stop, end of story.
  
  The current situation where they’re collected without being public is outrageous, and these privacy discussions have been ongoing for far too long. It’s time to sort them out once and for all.
  - Peter Westwood 10:01 pm on March 24, 2010
    
    I’m not sure I follow the arguments here and this is the sort of technical issue that the dev chats are meant to focus on.
- Peter Westwood 9:57 pm on March 24, 2010
  
  I don’t see the issue here with bringing over the functionality from wp-mu as part of the merge.
  I think the best place for discussion about what is / isn’t included is probably a tracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. but I will put this at the end of the agenda to allow people to give direct input in the meeting
demetris 9:26 pm on March 24, 2010

Here’s my question for tomorrow’s meeting:

Are we happy with the (non-existent) inline documentation of the new default theme?

This is a genuine question, not a rhetorical one: In my mind, one of the aims of the new theme was to provide high-quality inline documentation, to help people understand and learn. But I don’t know what other people think about this.

As a reference, a theme whose documentation I always found useful and instructive is Tarski. See, for example:

https://themes.trac.wordpress.org/browser/tarski/2.6/library/helpers/content_helper.php
- Andrew Nacin 10:07 pm on March 24, 2010
  
  https://core.trac.wordpress.org/ticket/12695
dd32 9:32 pm on March 24, 2010

Discuss the removal of wp-ajax.php – https://core.trac.wordpress.org/ticket/12400
If we remove it due to the concerns raised, I’d like to be able to point people to a discussion/consensus from the lead devs directly.

It was meant as a replacement for the large ammount of plugins who run ajax directly through their pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party files (and include wp-load.php) or who hook onto template_redirect to handle their front-end ajax, not for administrative tasks of any sort. I just feel this needs to be discussed in a meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. so that can be pointed to down the line as to why it was implemented, and then removed.
Denis de Bernardy 10:21 pm on March 25, 2010

I find it disgusting that:

1. The discussion on inline comments got dismissed to the greet kalends

2. The discussion on privacy issues did so as well.
- demetris 10:37 pm on March 25, 2010
  
  Denis, there is a fresh ticketticket Created for both bug reports and feature development on the bug tracker. for the inline documentation, and we can discuss it there:
  
  https://core.trac.wordpress.org/ticket/12695
  
  If we agree that SOME amount of documentation/comments would be good, then we can use the ticket to arrive at just the right amount.
Denis de Bernardy 10:22 pm on March 25, 2010

/s/greet/Greek/
Chinthaka 4:57 am on March 26, 2010

I have posted my project Idea in the below link and Can you answer me to below questions please.

As I mentioned there Is it ok to give details of what I have done as my project,that describe about wordpress import application that imports posts and comments from a remote wordpress blogblog (versus network, site). And is it ok to mention about that I have study about how blogger and livejournal imports are working in the current WordPress?. Can you please help me with these two questions after reading the proposal…

http://chinthakarukshan.wordpress.com/2010/03/21/google-summer-of-code-proposalwordpress-importexport/

Comments are closed.

Welcome!

Communication

Share this: