If you haven’t noticed, not much has been going on in the SVN, but don’t worry! I should be able to work on SnowCMS a lot more now, as I will have time to work on it in school every other day.
For those of you that care (which most probably won’t 
), I am going to submit SnowCMS in my nomination for the Oregon Student Technologist of the Year Award, and I would like to have a finished (or almost finished) product by May 7th. So be sure to pay close attention, as I should be working hard, especially with Spring Break starting Thursday!
Also, I have been pondering about changing SnowCMS a bit. I would like to start thinking of SnowCMS more as an operating system (which is why most things will be plugins), my thoughts started with the update part of SnowCMS. Usually CMS’s wait a bit to fix bugs, or at least to send out the update, same with security issues (well, except when it is major, it gets shoved out ASAP). However, with an operating system, updates come when they come, and separate (like with Windows, you know, Patch Tuesday 
), so why not with SnowCMS? Why not release a fix to a bug when it is fixed? Why not release a fix to a security issue when it is fixed (even if it is small, when it comes to large sites, a small issue can be made huge)? And of course, major security issues ASAP.
That is my idea… Updates will be dispatched on a once-its-fixed basis. Also, with versions, once a patch is released, the version is incremented, like with SnowCMS v1.0, the first patch would be v1.0.1, which isn’t so with operating systems. It is more like MAJOR.MINOR PATCH# or REV#, and that’s how SnowCMS will be as well, but if you choose to show the version in the footer, you will only see v1.0 or v1.1 (.1 would be like a service pack, by the way). When it is time to check for updates (either manually, or automatically), each system file will be checked for a version number (or a checksum, but if someone manually edited a file, that could lead to issues, though its probably not a good idea to edit it, but hey, it’s yours), if it doesn’t match what it should be, well, there is an update required! It is more than likely all patches will be distributed in unified diff format).
That is my idea at least. I would like to do that, but if it gets to be troublesome (or someone points out a major issue), I will reconsider.
Anyways, till next time, cya!