Hi everyone. A reminder post will go live on the dev blog at 4pm UTC/ 9am Pacific about the 24-hour has-patch marathon that's happening today/tomorrow, but I thought I'd drop a note in here as well. I sent a note to the testers list about testing the almost 200 patches that are currently in Trac, so hopefully a lot of the patches that have been submitted can be committed during the marathon.
There are almost 200 tickets with patches, but over 300 that need a patch. And we haven't even gotten to bug hinting for 2.8. We're in feature freeze for 2.8 as of today, so we'll announce a bug hunt sometime soon. It would be great to clear out some of these existing tickets. If you can make time to write a patch for any of these 300 today, that would be awesome. If you don't have time to code, maybe you could at least help out with the testing? Whatever you can do would be great.
Here are all the 2.8 tickets, if you want to start patching:
Here are the tickets with patches, if you want to start testing:
And if anyone plans to stay up and actually write or test patches for the full 24 hours, let me know. If you're blogging/twittering about it throughout the marathon (saying what tickets you're currently working on or whatever), I might point to you as an example from the WordPress twitter account.
When I put up the results of the marathon on the dev blog on Monday, I'll also link to the top 5 testers and top 5 patch contributors from the 24-hour marathon period, which begins in a few hours at 4pm UTC/ 9am Pacific and runs until 4pm UTC/9am Pacific on Friday.
Hmm this is the first I've heard of this. It would've been sweet if there'd been some advanced notification, I definitely would've set aside time, but now I have stuff to do and won't be able to participate.
It kinda sucks how little communication there is to the wp-hackers list from Automattic. I read the WP dev blog and subscribe to this list, and I haven't heard anything about this until just now. Is there some other location where this type of communication happens? IRC? I'd imagine that anything important mentioned in IRC would have to be archived somewhere like in a mailing list. I feel like this list (and the people who subscribe to it/contribute to Wordpress) have pretty much been ignored/abandoned by Automattic and the core WP team. We have no direction here, and as a consequence spend more time arguing and blowing hot air than getting anything done. Since I don't like wasting my time in this manner, I contribute less to this project than I would like to, and I'm sure I'm not the only one who feels this way.
On Thu, Apr 16, 2009 at 7:39 AM, Jane Wells <j...@automattic.com> wrote: > Hi everyone. A reminder post will go live on the dev blog at 4pm UTC/9am > Pacific about the 24-hour has-patch marathon that's happening > today/tomorrow, but I thought I'd drop a note in here as well. I sent a note > to the testers list about testing the almost 200 patches that are currently > in Trac, so hopefully a lot of the patches that have been submitted can be > committed during the marathon.
> There are almost 200 tickets with patches, but over 300 that need a patch. > And we haven't even gotten to bug hinting for 2.8. We're in feature freeze > for 2.8 as of today, so we'll announce a bug hunt sometime soon. It would be > great to clear out some of these existing tickets. If you can make time to > write a patch for any of these 300 today, that would be awesome. If you > don't have time to code, maybe you could at least help out with the testing? > Whatever you can do would be great.
> Here are all the 2.8 tickets, if you want to start patching:
> Here are the tickets with patches, if you want to start testing:
> And if anyone plans to stay up and actually write or test patches for the > full 24 hours, let me know. If you're blogging/twittering about it > throughout the marathon (saying what tickets you're currently working on or > whatever), I might point to you as an example from the WordPress twitter > account.
> When I put up the results of the marathon on the dev blog on Monday, I'll > also link to the top 5 testers and top 5 patch contributors from the 24-hour > marathon period, which begins in a few hours at 4pm UTC/9am Pacific and > runs until 4pm UTC/9am Pacific on Friday.
<regulatet...@gmail.com> wrote: > Hmm this is the first I've heard of this. It would've been sweet if > there'd been some advanced notification, I definitely would've set > aside time, but now I have stuff to do and won't be able to > participate.
> It kinda sucks how little communication there is to the wp-hackers > list from Automattic. I read the WP dev blog and subscribe to this > list, and I haven't heard anything about this until just now. Is there > some other location where this type of communication happens? IRC? I'd > imagine that anything important mentioned in IRC would have to be > archived somewhere like in a mailing list. I feel like this list (and > the people who subscribe to it/contribute to Wordpress) have pretty > much been ignored/abandoned by Automattic and the core WP team. We > have no direction here, and as a consequence spend more time arguing > and blowing hot air than getting anything done. Since I don't like > wasting my time in this manner, I contribute less to this project than > I would like to, and I'm sure I'm not the only one who feels this way.
> /rant
If you read the dev blog then you should have heard about this 2 days ago when the post was made.
----- Original Message ----- From: "Matt Martz" <mdma...@sivel.net> To: wp-hack...@lists.automattic.com Sent: Thursday, April 16, 2009 10:25:31 AM GMT -05:00 US/Canada Eastern Subject: Re: [wp-hackers] 24-hour has-patch marathon TODAY
On Thu, Apr 16, 2009 at 10:15 AM, Daniel Torreblanca <regulatet...@gmail.com> wrote: > Hmm this is the first I've heard of this. It would've been sweet if > there'd been some advanced notification, I definitely would've set > aside time, but now I have stuff to do and won't be able to > participate.
> It kinda sucks how little communication there is to the wp-hackers > list from Automattic. I read the WP dev blog and subscribe to this > list, and I haven't heard anything about this until just now. Is there > some other location where this type of communication happens? IRC? I'd > imagine that anything important mentioned in IRC would have to be > archived somewhere like in a mailing list. I feel like this list (and > the people who subscribe to it/contribute to Wordpress) have pretty > much been ignored/abandoned by Automattic and the core WP team. We > have no direction here, and as a consequence spend more time arguing > and blowing hot air than getting anything done. Since I don't like > wasting my time in this manner, I contribute less to this project than > I would like to, and I'm sure I'm not the only one who feels this way.
> /rant
If you read the dev blog then you should have heard about this 2 days ago when the post was made.
On Thu, Apr 16, 2009 at 10:25 AM, Matt Martz <mdma...@sivel.net> wrote: > If you read the dev blog then you should have heard about this 2 days > ago when the post was made.
I did read that after the fact - like most people I don't have time to check every blog I read every single day, so 2 days isn't what I'd consider ample notice.
Trite and useless responses don't help anyone and are an example of what sucks about this community. _______________________________________________ wp-hackers mailing list wp-hack...@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-hackers
I think what a few of us are trying to say is, while it was posted on the blog, if Core Devs expect any assistance from the specific group of wp-hackers mailing list subscribers, the advanced warning should have been given _to the wp-hackers mailing list_ as well as on the blog. I myself would have loved to participate in the marathon, but I needed advanced warning to shuffle work around to make time for it, and I didn't (until this incident) subscribe to the dev blog.
[mailto:wp-hackers-boun...@lists.automattic.com] On Behalf Of Daniel Torreblanca Sent: Thursday, April 16, 2009 12:45 PM To: wp-hack...@lists.automattic.com Subject: Re: [wp-hackers] 24-hour has-patch marathon TODAY
On Thu, Apr 16, 2009 at 10:25 AM, Matt Martz <mdma...@sivel.net> wrote: > If you read the dev blog then you should have heard about this 2 days > ago when the post was made.
I did read that after the fact - like most people I don't have time to check every blog I read every single day, so 2 days isn't what I'd consider ample notice.
Trite and useless responses don't help anyone and are an example of what sucks about this community. _______________________________________________ wp-hackers mailing list wp-hack...@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-hackers
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date: 04/16/09 08:12:00 _______________________________________________ wp-hackers mailing list wp-hack...@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-hackers
On Thu, Apr 16, 2009 at 12:53 PM, Silverstein, Jesse
<Jesse.Silverst...@xerox.com> wrote: > I think what a few of us are trying to say is, while it was posted on > the blog, if Core Devs expect any assistance from the specific group of > wp-hackers mailing list subscribers, the advanced warning should have > been given _to the wp-hackers mailing list_ as well as on the blog. I > myself would have loved to participate in the marathon, but I needed > advanced warning to shuffle work around to make time for it, and I > didn't (until this incident) subscribe to the dev blog.
Day in and day out all I see on this list are people whining about this or whining about that.
You don't need a patch marathon or bug hunt to be official to submit a patch, provide feedback or help clean up Trac. Numerous people spend large portions of their free time every day submitting bugs and patches for WordPress and keeping Trac active and up to date with current information. I spend over 40 hours a week of my "free" time giving to the WordPress community. Those who report bugs, submit patches, write plugins, help on the WordPress lists and in the WordPress IRC channel are who make this community great.
Could any of you who are complaining about the short notice be doing this? Why yes you could. Instead you are going to complain that you weren't given enough notice that there was going to be a patch marathon. You complain because you want to make it seem as though you would do the community a great service but cannot because the community and those behind WordPress make it too difficult or inconvenient for you to do so.
Start making the community better by helping out without having to be asked to help out. Don't make it seem like others are preventing you from helping out because they don't give you enough notice that they want your help. This bug hunt is 24-25 hours long. Go home tonight after work and help, stay up an extra hour before going to sleep and help, spend your lunch break tomorrow giving to the community. Make the community better by starting with yourself.
> Start making the community better by helping out without > having to be asked to help out.
When we try, we often get told our ideas are stupid, and when we submit patches they often get turned down w/o discussing better ways to address the issue the patch was submitted to address.
----- Original Message ----- From: "Matt Martz" <mdma...@sivel.net> To: wp-hack...@lists.automattic.com Sent: Thursday, April 16, 2009 1:20:02 PM GMT -05:00 US/Canada Eastern Subject: Re: [wp-hackers] 24-hour has-patch marathon TODAY
On Thu, Apr 16, 2009 at 12:53 PM, Silverstein, Jesse <Jesse.Silverst...@xerox.com> wrote: > I think what a few of us are trying to say is, while it was posted on > the blog, if Core Devs expect any assistance from the specific group of > wp-hackers mailing list subscribers, the advanced warning should have > been given _to the wp-hackers mailing list_ as well as on the blog. I > myself would have loved to participate in the marathon, but I needed > advanced warning to shuffle work around to make time for it, and I > didn't (until this incident) subscribe to the dev blog.
Day in and day out all I see on this list are people whining about this or whining about that.
You don't need a patch marathon or bug hunt to be official to submit a patch, provide feedback or help clean up Trac. Numerous people spend large portions of their free time every day submitting bugs and patches for WordPress and keeping Trac active and up to date with current information. I spend over 40 hours a week of my "free" time giving to the WordPress community. Those who report bugs, submit patches, write plugins, help on the WordPress lists and in the WordPress IRC channel are who make this community great.
Could any of you who are complaining about the short notice be doing this? Why yes you could. Instead you are going to complain that you weren't given enough notice that there was going to be a patch marathon. You complain because you want to make it seem as though you would do the community a great service but cannot because the community and those behind WordPress make it too difficult or inconvenient for you to do so.
Start making the community better by helping out without having to be asked to help out. Don't make it seem like others are preventing you from helping out because they don't give you enough notice that they want your help. This bug hunt is 24-25 hours long. Go home tonight after work and help, stay up an extra hour before going to sleep and help, spend your lunch break tomorrow giving to the community. Make the community better by starting with yourself.
First of all, I don't think I'm a whiner or a complainer. And secondly, if there are problems in a community, it is up to the community members to fix them. And fixing them requires *communication* from interested parties. I've spent HOURS working on patches only to have them dismissed outright with no discussion, no advice. I've spent my fair share of time tackling Trac issues, so don't presume to tell me what's what here. There's nothing wrong with wanting a little bit of extra notice for a combined effort.
I seriously don't know why you're so defensive about this. Do you think my points are not valid? If you actually believe that the communication/support in this community is at the level that it should be, then you obviously need to look at some other projects and see how they run things.
On Thu, Apr 16, 2009 at 1:20 PM, Matt Martz <mdma...@sivel.net> wrote: > On Thu, Apr 16, 2009 at 12:53 PM, Silverstein, Jesse > <Jesse.Silverst...@xerox.com> wrote: >> I think what a few of us are trying to say is, while it was posted on >> the blog, if Core Devs expect any assistance from the specific group of >> wp-hackers mailing list subscribers, the advanced warning should have >> been given _to the wp-hackers mailing list_ as well as on the blog. I >> myself would have loved to participate in the marathon, but I needed >> advanced warning to shuffle work around to make time for it, and I >> didn't (until this incident) subscribe to the dev blog.
> Day in and day out all I see on this list are people whining about > this or whining about that.
> You don't need a patch marathon or bug hunt to be official to submit a > patch, provide feedback or help clean up Trac. Numerous people spend > large portions of their free time every day submitting bugs and > patches for WordPress and keeping Trac active and up to date with > current information. I spend over 40 hours a week of my "free" time > giving to the WordPress community. Those who report bugs, submit > patches, write plugins, help on the WordPress lists and in the > WordPress IRC channel are who make this community great.
> Could any of you who are complaining about the short notice be doing > this? Why yes you could. Instead you are going to complain that you > weren't given enough notice that there was going to be a patch > marathon. You complain because you want to make it seem as though you > would do the community a great service but cannot because the > community and those behind WordPress make it too difficult or > inconvenient for you to do so.
> Start making the community better by helping out without having to be > asked to help out. Don't make it seem like others are preventing you > from helping out because they don't give you enough notice that they > want your help. This bug hunt is 24-25 hours long. Go home tonight > after work and help, stay up an extra hour before going to sleep and > help, spend your lunch break tomorrow giving to the community. Make > the community better by starting with yourself.
Mike Schinkel wrote: > "Matt Martz" <mdma...@sivel.net> wrote:
>> If you read the dev blog then you should have heard >> about this 2 days ago when the post was made.
> 2 days is still very short notice.
I agree. Especially when one of those days is Tax Day here in the U.S. I was one of the procrastinators who spent all day yesterday finishing up my taxes (and really it wasn't just procrastination -- my family has had a lot going on that made it hard to make time for it before now), so I didn't see the info about it until this morning. If it had been scheduled about a week later, I might have been able to participate in some patch testing/creation. :-/
That said, I think the original complaint kind of banged on Automattic a bit unfairly. There's nothing to stop us "regular" WP community members from contributing our thoughts, code, patches, testing, etc. at any given time. On the other hand, since Automattic *does* basically have the role of Benevolent Dictator, it *would* be nice if they'd lay out the Roadmap a little more clearly/transparently and communicate upcoming milestones/deadlines in advance.
I think it will be better if you stopped this discussion and found some patches to test or to add to the opened tickets, wasting your time in a letter typed here - that won't change something that is already on - can be a letter in the code typed there.
Thanks in Advance!
On Thu, Apr 16, 2009 at 10:58 PM, Dougal Campbell <dou...@gunters.org>wrote:
>>> If you read the dev blog then you should have heard about this 2 days ago >>> when the post was made.
>> 2 days is still very short notice.
> I agree. Especially when one of those days is Tax Day here in the U.S. I > was one of the procrastinators who spent all day yesterday finishing up my > taxes (and really it wasn't just procrastination -- my family has had a lot > going on that made it hard to make time for it before now), so I didn't see > the info about it until this morning. If it had been scheduled about a week > later, I might have been able to participate in some patch testing/creation. > :-/
> That said, I think the original complaint kind of banged on Automattic a > bit unfairly. There's nothing to stop us "regular" WP community members from > contributing our thoughts, code, patches, testing, etc. at any given time. > On the other hand, since Automattic *does* basically have the role of > Benevolent Dictator, it *would* be nice if they'd lay out the Roadmap a > little more clearly/transparently and communicate upcoming > milestones/deadlines in advance.
OK, well then. Two months ago I found a bug, created a trivial test case to prove it, put it in Trac (see: http://core.trac.wordpress.org/ticket/9146), immediately put in the appropriate patch -- exactly as I was told to here. Nothing has happened to it. AFAIK, nobody with any power has even looked at it. No feedback, no action, nada.
Hard to get excited about finding and fixing bugs when the process is obtuse and with little/no feedback.
> I think it will be better if you stopped this discussion and found some > patches to test or to add to the opened tickets, wasting your time in a > letter typed here - that won't change something that is already on - can be > a letter in the code typed there.
> Thanks in Advance!
> On Thu, Apr 16, 2009 at 10:58 PM, Dougal Campbell <dou...@gunters.org>wrote:
>>>> If you read the dev blog then you should have heard about this 2 days ago >>>> when the post was made.
>>> 2 days is still very short notice.
>> I agree. Especially when one of those days is Tax Day here in the U.S. I >> was one of the procrastinators who spent all day yesterday finishing up my >> taxes (and really it wasn't just procrastination -- my family has had a lot >> going on that made it hard to make time for it before now), so I didn't see >> the info about it until this morning. If it had been scheduled about a week >> later, I might have been able to participate in some patch testing/creation. >> :-/
>> That said, I think the original complaint kind of banged on Automattic a >> bit unfairly. There's nothing to stop us "regular" WP community members from >> contributing our thoughts, code, patches, testing, etc. at any given time. >> On the other hand, since Automattic *does* basically have the role of >> Benevolent Dictator, it *would* be nice if they'd lay out the Roadmap a >> little more clearly/transparently and communicate upcoming >> milestones/deadlines in advance.
On Apr 16, 2009, at 5:03 PM, Chris Williams wrote:
> OK, well then. Two months ago I found a bug, created a trivial test > case to > prove it, put it in Trac (see: http://core.trac.wordpress.org/ticket/9146) > , > immediately put in the appropriate patch -- exactly as I was told to > here. > Nothing has happened to it. AFAIK, nobody with any power has even > looked at > it. No feedback, no action, nada.
> Hard to get excited about finding and fixing bugs when the process > is obtuse > and with little/no feedback.
> From: Chris Williams <ch...@clwill.com> > Reply-To: <wp-hack...@lists.automattic.com> > Date: Thu, 16 Apr 2009 16:03:25 -0700 > To: <wp-hack...@lists.automattic.com> > Subject: Re: [wp-hackers] 24-hour has-patch marathon TODAY
> OK, well then. Two months ago I found a bug, created a trivial test case to > prove it, put it in Trac (see: http://core.trac.wordpress.org/ticket/9146), > immediately put in the appropriate patch -- exactly as I was told to here. > Nothing has happened to it. AFAIK, nobody with any power has even looked at > it. No feedback, no action, nada.
> Hard to get excited about finding and fixing bugs when the process is obtuse > and with little/no feedback.
>> I think it will be better if you stopped this discussion and found some >> patches to test or to add to the opened tickets, wasting your time in a >> letter typed here - that won't change something that is already on - can be >> a letter in the code typed there.
>> Thanks in Advance!
>> On Thu, Apr 16, 2009 at 10:58 PM, Dougal Campbell <dou...@gunters.org>wrote:
>>>>> If you read the dev blog then you should have heard about this 2 days ago >>>>> when the post was made.
>>>> 2 days is still very short notice.
>>> I agree. Especially when one of those days is Tax Day here in the U.S. I >>> was one of the procrastinators who spent all day yesterday finishing up my >>> taxes (and really it wasn't just procrastination -- my family has had a lot >>> going on that made it hard to make time for it before now), so I didn't see >>> the info about it until this morning. If it had been scheduled about a week >>> later, I might have been able to participate in some patch testing/creation. >>> :-/
>>> That said, I think the original complaint kind of banged on Automattic a >>> bit unfairly. There's nothing to stop us "regular" WP community members from >>> contributing our thoughts, code, patches, testing, etc. at any given time. >>> On the other hand, since Automattic *does* basically have the role of >>> Benevolent Dictator, it *would* be nice if they'd lay out the Roadmap a >>> little more clearly/transparently and communicate upcoming >>> milestones/deadlines in advance.
On Thu, 16 Apr 2009 16:03:25 -0700, Chris Williams <ch...@clwill.com> wrote:
> Hard to get excited about finding and fixing bugs when the process is > obtuse > and with little/no feedback.
I agree. I put in a patch for a nasty bug several months ago (http://core.trac.wordpress.org/ticket/6035), and it's gone nowhere. I've released a plugin in the meantime to help people affected by the problem, but this could easily have been part of 2.7.1 if someone had looked at it.
The has-patch marathon is great. I'm really glad it's happening. I wish I had a better idea of how to contribute without letting my patches languish until the next marathon rolls around.
I look at *a lot* of 'has-patch' tickets, however, most of the patches that were submitted were not matching up with the current changeset. So half the time was spent either trying to merge it together or do it manually.
Some of them was to crazy and we moved to them to 'needs-patch' again.
People gotta realize that patches need to stay updated along with the current changeset. Otherwise there is no way for us to easily check out the code and mark it 'tested commit'.
Stephanie Leary wrote: > On Thu, 16 Apr 2009 16:03:25 -0700, Chris Williams <ch...@clwill.com> > wrote: >> Hard to get excited about finding and fixing bugs when the process is >> obtuse >> and with little/no feedback.
> I agree. I put in a patch for a nasty bug several months ago > (http://core.trac.wordpress.org/ticket/6035), and it's gone nowhere. I've > released a plugin in the meantime to help people affected by the problem, > but this could easily have been part of 2.7.1 if someone had looked at it.
> The has-patch marathon is great. I'm really glad it's happening. I wish I > had a better idea of how to contribute without letting my patches languish > until the next marathon rolls around.
On Thu, Apr 16, 2009 at 12:39 PM, Jane Wells <j...@automattic.com> wrote:
> Hi everyone. A reminder post will go live on the dev blog at 4pm UTC/9am > Pacific about the 24-hour has-patch marathon that's happening > today/tomorrow, but I thought I'd drop a note in here as well.
Hi Jane, Core Devs and Automatticians,
Sadly I didn't get as involved as I would have liked to * but it was good to see this take place and I hope that the marathon is repeated at a similar point in the 2.9 dev process, is that a possibility?
Thanks!
S
* Sorry, just two patches as I managed to get seriously stuffed with my schedules this week :\
--- Sweet Interaction Ltd is Registered in England/Wales, no. 6610741 Registered office: 7 Malton Av, Manchester, M21 8AT _______________________________________________ wp-hackers mailing list wp-hack...@lists.automattic.com http://lists.automattic.com/mailman/listinfo/wp-hackers
On Fri, Apr 17, 2009 at 1:06 PM, Stephanie Leary <st...@sillybean.net> wrote: > The has-patch marathon is great. I'm really glad it's happening. I wish I > had a better idea of how to contribute without letting my patches languish > until the next marathon rolls around.
The best advice is to write your patches when you know you will be able to spend some time promoting them, then right after they are ready post your Trac ticket (with as much information as possible both about your problem/use-cases and about your solution) and go into #wordpress-dev IRC channel** and ask for a core dev to look at them. Sometimes no one is around/available but if you ping every half hour or so eventually someone will help you.
Ask if your patch/ticket makes sense, ask if they can test it, ask what you need to do. This has been the best system for me and has gotten me lots of important help that made my patches worth committing. Remember that they seem perfect to you but they just arent', there are things you didn't think of, and live chat with a core dev is the fastest way to find those problems and at the same time build up some trust with that core dev that your patch is important/necessary/safe.
If you don't get it committed that day then buck up and try again another day. You'll need to get your local install of WP up to the latest SVN version and make sure your patch still works and doesn't need editing, update the trac ticket if necessary, and start asking about it some more.
It's not a quick or easy system but I'm kind of glad it isn't, otherwise anyone's crappy, ill-considered patch with no oversight could get in, then we'd have to change the name of the project to TikiBlog :P
** on the irc.freenode.net server, you can sign in using http://mibbit.com/chat/ as a web frontend for IRC if you don't have a program like the wonderful Colloquy. Don't be afraid of IRC, it's like IM but with way more people in it! http://codex.wordpress.org/IRC
> On Fri, Apr 17, 2009 at 1:06 PM, Stephanie Leary > <st...@sillybean.net> wrote: >> The has-patch marathon is great. I'm really glad it's happening. I >> wish I >> had a better idea of how to contribute without letting my patches >> languish >> until the next marathon rolls around.
> The best advice is to write your patches when you know you will be > able to spend some time promoting them, then right after they are > ready post your Trac ticket (with as much information as possible both > about your problem/use-cases and about your solution) and go into > #wordpress-dev IRC channel** and ask for a core dev to look at them. > Sometimes no one is around/available but if you ping every half hour > or so eventually someone will help you.
> Ask if your patch/ticket makes sense, ask if they can test it, ask > what you need to do. This has been the best system for me and has > gotten me lots of important help that made my patches worth > committing. Remember that they seem perfect to you but they just > arent', there are things you didn't think of, and live chat with a > core dev is the fastest way to find those problems and at the same > time build up some trust with that core dev that your patch is > important/necessary/safe.
> If you don't get it committed that day then buck up and try again > another day. You'll need to get your local install of WP up to the > latest SVN version and make sure your patch still works and doesn't > need editing, update the trac ticket if necessary, and start asking > about it some more.
> It's not a quick or easy system but I'm kind of glad it isn't, > otherwise anyone's crappy, ill-considered patch with no oversight > could get in, then we'd have to change the name of the project to > TikiBlog :P
> ** on the irc.freenode.net server, you can sign in using > http://mibbit.com/chat/ as a web frontend for IRC if you don't have a > program like the wonderful Colloquy. Don't be afraid of IRC, it's like > IM but with way more people in it! http://codex.wordpress.org/IRC
I hate to beat a dead horse here, but while I think these suggestions are sound and helpful, I'm so incredibly disappointed with automattic. The original poster (and employee of automattic) didn't even reply to my statement - instead of discussion I received needlessly defensive and angry replies (and a few decent ones).
I've been involved with several open source (and non open source) distributed projects over the years and greatly enjoy volunteering my time and work to get things accomplished as well as the community participation. Unfortunately, I don't like the way in which this project is handled, and have a major problem with contributing to a project where I have to spend more time running around convincing people to take a look at what I've done and soliciting feedback (which rarely happens) than it takes to actually do the work. Because there doesn't seem to be true leadership/direction here, the volunteer aspect of this all seems like a grossly inefficient and unappreciated waste of time.
While there are several great people on this list, from which I've managed to learn a thing or two, that seems to be the exception rather than the rule. Most of what I read here is hot air, arguments and a whole lot of nothing, to be honest. So I'm outta here. Good luck wp hackers! :)
- Daniel
On Tue, Apr 21, 2009 at 12:01 PM, Jennifer Hodgdon
Daniel Torreblanca wrote: > I hate to beat a dead horse here, but while I think these suggestions > are sound and helpful, I'm so incredibly disappointed with automattic. > The original poster (and employee of automattic) didn't even reply to > my statement - instead of discussion I received needlessly defensive > and angry replies (and a few decent ones).
> I've been involved with several open source (and non open source) > distributed projects over the years and greatly enjoy volunteering my > time and work to get things accomplished as well as the community > participation. Unfortunately, I don't like the way in which this > project is handled, and have a major problem with contributing to a > project where I have to spend more time running around convincing > people to take a look at what I've done and soliciting feedback (which > rarely happens) than it takes to actually do the work. Because there > doesn't seem to be true leadership/direction here, the volunteer > aspect of this all seems like a grossly inefficient and unappreciated > waste of time.
> While there are several great people on this list, from which I've > managed to learn a thing or two, that seems to be the exception rather > than the rule. Most of what I read here is hot air, arguments and a > whole lot of nothing, to be honest. So I'm outta here. Good luck wp > hackers! :)
> - Daniel
> On Tue, Apr 21, 2009 at 12:01 PM, Jennifer Hodgdon > <yah...@poplarware.com> wrote:
>> Stephen Rider wrote:
>>> Wow. Jeremy's email should be posted to the list once a month. :)
>> Or perhaps added to the Codex in the section about contributing patches.
>> -- Jennifer
>> -- >> Jennifer Hodgdon * Poplar ProductivityWare >> www.poplarware.com >> Drupal, WordPress, and custom Web programming
On Fri, Apr 17, 2009 at 7:03 AM, Chris Williams <ch...@clwill.com> wrote: > immediately put in the appropriate patch -- exactly as I was told to here. > Nothing has happened to it. AFAIK, nobody with any power has even looked at > it. No feedback, no action, nada.
Two months is simply nothing. Almost a whole year for me on a few lines that's improvement and doesn't affect existing functionality. I'm not even allowed to remove my own ticket now.
>> I think it will be better if you stopped this discussion and found some >> patches to test or to add to the opened tickets, wasting your time in a >> letter typed here - that won't change something that is already on - can be >> a letter in the code typed there.
>> Thanks in Advance!
>> On Thu, Apr 16, 2009 at 10:58 PM, Dougal Campbell <dou...@gunters.org>wrote:
>>>>> If you read the dev blog then you should have heard about this 2 days ago >>>>> when the post was made.
>>>> 2 days is still very short notice.
>>> I agree. Especially when one of those days is Tax Day here in the U.S. I >>> was one of the procrastinators who spent all day yesterday finishing up my >>> taxes (and really it wasn't just procrastination -- my family has had a lot >>> going on that made it hard to make time for it before now), so I didn't see >>> the info about it until this morning. If it had been scheduled about a week >>> later, I might have been able to participate in some patch testing/creation. >>> :-/
>>> That said, I think the original complaint kind of banged on Automattic a >>> bit unfairly. There's nothing to stop us "regular" WP community members from >>> contributing our thoughts, code, patches, testing, etc. at any given time. >>> On the other hand, since Automattic *does* basically have the role of >>> Benevolent Dictator, it *would* be nice if they'd lay out the Roadmap a >>> little more clearly/transparently and communicate upcoming >>> milestones/deadlines in advance.
> Two months is simply nothing. > Almost a whole year for me on a few lines that's improvement and > doesn't affect existing functionality. I'm not even allowed to remove > my own ticket now.
Perhaps we should start tagging simple patches with the tag "simple" or "quick" in the hope that it will be reviewed faster?
Of course this defacto standard would need some publicity to be helpful.
|
