Migrating the wikis and bugtracker: please keep the bugs!

Matthew Toseland <mjt92-KWPb1pKIrIJaa/[email protected]> Sun, 28 Aug 2016 18:22:48 +0100
Newsgroups	gmane.network.freenet.devel
Message-ID	<[email protected]>
On 20/08/16 07:01, Florent Daigniere wrote:
> On Fri, 2016-08-19 at 22:31 -0400, Steve Dougherty wrote:
>> On 08/12/2016 04:00 PM, Florent Daigniere wrote:
>>> On Thu, 2016-08-11 at 14:28 +0000, Ian Clarke wrote:
>>>> Why don't you set a date since you're the one that would do it?
>>>
>>> I have created https://github.com/freenet/wiki/wiki ... and will
>>> remove the old wikis as soon as we deploy the new website design.
>> Huh? Why? 
> Because that's what the boss said we should do... and it took me 30s.
>
>> There's a bunch of documentation on the wikis already - what's
>> the reasoning for
>>
>> 1. changing wiki platforms (making administration GitHub's problem
>> and responsibility?)
> Ian has used another argument: github's syntax is trendier.
>
> But yes, you have made my points.
>
>> 2. not transitioning existing documentation (licensing?)
> I have made it clear that I don't have the will-power to do
> it. mrsteveman1 apparently does, so a lot of progress has been made in
> that area already, thanks to his efforts.
>
> I did mention to Ian that moving the wiki to another engine is yet-
> another-recurring thread (just like "the website design sucks"), where
> in last iteration concerns were raised regarding the licensing of some
> of the content. Apparently no one cares, so why should I?
>
>> This seems like discarding lots of work - especially about FCP and
>> GSoC projects.
>>
> It doesn't have to be; help with the migration if you care.
>
> Florent
Please could we keep a static copy of the content of the old wikis? Even
if we don't host it, somebody should spider/export a tarball for reference.

Just because the Internet Archive hosts a few pages doesn't mean it has
everything; often it only has part of a mirrored site.

What matters more is the bug tracker: The poll is problematic because
half of the suggestions are technically illiterate. In most of these
cases detailed design has been done and is on the bug tracker.
Occasionally the records are on one of the wiki's. While there may be
good financial reasons for moving services off Osprey, IMHO we need to
keep that information *in some form*, even if it's only a static archive
(in which case note the distinction between public and private
bugs/comments).

When I looked into it many years ago, migrating the bug tracker to a
third party (while keeping data) didn't look feasible, but I believe the
situation has improved since then - *if* we're just moving to another
Mantis instance.

_______________________________________________
Devl mailing list
[email protected]
https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
signature.asc (application/pgp-signature, 819 B)