Re: [Inflatableweb-devel] Where to from here?

[<inf...@li...>]

>> CCS fixed and tested
>
> what's CCS?
>
> I just added a really short summary. i didnt do anything nice because 
> i was
> too lazy to tramp in, so i just used emacs from the shell.

CCS is bad typing, I meant CSS.  While I prefer vi, you can use emacs 
if you want to ;)

I think the update you made is fine.  I want to fix the style sheet and 
rename the file to index.html.


>> 2.  I want to get a private Mason install set up on the SF server.
>> I'll need to see if the account provides everything we need.  I'd like
>> to be able to use SF to compare and contrast with my perlmonk.org
>> install.  Plus, as we get further along, it would be nice to 'eat our
>> own dogfood.'
>
> should be able to install mason because we have shell access. might 
> need
> serious .htaccess majic, but you know how to do that already.

I checked out the SF web services FAQ, and it looks like the .htaccess 
directives we need will be there.

I plan to keep super careful notes on the installation process and 
create a HOWTO.  The  HOWTO can act as a core design doc and as a tool 
to collect data for us on how the process works on different systems.

>
>> 3.  Design documents:
>> 	What features do we need/want?
>> 	Implementation ideas
>
> start poking stuff into the docs thing, however lame they are. then we 
> build
> from the docs.

Exactly.

>
>> 4.  Code.  Actual code.  Many SF projects choke when it comes to this
>> one.
>
> 'sfact. but i'll work best from docs, because it helps me think, so 
> i'll try
> and write my thoughts down. sometimes activity counts.

That's why this is #4.

>> 5.  User documentation.  See comment for #4, we'll need this too.
>
> that's easy for me. ideally, one could write all the docs first and 
> then
> implement the docs....but we all know that never happens.... :-)

4 & 5 should be concurrent.  But I'll be happy if we can manage any 
useable docs

> i've done my bit for the next few days, must attend to homeowners 
> association
> business next...i'm my own preemptive scheduler...

Thanks.  With my schedule being what it is, we're going to have to take 
baby steps.  Which is fine, as long as we keep making progress.

--Mark