`Gtfs Data Manager` is deprecated

Question

`Gtfs Data Manager` is deprecated

radumas opened this issue 6 years ago · comments

GTFS workflow tool This project is DEPRECATED, see conveyal/datatools-manager for current version. https://github.com/conveyal/datatools-manager

From the link there it seems the development version is now at https://github.com/catalogueglobal/datatools-ui
Quote from the documentation

The Conveyal Transit Data Tools suite provides web-based tools for creating, managing, evaluating, and publishing transit data, specifically data stored in the General Transit Feed Specification (GTFS) format.

Sean Barbeau · Answer 1 · Thu Feb 22 2018 23:59:53 GMT+0800 (China Standard Time)

Thanks for the heads up @radumas!

@landonreed I'd like to update the link to what was previously "GTFS Data Manager" - looks like that is deprecated, and now "Data Tools UI" is the new version - https://github.com/conveyal/datatools-ui.

However, that project says that "DEVELOPMENT NOW HAPPENING ON FORK AT: https://github.com/catalogueglobal/datatools-ui"

Which is the best repo to link to, the conveyal/datatools-ui, or catalogueglobal/datatools-ui?

Landon Reed · Answer 2 · Fri Feb 23 2018 00:02:40 GMT+0800 (China Standard Time)

Hi, @barbeau. I think we should just link to catalogueglobal/datatools-ui for now to minimize confusion. If active development moves to the conveyal repo, we can update as needed.

Thanks for catching this, @radumas!

Sean Barbeau · Answer 3 · Fri Feb 23 2018 00:25:51 GMT+0800 (China Standard Time)

So, if I'm going to be consistent here (see #88), I think there needs to be a little more clarity of why the fork exists in the README of the conveyal repo - i.e., a pointer to the catalogueglobal repo. Also, in the README of the catalogueglobal repo, it still hyperlinks back to the conveyal repos for the datatools-server and docs.

I've been trying to keep this list clean and easily understandable by developers by pointing only to master repositories and not forks, unless the fork and master are clearly documented and there is a good reason that both exist. I don't want to erroneously point developers to a fork to have them build something on top of that, just to find out that the master repo had the most recent code, or vice versa.

@landonreed Would you be willing to clarify the relationship in the READMEs and fix the links as well to make it clear what is happening where?

Andrew Byrd · Answer 4 · Mon Apr 30 2018 17:03:13 GMT+0800 (China Standard Time)

Hi @barbeau, we have a long-running partnership with some other organizations to help them develop the Catalogue platform, so to keep things simple we were all working on their fork. Since all our effort was concentrated there, it is now quite far ahead of Conveyal's original repo. However, Conveyal still develops and provides our Data Tools product, and within the next couple of months when our involvement in Catalogue winds down, we'll merge that fork back into the original repo.

So: for the time being, the fork contains the current generation of the software. But soon, we will shift our attention back to the original repo.

Landon Reed · Answer 5 · Tue Dec 11 2018 03:34:11 GMT+0800 (China Standard Time)

@barbeau, Conveyal is now working on the Data Tools application in the original repositories (conveyal/datatools-ui and conveyal/datatools-server). We can replace the GTFS Data Manager links with these if you haven't already done so. Or if it's helpful, I could submit a PR.

Thanks!

Sean Barbeau · Answer 6 · Tue Dec 11 2018 04:57:05 GMT+0800 (China Standard Time)

@landonreed PR would be great, thanks!