Re: [SPMSDev] Starting SPMS4

[Fleet A. S. D. <cn...@br...>]

Dan,

I would like for the Requirements listing you are putting together to be
public before we get started on any coding.

I would like us to have a solid requirements document put together, and
then additionally a solid design document detailing how each of the
requirements will be implemented. they should be two documents and the
three of us as project admins should review both documents before they
are made public.

Once that is done it makes it easier to assign tasks to other developers
for them to start working on.

Once you get your thgouhts together start posting them here and we can
work throguh the whole thing.

-Ed

Dan Taylor wrote:

> Hey Folks,
>
> As your both aware I've started doing things towards a new version of
> SPMS, despite my leanings towards Java code recently SPMS will
> continue to be a PHP project (However, I have considered a Java Port ;)).
>
> Initially I'm calling this SPMS4 rather than SPMS 3.1, all of the
> version 3 source code and database layout has been dropped. I'm
> re-developing SPMS from the ground up, this is in response to the
> feedback I've been given by users and because of my own experiences
> with SPMS. The main aim of the project is to remove a series of
> security concerns I have with version 3, and to re-build the core of
> SPMS in to a series of objects. Additionally I am going to be adding
> functionality beyond that provided by previous versions of SPMS.
>
> I tidied up the Sourceforge site a little yesterday, I have disabled
> CVS access for everyone but us at the moment. While I'm working on the
> SPMSCore package I would prefer it if I was the only person committing
> code to the repository, I have set up a CVS ACL which limits commit
> rights to the three of us (Yeah, we're the only ones on this list
> right now too, I'll add other people back if they request it).
>
> Currently I have a draft requirements list for SPMS4, as I analyse
> each requirement I'm designing it too. Currently I have a firm design
> for the SPMSCore Package and for the manifest system, other sections
> of the system will be designed as a get through the mountain of
> possible additions and modifications to version 3.
>
> As I get further through this I'll send out more updates, because I'm
> LOA from stuff Thursday and Friday this week I suspect I'll have most
> of the Core written (hotel rooms are lonely places ;))
>
> ~Dan
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing
> & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Spms-developer mailing list
> Spm...@li...
> https://lists.sourceforge.net/lists/listinfo/spms-developer
>
>