r1097 - website
Carlo Segre
segre-guest@costa.debian.org
Thu, 02 Jun 2005 04:20:49 +0000
Author: segre-guest
Date: 2005-06-02 04:20:49 +0000 (Thu, 02 Jun 2005)
New Revision: 1097
Removed:
website/policy.txt
Modified:
website/policy.pod
website/subversion.pod
Log:
Removed policy.txt and fixes some spelling errors in the *.pod files
Modified: website/policy.pod
===================================================================
--- website/policy.pod 2005-06-01 20:34:28 UTC (rev 1096)
+++ website/policy.pod 2005-06-02 04:20:49 UTC (rev 1097)
@@ -36,14 +36,14 @@
All members of our group should be subscribed to debian-perl@lists.debian.org
and read this list (at least skim all messages for Debian Perl Group related
-stuff). Additionally, every members should be subscribed to
+stuff). Additionally, every member should be subscribed to
pkg-perl-maintainers@lists.alioth.debian.org to receive bug reports and
-similar.
+similar information.
All members are encouraged to have all our packages installed. They are also
encouraged to check our webspace (L<http://alioth.debian.org/projects/pkg-perl>),
our svn repository (L<http://svn.debian.org/wsvn/pkg-perl/>) and the tracker on
-alioth (L<http://alioth.debian.org/tracker/?group_id=30274>) regulary. You can
+alioth (L<http://alioth.debian.org/tracker/?group_id=30274>) regularly. You can
watch the work on our svn repository subscribing to our svn commits
list (L<http://alioth.debian.org/mail/?group_id=30274>), listed there as
pkg-perl-cvs-commits.
@@ -107,7 +107,7 @@
Perl is distributed under your choice of the GNU General Public
License or the Artistic License. On Debian GNU/Linux systems, the
complete text of the GNU General Public License can be found in
-`/usr/share/common-licenses/GPL' and the Artistic Licence in
+`/usr/share/common-licenses/GPL' and the Artistic License in
`/usr/share/common-licenses/Artistic'.
Deleted: website/policy.txt
===================================================================
--- website/policy.txt 2005-06-01 20:34:28 UTC (rev 1096)
+++ website/policy.txt 2005-06-02 04:20:49 UTC (rev 1097)
@@ -1,92 +0,0 @@
-Debian Perl Group
-~~~~~~~~~~~~~~~~~
-
-Project Internal Policy
-
-Here we document how we do stuff internally. This file is of course
-work in progress and will probably always be.
-
-0) Content
-
- 1) Mandatory mailing lists and such
- 2) debian/changelog Handling and CVS tagging
- 3) debian/control Handling
- 4) Release Process
-
-
-1) Mandatory mailing lists and such
-
-All members of our group should be subscribed to
-debian-perl@lists.debian.org and read this list (at least skim all
-messages for Debian Perl Group related stuff).
-Additionally, every members should be subscribed to
-pkg-perl-maintainers@lists.alioth.debian.org to receive bug reports
-and similar. (Is there anything the PTS would send that the Maintainer
-e-mail-address wouls not recieve?)
-
-All members are encouraged to have all our packages installed. They
-are also encouraged to check our webspace and the tracker on alioth
-regulary. (Hint: see http://svn.debian.org/wsvn/pkg-perl/) And there is
-pkg-perl-cvs-commits@lists.alioth.debian.org where anybody can watch
-us work.
-
-2) Changelog Handling and CVS tagging
-
-We use the debian revision to count our releases to the debian
-archive, not internal steps. So if and only if you do the first change
-after a release, you add another debian/changelog entry (dch -i).
-Since your name and e-mail will then be in there, you have to check
-that you are listed in Uploaders: in debian/control (otherwise katie
-or whoever will think that you are doing a NMU).
-
-If someone else changed something that has to be noted in
-debian/changelog, he just adds a line to the current entrry (dch -a).
-He should not put his name there - the user does not care and we can
-always check the CVS log.
-
-!!! OUTDATED: we are currently switching to SVN, this has to be rewritten
-After each changes (and to make sure, before you build the package),
-you should run something like
-# cvs tag -F debian_version_1_12-3
-in the top directory of your working copy. The -F is to move the tag
-if it has be set already. 1_12 is the upstream version (replace points
-and stuff with _), and 3 the debian version (if for some reason this is
-a NMU, then name this 3_1). This is the naming scheme from
-cvs-buildpackage. The version as to correspond exactly with the one
-in the current entry in debian/changes.
-
-Hint: use
-# cvs status -v debian/changelog
-to see the already-set tags, in case you are unsure about the naming
-scheme or wheter your taggin actually worked.
-!!! /OUTDATED
-
-3) debian/control Handling
-
-Before importing a package into the SVN repository for the first time
-you should change the Maintainer field to
-pkg-perl-maintainers@lists.alioth.debian.org. You should put your own
-email address and name in the Uploaders field. If there are others
-that you know of who will be modifying the package in the future, you
-should add their name and email address to the Uploaders field as
-well.
-
-When modifying a package in the repository, you should add your name
-to the Uploaders file. You should keep the names of other maintainers
-who added their name before you. In other words, the Uploaders field
-must be updated to contain everyone that worked on the package. The
-Maintainer field must remain unchanged after the first import.
-
-4) Release Process
-
-If you are a full DD, upload but be prepared to receive (at least
-parts of) the blame. If you are not, some DD in the Group will surely
-sponser the package. He will check the package first, too, but make
-sure he has no reason to complain. Feel free to use the "Packages to
-Upload" tracker for finding a sponsor.
-
-Always feel free to ask other to check a package if in doubt.
-
-
-$Id$ vim:tw=70
-
Modified: website/subversion.pod
===================================================================
--- website/subversion.pod 2005-06-01 20:34:28 UTC (rev 1096)
+++ website/subversion.pod 2005-06-02 04:20:49 UTC (rev 1097)
@@ -198,16 +198,16 @@
package with the .orig.tar.gz that svn-buildpackage creates from the svn
repository. To avoid this, put the .orig.tar.gz file from the debian
archive in you build directory (manually or just using apt-get source).
-If you upload the the first and subsequential packages of an upstream
+If you upload the the first and subsequent packages of an upstream
version, you don't have to worry about this.
-If you are satisfied with the package, and want to build the final packge
+If you are satisfied with the package, and want to build the final package
(the one that is going to be uploaded to the archive), use
svn-buildpackage --svn-tag [-rfakeroot] [-kyourkey] [-uc] [-us]
to make svn-buildpackage create a tag of this release. You should
-harldy ever need to tag a release by yourself.
+hardly ever need to tag a release by yourself.
=head2 4.2 Building an already tagged release
@@ -218,7 +218,7 @@
libcgi-safe-perl_0.04-1
Now, if we want a full build, we need the sources. Therefore, we have
-to sortof hack around some limitations of svn-buildpackage. We need to
+to sort of hack around some limitations of svn-buildpackage. We need to
add a line to libcgi-safe-perl_0.04-1/.svn/deb-layout:
upsCurrentUrl=svn://svn.debian.org/pkg-perl/packages/libnet-imap-simple-perl/branches/upstream/0.93
@@ -232,7 +232,7 @@
We will need to be able to fetch the source to any debian release that
is out there. This is why we have to tag our repository after every
package release. Like we said before, tagging is not exactly the same
-as in CVS. In CVS, the versionnumber for every tagged file is aliased
+as in CVS. In CVS, the version number for every tagged file is aliased
with that tag. That way, version 1.1.1 is aliased debian_version_0.1-1
and version 1.1.2 is aliased debian_version_0.1-2, for example. In
SVN, this works differently.
@@ -241,7 +241,7 @@
tags. This way, file revisions aren't aliased, we simply copy the tree
in its current form to a different location just like you would in a
regular filesystem. SVN does this cleverly, so you can keep track of
-logentries and the copied tree doesn't take up any extra space on
+log entries and the copied tree doesn't take up any extra space on
disk.
Note that using our usual workflow, the tags will be created by
@@ -249,8 +249,8 @@
svn-buildpackage --svn-tag
when building the final version of the package that is going to be uploaded
-to the archie. Only execption might be the initial upload of a package
-with a version alread in the archive (though it might be arguable if we
+to the archive. Only exception might be the initial upload of a package
+with a version already in the archive (though it might be arguable if we
actually need this version as a tag).
Anyways, it works like this:
@@ -303,7 +303,7 @@
automatically after an hour or so.
If you're really 1337, you can use the web interface on Alioth to
-copy your ssh public key permanently. Use the follwing URI to do that:
+copy your ssh public key permanently. Use the following URI to do that:
https://alioth.debian.org/account/editsshkeys.php
You can also consider the use of an ssh-agent (see ssh-agent(1),
@@ -331,6 +331,7 @@
=over
=item * Allard Hoeve
+
=item * Joachim Breitner
=back
@@ -344,7 +345,7 @@
Perl is distributed under your choice of the GNU General Public
License or the Artistic License. On Debian GNU/Linux systems, the
complete text of the GNU General Public License can be found in
-`/usr/share/common-licenses/GPL' and the Artistic Licence in
+`/usr/share/common-licenses/GPL' and the Artistic License in
`/usr/share/common-licenses/Artistic'.
=for comment