What's in for the future of pytest-bdd?

[manoelpqueiroz]

Hi guys!

I feel there is not so much information to help community members get more familiar with the vision for the project and its goals in the short, medium and long terms, either as a means to understand what users should expect for future versions or as a potential contributor towards this vision.

For instance, the CONTRIBUTING.md guide only mentions how to setup a development environment, but doesn't have any guidelines on how contributors should behave, things to pay attention at or general policies adopted by the project.

I quite like using pytest-bdd in my projects and I'd certainly look forward to helping maintain this library, but with the insane amount of information one has to deal on a daily basis, it's hard to commit to a new endeavour while oblivious of priorities and technical information/caveats about implementation.

If the maintainers could come forward and answer the following questions, it would already help a lot and, if possible, I'm willing to help with organising the work and vision in formal documentation while the team focuses on implementation! 😃

• What is the roadmap for pytest-bdd? What are the major features that would be desirable to be implemented in the future? What are the main technical debts the project currently faces?
• What aspects of the project that are not directly related to the codebase would you like to see improved and why?
• What role do you see pytest-bdd could play in the current software engineering landscape? Do you see pytest-bdd could be integrated with other development tools? If so, which ones?

Looking forward to hearing from you!