os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Grammar and spelling nits, and add a bit of verbosity to the PLZ HELP US section.

Browse source
This commit is contained in:
Adam Weinberger 2003-12-28 02:08:35 +00:00
parent 8437839e45
commit d70223cc12
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=19311
1 changed files with 14 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
en/gnome/docs/develfaq.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.1 2003/12/27 23:03:10 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/develfaq.sgml,v 1.2 2003/12/27 23:19:31 adamw Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME Development Branch FAQ">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -101,12 +101,12 @@ STRIP=
<p>The long answer is that keeping up-to-date with the GNOME
development branch is complicated. Sometimes components change
in a way that makes portupgrade fail, or causes strange end results.
in a way that makes <tt>portupgrade</tt> fail, or causes strange end results.
If you plan to track the development branch, it is a good idea
to join the
<a href="http://lists.freebsd.org/mailman/listinfo/freebsd-gnome">
freebsd-gnome</a> mailing list, as well as join the
<em>#freebsd-gnome</em> IRC channel on FreeNode.</p>
freebsd-gnome</a> mailing list, as well as to join the
<em>#freebsd-gnome</em> IRC channel on FreeNode (<tt>irc.freenode.net</tt>).</p>
<p>If all of this sounds scary, or you need a desktop that
"Just Works," you should stick with the stable GNOME branch.</p>
@ -118,10 +118,10 @@ STRIP=
<!-- A5 -->
<p>It depends. If you think the problem is truly a bug with the
GNOME component, you can report a bug using <b>bug-buddy</b> or
through the GNOME <a href="http://bugzilla.gnome.org">BugZilla</a>
the GNOME <a href="http://bugzilla.gnome.org">BugZilla</a>
interface (<b>NOTE:</b> Evolution's BugZilla interface can be
found <a href="http://bugzilla.ximian.com">here</a>). If you think
the problem lies in the FreeBSD port, or is FreeBSD-specific, send
the problem lies in a FreeBSD port, or is FreeBSD-specific, send
email to <a href="mailto:&email;@FreeBSD.org">&email;@FreeBSD.org</a>,
or report the problem on the <em>#freebsd-gnome</em> IRC
channel on FreeNode.</p>
@ -135,10 +135,10 @@ STRIP=
<li style="padding-bottom: 0.5em"><a name="q6"></a>
<p><b>How can I help with the development versions?</b></p>
<!-- A6 -->
<p>Currently, we need people to test as much as possible, and file as
<p>Currently, we need people to test as much as possible, and to file as
many good bugs as possible. We also need people with artistic
skills to create some hot <a href="/gnome/screenshots.html">
screeshots</a>.</p>
screenshots</a>.</p>
<p>If you like coding, and you know Perl, we <em>really</em> need
someone to help in porting
@ -146,6 +146,12 @@ STRIP=
gnome-system-tools</a>. Please contact
<a href="marcus@FreeBSD.org">marcus@FreeBSD.org</a> if you are
interested in helping with this.</p>
<p>Even if you don't like working directly with code, we need reports on experiences
upgrading from GNOME &gnomever; to GNOME &gnomedevelver;; we need information on
which apps are exhibiting strange behaviour; we need to know in advance everything
that an end-user is likely to wind up scratching his or her head about in the future.
</p>
</li>
<!-- Q7 -->