Am 18.08.2006 um 07:10 schrieb Tom Gregory:
Thomas,
Sorry for the delayed reply. This is the first time since the
release that the bug tracker has worked for me, despite several
attempts daily. (It failed a couple of times today too.)
Hi there!
I *think* the server move is now complete, so everything should more
or less work fine now.
There are still a few issues with scrolling and draggables. Bug
5017 has references to several of them, and the patch suggested
there can be implemented independent of the other scrolling drag/
drop issues.
Applied. :)
I also have some more general questions. The bottom line here is,
I want to help, but am a "guest" in your "house"--I don't want to
be figuratively rearranging the furniture without your permission.
A set of posted community standards would be helpful to me.
Specifically: Do you want our help filtering the bug list? What's
the best way to go about it--do you have some "moderator"
guidelines available?
I definitely could use some help on filtering the list out. Basically
everything should be thrown out that's either > 4 months old (time of
last release), or where there is not enough information (including no
test cases, non-working urls, ambigous reports) and the reporter
doesn't answer to comments to complete it within a reasonable time
frame (i'd say a month). These should be closed as "invalid".
Also, all requests that are purely being support questions should be
redirected to this mailing list, and closed as "invalid".
See bug 2766, for example. The problem is most likely with the
submitter's style sheet, not Scriptaculous. Despite two requests
for a test case, the submitter hasn't responded in six months. Do
you want our help in closing these bugs?
Yes. :)
If you wish to retain control over closing bugs, may I suggest a
common set of helper keywords, such as "DUPLICATE", "NOTABUG", and/
or "ABANDONED"?
As I don't want to retain control over this, no. But see also the
next question.
Other questions regarding the bug tracker:
1. Is there a better way to filer by Scriptaculous component? For
example, Draggables, Effects, Builder, etc. I'm significantly more
comfortable in the Draggable code than in the Builder code, for
example. Is there a custom field or set of accepted keywords that
can make filtering the list a bit easier?
I'd say we should use these keywords: "effects", "builder",
"controls", "unittest", "dragdrop", for a start (so the library file
name minus the ".js").
2. Is there a way for us to indicate "votes" for a particular bug/
patch in a way that will appear on the search results list?
I guess not really. What we can do is add a "final" keyword (maybe
someone can think of a better name?) that
indicates fully-tested (including unit tests and functional tests, as
a requirement), cross-browser verified,
ready-to-apply patches, and a "vote" keyword to indicate tickets that
have some voting ("+1") going on in the comments.
3. What methods are in place to reduce/eliminate comment spam?
I guess some of the spam was elimanted with the server move. If there
should be any more issues, I can ping the admins.
Best,
Thomas
Regards,
Tom Gregory
_______________________________________________
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
