[steering] Migration plan (was: Gonna start calling votes)

[Martin Burns]

On Sun, 12 Jan 2003, Dean Mah wrote:

> But at what point do we open this up to theforum?  I don't think that
> we should make any more decisions until it is opened up to the
> membership as a whole.  I think what we've done here (in steering) is
> to decide in principle that we would like to change the hosting,
> change the backend, and change the design.  Shouldn't it be opened up
> to comments or a vote now by the membership?

2 possibilities:

1) Take it to theforum as an in principle thing ie a simple yes/no on the
principle and *not* as an extended discussion which repeats everything
we've said, but take 5 times the time.
[btw unless there's absolute revolt over the principle, I would expect
a principle we recommend to be accepted. I would also expect our relevant
groups to also work with it and be happy about working out the detail]

2) Work this to a slightly greater level of detail and write it up into a
solid proposal.

> If we are going to make progress with this, I'd suggest that we break
> it down into smaller pieces.  I'd like to see more people get in on
> the discussion and that might mean moving it to desdev or theforum or
> sysadmin.

Bits will of course need to go to all our respective groups...

Cheers
Martin

> On Sat, Jan 11, 2003 at 10:39:40PM -0800, Marlene Bruce wrote:
> > >It sounds like no one is opposed to moving the sites in general.  It's
> > >the specifics that need to be hashed out.  Perhaps this should be
> > >moved to another list like desdev or theforum.
> >
> > We can do that once we know what the big picture is, and it's more
> > than just moving the sites. We need to define that picture a little
> > more or we risk having too much chaos by moving to the lists early.
> > Hence my suggestion that we develop a "deadline for the big
> > picture/pieces, and then milestones to measure our progress."
> >
> > I applaud you for wanting to push ahead, we could use more energy. If
> > you can keep doing what you are doing (figuring out the pieces that
> > need to be figured out and asking good questions) we'll get further
> > faster. I think rather than theforum we should take questions to the
> > different committees and have them help define things a bit more.
> >
> > If you know enough to proceed to desdev about moving the sites, go
> > for it. But will doing that impact any of the other things I
> > outlined?
> >
> > Where will evolters be hosted? What will evolters require?
> > When will we dump m.e.o.? Will we have to move those files too? Will
> > the same tools be available after a move? When will we ditch Oracle
> > and what will take its place? Will a site redesign affect the move in
> > any way (or be affected by it)?
> >
> > I'm far from knowing everything, so I'm relying on your feedback to
> > help decide the best course of action. If that feedback need to
> > include the opinions of others not on this list, by all means develop
> > it elsewhere and bring it back here. Just keep the big picture and
> > impact on other things in mind.
> >
> > >What is evolters.org?  What needs to be done to get it going?
> >
> > It's intended to take over m.e.o. in a way, but basically comprises
> > the community end of things that were outlined by Isaac (more below).
> >
> > > > 2. Move l.e.o. to:
> > >> a) e.o.uk, or
> > >> b) a sponsored (or inexpensive) service
> > >> (How is CSS-D doing as a proving ground?)
> > >
> > >I liked the idea that was proposed to move this first.  My message
> > >below questions how we are going to do that.  I'd like to see a
> > >concrete migration plan in place that addresses all of the issues.
> >
> > Can other people on desdev help you define what's needed? I'm not
> > back-end so I can't help there.
> >
> > > > 3. Ditch Oracle (for which our license was never satisfactorily
> > >> confirmed by Dan, BTW) in favor of MySQL or Postgres.
> > >
> > >Send this to desdev and have someone work on porting the database.
> >
> > Someone else who knows back-end stuff should do this. Feel free.
> >
> > > > 3. Create evolters.com to foster the community.
> > >> What Isaac said:
> > >> Some kinda blog space, member profiles, ability to network
> > >> (professionally or socially -- find other people in your area).
> > >> News/community articles, and recipes if people want to post them
> > >> (taking care of FEO).
> > >
> > >So is this a one page kind of thing?  No FTP uploads?  What needs to
> > >be done for the backend?  Database?
> >
> > See Isaac's email to theforum on 10/31/2002, subject line "Evolters"
> > (http://lists.evolt.org/theforumarchive/Week-of-Mon-20021028/006537.html).
> > That and the subsequent discussion should fill you in.
> >
> > > > Given what I understand to be the issues, I don't have any
> > >> objections to the above.
> > >
> > >I'm interested in the technical issues.  But maybe that discussion
> > >should be moved to desdev or theforum.
> >
> > I'm obviously interested in the bigger picture. Feel free to go to desdev.
> >
> > > > Do we want to set a deadline for the big picture/pieces, and then
> > > > milestones to measure our progress?
> > >
> > >We really need someone to take the lead on this.  This is where
> > >Mishka's whip really got things moving.  :)
> >
> > Hey, what do you think I'm doing by asking all these questions? I was
> > the whip long before Michelle. I've just mellowed a bit. :o)
> >
> > Marlene
> > ------------------------------------------
> > steering
> > http://lists.evolt.org/steeringarchive/
> ------------------------------------------
> steering
> http://lists.evolt.org/steeringarchive/
>

--
"Names, once they are in common use, quickly
 become mere sounds, their etymology being
 buried, like so many of the earth's marvels,
 beneath the dust of habit." - Salman Rushdie