Regarding Avalon: 

I don't have anything against calling it "avalon2" if the majority wants
that. 

Regardless of how we call it, we should make it clear on the web site that
this is partly based on ideas from Avalon.

The only think that I don't want is to have the code base from the current
avalon having any "special" status, by association with the name - if we
are to share, all components should be treated in the same way, regardless
of source.

Avalon people are as wellcomed to join and help as people from any other
project - so that shouldn't be an issue.

The name of a project can be decided only by the project commiters, so
only the final vote can tell us if it'll be "commons", "agora",
"avalon", "rupert" or "library".

Costin

Reply via email to