-
Notifications
You must be signed in to change notification settings - Fork 17
Move to the mongoid organization? #5
Comments
Hello, sure, sounds like good idea. |
I cannot change the repo ownership as I don't work for Polarion anymore and cannot administer the repo. But as it's under MIT licence I don't see problem to clone the repo for mongoid. |
I've emailed ^ today, if we don't get a response lets make a fork in mongoid, I'll take care of it @davidsevcik. |
@dblock let's do it? |
Yes please! Just transfer this repo to me and I'll move it to mongoid immediately. |
I'm not the owner, in this case I think we should fork/move @bopm https://github.com/bopm/mongoid_relations_dirty_tracking |
The whole point was to not fork, lets wait to hear from these guys? We have an email thread. |
I am not an owner of those changes, I just borrow them from @Megawolf492 who moved in a different direction with his fork after those. So I am ok with any outcome. Especially with some which will allow me to return stable release to Gemfile instead of link to my github :) |
I am waiting for a confirmation from within my organization to OK this.
Give us a little more time please.
Martin
2017-04-25 0:46 GMT+02:00 Sergey Moiseev <notifications@github.com>:
… I am not an owner of those changes, I just borrow them from @Megawolf492
<https://github.com/Megawolf492> who moved in a different direction with
his fork after those. So I am ok with any outcome. Especially with some
which will allow me to return stable release to Gemfile instead of link to
my github :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFYfoj_m7vnLBKrTmdYe-ydjTkmTYvpks5rzSY0gaJpZM4M6BKQ>
.
|
Would you like to move this repo to the github/mongoid org? See http://mongoid.github.io/.
It could use some more active maintenance, support for Mongoid 6, etc.
(I'm coming from mongoid/mongoid-history#187).
The text was updated successfully, but these errors were encountered: