Delcaration of Intent

I don't have a significant objection to what you say as an intent, but I
wonder if one cannot compromise on the intent of the project, per se,
without including such broad justification for the project.  Is not the
project simply to provide certain "tools" that permit anonymous
communication within a system that inherently was designed to try to
provide complete transparency to knowing both the origin and destination. 
That alone certainly has inherent merits without the need for justification
of philosophical or political reasons.  I.e., use a vehicle that exists to
provide a function that might well not be able to financially support an
independent system of communication itself.


> [Original Message]
> From: <auto97841-revL73yDgGBWk0Htik3J/[email protected]>
> To: <[email protected]>
> Date: 8/10/2003 11:05:40 AM
> Subject: [iip-dev] Delcaration of Intent
>
> 'lo y'all
>
> I understand what you are both saying, but I think there's still a
misunderstanding.
>  The point of including a declaration of intent in a project overview
> document is not to promote or explain what the personal motivations of
> any particular developers building the system are.  It is to give
grounding
> for where the project is headed - to declare that the project will not
> stop short of providing anonymous, secure, and uncensorable communication
> to those who are under attack by the governments and corporations of
> the world.  That individuals are under attack from those organizations
> is an undisputed fact (though some may say thats ok, because the
individuals
> under attack are "bad" people).  Even if one is in denial that such
terrible
> things are going on in one's own community, don't we all acknowledge
> that they go on elsewhere - in Iran, China, the Philipines, or what have
> you?
>
> Anyway, in order to not hold up the 0.1 release debating this, I've
revised
> the doc pulling the first page out and updating the project overview
> accordingly.  We will need to have a declaration of intent - or project
> goals if you prefer - before the I2P 1.0alpha release in september. 
> Bundling a dozen "why *I* work on I2P" documents with releases isn't
> appropriate - no one cares why I develop for I2P as long as my efforst
> move it towards the project's goals.
>
> So, here's the hopefully final doc.  Please review fully (I know, getting
> a 3 page reading assignment on the weekend sucks ;), as I'd like to have
> the release out tomorrow.
>
> Gracias
> -jrandom