We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
Would the Omnibus project be interested in a contribution to add Mercurial support in the
source DSL directive?
I am the maintainer of the Heptapod project, an open source fork of GitLab that provides Mercurial support. Omnibus is a major packaging and deployment tool for GitLab, as well as for Heptapod (only partially at this stage).
Because its own source is versioned with Mercurial, the Heptapod project will need Mercurial support to complete its Omnibus packaging effort. I'd rather do it directly upstream in Omnibus so that other projects could use it than in our [configuration repository](https://foss.heptapod.net/heptapod/omnibus-heptapod).
The DCO and Apache2 license are fine with me.
What do you think ?
Thank you for submitting this. Omnibus primarily serves to build Chef products. We're glad that it has helped out other developers all over the world, but we don't put active development into functionality not required by Chef products. At Chef we build all our projects off GitHub so expanding core SCM functionality past git isn't something we'd be taking on. You're more than welcome to add this functionality and create a pull request to the project if you'd like to see it part of the tooling.
Attachments Open full size