-
Notifications
You must be signed in to change notification settings - Fork 71
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
Salmon back in Alpaca #552
Comments
As long as that code is in Alpaca at some point in time in the history, we can just toss it. No need to re-integrate it just so we can write over it. |
Just checked: https://github.com/Islandora-CLAW/Alpaca/tree/ea09a6970477ab8d5103b3add55f5aca3f3cd157/sync It's in there. |
I'm cool with that. |
Conversation of irc this morning shown a consensus on deleting the repo completely. |
Salmon is gone. I'll update MVP documentation. |
I have a clone on my local machine, so if we ever need it again, I can push it up somewhere. |
Final PR: #553 |
👏 👏 👏 |
Resolved with: 75b3030 |
@dannylamb and I have had some preliminary discussions on bringing Salmon back into Alpaca as a sub-project. If we do go this route, do we want to preserve the history on Salmon, since we preserved it when we pulled it out of Alpaca? The process looks fairly complicated as outlined here.
Or, we can forgo the history, and just integrate Salmon back into Alpaca.
Either way, this affects commits by @dannylamb (as @daniel-dgi), @whikloj, @acoburn, @manez, @Amandarl, and me. So, I'd like to get input from everybody involved before I proceed. Thumbs up on preserving history. Thumbs down on tossing the history out the window.
I'm fine with either way, and will volunteer to do the work either way.
The text was updated successfully, but these errors were encountered: