"church.of.emacs.ml" <church.of.emacs.ml(a)googlemail.com> wrote in message
news:4BF2632F.8000301@googlemail.com...
Hi,
There's another discussion happening at
enwiki at the moment about the
stalled rollout of RevisionDelete for admins; which is backed up in the
chain of bugs which boils down to "our deletion mechanism is borked".
Indeed. Basically, we have two deletion schemas in parallel at the
moment, one of which is only half-complete, the other one sucks in many
ways.
I don't know if others share that view, but imho the long-term goal is
to make RevisionDelete powerful enough to eventually replace the old
deletion schema.
See also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=21279#c7
Reviewing the whole deletion mechanism was on the
topic list for the last
dev meetup, but AFAIK despite that event running for three times as long
as
it was expected to, it never got raised? I think this would be as good a
time as any to do so. Do we have any clear idea or overall plan for page
and revision deletion, the archive table, a page_deleted field, a
deleted_page table, etc etc??
I don't know why you think the meetup was three times as long as
expected. Just because some devs were stuck in Berlin doesn't mean the
conference magically continued on these days.
That *was* a joke... :-P
I think fundamentally this is an area where a solution which is
super-efficient at *everything* is technically impossible, and we have
various methods, implemented or proposed, which resolve some issues at the
expense of others. It's mainly a question of working out what we definitely
need to achieve, and what we can afford to be expensive/slow actions (for
instance, one out of reading deleted revisions, and *restoring* deleted
revisions, pretty much has to be expensive). Right now everyone who has
ideas for *an* implementation isn't working on it because they don't know if
it's *the* implementation we want.
--HM