Hi. My name is Nathan Hammond. I'm new here. I also plan to stick
around. But so that I'm not just taking up space, I figured I should
come up with something to do.
So, that thing is to one by one go through all outstanding tickets in
Trac and see them through to a resolution. Reporter didn't provide a
test case? I'll try and create one. Browser-related problem? If it
isn't a Mac browser, I'll put the browser through its paces. If it is
to be resolved by a change to jQuery, I'll provide a patch. If the
patch is not trivial I will bring it up for discussion here. If the
change is worthy of creating or modifying a test, I'll do it. If it
necessitates a change in the documentation, I'll make that change. And
then I'll move on to the next one. My goal is to have only a small set
of outstanding tickets, of which all are actively being worked on.
All of my patches will be targeted at the head revision and will not
be intended for porting back to old versions. At the beginning I'll be
choosing the easy ones or ones that interest me. As I become more
familiar with the library in its entirety I'll tackle more difficult
items.
I look forward to the challenge, and put my name on it so you can hold
me to it.
Nathan Hammond
That's fantastic news and exactly what I would recommend, as well. Be sure to drop emails here to the list so that we know what you're up to (and so that we can provide feedback, commit patches, etc.).
Be sure to ask Ariel Flesler if you have any questions - he does work very similar to what you've outlined.
> Hi. My name is Nathan Hammond. I'm new here. I also plan to stick > around. But so that I'm not just taking up space, I figured I should > come up with something to do.
> So, that thing is to one by one go through all outstanding tickets in > Trac and see them through to a resolution. Reporter didn't provide a > test case? I'll try and create one. Browser-related problem? If it > isn't a Mac browser, I'll put the browser through its paces. If it is > to be resolved by a change to jQuery, I'll provide a patch. If the > patch is not trivial I will bring it up for discussion here. If the > change is worthy of creating or modifying a test, I'll do it. If it > necessitates a change in the documentation, I'll make that change. And > then I'll move on to the next one. My goal is to have only a small set > of outstanding tickets, of which all are actively being worked on.
> All of my patches will be targeted at the head revision and will not > be intended for porting back to old versions. At the beginning I'll be > choosing the easy ones or ones that interest me. As I become more > familiar with the library in its entirety I'll tackle more difficult > items.
> I look forward to the challenge, and put my name on it so you can hold > me to it. > Nathan Hammond
You may want to get in touch with Ariel Flesler, who is currently the primary core maintainer. He should be able to give you some background on a lot of the open tickets. These days most tickets are either invalid (reporter should have asked on the mailing list instead), or very trick/nearly impossible to solve.
To prioritize enhancements/features, take a look at the roadmap for 1.3: http://docs.jquery.com/JQuery_1.3_Roadmap In general, filesize and performance are the two important factors to keep in mind. A bugfix shouldn't make both worse.
> Hi. My name is Nathan Hammond. I'm new here. I also plan to stick > around. But so that I'm not just taking up space, I figured I should > come up with something to do.
> So, that thing is to one by one go through all outstanding tickets in > Trac and see them through to a resolution. Reporter didn't provide a > test case? I'll try and create one. Browser-related problem? If it > isn't a Mac browser, I'll put the browser through its paces. If it is > to be resolved by a change to jQuery, I'll provide a patch. If the > patch is not trivial I will bring it up for discussion here. If the > change is worthy of creating or modifying a test, I'll do it. If it > necessitates a change in the documentation, I'll make that change. And > then I'll move on to the next one. My goal is to have only a small set > of outstanding tickets, of which all are actively being worked on.
> All of my patches will be targeted at the head revision and will not > be intended for porting back to old versions. At the beginning I'll be > choosing the easy ones or ones that interest me. As I become more > familiar with the library in its entirety I'll tackle more difficult > items.
> I look forward to the challenge, and put my name on it so you can hold > me to it. > Nathan Hammond
|
