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

Migration of pkgs to non-experimental repository #27

Open
gavanderhoorn opened this issue Jun 19, 2018 · 7 comments
Open

Migration of pkgs to non-experimental repository #27

gavanderhoorn opened this issue Jun 19, 2018 · 7 comments
Labels

Comments

@gavanderhoorn
Copy link
Member

Triggered by discussion in #26.

@nilsmelchert
Copy link
Contributor

So in order to create PRs for the staubli repository, I just fork the current master branch from the staubli repository and add the packages I want to migrate from the staubli_experimental repository manually?

@gavanderhoorn
Copy link
Member Author

@nilsmelchert wrote:

I actually like that the location of the hardware driver. Since the Issue you mentioned is still open, I would recommend to also move the staubli_val3_driver to the staubli repo for now.

Tbh it doesn't make much sense to me to migrate the driver to staubli and then migrate it again to its own repository.

The issue is still open, as the migration/extraction hasn't happened yet, but the decision has already been made. See gavanderhoorn/staubli_val3_driver for a prototype for staubli_val3_driver.

@gavanderhoorn
Copy link
Member Author

@nilsmelchert wrote:

So in order to create PRs for the staubli repository, I just fork the current master branch from the staubli repository and add the packages I want to migrate from the staubli_experimental repository manually?

at a high level, that is what needs to happen yes. But in order to make this a bit more of a structured process, and to make sure we don't completely disconnect things, there is a procedure to follow. As I wrote in #26 (comment), I have that procedure documented, but it's not publicly accessible right now.

The reason for that is the discussion I mentioned earlier (ie: with or without history).

Summarising: it's slightly more complex than just creating PRs and git rm ...

@nilsmelchert
Copy link
Contributor

Alright. So are you going to make the process of migrating certain packages public?
How can I help?

@gavanderhoorn
Copy link
Member Author

I'm really rather busy right now, so I'll see if I can find 20 mins somewhere to make it available. It won't be today though I'm afraid.

@gavanderhoorn
Copy link
Member Author

@nilsmelchert wrote:

How can I help?

and 👍 💯 for offering to help here btw, really appreciated.

@nilsmelchert
Copy link
Contributor

No worries. Let me know, when you want me to start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants