i2 patches and tickets

I'm working a little project to clean up the rails trac system. I
found a ton of tickets for an old app called i2 in the rails repo. I
believe it has been abandoned and all these tickets are sitting there
with modification dates over 1 year ago. I was just wondering if
anyone would have a problem with me closing them all. There is like 10
open ones.

I'm working a little project to clean up the rails trac system. I
found a ton of tickets for an old app called i2 in the rails repo. I
believe it has been abandoned and all these tickets are sitting there
with modification dates over 1 year ago. I was just wondering if
anyone would have a problem with me closing them all. There is like 10
open ones.

Isn't i2 the wiki? Perhaps the dudes slaving away on keeping the
wiki spam free can evaluate and close them.

Koz, do you mind me or other volunteers going through unprocessed
patches and tagging/filing them were they belong? Or should this be
for core members only.

I'm just looking for a way to help process the good number of patches
in Trac.

Koz, do you mind me or other volunteers going through unprocessed
patches and tagging/filing them were they belong? Or should this be
for core members only.

I'm just looking for a way to help process the good number of patches
in Trac.

The more the merrier! There's a lot of stuff in there which should
be triaged, things like no tests, no longer applies cleanly,
introduces failing tests etc. We have full history, so the worst you
can do is offend someone, there'll be no data loss, and they can just
reopen the ticket.

Good, good. My goal is get unprocessed patches down to a manageable
number. Then start sorting through needy and unverified ones.

Michael Koziarski wrote:

I'm working a little project to clean up the rails trac system. I
found a ton of tickets for an old app called i2 in the rails repo. I
believe it has been abandoned and all these tickets are sitting there
with modification dates over 1 year ago. I was just wondering if
anyone would have a problem with me closing them all. There is like 10
open ones.

Isn't i2 the wiki? Perhaps the dudes slaving away on keeping the
wiki spam free can evaluate and close them.

Yes, i2 is the wiki.

Josh, if you could send me (justin@j-m-f.demon.co.uk) the ticket numbers I'll look them over. I'm pretty sure we should close them all as "wontfix" (or whatever the Trac equivalent is), as the i2 held in the Rails repository is not the one being used to run the Rails wiki, and hasn't had a maintainer for some time. But I'd like to take a look, in case there are some useful ideas there.

By the way, Koz, since we got Rob Sanheim's logic CAPTCHA installed two weeks ago "slaving away" at the spam seems to be a thing of the past (fingers crossed). We were getting up to 3000 page updates a day before putting the CAPTCHA on; now it's more like 30 (and most of those seem to be a couple of people fighting over the RailsWebHosts page).

regards

   Justin Forder

http://dev.rubyonrails.org/query?status=new&status=assigned&status=reopened&component=Web&summary=~[PATCH]&order=priority

Josh Peek wrote:

Josh, if you could send me (justin@j-m-f.demon.co.uk) the ticket numbers
I'll look them over. I'm pretty sure we should close them all as
"wontfix" (or whatever the Trac equivalent is), as the i2 held in the
Rails repository is not the one being used to run the Rails wiki, and
hasn't had a maintainer for some time. But I'd like to take a look, in
case there are some useful ideas there.

http://dev.rubyonrails.org/query? status=new&status=assigned&status=reopened&component=Web&summary=%7E% 5BPATCH%5D&order=priority

Thanks - that gives me #2573, #2715, #2355 and #3789.

#2573 is a genuine defect, but duplicates #2668, which is closed/fixed.
The fix for #2668 was in Alexey's branch (changeset [2857]).
The current live wiki code has exactly what the update to ticket #2573 is asking for:

   http://svn.jufo.org/i2_rails/trunk/app/controllers/books_controller.rb

I suggest you add a comment that this duplicates #2669 and close with resolution 'duplicate'.

#2715 is an enhancement (so I don't think your keyword of 'unverified' really fits). Please close as 'wontfix'.

#2355 claims to be a defect, but is actually an enhancement. Please change the type and close as 'wontfix'.
(Chad/Dieter: This ticket is moderately interesting, in that any technique for finding inbound links could be used for making page cache expiry on new page creation more focussed than it is at present).

#3789 is an enhancement. Please close as 'wontfix'. Ryan is a good guy (Locomotive author), so consider adding a comment explaining that i2 is no longer actively maintained.

If you would rather I made any of these changes I'll be happy to.

regards

   Justin Forder

Done! Thanks for your help. Much appreciated.

-- Josh Peek