From 3b97e76aa528e3c957df4b1110ed2b2454025fb6 Mon Sep 17 00:00:00 2001 From: Chris Allegretta Date: Sun, 16 Mar 2008 18:25:31 +0000 Subject: [PATCH] faq.html: Updates for Alpine, subversion access and Savannah. git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@4232 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- doc/faq.html | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/doc/faq.html b/doc/faq.html index c6762c18..d0b5faa6 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -19,7 +19,7 @@

2.1. FTP and WWW sites that carry nano.
2.2. RedHat and derivatives (.rpm) packages.
2.3. Debian (.deb) packages.
- 2.4. By CVS (for the brave).

3. Installation and Configuration

3.1. How do I install the RPM or DEB package?
3.2. Compiling from source: WHAT THE HECK DO I DO NOW?
@@ -58,9 +58,9 @@
7. Miscellaneous

7.1. nano-related mailing lists.
7.2. I want to send the development team a big load of cash (or just a thank you).
- 7.3. How do I submit a patch?
+ 7.3. How do I submit a bug report or patch?
7.4. How do I join the development team?
- 7.5. Can I have CVS write access?
+ 7.5. Can I have write access to the subversion tree?

8. ChangeLog

1. General

@@ -112,8 +112,8 @@

You can also have a look at the Package Pool to see all the available binary and source packages.

Note that versions < 0.9.10 are probably not for those wanting to get serious work done, so if you are using Debian 2.2, check that you have updated to 2.2r3, which comes with nano 0.9.23. If you're tracking unstable, you probably have the newest version already.

2.4. By CVS (for the brave).

For the 'bleeding edge' current version of nano, you can use CVS to download the current source code. Note: believe it or not, by downloading code that has not yet stabilized into an official release, there could quite possibly be bugs, in fact the code may not even compile! Anyway, see the nano CVS page for info on anonymous CVS access to the nano source.

2.4. By subversion (for the brave).

For the 'bleeding edge' current version of nano, you can use subversion to download the current source code. Note: believe it or not, by downloading code that has not yet stabilized into an official release, there could quite possibly be bugs, in fact the code may not even compile! Anyway, see the nano SVN document for info on anonymous SVN access to the nano source.

3. Installation and Configuration

3.1. How do install the RPM or DEB package?

@@ -236,7 +236,8 @@

6.3. What is so bad about the older Pine license?

The U of W license for older versions of Pine and Pico is not considered truly Free Software according to both the Free Software Foundation and the Debian Free Software Guidelines. The main problem regards the limitations on distributing derived works: according to UW, you can distribute their software, and you can modify it, but you can not do both, i.e. distribute modified binaries.

6.4. Okay, well, what mail program should I use then?

If you are looking to use a Free Software program similar to Pine, and Emacs is not your thing, you should definitely take a look at mutt. It is a full-screen, console based mail program that actually has a lot more flexibility than Pine, but has a keymap included in the distribution that allows you to use the same keystrokes as Pine would to send and receive mail. It's also under the GNU General Public License, version 2.0.

If you are looking to use a Free Software program similar to Pine, and Emacs is not your thing, you should definitely take a look at mutt. It is a full-screen, console based mail program that actually has a lot more flexibility than Pine, but has a keymap included in the distribution that allows you to use the same keystrokes as Pine would to send and receive mail. It's also under the GNU General Public License, version 2.0.
+Of course, due to the license change you can now use the Alpine distribution of PINE as it is now considered Free Software, but you would be sacrificing many of nano's features to do so.

7. Miscellaneous

7.1. nano-related mailing lists.

@@ -246,14 +247,17 @@ nano-devel - http://mail.gnu.org/mailman/listinfo/nano-devel/

7.2. I want to send the development team a big load of cash (or just a thank you).

That's fine. Send it our way! Better yet, fix a bug in the program or implement a cool feature and send us that instead (though cash is fine too).

7.3. How do I submit a patch?

See Section 7.2.

7.3. How do I submit a bug report or patch?

+
The best place to submit bugs is to the Savannah bug tracker as you can check whether the bug you are submitting has already been submitted. +
Please submit patches for nano via the Savannah project's patch manager for the nano project.

7.4. How do I join the development team?

The easiest way is to consistently send in good patches that add some needed functionality, fix a bug or two and/or make the program more optimized/efficient. Then ask nicely and you will probably be added to the Savannah development list and be given CVS write access after awhile. There is a lot of responsibility that goes along with being a team member, so don't think it's just something to add to your resume.

7.5. Can I have CVS write access?

The easiest way is to consistently send in good patches that add some needed functionality, fix a bug or two and/or make the program more optimized/efficient. Then ask nicely and you will probably be added to the Savannah development list and be given SVN write access after awhile. There is a lot of responsibility that goes along with being a team member, so don't think it's just something to add to your resume.

7.5. Can I have write access to the subversion tree?

Re-read Section 7.4 and you should know the answer.

8. ChangeLog

2007/12/21 - Update maintainer information. (DLR)
+2008/03/16 - Update docs to refer to subversion instead of CVS, add more words about Apline, and refer to Savannah for bugs and patches. (chrisa) 2007/12/09 - Add minor punctuation and wording fixes, and update various sections to account for Alpine. (DLR)
2007/08/26 - Update links to the Free Translation Project. (DLR)
2007/07/29 - Update RPM links for nano 2.0.x. (DLR)
-- 2.39.5