Ok so what you're seeing is pretty much beta actually. There is only one more core function that I need to finish up and that's the ability to leave comments on each media item. So you can leave comments on specific photos, videos, audio, etc. under each one when you view them.

Then I need to finish up with design. I have setup "theming" provisions so there will be a default theme and then users will be able to add new folders with themes where there will be files that override the default if present. So I also have ot add in the backend the ability to choose which theme the site is using. Then we'll be cooking with fire. It will actually be a completely customizable application there in terms of looks.

Now. WHEN that is all done I will be releasing a limited beta version to people. Not that many people are stumbling upon this site now...so I also have to advertise, but I'm only going to need feedback from a few people and more specifically those who are more inclined to spot errors and understand web design and development a little bit. Not that some random person stumbling upon this site couldn't get their hands on a beta copy...just ask.

AFTER I start to get some feedback and start to work on some tasks in my trac for RC1 I will release a true beta open to the public. This will be a larger effort in advertising and getting this app out there. It will also be a half step between beta and release candidate 1.

This is where I plan to be in shock haha. I expect all my todo's and issues in trac to go WAY up for RC1 pushing off my anticipated delivery date of March 1st...ha. Yea, way off there. However, what we'll have is a very stable blog application for everyone to use. I'm hoping any major issues (don't exist ha) will be solved by then and I'll begin to polish things off and make everything more user friendly.

So we'll be in the thick of it soon then. After I finish RC1, I'll be setting up provisions for accepting feature requests and such. I'll probably have a public trac setup at this point too where I can keep things separate from my svn and core tasks (two sets of books, ooh).  

I've come up with the licensing and game plan for Minerva. Phew. That was hard. I did a lot of thinking, but I'm going to release Minerva blog as a blog (not a larger social/commnity site thing like myspace, etc.) and as far as anyone is concerned it will be like a cross between Blogger and WordPress...Semi-restricted. The core functionality will be encoded and people won't be able to change it. People will be able to change how it looks though. 100%

So that may come as a big disappointment...but I've been around open source projects for quite some time. Many are not very successful. LOL I know I'm using CakePHP to build this app which is an open source project...one of the few I DO consider successful, but I won't have my application tainted dammit. That doesn't mean it isn't open to change by public voice...there will just be a process to these things.

I do believe in a community effort and value the insight of everyone no matter how silly it may seem. It means they are thinking and are aware of things. Everyone needs something different and Minerva blog will NEVER be 100% solution. So I'm not going to try and make it so. That's the mistake of too many open source projects and CMS'. Too much push and pull and too much spread. BUT. If you're looking for a great blog where you can also share all your media...then Minerva blog is going to be for you.