Suggested Changes to Manifesto

[Matt McParland <matt engsoc org>]

The following are a few updated paragraphs from the Epiphany manifesto at 
  
  http://www.gnome.org/projects/epiphany/documentation/manifesto.html

I changed some of the wording to be more clear (I hope).  Feel free to 
use this, or not.

--- 

Epiphany achieves simplicity by using modular components to make a light
and powerful application.  If something can be implemented sensibly
using external applications or components, we us that rather than
wasting resources reinventing the wheel and adding bloat to the browser.
Epiphany integrates with CORBA, Bonobo and the ever popular command
line.




The introduction of non-standard features in other browsers could make
it difficult or imposisble to use alternative produts like Epiphany if
developers embrace those features.  Alternative (read: standards
compliant) browsers, like Epiphany, may not be able to fully access web
sites making use of non-standard features and this could lead to
proprietary browsers dominating the market.

Standards compliance ensures the freedom of choice.  Epiphany is
designed with that in mind.





Epiphany follows version 1.0 of the GNOME user interface guidelines 
(HIG).  Unless there are valid reasons to make exceptions, non-compliance 
with the HIG is considered a bug.  "We follow the HIG when it suits us."
is not a valid approach.  Any areas where we diverge from the HIG will
be proposed to the HIG working group for future consideration.




Epiphany's main goal is to be integrated with the GNOME desktop.
Consequently, Epiphany is not designed to be used outside of GNOME.  If
you want to use it outside of GNOME anyways, by all means go right
ahead.  But, for example, making people happy by including MIME
configuration in Epiphany because they don't run GNOME Control Centre is
not something we will do.





We target non-technical users by design as this happens to cover 90% of
the end-user popularion.  We target web users and not web developers
(directly).  We do not believe that "geek-oriented" features should be
forbidden so long as they are not obtrusive.  Technical details should
not be exposed in the interface.


-- 
Matt McParland