-
Notifications
You must be signed in to change notification settings - Fork 13
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
Migrate project to sugarlabs? #4
Comments
Maybe, but won't that break the git submodules? This project is a dodgy hack anyway. Hacks should not be made official. The aim is for this api to eventually be intergrated into sugar3 - rather than just adding another layer to the onion that is Sugar's collab stack. Really, our stack is a lot like an onion, as the more I peel back it's layers, the more I start to cry. |
No, a redirect is maintained by GitHub. Regardless of how dodgy it is, we've ended up using it, so it should be moved. |
Not a biggie. If not moved by owner, then we'll just have to clone it and repoint the submodule references. 😁 |
Sounds good. I will move it asap, but I'm Afk for the next few days.
…On 21 April 2017 8:24:15 am AEST, James Cameron ***@***.***> wrote:
Not a biggie. If not moved by owner, then we'll just have to clone it
and repoint the submodule references. :grin:
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#4 (comment)
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Thanks. Again, not a biggie, see godiard/help-activity#26 (comment) for my wider opinion. I'll clone it Tuesday 9am Canberra time if you haven't moved it by then. |
Perhaps this should be migrated?
The text was updated successfully, but these errors were encountered: