deadtrickster

deadtrickster

Hi, I don’t work at Kobil anymore nor Lukasz.

0
Post #21
Ankhers

Ankhers OP

In that case, would you mind transferring the packages back to myself and Scott?

0
Post #22
deadtrickster

deadtrickster

Although I’m still a member of the organization (not sure why though, but anyway), I won’t be doing the transfer since it’s a company owned organization. Please contact Erik Dahmen at erik.dahmen@kobil.com.

1
Post #23
Ankhers

Ankhers OP

You are currently the hex owner. If I get Erik’s permission, would you be willing to transfer the project to me?

1
Post #24
KoushikDasika

KoushikDasika

This speaks to the need of an Elixir Mongo github organization

2
Post #25
scottmessinger

scottmessinger

@Ankhers Would you be okay with an Elixir mongo org? I can set that up and invite you and @peoj

0
Post #26
Ankhers

Ankhers OP

I have just sent Erik an email. I will update this thread once I hear back from them.

As for the GH org. I’m not against it. I just don’t think it solves the issue of hex maintainership. But if you feel that it will help in some capacity, feel free to create it.

0
Post #27
scottmessinger

scottmessinger

Done! elixir-mongo · GitHub

It definitely won’t help with the hex ownership, but I’m hoping it helps with the code ownership so we don’t get into a place where someone or some company took over a repo but ran out of resources to maintain it.

5
Post #28
scottmessinger

scottmessinger

I was hoping we’d have access to the original repos by now, but, since we don’t, I transferred my forks into the organization. If we ever get access to the originals, we can delete those forks and clean things up.

As soon as we have clarity on the hex.pm situation, we’ll cut a new release and get some momentum going!

6
Post #29
KoushikDasika

KoushikDasika

Your hardwork and initiative (and everyone else’s in this thread) is appreciated. I’ll try to chip in where I can.

1
Post #30