Well, to make a short story long, I have a friend in charge of online education at a 90 school for profit education group, teaching college/grad students. They had a custom solution being developed for them that would roll out in mid Jan. The corp the developers were part of got taken over by outsiders who shut down their IT/DEV group last month. Now he's only got the moodle install they were using for a small group of courses, no moodle staff, and no budget for moodle staff until 3rd quarter of next year because they spent 7 figures on development over the last year. So I am doing this on my own time and dime to help him out while he gets it up to speed to handle the entire online course load. And I still need to do work on my own client's projects if I want to eat and live indoors.
Sooo, I've got no time for being part of the full time dev cycle here, or creating/finding/joining/managing the "appropriate" git project to post code, request reviews, etc., and I won't have the luxury of waiting for code changes to be approved and fully tested by moodle and then slowly bubble up through consecutive releases. If I have to fix something in the core, or anywhere really, I'll code it, test on the server, and if it seems sound, I'll implement it and just keep to myself ;)
That way I can fix useless error messages like this one that has popped up 3 times in the last 2 days while clicking around here, without waiting on the dev bureaucracy or posting to and managing git repositories.
"Coding error detected, it must be fixed by a programmer: No further information available for this branch"
That's an error that should go straight to a log with some useful data attached, not shown to an end user with no way of acting on it or reporting it. The pages it came up on didn't even have a contact link. They need to review the ui standards and error handling for this project in a big, big way, and I certainly don't have time to lobby for that either.
After spending 2 full weeks reading everything I can about moodle and it's use, I've come to the conclusion that's it become so large and overly dogmatic and controlling over recent years, it's stifling it's own growth, creativity and usefulness. Like wanting people to read and comprehend a 10 page long statement of "Moodle's social constructionist pedagogy" before learning how to contribute, so they can stay in keeping with it. Really? I'm a programmer, not a philosopher or sociology professor. The fact that one even exists says something, let alone that they're pointing programmers to it as a guideline. Enough of my whining though, thanks for the themes and input, I really do appreciate you taking the time, I wish you the best of luck