Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move work off ODIQueensland #1006

Closed
JDziurlaj opened this issue Apr 30, 2020 · 7 comments
Closed

Move work off ODIQueensland #1006

JDziurlaj opened this issue Apr 30, 2020 · 7 comments
Labels
est:Minor Minor effort to implement est:Score=1 Score for estimate of effort required (scale of 1 upwards) News An issue dedicated to project news priority:High support This issue is a candidate to complete under the support agreement

Comments

@JDziurlaj
Copy link

If ODIQueensland is defunct, would be it advisable to move work off this account to somewhere else?

@ghost
Copy link

ghost commented Apr 30, 2020

Hi @JDziurlaj
It's a good point. I guess at this stage, personally I find that:

  • it keeps this project organised with the others (including examples) started with ODI and ODIQueensland. So it kinda makes sense just in terms of where I find this and related work.
  • I like the idea of keeping it in a place where @Stephen-Gates is also an overseer, as the project was his concept originally.

But yes perhaps I should fork this project now and place under QCIF, as from a maintenance point of view, it makes more sense there.

I'll leave this open for a bit - there might be other opinions out there. If I keep it here I'll add in other members from QCIF or if I fork the repo, I'll ensure @Stephen-Gates is added back in, and any existing reps from our sponsors.

@Stephen-Gates
Copy link
Contributor

Stephen-Gates commented May 1, 2020

I have no problem with forking but a number of other sites point here so a note in the readme point ing to the new location would help.

Known sites linking here:

Frictionless Data
Tooling and approaches to data that are in varied stages of maturity.
Frictionless Data
Data Curator is a simple desktop editor to help describe, validate, and share usable open data.
A desktop CSV editor for data publishers

@ghost
Copy link

ghost commented May 1, 2020

Thanks @Stephen-Gates Much appreciated. I've also added 2 other devs from QCIF as admins to this repo just as an extra layer of redundancy.
Thanks @cofiem and @grahame

@ghost ghost added est:Minor Minor effort to implement est:Score=1 Score for estimate of effort required (scale of 1 upwards) News An issue dedicated to project news support This issue is a candidate to complete under the support agreement labels May 14, 2020
@ghost
Copy link

ghost commented May 18, 2020

Started updating main page (see #1016) and README.md.

@chris48s
Copy link

chris48s commented May 19, 2020

It is possible to move a repo without breaking links. If you transfer a repo rather than forking it, github will redirect traffic from the old URL so links won't break. Github will maintain the redirect indefinitely unless you create a new repo with the same name in the old user/org namespace.

There are various example of big projects which moved owner where this redirect still applies e.g:

more info https://help.github.com/en/github/administering-a-repository/transferring-a-repository

GitHub
A simple, yet elegant HTTP library. Contribute to psf/requests development by creating an account on GitHub.
GitHub
A simple, yet elegant HTTP library. Contribute to psf/requests development by creating an account on GitHub.
GitHub
PHP Database Migrations for Everyone. Contribute to cakephp/phinx development by creating an account on GitHub.
GitHub
PHP Database Migrations for Everyone. Contribute to cakephp/phinx development by creating an account on GitHub.
You can transfer repositories to other users or organization accounts.

@ghost
Copy link

ghost commented May 19, 2020

Hi @chris48s
Yep for sure. Sorry for confusion - I think I was considering a fork initially as a conservative way to get started (in case there was resistance to the idea) - I should have made this more clear as discussions with our sponsors have moved on from this. Our sponsors support us moving completely from ODIQueensland to QCIF, knowing that Github will allow the redirects from old site, and I haven't seen any feedback suggest why we shouldn't move.
I've proposed that we do the move as part of our next Beta release, and have announced the move in our news. That way we have a bit of allocated time to fix up any redundant links/refs to ODIQueensland or to the old repo in our integration tests.
So yes a move, not a fork, will be happening within the next couple of weeks - thanks for the pickup :)

@ghost
Copy link

ghost commented May 19, 2020

I'll add this in to our current milestone.

@ghost ghost added this to the Import and Export enhancements milestone May 19, 2020
@ghost ghost added the priority:High label May 19, 2020
@ghost ghost closed this as completed Jul 6, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
est:Minor Minor effort to implement est:Score=1 Score for estimate of effort required (scale of 1 upwards) News An issue dedicated to project news priority:High support This issue is a candidate to complete under the support agreement
Projects
None yet
Development

No branches or pull requests

3 participants