Something I was thinking of this morning...haven't really seen one going through the threads but I think it'd be a good idea to have an overall checklist (or punch list, if you prefer) of items to accomplish between now and full website operability.
Are we including current route systems maintenance and if so, migrating route updates and 6-month outlook threads?
It's in several sub projects, so here's the Highway data
1) Copy data over from CHM
2) Reassign regions (esp Tim's)
3) Get data up to date
4) Create new manual
5) Get data up to code
6) Import updated data
7) Create new systems
8) Process new systems
Quote from: english si on June 22, 2015, 12:49:27 PM
It's in several sub projects, so here's the Highway data
1) Copy data over from CHM
2) Reassign regions (esp Tim's)
3) Get data up to date
4) Create new manual
5) Get data up to code
6) Import updated data
7) Create new systems
8) Process new systems
[color-coding removed for readability, pastel text on light background doesn't work for some -- o.v.]
Not sure whether this list is intended to be comprehensive or partial, but creating a separate new forum (and, if possible, importing info from the old CHM forum, before it winks out) should be on a list, and indeed has been discussed.
My idea for the list was comprehensive...in that W, X, Y, and Z are all steps needed to be taken to get a full website operational.
Quote from: oscar on June 22, 2015, 01:21:49 PM
Quote from: english si on June 22, 2015, 12:49:27 PM
It's in several sub projects, so here's the Highway data
1) Copy data over from CHM
2) Reassign regions (esp Tim's)
3) Get data up to date
4) Create new manual
5) Get data up to code
6) Import updated data
7) Create new systems
8) Process new systems
[color-coding removed for readability, pastel text on light background doesn't work for some -- o.v.]
Not sure whether this list is intended to be comprehensive or partial, but creating a separate new forum (and, if possible, importing info from the old CHM forum, before it winks out) should be on a list, and indeed has been discussed.
I put in a request for subforums to be added.
Quote from: oscar on June 22, 2015, 01:21:49 PMNot sure whether this list is intended to be comprehensive or partial, but creating a separate new forum (and, if possible, importing info from the old CHM forum, before it winks out) should be on a list, and indeed has been discussed.
But is that a Highway Data action, or a website one? My list was a comprehensive one that almost certainly forgot something.
I guess importing info from old CHM is related to getting data up to date and keeping it so.
You might want to do that quick - The domain expires June 29 (This coming Monday!)
http://www.whois.com/whois/m-plex.com
Quote from: SSOWorld on June 24, 2015, 01:01:34 PM
You might want to do that quick - The domain expires June 29 (This coming Monday!)
http://www.whois.com/whois/m-plex.com
Agreed, but if the web hosting setup is similar as with my websites (with the same company), both monthly web hosting and annual domain registration continue/renew automatically so long as a valid credit card is on file. If there were going to be an issue with the site remaining "alive" (albeit frozen), it probably would be triggered by the monthly hosting fee, rather than the annual domain registration renewal.
Quote from: oscar on June 24, 2015, 01:45:27 PM
Quote from: SSOWorld on June 24, 2015, 01:01:34 PM
You might want to do that quick - The domain expires June 29 (This coming Monday!)
http://www.whois.com/whois/m-plex.com
Agreed, but if the web hosting setup is similar as with my websites (with the same company), both monthly web hosting and annual domain registration continue/renew automatically so long as a valid credit card is on file. If there were going to be an issue with the site remaining "alive" (albeit frozen), it probably would be triggered by the monthly hosting fee, rather than the annual domain registration renewal.
True. There is that.
I'm wondering how much of the functionality of the old forum, at least for problem reports with highway data, can be replaced by GitHub's issue tracking. Does anyone have experience with this? I just added an issue about what looks like an error in NY 100's file to GitHub in addition to posting a note about it on the old forum.
Quote from: Jim on June 24, 2015, 07:33:35 PM
I'm wondering how much of the functionality of the old forum, at least for problem reports with highway data, can be replaced by GitHub's issue tracking. Does anyone have experience with this? I just added an issue about what looks like an error in NY 100's file to GitHub in addition to posting a note about it on the old forum.
How could non-team members report problems in a GitHub-based system? Ordinary users have been very helpful in flagging highway system changes. ISTM you'd want a new forum, with an "Updates" subforum open to non-members, to replicate what CHM has now. But maybe GitHub would be useful, internally, to track any followup on problem reports,
Quote from: oscar on June 24, 2015, 07:46:42 PM
Quote from: Jim on June 24, 2015, 07:33:35 PM
I'm wondering how much of the functionality of the old forum, at least for problem reports with highway data, can be replaced by GitHub's issue tracking. Does anyone have experience with this? I just added an issue about what looks like an error in NY 100's file to GitHub in addition to posting a note about it on the old forum.
How could non-team members report problems in a GitHub-based system? Ordinary users have been very helpful in flagging highway system changes. ISTM you'd want a new forum, with an "Updates" subforum open to non-members, to replicate what CHM has now. But maybe GitHub would be useful, internally, to track any followup on problem reports,
Definitely things to figure out. I just created a new GitHub account with no connection to our TravelMapping GitHub organization and it let me submit an issue, so anyone can submit one. But would we want the end user to need to create a GitHub account? Probably not. So we'd want some kind of more conventional forum or "bug report" email address from which issues are added into GitHub.
I found this to be a useful quick intro to GitHub's issue tracking:
https://guides.github.com/features/issues/ (https://guides.github.com/features/issues/)
I might be getting ahead of myself here, but I think a bug tracker (like Trac (http://trac.edgewall.org/)) would be a good idea. If that's not feasible you might as well keep it on the forum.
Right now, I don't have access to GitHub due to the fact that I'm on a Chromebook. (Yeah, I suppose I could install Crouton, but it caused trouble for me in other ways.) So GitHub reporting is a pain for me. I doubt I'm the only person who will be in this situation but with even fewer computer chops.
Quote from: sammi on June 24, 2015, 08:08:56 PM
I might be getting ahead of myself here, but I think a bug tracker (like Trac (http://trac.edgewall.org/)) would be a good idea. If that's not feasible you might as well keep it on the forum.
Let's look at what GitHub has to offer first.
Quote from: sipes23 on June 24, 2015, 08:16:56 PM
Right now, I don't have access to GitHub due to the fact that I'm on a Chromebook. (Yeah, I suppose I could install Crouton, but it caused trouble for me in other ways.) So GitHub reporting is a pain for me. I doubt I'm the only person who will be in this situation but with even fewer computer chops.
Chromebook? That's your first mistake ;) :awesomeface:
Quote from: SSOWorld on June 24, 2015, 08:19:13 PM
Quote from: sipes23 on June 24, 2015, 08:16:56 PM
Right now, I don't have access to GitHub due to the fact that I'm on a Chromebook. (Yeah, I suppose I could install Crouton, but it caused trouble for me in other ways.) So GitHub reporting is a pain for me. I doubt I'm the only person who will be in this situation but with even fewer computer chops.
Chromebook? That's your first mistake ;) :awesomeface:
Don't remind me. :pan: I needed a computer that I could connect to the internet and cheaped out. :banghead:
I've never used or even seen a Chromebook, but why wouldn't it let you use GitHub? You can do it all through the web interface.
Another item for thought: each GitHub repository has a wiki.
Quote from: vdeane on June 24, 2015, 09:06:36 PM
Another item for thought: each GitHub repository has a wiki.
We should definitely make good use of these. I'm happy to see that Si edited the HighwayData repo's wiki with a lot of useful information.
Quote from: Jim on June 24, 2015, 08:08:36 PM
Quote from: oscar on June 24, 2015, 07:46:42 PM
Quote from: Jim on June 24, 2015, 07:33:35 PM
I'm wondering how much of the functionality of the old forum, at least for problem reports with highway data, can be replaced by GitHub's issue tracking. Does anyone have experience with this? I just added an issue about what looks like an error in NY 100's file to GitHub in addition to posting a note about it on the old forum.
How could non-team members report problems in a GitHub-based system? Ordinary users have been very helpful in flagging highway system changes. ISTM you'd want a new forum, with an "Updates" subforum open to non-members, to replicate what CHM has now. But maybe GitHub would be useful, internally, to track any followup on problem reports,
Definitely things to figure out. I just created a new GitHub account with no connection to our TravelMapping GitHub organization and it let me submit an issue, so anyone can submit one. But would we want the end user to need to create a GitHub account? Probably not. So we'd want some kind of more conventional forum or "bug report" email address from which issues are added into GitHub.
I found this to be a useful quick intro to GitHub's issue tracking:
https://guides.github.com/features/issues/ (https://guides.github.com/features/issues/)
Jim, as I've said before, a normal forum would be 10x better for reports IMO. GitHub should just be left for errors in the code base IMO. Errors of the map data, on a forum. If we go SMF, it's very easy to setup a way to allow guests to post in a 'report' section where there is an error in the data without having to signup for the forums if they don't want to (if they want to post in other sections, then they can signup). Also, you can get a RSS feed from the forums (and there's mods out there to allow you to get a specialized feed from just one section of the forum if you want it) to keep up-to-date on new posts and stuff. I know I check the forums out here @ AARoads a lot via my RSS feed of here. Plus, there's ways to manually tweak the RSS feed to get more than the default 20 (or is it 10) most recent posts in case you're away from the computer a lot and thus, keep up-to-date.
Quote from: Jim on June 24, 2015, 09:02:09 PM
I've never used or even seen a Chromebook, but why wouldn't it let you use GitHub? You can do it all through the web interface.
I *had* thought it was all in the terminal, but the kids have been very demanding since school let out (and I'm the man in charge all day). I'll look into it a bit more when they're not wearing me out so much. I'd really love to be able to manage the .list via GitHub.
One thing regarding the new forum - understanding that the m-plex collaborator team had no problem with this AFAIK - is if we don't have a standard for highway corrections, that we create one. Having one would make it easier for searching out these corrections whether it be by region, system, whatever. If one were to do regional boards, keep it limited because we have a lot of different systems intermixed with regions - add on that some issues might cover multiple systems and/or regions. Also educate users and new collaborators regarding it so they can (hopefully) follow it.