Open Seanny123 opened 8 years ago
Probably something to talk about at a lab meeting? As far as Nengo stuff is concerned, the Software stuff should definitely be moved to the appropriate Nengo repo (you can make a PR on Nengo 1.4 with the markdown files unchanged in it, just so we have them somewhere but you don't waste a lot of time trying to incorporate them in the current docs).
Not sure where the modelling constants and constraints should go, but they're linked to in a few places, so at the very least they should redirect to their new location. Probably easiest to keep them where they are though...
Indeed, I've already entered it into the schedule of the lab meeting!
FYI, for redirecting links, there's a repository for that.
FYI, for redirecting links, there's a repository for that.
This repo doesn't use Jekyll; however, I built in the ability to easily redirect pages since there were links to an old version of compneuro.uwaterloo.ca published in various places.
Gah, I always get Jekyll confused with Flask. My bad.
Here's my plan so far, which we can discuss during the meeting:
nengo_1.4/simulator-ui/docs/
nengo_1.4/simulator-ui/docs/advanced/
http://compneuro.uwaterloo.ca/codelibrary/NEHelp/index.html
is dead and gone.software/nengo-model-archive.html
to note that this archive is only for Nengo 1.4 and that we are in the process of creating a new searchable archivestatistical-inference.md
and re-include it in the NEF section.
During the CTN meeting the following things were concluded:
Still digging through these folders to figure out what can be salvaged. Couple of questions:
Also, some notes to myself:
A lot of stuff under the "Research Tab" is either broken, so out of date that it's useless or really awkwardly placed.
Files that are worth saving:
Out-of-date files to be archived:
Should be moved, but I'm not sure where and I'm afraid of breaking other links:
May I delete from the website the files that aren't worth saving and fix the ones that are?
If any of these project sections (which seem to be an earlier attempt at the lab blow) will be missed, may I recommend the alternative of somehow tagging our publications to automatically generate these sections so they don't go out of date?
As for the method of archiving, is the fact that these are contained on GitHub good enough or do we want some sort of hidden link so that they're still a part of the website? Do we need redirect links so that ancient links to these sections aren't broken?