horizon
horizon copied to clipboard
rethinkdb
Roadmap
@deontologician, @Tryneus, @dalanmiller, @coffeemug, @danielmewes, @flipace Horizon is currently unmaintained. I think its a shame and would like to get some insight into the status quo:
- Who is/feels currently responsible for the project?
- Who are candidates for future project ownership?
- Is there a roadmap?
- Before RethinkDB shut down there were major refactoring efforts being undertaken - are those going to be completed?
If none of the previous core contributors are available to continue development of the project, would you be willing to open it up to a new team of developers?
hi @lgleim, i'm not sure what's the current state of horizon itself and have not been contacted by any of the rethinkdb folks about it too (I have not been a RethinkDB employee)
I could spare some time to work on some issues and help out on the repository if I get some clear picture about where it should go / who's the future lead of this project. I know that there are a couple of other people interested in this, but I'm not sure if there is anyone who's currently taking care of the horizon repo.
If there's anything I could help with regarding horizon, you can directly mention me with @flipace in an issue and I'll let you know if I can help out. I don't follow the big pile of issues in here at the moment since there's loads of them and I can't edit them in any way to clean up (like, set labels or so - i guess that would already help a lot ;))
According to https://rethinkdb.com/blog/rethinkdb-joins-linux-foundation/ there should be news about this coming somewhen soon, however since transitioning all the different things (code, artwork, docs, legal stuff) behind RethinkDB takes time this might take longer than people would like. I know however that @mglukhovsky is passionate and really hard at work to make this as painless and pleasant as possible for everyone - which is not an easy task in any way.
I would love to join in aswell if i can be of any help i really think its a cool project, and worth keeping alive. Ping me and i will see what i can do
@flipace Thank you for keeping us in the loop. It makes all the difference to know that our messages regarding continuation are even being read. Much appreciated .. small feedback better than none.
This project has great potential.
pinging @marshall007 and @mglukhovsky. It would be nice to know if anything is on the way with regards to this project.
My personal thought is: this project started on Oct 25, 2015 and after almost one year it became something with big potential (I say this because of the real time functionality that sets this project and rethinkdb apart from other projects yet sadly the company closed). So I truly believe that a lot can be achieved with this project in a short period of time and I hope that in the near future we will be able to pick up the rapid pace of development again.
@flipace lovli really stands for it's name.
First of all, I just want to say I appreciate how passionate everyone is about this project and I feel much the same way. Unfortunately the project is in a pretty weird state right now. As most of you know, there are some key issues that need to be addressed before Horizon can really be considered a "production-ready" and productive development tool.
Most, if not all, of these issues were being addressed as part of the refactor to a plugin-based architecture in #865. The timing on the company shutting down was unfortunate because while that PR is nearly feature-complete it is lacking in a functional CLI, documentation, updated examples, and tests.
If none of the previous core contributors are available to continue development of the project, would you be willing to open it up to a new team of developers?
We’re ramping things back up with integrating with the Linux Foundation. I’m about to get married, but we’re going to have a meeting on April 5th (see #873) for anyone interested in taking a contributor/leadership role for Horizon. We’ll have former team members as well as current leadership members on the hangout available to discuss the roadmap, issues, etc.
In the meantime, if any of you have the time and are willing to polish up and document #865 we will merge it. My thought is that if someone can take ownership of that PR and provide us with good docs we'll be in a great position for continued active development.
Polishing and documenting https://github.com/rethinkdb/horizon/pull/865 is not really an easy feat for anyone but the author of all of the changes. People are waiting for this. Can you, the original developers, please just take a day and provide some reasonable documentation. I'm happy to commit to the project and I think there are quite a few others. You are blocking all progress by saying nobody should continue working on v2 but not making it possible to work on the https://github.com/Tryneus/horizon/tree/grey_plugins branch. You cannot expect anyone to put in weeks of following along the commit history to reverse engineer what you were trying to accomplish there.
