I recently posted a release note on the mod_perl mailing list. Someone responed to my cry for help and we started discussing the project a little. One of the comments was that, he didn't know it existed. If he had known, he would've helped sooner. Here's my question.. I posted 'it' on Freshmeat, I posted releases on the Sourceforge pages. I occasionally update the listings at CMS Matrix. What else can I do to let people know the project exists without bragging?
Re:blog it
Beatnik on 2006-06-07T20:04:44
In that case... Spine: Just do it! You can't beat the feeling! Keeps on going and going! Be the first to know! Get more! The cream of Manchester! I am Canadian!Re:blog it
parv on 2006-06-09T04:40:12
I was quite surprised to find no mention (or link) of (to) name of the software in your blog entry itself; found, instead, links to three "entry points" of the sites where you did mentioned your software.
Anyway, thanks for the relevant SourceForge link. BTW, "Alternate datatypes" page -- http://spine.sourceforge.net/alternate.html -- seems to be missing (file-not-found).
I also thank you that SPINE can work with mod_perl2 for various reasons
...
- Currently i am working with a PHP4 CMS (of rather messy code base where global variables play hide & seek; powers-that-be have focus on the web interface, not so much on cleanup/maintenance of the code) which is used with Apache2. I rather not deal with two versions (2.2 & 1.3; latter is used by Pair on shared servers & i installed locally to mirrot/test my portion of the Web) of Apache.
- I really need to learn about Perl DBI, some major/popular database, and mod_perl* so to be able to change jobs (especially now that i can put PHP too on my resume).
Re:blog it
Beatnik on 2006-06-09T09:27:54
I suck at marketing:) I always feel like I'm overdoing it. Anyway, I'm glad you find it useful. There's actually a lot more stuff included than it first appears. I hope to update some documentation pretty soon (thanks to a new contributor).. as well as get the stable release out the door. The mod_perl support has been added since that beta, but I tried to stick to the same basics as mod_perl 1. Let me know what you think and spread the word if you will. Patches, contributions, cash, free beer welcome :) Re:blog it
Alias on 2006-06-08T06:29:04
Half the problem is that it's a bloody CMS.
Which is not to insult your application, since I've never used it, but you have created an application in the most sexy/popular area (CMSes) or the most sexy/popular coding type (Web Programming).
You are bound to have some significant issues with promotion amoungst the bazillion other CMSes.
But on that note, there's a number of CMS recommendation/listing sites out there, and you should be listed on every single one of them if you can.
Most of those lists are PHP-heavy and whenever I'm looking for something like that I get annoyed there aren't many Perl options available.
And finally, add it to your sig, and boil your app down to something that set you apart, so people will get curious.
is trivia
Best Regards
Adam Kennedy
Spine - The Perl CMS that installs anywhere (standalone/CGI/mod_perl/clusters)
Re:blog it
Beatnik on 2006-06-08T08:20:51
I think one of the problems is that I don't have any reference sites. Back in 2000, when I started developing it, there were only a handful of of CMSs out there. I based the concept on a patchy PHP based CMS. It was pretty difficult to have the app grow as fast as the technology... so it got old pretty fast. Moving it to mod_perl was, IMHO, a pretty smart thing to do. It boosted functionality and stability. I still try to stay away from the real buzzword technologies, try to keep the dependency list as small as possible and do what I think is right. In the end, I do it for myself:)
I'll probably start looking at some other listings and get it added. I'm not sure what I'll have to do to get it added to the mod_perl related software page but I'll try sending a mail to the docs-dev mailing list.
