Looking for volunteers to join your project? Need help with a script but can't afford to pay? Want to offer your services as a volunteer to build up your portfolio? This is the place for you...
regarding __autoload : i strongly vote for using autoload. if the only reason for not using it would be that users will have problems getting their own class loaded i really think that this could be easily handled through documentation or via a configurable class locator. e.g. :
astions wrote:We aren't designing this system to be easily changed by developers, we are developing it to by a high performance store for businesses.
Noone running a store that needs particularly high performance will run it on a basic installation of an application. It will always be tailored to the specific environment.
Noone running a small store requiring average performance is going to settle for a standard installation, they'll want custom features.
Writing an inflexible system simply means noone will use it.
After I thought about it for a second I edited my post and took back what I said about it being easy to modify. It does need to be easy to modify in the sense that it should be very, very easy to change the look & feel of the site and to add/remove features.
As for your comments about noone using it because it will be tailored for a specific environment, I'm tempted to disagree, but I might not fully grasp what you are saying.
This is an ROI issue, Return on Investment. There are hundreds of thousands, if not millions of business that simply cannot afford to pay programmers to modify/develop a complex system such as this.
Our goal is to create a system that is flexible and can be used in the widest variety of circumstances, and to provide a high ROI. I also feel that the system should be as responsive as possible, hence the use of an autoloader.
I've added myself to the volunteers page in a non-coding capacity. I've written several shops and managed the development and installation of several more. Looking through the volunteer list it occured to me that everyone is interested in coding the thing .. fair enough obviously .. but someone needs to be looking at this project from the perspective of a shop owner .. I've got enough time to spare to do that I think.
This means I'm very, very likely to be the person who asks the most annoying questions, and pesters people to comment/document their code. I apologise in advance.
I'll go for the code reviewer and/or maintainer roles.. the others seem to require knowledge of areas I am not familiar with At a push I could do the DB role but I'm no DBA
Jenk wrote:I'll go for the code reviewer and/or maintainer roles.. the others seem to require knowledge of areas I am not familiar with At a push I could do the DB role but I'm no DBA
Good point, we should define required skills for each role.
Jenk wrote:I take it you won't be volunteering for the business logic role then Onion?
Heh. I've developed several online commerce applications, and I'm certainly willing to do it, but I actually think it'd better suit a small group. I've only worked with British retail companies so I realise I know nothing at all about US online retail (such as how sales tax rules work..)
Actually I rather fancy the Project Manager gig. Entirely for personal reasons.. I think project management of a good size OSS project would look lovely on my resume.