Call for maintainers 💡

[jstoiko]

@alecsammon does not have the bandwidth to maintain the project anymore. He has agreed to hand over the project to whoever is willing to take over. We could also consider hosting it under the https://github.com/raml-org organization.

I am tagging a few people here based on the latest PRs. I also think those PRs would be a good starting point for a new release.

@vbartusevicius
@InfopactMLoos
@AnzeDspot
@therealgambo
@jefferson-lima
@RETFU

(I apologize in advance if you're not interested but this seemed like the best way to do this)

[therealgambo]

Sounds like a great idea to have it hosted and maintained under the scope of the raml-org namespace. This should provide additional credibility not only to this project, but also to the RAML specification.

I'm still surprised to this day about how little traction there has been (other than this project) for a fully compliant PHP library that implements the RAML specification considering there are still plenty of PHP powered API's and websites all throughout the internet.

Personally, I feel like this is something Mulesoft has dropped the ball on slightly, the RAML spec is great however I always feel like it is a daunting task trying to incorporate it into a project with such few libraries that met the spec unless you are writing something in Node, Java or .Net.

At the moment I think this (https://github.com/eLama/php-raml-parser) is probably the most recent fork currently alive with activity. Please correct me if you find another.

[jstoiko]

Thanks for the pointers.

@arheyy: would you and the folks @Elama be interested in merging your fork back upstream and taking over php-raml-parser?

[InfopactMLoos]

@jstoiko thanks for the mention but as my company switched to swagger we are not currently working on RAML at the moment. I really liked working with RAML so its good to see this being picked up again, good luck with the project!

[vbartusevicius]

@jstoiko - our company uses RAML to automatically generate PHP/JS code, so I think it could be maintained at least temporary by me. I would prefer https://github.com/eLama/php-raml-parser fork to be moved under raml-org. This means RAML0.8 support gets dropped.

[martin-georgiev]

@jstoiko, here in @Lendable we are also using RAML. I and my team can give a helping hand in keeping the project alive and cared for.
As an original author @alecsammon suggests handing the project to RAML.org, is there a broad consensus on this?

[vbartusevicius]

I think official parser for PHP would be great, of course if raml-org agrees.

[jstoiko]

Sounds good! I propose that we continue this conversation on Slack. If that’s ok with you folks, you can join here: https://raml.org/slack and ping me there, I will create a dedicated channel for the PHP parser.

[jefferson-lima]

Thanks for mention, but currently I don't have the time to make a commitment with this project, but I will keep following it and contribute whenever I can.

[vbartusevicius]

I wanto to invite @eduard-sukharev in this discussion as I see he did a lot of code reviews/merges.
Eduard, maybe you could help us on moving https://github.com/eLama/php-raml-parser fork under official raml.org? Or maybe you know the person currently maitainig this fork?

[martin-georgiev]

I've merged the @Elama 's fork back in master and some RAML 1.0 support is now provided by the new major version 3. This brings us very close to a state where the repository can be moved to the @raml-org organisation.

[jstoiko]

The repository transfer has been completed and I am happy to report that raml-php-parser is now hosted under raml-org.

@martin-georgiev has been helping a lot lately and will keep contributing, but the more we are the better. So if you are interested in contributing, please feel free to get in touch. The best way is to join our #raml-php-parser channel on Slack.

[martin-georgiev]

@DenisovMaksim will you and your team also be interested in collaborating on the project?

[martin-georgiev]

@arheyy will you be interested in collaborating on the project?

[eduard-sukharev]

@martin-georgiev we as eLama team are glad to see our contributions were merged back upstream, we'd gladly provide more contributions if our company feels the needs for ones. Currently, though, we don't have much dev power available to do more development on this project, although we still use RAML and Raml parser lib.

[arheyy]

@arheyy will you be interested in collaborating on the project?

Sorry guys, have no time