Find the new maintainer

[X13454]

Hello guys,

This library is awesome however it looks like it is not maintained anymore?
Could you add a message on top of the readme saying you're looking for a new maintainer?

@indexzero @vesse @pksunkara

Cheers,

Xavier

[SpaceK33z]

I forked this repository, fixed a few issues and published it on npm: https://github.com/CodeYellowBV/tarantino

I don't plan to actively do much work on it, but I will review PR's. If anyone is interested in helping me maintain it, that is also welcome.

When this repository starts getting maintained again, I will migrate to Director again.

[mhulse]

Seems like this repo could just use someone to push the merge PR button. Are there any maintainers out there?

Anyone know of a good 2017 alternative to Director?

[SpaceK33z]

@mhulse, see https://github.com/CodeYellowBV/tarantino, I merged a few critical PR's and published it on npm. I will review PR's.

[mhulse]

@mhulse, see https://github.com/CodeYellowBV/tarantino, I merged a few critical PR's and published it on npm. I will review PR's.

Hey @SpaceK33z! Thanks for the reply!

I actually tried your fork out last night but I found it was not a total drop-in replacement. With that said, I should try it again, as I really like Director, and I'd love to use something that's more maintained.

If I had more time, I would want to help out with, and suggest, this:

Let's create a "Director" organization! Maybe, call it director-next or director-router

Organizations, in my mind, would make it more approachable in terms of maintainers and contributors.

To start out, the org could contain these repos:

1. Your fork, Tarantino (you would move it to the org)
2. A fork of Director (or get @flatiron to xfer it to the new org, this would be preferable)
3. Maybe a new repo, with Tarantino latest code, but renamed back to Director (I am not sure if I really dig the name Tarantino, but I see where you were going with the theme) 😆

From there, I personally would like to see Director broken into multiple repos:

1. Browser-specific build
2. Node-specific build
3. CLI build?

Do we really need the two (client/server) to exist together? Maybe we could create a plugin/module system, where there's a core repo, and addon repos.

If node needs the browser bits to work, then make the browser a dependency of the npm module. This would free up browser-only users from having to work their way through the server-side specific docs/data/comments.

Thoughts (anyone)?

I'd be more than happy to help maintain, but I just like the sound of an organization over individual user accounts. Orgs seem more future-proof.

[au-phiware]

It's clear that this project needs a new maintainer and that it still has interest/value. I think creating a Github organization for this project is a very good idea; that would ensure the longevity of this project.

@indexzero @vesse @pksunkara

[Marak]

I don't think any of the previous maintainers care.

I use to have admin rights on this repository, but was taken away for reasons I'm not certain. Since that time, I haven't seen much momentum on any of the Flatiron projects.

Probably best to move on.

[pksunkara]

I didn't have maintainer access since 2013 in flatiron organization. So, can't help you guys.

[dandv]

If anyone with admin access to the repo is still around, please archive it.