Setting up page to collect repository corruption reports?

Inspired by a vocal group on users@ which complains about the lack of
repository recovery tools (yet having known corruption problems), I
started to think we need to collect data on corruptions.

My reasoning is that we're currently seeing some corruption reports,
but probably only the tip of the iceberg which can't be solved with
John's fsfsverify tool and then even only those which aren't handled
by Collab, or any of the other commercial support suppliers.

In order to improve our handle on things, I think it would be a good
idea to set up an incident-report page. This page can help gather data
about incidents and the system setup on which it occurred. That way -
I hope - we can start to work out correlations between certain system
setups and certain types of corruption.

The incidents gathering page should help gather all relevant data and
to gather it all at once: the current reports on users@ are far from
complete. Possibly we could collect data on how people solved the
issue, if applicable.

The incident data should be only available to full committers doing
backend stability analysis, unless the submitter agrees on full
disclosure.

What do people say to this idea?

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 14 23:11:26 2007