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

Submodule restructure #10

Open
kshedstrom opened this issue Nov 3, 2016 · 1 comment
Open

Submodule restructure #10

kshedstrom opened this issue Nov 3, 2016 · 1 comment

Comments

@kshedstrom
Copy link
Contributor

I just want to start a conversation about how this will go. Split out bathy_smoother and the toolbox(es) as their own repos? Leave the examples here? If the pycnal code becomes its own thing, is pycnal/PyCNAL going to be a problem?

@braney, would you like to do the conversion since you have a branch? I wouldn't want to mess you up.

@braney
Copy link
Collaborator

braney commented Nov 7, 2016

I don't have a very good sense for how all the pieces of the existing PyCNAL organization work together. For example, why is bathy_smoother separate from pycnal_toolbox (formerly pyroms_toolbox)?

I suggest we use the wiki to work out how we want things organized. I made a page:

https://github.com/ESMG/PyCNAL/wiki/PyCNAL-Organization

As for my branch, I actually created a separate directory ("mom6_tools") under PyCNAL, since I didn't want to make major changes to the existing pieces. I'm OK with performing the reorganization or not, but I think we should plan it out first and make sure everyone is on board.

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

No branches or pull requests

2 participants