On the other hand, it was not clear to me that we would
keep trac forever (eg moving to gitlab or github was
mentioned several times). Migrating the wiki as you propose
will make it harder to leave trac.

1) If it is just a problem of "login with github", why can't we
provide github login to the wiki?

2) I don't understand why outdated content is a reason to move
the wiki. Just delete or update the content seems a more
reasonable option to me.

3) Regarding history : the trac wiki appeared *after* the
wiki.sagemath.org.

Unless there is a good reason to do so, let us not migrate the
original Sage wiki.

Vincent

Le 18/04/2022 à 20:45, Matthias Koeppe a écrit :
Let's get rid of the old Sage wiki (https://wiki.sagemath.org/SageWiki).

1) It excludes new and newish developers who do not have the required
legacy trac account but log in to Trac using their GitHub accounts.
2) It has very little non-outdated content (see below) -- it reflects
poorly on the project.
3) We already have another Wiki as part of the Trac
server. https://trac.sagemath.org/wiki/WikiStart

Steps done:
a) I went through in the last few weeks and reviewed and then deleted many
wildly outdated pages and pages that only duplicated information that is
available in our
manuals. https://wiki.sagemath.org/RecentChanges?max_days=90
b) I have migrated https://wiki.sagemath.org/ReleaseTours/sage-9.6
and https://wiki.sagemath.org/patchbot (and subpages) to the Trac wiki.

To do:
c) Migrate some info to our documentation
- see for example https://trac.sagemath.org/ticket/30500 on IDE & text
editor configuration
d) Migrate the rest of the pages to the Trac wiki -
https://trac.sagemath.org/ticket/33725
- for example the archive of SageDays activities



--
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1afbc590-80f9-2b2a-cfc0-60ddd3dc2126%40gmail.com.

Reply via email to