The CAPI Manifesto

[Jonathan M Davis]

Overall, I think that it sounds like a good idea, but I'd suggest that we 
namespace stuff. So, instead of

import foo;

you'd get something like

import capi.foo;

Otherwise, we unnecessarily increase the odds of module names conflicting with 
modules in other projects.

Also, if we're putting it up on github, we may want to come up with a cooler 
name than CAPI (though it _is_ right to the point). There's already a user 
with the name CAPI ( https://github.com/capi ), so aside from whether CAPI is 
a good name in its own right or not, that might cause problems. Maybe pick 
something suitably Greek or Roman, given that we already have Phobos? The name 
of one of the Titans would be fitting given that it relates to C (on the theory 
that the Greek gods are the successors of the Titans and D's standard library 
is named after a Greek god).

It also brings up the question of who is going to manage this project. Someone 
(or preferrably, a group of someones) is going to have to have commit access 
in order to merge in pull requests. Do want to just start off with that being 
the same group of folks with Phobos commit access and grow it from there as 
appropriate? We certainly wouldn't want to insist that the two groups be the 
same, but it does seem like a good place to start from.

- Jonathan M Davis