Guidelines

[Jesper]

Hello list,

First of all, thanks for taking an interest. I had no way of knowing
if anyone at all would be interested, but you'll never know if you
don't ask.

It looks like a few people will be able to help out somewhat with
implementation. The way I've been talking about helping out, you might
have gotten the impression that I was waiting for people to break down
the doors and start implementing most pieces for me. That was never
the case. I just wanted to cast a wide net.

It also looks like everyone's discussing their favorite feature, which
is quite alright. It's exactly what I asked for. This only turns into
a problem when paired with the schedule I'm trying to keep, where we
won't get to most of the stuff being mentioned until at least one
milestone away. Thus, I'd like to start collecting "things you'd like
to have" separately and stockpile them for later on, and collecting
"here's how what should be built tomorrow or is already here should
work" and applying them more directly.

As far as features go, I'm open to suggestions. I'd still like to keep
the browser light, but making a capable browser feel light isn't
unprecedented. And I'd still like to reserve my status as effective
BDFL of Rouse to steer the general direction. I'm perfectly willing to
share this process and the fruits of it with everyone else, but I
won't ever not be doing this for me. I don't believe that there's
anything wrong with that per se either.

I'm working on an embryonic shell that will share as much as possible
with the proper Rouse. This should make it easier to think about the
architecture and start implementation.

Thanks again,
/Jesper


--
Subscription settings: http://groups.google.com/group/rouse-dev/subscribe?hl=en