archiving deprecated repos

[Dan Kortschak]

We continue to get issues against the deprecated repositories, but
there is a feature (newish I think; Vladimir has used it on some of his
personal repos) to archive the repo[1]. This appears to be reversible
according to that page, but we get the following:

> When a repository is archived, its issues, pull requests, code,
> labels, milestones, projects, wiki, releases, commits, tags,
> branches, reactions, and comments become read-only. To make changes
> in an archived repository, you must unarchive the repository first.

So, I' propose that we add text to the repos' README saying that
outstanding issues should be moved to gonum/gonum or gonum/netlib if
comments are wanted to be made (just opening a new issue at the
destination linking to the existing issue saying that it is a
continuation of the old).

Does this sound reasonable?

[1]https://help.github.com/articles/about-archiving-repositories/

[Sebastien Binet]

SGTM.

-s

sent from my droid

--
You received this message because you are subscribed to the Google Groups "gonum-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gonum-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robin Bartholdson]

On a similar note: Would it make sense to also update the documentation of all the deprecated repos with pointers to the new repos?

I sometimes find myself googling for feature X + gonum, ending up in an old repo on godoc.org and then have to remind myself to check the path of the repo. Might not be obvious for newcomers.

Best,

-Robin

--
You received this message because you are subscribed to the Google Groups "gonum-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to gonum-dev+...@googlegroups.com.