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

Connect ontoportal-lirmm to ontoportal #312

Closed
1 of 3 tasks
Tracked by #343
syphax-bouazzouni opened this issue Nov 3, 2022 · 3 comments
Closed
1 of 3 tasks
Tracked by #343

Connect ontoportal-lirmm to ontoportal #312

syphax-bouazzouni opened this issue Nov 3, 2022 · 3 comments
Assignees
Labels
project managment issues used as development tasks in our projects

Comments

@syphax-bouazzouni
Copy link
Contributor

syphax-bouazzouni commented Nov 3, 2022

Context

Starting from 2023, the centralized code for the ontoportal technologies would no more be in the NCBO organization but instead in the new ontoportal organization

Goals

Make the ontoportal organization, the entry point for anyone that wants to take/use our technologies. And make it the centralized place for our all generic issues/projects

Issues

  • Currently, all our codes are forked from NCBO organization and GitHub does not offer any solution to change the fork source. So the only solution is to remove the current repositories and fork them again from ontoportal organization
  • Managing issues, do we transfer all our current generic issues to the ontoportal organization
  • Update our deployment tools (not a significant matter)

Requirements

@syphax-bouazzouni
Copy link
Contributor Author

@jonquet here is our local road map to connect to ontportal, to confirm and tell when we start it.

A more generic road map to connect to ontportal, for the other members will be done as discussion in the ontoportal-project repository later.

@syphax-bouazzouni
Copy link
Contributor Author

syphax-bouazzouni commented Jan 23, 2023

The message sent to GitHub support at https://support.github.com/request/fork

Hi,
Can you reroute the following forks?

https://github.com/ontoportal-lirmm/bioportal_web_ui to https://github.com/ontoportal/ontoportal_web_ui

https://github.com/ontoportal-lirmm/goo to https://github.com/ontoportal/goo

https://github.com/ontoportal-lirmm/ontologies_linked_data to https://github.com/ontoportal/ontologies_linked_data

https://github.com/ontoportal-lirmm/ontologies_api to https://github.com/ontoportal/ontologies_api

https://github.com/ontoportal-lirmm/ontologies_api_ruby_client to https://github.com/ontoportal/ontologies_api_ruby_client

https://github.com/ontoportal-lirmm/ncbo_cron to https://github.com/ontoportal/ncbo_cron

https://github.com/ontoportal-lirmm/sparql-client to https://github.com/ontoportal/sparql-client

https://github.com/ontoportal-lirmm/ncbo_annotator to https://github.com/ontoportal/ncbo_annotator

Thanks,

Results

Image

Image

Image

@syphax-bouazzouni
Copy link
Contributor Author

syphax-bouazzouni commented Feb 8, 2023

I close because it is done, and move #401 and #402 to a future iteration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project managment issues used as development tasks in our projects
Projects
None yet
Development

No branches or pull requests

2 participants