Hello,
I'm testing out Observium and I like a lot of the things that Observium does. But what really irks me is the way and style of releasing new versions and committing to the SVN repository.
1) Commit messages. To quickly get a feel what changed between revisions I consult the svn log. That is the primary source of information. In the Observium SVN this often leads me to read things like this:
r4147 - CODE, Y U NO LOOK RITE r4140 - Me need your soul, more souls. >:-> r4139 - you're not ready for this. :) r4125 - disable whatever the fuck that is r4101 - add some crappy errors
And on and on.
Things like that make me question the code quality that is committed to the repository. What kind of project do you want to be with these kind of commit messages? Mind you, I know that many people use cheeky or funny commit messages but normally they include some kind of explanation/context to see what has changed. That's missing here.
This hurts the project. It projects an immature image.
2) Follow up to this: How is code quality review done? What are the procedures to decide when code is added to the repository and how do you make sure that the repository is stable for the majority of the users?
Also I noticed that you do not separate code and HTML output which is another source of potential problems and accidental breakage. Is it planned to rewrite this to use a templating system?
Regards
Sebastian