update edelight's tickets to reflect what has been resolved here

[josephholsten]

I don't want people to get lost at https://github.com/edelight/chef-mongodb

So I've created PR edelight/chef-mongodb#399

and I've closed my tickets. Could someone go through the rest of them and point folks over here, especially if we've resolved their issue?

[zarry]

@josephholsten Can we really not get in touch with anyone from edelight? Would be nice to either close that repo or put up a disclaimer/redirect at the top of the README. Will take a while for ours to overtake theirs in google search land.

[tobami]

I do no longer work for edelight, or maintain chef-mongodb but I agree that chef-brigade would be a better home for it, as edelight didn't contribute much in the last years and it was mostly others who maintained it.

That said, the person you need to ask is @thekorn , who originally did most of the work and would be the one who could help you there, if he agrees.

[shortdudey123]

@josephholsten should we consider this done w/ RFC088?

[josephholsten]

@shoekstra your call. I can do a manual review though.

[josephholsten]

actually, I went through and verified all the recent tickets all have pointers to here.

🔤

[shortdudey123]

sounds good 👍

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.