Re: Barracuda: BarracudaMVC Roadmap

Hello Christian,

I don't have anything super important that I'd like to get into CVS
right now.  Just name the date and I won't commit anything after that.

Diez is supposed to be moving some stuff from his contrib package to
the comp package, but I'm not sure what his timeline is on that?  That
probably isn't overly important either except that it should be done
before the next release.  I think we can move stuff to the new server,
work on things for a while, and then release, so this shouldn't be an
issue.

And I like the idea of not worrying about the re-work of the docs for
now.  Getting the server up and running and moving it to hosting is much more
important right now.

Jake

Friday, December 13, 2002, 11:39:58 AM, you wrote:

CC> Hi folks,

CC> Ok, Shawn has got the server up online at ATMReports so that we can finish
CC> setting everything up and start testing it. SO...one of the things we need
CC> are people who can spend a bit of time playing around with it to make sure
CC> things are working correctly. Once that is done, we can then box it up and
CC> ship it off to our coloc site. I'd really like to get this done as soon as
CC> possible, SO...lets put together a roadmap of what needs to happen in the
CC> next two weeks so we can get this done before Christmas!

CC> Consider this a working list... (we probably need to create a page for this)

CC> Setup & Installation
CC>   -set up mailman lists
CC>   -figure out how we are going to archive/search
CC>   -set up bugzilla (do we want to do this now? later?)
CC>   -set up ssh access for committers
CC>   -set up anonymous cvs access for everyone else
CC>   -set up the /Barracuda website
CC>   -set up a daily builds mechanism

CC> Testing
CC>   -recruit a small group of 10 or so who will be willing to test things out

CC> What else do we need to do? One of the obvious things that needs to be done
CC> is to revamp all the documentation, etc so that its current. I was going to
CC> take this opportunity to rework the look and feel, freshen up all the
CC> content, etc. HOWEVER...now that I think about it, maybe the fastest way to
CC> do the cutover is simply to roll everything over as it is (ie. in terms of
CC> look and feel and content). Then we can revamp the website part of things
CC> once its up and running...

CC> The advantage of doing it this way would be that we could make the cutover
CC> much more quickly. Which would really help as I'm going to be offline all of
CC> next week while I travel back to MT (where I'll be through Jan).

CC> SO...that would be my suggestion...thoughts? My basic thought here is that
CC> we want to get switched over as quickly as possible, update the build
CC> structure and the location of the source, and then get the site up and
CC> running. To do this, we really need to freeze cvs submissions at b.e.org as
CC> soon as possible...this is a good time for me: I don't have any pending work
CC> to be done anytime soon; Jake and Diez, will it work for you?

CC> Let's get this thing rolling...

CC> Christian
CC> ----------------------------------------------
CC> Christian Cryder [[email protected]]
CC> Internet Architect, ATMReports.com
CC> Barracuda - http://barracuda.enhydra.org
CC> ----------------------------------------------
CC> "Coffee? I could quit anytime, just not today"

CC> _______________________________________________
CC> Barracuda mailing list
CC> [email protected]
CC> http://www.enhydra.org/mailman/listinfo.cgi/barracuda
CC> FAQ - http://www.jguru.com/faq/Barracuda



-- 
Best regards,
 Jacob                            mailto:[email protected]

_______________________________________________
Barracuda mailing list
[email protected]
http://www.enhydra.org/mailman/listinfo.cgi/barracuda
FAQ - http://www.jguru.com/faq/Barracuda