[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Should we mark #388141 as jessie-ignore?



On Mon, 16 Feb 2015 18:30:44 +0100
Tomas Pospisek <tpo2@sourcepole.ch> wrote:
> Am 13.02.2015 um 21:15 schrieb Riley Baird:
> > On Thu, 12 Feb 2015 21:16:39 +0100
> > Tomas Pospisek <tpo2@sourcepole.ch> wrote:
> >> Am 12.02.2015 um 20:59 schrieb Riley Baird:
> >>
> >>> Bug #388141 [RC] refers to the relicensing of the debian www pages.
> >>> After contacting debian-www, it seems that there isn't much interest in
> >>> fixing it.
> >>
> >> I interpret the relative silence in #388141 differently then you. I'd
> >> say that everybody is busy with doing other stuff. So if you want the
> >> state of affairs to change, just go after it, bit by bit. As you
> >> describe here:
> >>
> >>> The next step would involve compiling a list of website
> >>> lines which are still active yet which relicensing permission has not
> >>> been received.
> >>
> >> And then just ask for permission, line by line.
> > 
> > Surprisingly not! Everyone who has been contacted has already been contacted. The reason for collecting these lines is that we need to determine whether the lines in question are copyrightable, and whether they are still in use.
> > 
> >> In the end I think it's work and if it should be accomplished then
> >> someone has to do that work. Since you are interested, just go and hit
> >> the work, it may well be that people will join or help you along the way.
> > 
> > I've always been happy to do the work, but I thought that access to the wiki databases was necessary to compile such a list. Or is it possible to compile such a list with just a user account on the wiki?
> 
> I'm not sure I really understand what you want to do.
> 
> Is something like this:
> 
>   https://wiki.debian.org/LXC?action=info
> 
> not what you need?

Kind of, but it's only for that one article. Is there something similar
that lists all edits to the wiki itself like that? If not, I could make
one by downloading the revision histories for all pages on the wiki and
then parsing them, but this might place strain on the server (and would
be much more difficult).

Attachment: pgpqPUgqEIp5t.pgp
Description: PGP signature


Reply to: