Re: [binarycloud-dev] Awwww man, facility, not policy!!!

[alex b. <en...@tu...>]

I think I should make this clear, so everyone know how this is going to
happen:

The releases I am doing right now of r2 are, while functional, almost
experimental. I'm playing. Nothing major will change, in the sense that I
don't intend to rename the project "CowPharm" and change the directory
structure :) - but at the same time all these early CVS snaps are just that:
pictures of a moving target.

These releases are not meant to be even remotely final, i.e. they are not
rigid statements about "how it will be" - they are "how it is now, but it
could change!"

So, this is not about policy, I don't ship policy. All of this stuff is
moving, and when we're done it will accomodate almost any changes, strange
configs, etc that everyone needs.

For the moment I'm concerned with getting a working system, even if it lacks
a few things - so we can take that and add flexibility and power.

I am being _extremely_ careful not to design in any restrictions - not to
say that there aren't assumptions in the current cvs snapshots (as Justin's
previous mail points out) - but to say that there _will_not_ be high level
assumptions unless there _absolutely_must_be_ to have a functioning system.

i.e. we all have to agree that modules are loaded by Page - but not
necessarily how to always name files, or how to run your make + development
process.

In the end all of this back and forth, and _early_ exposure to the community
(i.e. all of you) will help me judge how to proceed. It's extremely helpful,
and I thank you all for it. (Keep on crackin' the whip, justin :)

_alex