Drupal, PeopleAggregator and the People's DNS

[Marc C. <ma...@br...>]

As our technology spreads around the world - it's important to keep in
mind marketing these technologies. 
 
Not just getting people to use them, but also explaining what the
technologies do, how they're used and (most importantly) the benefits
they'll have to everyday humans.
 
That's why we name our technologies as close as possible to what they
do: MediaBand, ServerInTheCloset, PeopleAggregator and People's DNS.
 
That's also why it's important that we maintain separate 'identities'
between these technologies - as developers out there may choose to mix
and match them with the code they already have.  
 
Not everyone needs a coolio CMS, framework, plumbing platform - so we
need to be able to slice out the PeepAgg code from the Drupal code and
let folks use it with their code.  Same goes for the pDNS. At the
install stage - we'll (eventually) let folks decide which pieces they
want..
 
But first things first - let's get it all to work together!
 
So just to be clear - these three projects are separate projects, they
just happen to be given birth within the context of Drupal - and god
dammit Drupal it is!
 
-          Marc
 
P.S. Joel and I have had 'some' discussion as to the difference between
People's DNS and the PeopleAggregator.  That hasn't been entirely
resolved, but let's leave it at this "one could CERTAINLY imagine other
FOAF interfaces using the pDNS - while they prefer to NOT use the
PeepAgg."
 
P.P.S. [BTW since I used the ID word above - that DOES bring up the
notion of FOAF for code, certainly FOAF for groups and maybe even one
day - FOAF for all things (i.e. items, products, services, etc.)  Marc
Smith is doing interesting work like that at Microsoft.  We DO have FOAF
for groups coming....]