My company is evaluating Open Project, among other solutions. We're outgrowing our current system, and also beginning to suspect the developers aren't interested in moving it forward, or even properly maintaining it. We like that Open Project is open source. We think building as much as possible on open source will, in the long term, be a win. We also have a lot of Ruby knowledge in house, so we could contribute to it ourselves.
> beginning to suspect the developers aren't interested in moving it forward, or even properly maintaining it
This will be true of all systems. Devs hate adding comments, writing documentation, maintaining tasks/wikis/etc., and everything else that we need them to do. Some people try to make them track their time, which I think is both pointless and unlikely to happen.
The only solution to this is to move it out of the "discipline" column and into the "process" column. For example, I set up git hooks so that a commit will be rejected unless it's tagged with an issue number. And then I have another rule that says that issues aren't accepted unless they have the important fields filled out ("steps to reproduce" for a bug, "user story" for a feature).
It's not perfect, but it definitely creates better habits overall.
Core maintainer of OpenProject here. We do welcome all outside contributions, but please note that while the application relies heavily on Ruby/Rails for backend, API and rendering, a large portion is also Angular/Typescript.
This will sometimes make it harder for developers to start working with OpenProject since for many topics, you will need both (e.g., API changes and frontend work). Especially so since the application has evolved for more than 10 years.
I wasn't clear. I'm describing the developers of the project management system we now use. They announced new scheduling features over a year ago, and nothing has happened. And there have been a lot of slowdowns and crashes, which they have been slow to fix.
Our developers like tools that support their processes. They just want something that works, and is under active development.
I'd suggest you also consider ProjeQtor. It's astonishingly feature rich and at the same time, very lightweight resource-wise (PHP + MySQL and you are good to go).
Core contributor of OpenProject Here, this ist an Epic that ist high up in the roadmap but due to its complexity has been pushed out the past two releases.
This is something where we know it's painfully missing and is being planned and actively worked on.
What has everybody's experience been?