-
Notifications
You must be signed in to change notification settings - Fork 29
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
Merge demisjohn fork/transfer ownership #3
Comments
Hey, |
If I understand this correctly, https://help.github.com/articles/about-repository-transfers/ , |
Ok, I will mostly overwrite all your changes with mine.
Will submit the PR for brach `master` now.
Following these instructions to transfer the py35_compat branch:
https://stackoverflow.com/a/5884825/2453202
Also will find some way to transfer Issues, in which I've tried to document much of the work.
By the way, thanks for creating the GitHub repo from SourceForge in the first place, that was a great move.
…-- Demis --
°•Oo.oO•°*°•Oo. Sound OK
<http://www.google.com/search?q=sound+ok+horn&tbm=isch> Horn *°•Oo.oO•°*°•O
o.
On Tue, Apr 10, 2018 at 12:12 AM, Pavel Dmitriev ***@***.***> wrote:
If I understand this correctly, https://help.github.com/
articles/about-repository-transfers/ ,
For me to transfer ownership to you, you would first have to delete your
fork.
So I guess you could do a pull request of all of your commits to this
repository, then delete your fork and then I will transfer ownership.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/kitchenknif/CAMFR/issues/3#issuecomment-379998145>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFHxRSQ8yWX73kklMgDtpVinT0yKsD7kks5tnFtogaJpZM4TDJBy>
.
|
I'll transfer ownership once you move everything to this repo, cannot while your fork still exists. |
I've transferred all issues, and Deleted my repo! Thanks! |
Done, |
Hello,
I was wondering if I could somehow take over ownership of this repo, and just add you as a maintainer.
Not sure of the exact logistics of that, but I assume it's possible somehow. Happy to add anyone as collaborators, but I will actually take the time to look at pull requests etc.
GitHub looks like a perfect place to continue development and post upgrades to CAMFR, continuing it's excellent utility. Although I'm not particularly great at coding up mathematical models, I will try to upgrade the package to keep it current (currently working on Python3 upgrade). Maybe the community can help with actual modeling coding.
Let me know what you think.
-- Demis
The text was updated successfully, but these errors were encountered: