Contributors mailing list archives
Open Source Integrators, Daniel Reis
Regarding the "smarter bot" ideas: although it's typical for a bunch of programmers to come up with a solution to a problem by throwing more engineering into it, I feel there's something to it, it just needs more crystallization and then a hackathon to make it happen. Maybe a good theme for a team at this year's online code sprint?
As a reminder, OCA Days are coming up, and there will be the usual code sprint.
It would be nice to have a group working on OCABot improvements.
This can be to work both on code or process change proposals.
It has been discussed.A question that popped to my mind yesterday is one for the board - has it ever been considered for OCA to pay people to fulfill maintainer roles within the organisation? Money seems to be something thats available, and the spending of money on OpenUpgrade has been a great things throughout the last years also.
The feeling was that doing so it would work against the volunteer spirit of the community, and could break volunteers motivation.
Investing on better tooling would be better.
For the record, there has been an initiative for bounties, where people could publish a bounty, awarding a payment for a task, but it didn't get traction.