do you need www.kde.org write access?

Thu Mar 8 18:53:05 GMT 2018

On 8/03/2018 10:47 PM, "Jaroslaw Staniek" <staniek at kde.org> wrote:

On 8 March 2018 at 09:51, Clemens Toennies <starbuck at netrunner-os.com>
wrote:

> On 08.03.2018 08:44, Boudewijn Rempt wrote:
>
>> On Thursday, 8 March 2018 07:57:27 CET Ben Cooksley wrote:
>>
>>> On Thu, Mar 8, 2018 at 12:42 AM, Boudewijn Rempt <boud at valdyas.org>
>>> wrote:
>>>
>>>> On Wednesday, 7 March 2018 12:31:21 CET Sebastian Kügler wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> We have been working on a modernized website and backend for
>>>>> www.kde.org.
>>>>> The new site will do away with the old PHP custom CMS and will run
>>>>> wordpress instead.
>>>>>
>>>> Does that mean we'll lose our history, just like koffice.org history
>>>> from
>>>> the php times is only in subversion anymore and the wordpress (or
>>>> whatever it was) content is completely gone?
>>>>
>>> The current content of www.kde.org will still remain in Subversion at
>>> the very least.
>>>  From my understanding the plan Sebas has mentioned envisages a
>>> temporary www-legacy.kde.org hostname being kept around until a full
>>> migration is completed.
>>>
>> So we _will_ lose proper access to KDE's release history. That's not good.
>> Pages like  https://www.kde.org/announcements/ and everything it links to
>> should be kept up in eternity.
>>
>
> As far as i can see they will be all available, as they will be imported:
> https://www-backstage.kde.org/announcements/
>

That's very good the content is there. Question I would have to the www
community, are we going to keep exact the same URLs?
This it kind of important key since we link heavily, typically between blog
entry and announcement for example.
I've found our blog content, including blogs.kde.org or forums having dead
links to kde.org.

Technically, maybe URL rewriting would help for URLs that were in
standardized form.

Example of koffice.org as topic harder to handle but possible: currently it
100% redirects to calligra.org but it could redirect from koffice.org/X to
calligra.org/X maybe or calligra.org/koffice/X. Or rewrite the URL so
koffice.org/X would not redirect at all (it depends how we want to have it
presented).

Example link: to http://www.koffice.org/news/koffice-2-1-released/ from the
DOT: https://dot.kde.org/2009/11/24/koffice-21-released.
Missing. So relevant announcements for the history of computing, where we
have a place: software for Nokia n900... it's missing so also Wikipedia
references would be dead. The Wiki must to dig in archive.org now (see "KOffice
1.6 Released" at https://en.wikipedia.org/wiki/KOffice).

Sibling topic is: dead URLs to relatively new software such as
https://download.kde.org/stable/koffice-2.3.3 (link from
https://marc.info/?l=koffice-devel&m=129901230231557). If we have no
resources to share the old files (and mirrors refuse that), maybe we could
at least have a landing page that lists possible options how to find the
archived tarballs?

In relation to tarballs, you will find most of these in the Attic/
directory of download.kde.org

After a while we move things there as we have an agreement with the mirrors
that only carry stable that it will be kept to a certain maximum size.

Even more trouble is missing old image resources but this is lesson to
learn, we still have no ultimate solution IMHO, hash filesbased URLs get
created in share.kde.org and this seems to be fragile approach. I'd think
about at the topic as a matter of Freedom in content area. If we're not
solid here, what can we tell to next generation of contributors that say
"Facebook and YouTube just work".

Then we lost image content on blogs, even image tags seem to be somethow
lost: example https://blogs.kde.org/2004/02/24/one-little-feature, archived
at https://web.archive.org/web/20040531171636/http://www.
kdedevelopers.org:80/node/view/359
No images, no context... :(

Older posts like this can unfortunately be broken with platform migrations
I'm afraid. That particular post has been through two major Drupal upgrades
at least, along with a change in the domain.

While we do our best it is unavoidable that some loss will occur with any
change.

I see the task is not light but preserving KDE history is worth investment
maybe even financial. Blogs are to me part of KDE's identity.
Good part of it is done nicely in the form of preserving the KDE 1.0 / 2.0
desktops.

-- 
regards, Jaroslaw Staniek

Regards,
Ben

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
KEXI:
: A visual database apps builder - http://calligra.org/kexi
  http://twitter.com/kexi_project https://facebook.com/kexi.project
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20180309/2507ade0/attachment.htm>