Online help,
should be:
* correct
* accurate
* up-to-date
* useful
* usable
* w/o references to netscape6.
Someone else can define each of the terms used above, but I reserve the right to
complain about each definition. 'w/o' is defined to mean without and a simple
explanation of that line follows:
There should not be any references to Netscape Instant Messenger, nor 'Netscape6' nor
'Netscape 6' nor any other product that is included in netscape6 which is not in
mozilla1.0. any product which has a different name between netscape6 and mozilla
should be referenced by the mozilla name. -- this is of course all obvious but ...
Online help should probably behave just like browser (the 092 branch build i have
doesn't have icons for back, forward, home among other things).
Imo the toolbar should also have contents, index, find, zoom and optional labels.
Plugins.
We should support the top 10 plugins by platform. We should correctly locate plugins
according to platform rules and netscape4 fallback rules according to decisions of the
plugins team.
this means that if netscape4 plugins are deemed incompatible or impossible to find
then it's ok for them to not be searched for. this also means that we should find
system plugins on macos classic and X.
Is having a plugin manager of some sorts a 1.0 req? perhaps just the ability to
disable plugins.
Evangelism.
the following is my off the cuff opinion and should have no weight in the discussion:
Ideally top100 sites should not have open severity:critical evang bugs.
Versioning - Ports.
If a platform team would like to hold off declaring 1.0 state they should be able to.
If all ports team leaders declare that they are unwilling to brand 1.0 then we should
not declare mozilla1.0. -- There are probably 5 major ports, I think if 2 say they're
ready that's probably good enough, perhaps even one ... but of course some of the
major porters tend to delay releases so this is an interesting requirement.
License - About.
I should fix the about:license and about:credits pages to correctly mention relevant
things (sorry notes to self probably don't belong in posts). We should give people a
reminder about getting themselves added to the about:contributors page for 1.0 w/ a
clear deadline and explanation of how to get added.
License - Art.
Ack. We can't release mozilla1.0 until the Art stuff is cleared. This means that if
lawyers representing mozilla.org say we aren't clear we don't ship.
Request: please don't gripe about specific art in this thread, i'm more interested in
the License perspective because Legal things do matter. I'm sure there are other
threads available for gripes about specific art.
Bugzilla - Closing bugs.
news://news.mozilla.org/3B421BED.ED76A435%40wam.umd.edu
Bugzilla has the ability to recognize bugs as closed, but mozilla.org doesn't use this
ability yet, as we approach 1.0 we are approaching 90000 (and 100000) bugs so perhaps
it's time to consider using close especially since 1.0 is a release by the normal
definition.
Printing.
Heh, should users be able to print from mozilla? Is this an open question?
[Headers, Footers, Margins, Orientation, Collation, ...]
What about print preview? It wasn't a stop ship for ns6.0, but i think it might be for
mozilla1.0
What about CUPS?
Proxies.
ns6 shipped w/o PAC support, this prevented large corps from rolling it out, mozilla
currently has proxy support but we should probably improve the support a bit before 1.0
Mail Window.
nc4messenger had 3 columns in the folder view which allowed people to see how many
messages were in _all_ visible folders. Mousing over a folder gave aggregate totals.
afaik Mozilla only gives per folder numbers on mouse over.
News.
Searching newsgroups, online and offline.
Composer.
We don't support frames, we aren't really css happy, it'd be nice if we at least were
css friendly enough to support these features from tidy:
options for tidy released on 30th April 2000
-clean or -c replace font, nobr & center tags by CSS
-numeric or -n output numeric rather than named entities
-asxml to convert html to wellformed xml
Publish support?
Offline.
Should we try to have archiving working (Web Archive: multipart/mime-encoded;
Complete: wget style)?
Ratings.
Afaik we have very little ui for this probably useless feature, yet people contributed
a p3p engine. We should probably add at least something (I know we do recognize
ratings, but i've never met a ui for it)
Toolbars.
Should we have fully customizable toolbars before 1.0?
SpellChecker.
We should have one. Amaya has one. Amaya seems to be BSD license so maybe we can
actually get one by 1.0 ...
