savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-hackers] Re: commonc++ integrated to http://savannah.gnu.org/p


From: David Sugar
Subject: [Savannah-hackers] Re: commonc++ integrated to http://savannah.gnu.org/projects/commonc++/
Date: Sun, 25 Feb 2001 09:45:13 -0500
User-agent: Mozilla/5.0 (X11; U; Linux 2.2.16-9mdk i686; en-US; m18) Gecko/20001013

I have a strange situation I would like to discuss that involves Common C++. In the case of Common C++, I have also written some additional class libraries based on it that are not officially designated as part of the GNU project (but of course are also free software under the GPL). However, these additional class libraries are actually used in at least one current and one future GNU package as well as in several things that fall into the GNUCOMM meta project.

What I would like to do is consolidate these extra libraries in one place along with Common C++ itself as a convenience to users. I would like to do seperate module checkins to cvs and perhaps distribute these as seperate sub-packages in savannah under the Common C++ work area. Please let me know what you think about this and if this would be appropriate to do. I have also considered consolidating at least some of these extra packages into Common C++ itself and that might happen as well in some future release, at which point there would be no question of their status as part of GNU.

David

address@hidden wrote:

  Hi,

  commonc++ was integrated in the SourceForge.net clone dedicated to GNU
projects that can be found at http://savannah.gnu.org/. The URL of
the commonc++ project on Savannah is http://savannah.gnu.org/projects/commonc++/
It provides you with the following facilities:

  . Web interface to handle contributors CVS write access. You don't
    need to ask someone, it is automated. Only the commonc++ project
    administrators on Savannah can give CVS write access to new
    contributor or deny access to an existing one. This is basically a
    one click operation.  If you want to become a project
    administrator ask an existing administrator to grant you the right
    or, if there are no project administrator, ask address@hidden
    to become one.

. Editing http://www.gnu.org/software/commonc++/ pages using CVS instead of login onto gnudist.gnu.org. As soon as you commit information in this CVS tree, it will show on http://www.gnu.org/software/commonc++/.

  . The commonc++ CVS tree now has a separate CVS history instead of an
    history merged with all other projects hosted on
    subversions.gnu.org.

  For more information on how to access the CVS trees, click on the
CVS menu at http://savannah.gnu.org/projects/commonc++/.

  No action is required from you, the Savannah setup does not require
that you change your habbits. However, it would be nice of you to do
the following:

  - login at least once on https://savannah.gnu.org/account/login.php
  - read the CVS instructions for the commonc++ project
  - checkout the commonc++ CVS tree according to these instructions

  When all contributors will be using the new CVS tree, we will be
able to remove the backward compatibility installation for commonc++.

  When you login Savannah, the transaction is secure (SSL).  In case
you wonder what all this is about you can check the cvs-hackers and
webmasters mailing lists archive, they contain a lot of discussions
regarding this planned integration.
  If you have a Kerberos account on gnu.org, use the same login and
password on Savannah and change the password immediately afterwards:
it will not change your Kerberos password, just the Savannah
password.
  If you only have a pserver account, use the same login and
password on Savannah.
  If you have both (Kerberos and pserver), use the Kerberos account
login and password. Note that after login for the first time your
pserver password will be set to the same password you use to login on
Savannah. Please change the Savannah password immediately after your
first login: it will not change your Kerberos password, just the
Savannah password.

  If you have none and access CVS using SSH public keys, ask to
address@hidden to give you a password. This last case requires
human interaction to prevent someone from stealing your account name.

  Please report problems or questions to
https://savannah.gnu.org/support/?func=addsupport&group_id=11 or by
email to address@hidden if you don't have (or don't want to
use) a web browser.

  Cheers,




reply via email to

[Prev in Thread] Current Thread [Next in Thread]