Hey,
A few weeks ago Micheal Martin posted bug 544 [1] on the tracker. The bug report has sparked an interest in preserving the tutorials and documentation that exists on the KDE servers for KDE 3.5. Much of this information could be potentially useful to new developers, and it will give us insight into previous development and practices.
I have started transferring pages from the KDE techbase, but there are also many external links and other misc pages floating around the Internet. Many of these links are broken, but can be found on the Wayback Machine [2]. There are entire websites that have been saved on the Wayback Machine as well.
The purpose of this email is to figure out what to do, and recruit any interestoied parties to help out.
Should we just link to the archived pages? Should we copy them to our own web server?
I am just getting started and this will be an ongoing project. So far I have just created one page on the Wiki, the Developers Tutorial [3]. It is to be the central hub for development pages.
Any r / Comments would be appreciated.
Calvin Morrison
[1] http://bugs.trinitydesktop.org/show_bug.cgi?id=544 [2] http://www.archive.org/web/web.php [3] http://www.trinitydesktop.org/wiki/bin/view/Documentation/DeveloperTutorial
Hey,
A few weeks ago Micheal Martin posted bug 544 [1] on the tracker. The bug report has sparked an interest in preserving the tutorials and documentation that exists on the KDE servers for KDE 3.5. Much of this information could be potentially useful to new developers, and it will give us insight into previous development and practices.
I have started transferring pages from the KDE techbase, but there are also many external links and other misc pages floating around the Internet. Many of these links are broken, but can be found on the Wayback Machine [2]. There are entire websites that have been saved on the Wayback Machine as well.
The purpose of this email is to figure out what to do, and recruit any interestoied parties to help out.
Should we just link to the archived pages? Should we copy them to our own web server?
I am just getting started and this will be an ongoing project. So far I have just created one page on the Wiki, the Developers Tutorial [3]. It is to be the central hub for development pages.
Any r / Comments would be appreciated.
Calvin Morrison
[1] http://bugs.trinitydesktop.org/show_bug.cgi?id=544 [2] http://www.archive.org/web/web.php [3] http://www.trinitydesktop.org/wiki/bin/view/Documentation/DeveloperTutorial
Copying the pages to our servers (the Wiki to be precise) is by far the best way to go. That would allow us to easily edit parts of the TechBase that are obsolete or incomplete.
Tim
On 24 October 2011 13:22, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
Hey,
A few weeks ago Micheal Martin posted bug 544 [1] on the tracker. The bug report has sparked an interest in preserving the tutorials and documentation that exists on the KDE servers for KDE 3.5. Much of this information could be potentially useful to new developers, and it will give us insight into previous development and practices.
I have started transferring pages from the KDE techbase, but there are also many external links and other misc pages floating around the Internet. Many of these links are broken, but can be found on the Wayback Machine [2]. There are entire websites that have been saved on the Wayback Machine as well.
The purpose of this email is to figure out what to do, and recruit any interestoied parties to help out.
Should we just link to the archived pages? Should we copy them to our own web server?
I am just getting started and this will be an ongoing project. So far I have just created one page on the Wiki, the Developers Tutorial [3]. It is to be the central hub for development pages.
Any r / Comments would be appreciated.
Calvin Morrison
[1] http://bugs.trinitydesktop.org/show_bug.cgi?id=544 [2] http://www.archive.org/web/web.php [3] http://www.trinitydesktop.org/wiki/bin/view/Documentation/DeveloperTutorial
Copying the pages to our servers (the Wiki to be precise) is by far the best way to go. That would allow us to easily edit parts of the TechBase that are obsolete or incomplete.
Tim
As for external websites that have been archived? I think it would be prudent to copy those onto the website as well.
Calvin
Copying the pages to our servers (the Wiki to be precise) is by far the best way to go. That would allow us to easily edit parts of the TechBase that are obsolete or incomplete.
Tim
As for external websites that have been archived? I think it would be prudent to copy those onto the website as well.
As long as there is no questionable content or potential copyright issues I would agree. Before copying sites to the Wiki perhaps you could run them by me first? Obviously the KDE TechBase uses a free license and therefore can be copied as you see fit, but other websites may not have been so generous with their licence terms.
Tim
-
Calvin Morrison -
Timothy Pearson