eXhale
5th October 2003, 05:46 PM
OK I have finally found a possible solution for the current problems with VJCentral. I want to post about it here (and not just on the editors forum) so that everyone can give their feedback. Here are the problems I'm talking about:
VJCentral badly needs new features and more functionalities. I feel that the lack of development of the website has been slowing down the evolution of the community, despite fantastic projects like AVIT.
The code of VJCentral is very much outdated, I wrote it about two years ago when I was just starting with PHP and now I feel that things could be done a lot better. Furthermore I feel that VJC could do with a redesign.
I have looked at many many other content management scripts and, while some are quite good, none of them fit my needs. Besides most of the features of VJC would require to write whole new modules.
At the moment I'm pretty much the only developer who can work on the code. Rovastar and robotfunk have much helped me but I'm still the only one who can really dig into the code as I wrote it. I was hoping to find more PHP developers as the site grew but I guess VJing is a pretty remote topic from PHP.
I have three other non-profit websites under development or redesign, all of which are very important for me. I don't give much time to them at the moment but it still takes time I could use for VJC.
I need to pay the bills. I can't dedicate all my time to non-profit projects or I'll be on the streets. It's already difficult for me to keep up with this side of thing.So, I've thought much (too much?) about all this and I've come to a possible solution: I will develop a full-on content-management script (CMS) with many new features, I will use it for my three other non-profit websites AND I'll sell licenses of this script in order to pay the bills.
Now I would love to keep the whole thing open-source, I know that this would be in the spirit of VJC and in fact open-sourcing is what I had promised. However there is just no way I can develop a full CMS by myself if I can't get anything back from it. Open-sourcing would really need a team of programmers and as I said we don't have this here.
There are several advantages to this solution:
The CMS will use a CSS-based template engine, it means that all the web designers here will be able to help if they want. CSS gives a lot of freedom regarding the design.
The CMS will be module-based, this means people with some PHP knowledge will be able to write new sections to VJC without having to touch to the core of the code. I'll setup a module repository with free access, only the core of the CMS and some essential modules will require a fee.
I'll be able to finish my other non-profit scripts without too much efforts.
I can get paid a bit for my efforts and the content and features of VJC will keep on being free. No changes for end users.The only disavantage I can think of, aside from the code not being 100% open-source, is that I'm taking risks by putting my energy into such a big project without knowing if I'll be able to sell licenses. But I'm pretty confident that if the script is what I'm thinking about, it will all work out fine.
So what do you think of this? If this solution is chosen I'm going to just finish a few things which need to be done and then I'll be able to focus most of my time to the development of the CMS. With a bit of hope it will all be online by early next year and VJC will finally be able to keep its initial promises.
VJCentral badly needs new features and more functionalities. I feel that the lack of development of the website has been slowing down the evolution of the community, despite fantastic projects like AVIT.
The code of VJCentral is very much outdated, I wrote it about two years ago when I was just starting with PHP and now I feel that things could be done a lot better. Furthermore I feel that VJC could do with a redesign.
I have looked at many many other content management scripts and, while some are quite good, none of them fit my needs. Besides most of the features of VJC would require to write whole new modules.
At the moment I'm pretty much the only developer who can work on the code. Rovastar and robotfunk have much helped me but I'm still the only one who can really dig into the code as I wrote it. I was hoping to find more PHP developers as the site grew but I guess VJing is a pretty remote topic from PHP.
I have three other non-profit websites under development or redesign, all of which are very important for me. I don't give much time to them at the moment but it still takes time I could use for VJC.
I need to pay the bills. I can't dedicate all my time to non-profit projects or I'll be on the streets. It's already difficult for me to keep up with this side of thing.So, I've thought much (too much?) about all this and I've come to a possible solution: I will develop a full-on content-management script (CMS) with many new features, I will use it for my three other non-profit websites AND I'll sell licenses of this script in order to pay the bills.
Now I would love to keep the whole thing open-source, I know that this would be in the spirit of VJC and in fact open-sourcing is what I had promised. However there is just no way I can develop a full CMS by myself if I can't get anything back from it. Open-sourcing would really need a team of programmers and as I said we don't have this here.
There are several advantages to this solution:
The CMS will use a CSS-based template engine, it means that all the web designers here will be able to help if they want. CSS gives a lot of freedom regarding the design.
The CMS will be module-based, this means people with some PHP knowledge will be able to write new sections to VJC without having to touch to the core of the code. I'll setup a module repository with free access, only the core of the CMS and some essential modules will require a fee.
I'll be able to finish my other non-profit scripts without too much efforts.
I can get paid a bit for my efforts and the content and features of VJC will keep on being free. No changes for end users.The only disavantage I can think of, aside from the code not being 100% open-source, is that I'm taking risks by putting my energy into such a big project without knowing if I'll be able to sell licenses. But I'm pretty confident that if the script is what I'm thinking about, it will all work out fine.
So what do you think of this? If this solution is chosen I'm going to just finish a few things which need to be done and then I'll be able to focus most of my time to the development of the CMS. With a bit of hope it will all be online by early next year and VJC will finally be able to keep its initial promises.