Page 5 of 27

Posted: Thu Aug 24, 2006 9:37 am
by Benjamin
I can start on a feature list, I'll see if I can throw it up tonight.

Posted: Thu Aug 24, 2006 10:21 am
by Luke
I wouldn't mind doing the documentation, but I would need to do research on how to write documents like that first. If there is anybody willing who already knows, go right ahead. Otherwise, I will do it.

Posted: Thu Aug 24, 2006 10:23 am
by feyd
Some reading to get you started: http://en.wikipedia.org/wiki/Project_management

Posted: Thu Aug 24, 2006 11:49 am
by Luke
thanks feyd!

How about something like EZCommerce or SimpleCommerce for the name? (Just throwing things out there)

Posted: Thu Aug 24, 2006 2:06 pm
by onion2k
Jenk wrote:or rather, who is going to volunteer to be the doc monkey? :lol:
The doc monkey wields lots and lots of power over code monkeys in a project .. basically the doc monkey is the one who tells the code monkeys what to write .. don't scoff. It's a great job.

Posted: Thu Aug 24, 2006 3:16 pm
by feyd
onion2k wrote:The doc monkey wields lots and lots of power over code monkeys in a project .. basically the doc monkey is the one who tells the code monkeys what to write .. don't scoff. It's a great job.
Indeed. Consider the role analogous to being the game designer of some game. They are often the pitch-man and interface to "the money" -- the people who say "sounds great, build it."

You can choose to share this responsibility amongst each other or whatever you like.

Posted: Thu Aug 24, 2006 3:53 pm
by Jenk
onion2k wrote:
Jenk wrote:or rather, who is going to volunteer to be the doc monkey? :lol:
The doc monkey wields lots and lots of power over code monkeys in a project .. basically the doc monkey is the one who tells the code monkeys what to write .. don't scoff. It's a great job.
I'm the doc monkey in my team at work.. by doc monkey I mean the person who writes the docs, and that's it. No power, just docs. :(

Posted: Thu Aug 24, 2006 10:04 pm
by Luke
Jenk... are you willing to be the doc monkey for this project too? :D Since you already know how, you are obviously the first candidate. I understand if you don't want to though. Either way, we should get rolling on at least a feature set.

Posted: Thu Aug 24, 2006 10:08 pm
by Jenk
I can do, but I'm not going to lie and say I know everything that needs to go into these documents.

However the documents will conform to ISO, GSMS and CMM standards :P

Posted: Thu Aug 24, 2006 10:10 pm
by Luke
do you have a gmail account so we can add you to the googlecode admin list?

Posted: Thu Aug 24, 2006 10:38 pm
by DrTom
I'm very interested in aiding this project. I've had my fair share of time spent
banging my head against the osCommerce code, and have wanted to do
a rewrite for a long time, but never had the drive to tackle such a project
alone.

Anyway, something OOP would probably be the ideal way to tackle this.
Also I generally lean towards Test Driven Development, but that decision is
to whoever is "leading" this project.

Posted: Thu Aug 24, 2006 11:08 pm
by Benjamin
Ok great.

As feyd said we should first create detailed specifications for the store. If anyone wants to start on this feel free. I'll be working on this very soon. I didn't get a chance to tonight as I was hoping. I'll be setting up a default installation of OSC for us to play around in shortly. Once we get the specifications hammered out, we can break it into chunks and distribute the pieces to all the volunteer programmers.

Posted: Thu Aug 24, 2006 11:17 pm
by Luke
I just downloaded osCommerce and I am poking around in their source code right now. I will be jotting down features/modules/etc. while poking around.

Posted: Thu Aug 24, 2006 11:20 pm
by Luke
osCommerce requires register_globals to be on?? WOW. (I have only worked with pre-installed osCommerce sites... so this is the first time I've installed it)

Posted: Thu Aug 24, 2006 11:21 pm
by feyd
If you guys are going to share the documentation duty, it may be a good idea to use a Wiki of some fashion to keep the document in sync and easily editted. I would suggest using one that supports ~dynamic generation into PDF of the current page (if not the entire structure.)