[Seattle-editorial] Re: seattle imc mir migration

[{m2}]

seattle imc comrades,

hello there.  portland indymedia would be proud to assist seattle imc with
the migration to mir.

> Can we set up the new website
> with default templates and change the design (look) after the fact or
> does it need to be a more integrated process?

yes, you can use existing templates (portland for example) and change them
as you go once the dev/test seattle mir site is up and running.

> there are methods available to make our archives
> available as part of the new website.

yes, this is well established.  and since san diego imc most recently went
down this path, i believe they can help.

> What are the hardware requirements?

portland indymedia has collected all the hardware you need to setup your
initial seattle mir site.  donated and purchased items give you the
following:

1 - 1.3 Ghz, 512 MB RAM, xxGB drive "publish" server
2 - 500 Mhz, 256MB RAM, 30GB drive "static web content" servers

the only remaining hardware item you need is a 40GB+ hard drive for the
"publish" server.  the non-donated hardware portion of these three servers
(RAM, 2 cpus, 2 motherboards, 2 hard drives) was purchased used by me (m2)
and i am requesting to get re-imbursed by seattle imc for the $175 total
cost of all three servers (how is that for a bargain!).

three of you will need to locate these three servers on a dsl/cable
connection.  the publish server needs to be located on the connection with
the fastest of the three connections (upload), and preferrably a static ip
for the publish connection.  before we can begin the dev/test install, we
need two of you to provide a dsl/cable connection for the static content
web servers (and find a way to get the servers up to you), but the publish
server connection can come later because we have a location with a static
ip address right now where we can setup the publish server for dev/test in
the short term.

m2
portland indymedia collective


> Ok folks, it's official.
>
> I propose MIR as the new code base for the Seattle IMC website because I
> like the look and feel of other sites using it most and we have more
> possibility of local or regional support for it than for SFActive.
> According to Kellan, there are methods available to make our archives
> available as part of the new website.
>
> I'd like to try to solicit the help of the Portland IMC techies and
> Kellan in the migration process and in the mean time put the call out
> for more locals who are interested in getting involved on the long term.
>     It seems like there is volunteer energy already waiting to be tasked
> with website design tasks.  How do the different tasks involved with
> code migration need to be broken down?  Can we set up the new website
> with default templates and change the design (look) after the fact or
> does it need to be a more integrated process?  What are the hardware
> requirements?  Stefani or Sheri, where do we (the Seattle IMC) stand in
> regards to our DSL service with Speakeasy?  Hasn't the bill been going up?
>
> my 2 cents.
>
> -jason
>