The InriaGforge FAQ
InriaGforge has been setup to enable people to work on projects related to Inria.
Anyone can take part, but only people working for Inria can start a project. You
can read more about the general terms of service
Who can delete a project ?
Deleting a project is a privileged operation that can only be performed by InriaGforge's admins. Please sent any request to help.et.gforge<AT>inria.fr.
To do so :
- Go to "My Page" tab
- Check the "My Projects" paragraph at the bottom right of the page
- Select the project you want to be removed from and click on the trash bin image appearing next to the project name.
The trash bin image must not be slashed, otherwise it means you are an admin of the project and you are not allowed to remove yourself from the project this way.
- You get a page that will ask you to confirm your deletion.
If you are tired of your browser asking you if you trust InriaGforge because it could not verify its certificate, you should download the identity of the certificate authority that is available on Irisa's site.
InriaGforge's interface is maintained in French and in English.
Depending on your browser settings and on your personnal preferences
when you are logged in you will see the web interface in French or in English.
To be more precise :
- When not logged in, the language used will be the first of French
or English seen in your browser settings.
- When logged in, the language used will be the one you last set in your preferences.
Nervertheless, some elements are not bilingual: this FAQ for instance, is only
available in English; the news items on the front page are only available in the
language the project submitting the news has written them.
Each project also defines a natural language. This is an indication of the
language that should be used when submitting bugs or writting to the mailing
lists of the project. It has no known influence on the language of the interface,
even when browsing the project's pages.
Finally, the websites each project can setup on <project_name>.gforge.inria.fr
define their own behaviour. The gforge team or software has no influence on them.
Your code repository is located on the InriaGforge server on host scm.gforge.inria.fr, directory :
- for CVS repository : /cvsroot/<project_name>
- for SVN repository : /svnroot/<project_name>
It can not be accessed directly on the InriaGforge server via ssh. Nevertheless, the data can be retrieved using the commands sftp, rsync or scp.
For example, to list the svn code repository on InriaGforge server :
$ sftp <yourlogin>@scm.gforge.inria.fr:/svnroot/<project_name>
sftp> ls
sftp> exit
To know who can access the code repository, go to next FAQ entry.
With the default settings, project members with Doc
Writer or Support Tech roles cannot commit changes into the
SCM.
Source code repository access depends on the settings of the
project and on the privileges of the user trying to access
the code repository. The following table sums the situation.
| |
|
Read access to source
code |
Write access to source
code |
| |
|
cvsweb
pserver |
ssh |
webdav |
ssh |
webdav |
| Public project/anonymous acces enabled |
Anonymous user |
|
|
|
|
|
| Logged user |
|
|
|
|
|
| Project member, no SCM access |
|
|
|
|
|
| Project member, read access to SCM |
|
|
|
|
|
| Project member, read/write access to SCM |
|
|
|
|
|
| Public project/ anonymous access disabled |
Anonymous user |
|
|
|
|
|
| Project member, no SCM access |
|
|
|
|
|
| Project member, read access to SCM |
|
|
|
|
|
| Project member, read/write access to SCM |
|
|
|
|
|
| Private project |
Anonymous user |
|
|
|
|
|
| Project member, no SCM access |
|
|
|
|
|
| Project member, read access to SCM |
|
|
|
|
|
| Project member, read/write access to SCM |
|
|
|
|
|
Changing user privileges is done through the edition of user roles in a project's admin tab, whereas projects SCM setting can be edited either using the admin link at the top of the project's SCM page of by editing the observer role.
Even though CVS is very stable and widely used, it has some known drawbacks:
It doesn't keep track of renaming files and directories or doesn't store information
about a commit as a whole, and handling branches is a pain.
Subversion was written by the maintainers of CVS and is a stable alternative to CVS.
Subversion is based on the idea that you don't create branches or tags but just create
a copy of your sources as one would do with no other tools at hand than just the 'cp' copy command.
To avoid the overhead of copy operations an efficient storing system (Berkley DB or FSFS)
is used to hold all the data.
Ok, but how to change from cvs to subversion when migrating to InriaGforge ?
You can import your whole existing CVS repository, or just one module,
into your newly created Subversion repository on the GForge. First, you have
to create a local Subversion repository from your local CVS repository
(SVN_REP is the path of your temporary local subversion repository,
automatically created by the cvs2svn tool):
cvs2svn --fs-type fsfs -s SVN_REP /path/to/my/local/cvs/repository
or from only one module of your local CVS repository:
cvs2svn --fs-type fsfs -s SVN_REP /path/to/my/local/cvs/repository/this_module
This will create the SVN_REP directory and fill it with the history
of your CVS repository/module history. When this is done, follow the
instructions of How do I import my Subversion history ?.
You can find the cvs2svn tool and its documentation
here. Packages exist for various Linux distributions
(Debian, RedHat, Fedora, Mandrake, ...).
Importing CVS history is a simple task : supposing you have a copy of the
module you want to import (ie you have a version of $CVSROOT/ModuleToMigrate)
in the current working dir of your machine.
Then these commands
find ModuleToMigrate -type d -not -perm -2005 -exec chmod o=rx '{}' \;
find ModuleToMigrate -type f -not -perm -0004 -exec chmod o=r '{}' \;
scp -rp ModuleToMigrate <yourlogin>@scm.gforge.inria.fr:/cvsroot/<project_name>/
will fix file permissions to be able to browse it through the cvs web interface located on http://gforge.inria.fr/plugins/scmcvs/cvsweb.php/?cvsroot=cvsroot/<project_name> and will install your project in the CVS repository of your project.
Beware: pre and post commits
scripts might no longer work after the importation. You should check this is you have set any up in your previous repository.
Please note that the following does not work when you use subversion 1.0.9 (packaged with Fedora Core 2 for example).
You'll need to upgrade the version of subversion you are using.
Please note that since 4th December 2008, InriaGforge recognize svn repositories which complies to format 5 (information stored in /svnroot/<project>/format).
Please note when creating a repository with svnadmin, check the version using svnadmin --version.
If the version is higher than 1.4 you have to use the following option in addition :
- --pre-1.4-compatible: use this option if you're running at least version 1.4 and want to produce a format 3 repository usable by versions older than 1.4.
If you're confused about your svn version and what it produces, you may refer at this
page.
Please note that Subversion repositories
on the GForge use the FSFS format. If your svn Subversion repository is in BDB format, then you have to convert
it to the FSFS format using the commands given below.
The format of your Subversion repository can be checked by looking at the contents
of the SVN_REP/db/fs-type file. To convert your Subversion repository
from BDB format to FSFS, use the following commands
(SVN_BDB is your local Subversion tree in BDB format, SVN_FSFS
is the directory that will contain your tree in FSFS format after the
execution of the commands):
svnadmin create --fs-type fsfs SVN_FSFS
svnadmin dump -q SVN_BDB | svnadmin load SVN_FSFS
Now here is how to import your Subversion repository tree in FSFS format.
Let SVN_REP be your local Subversion repository tree,
and <project_name> the unix name of your project on gforge.
Make sure you did upload your ssh key in order to be able to connect to
scm.gforge.inria.fr. Then,
chmod -R g+w SVN_REP/*
scp -rp SVN_REP/* <yourlogin>@scm.gforge.inria.fr:/svnroot/<project_name>
This copies your subversion tree in place of the one on gforge.
Don't forget the /* after SVN_REP, or else
a directory will be created in /svnroot/<project_name> and you definitely don't
want this.
First, let's imagine we have three repositories that we want maintained under <project_name>.
Let's call them calc, calendar and spreadsheet (names taken from the subverison book).
The first step is to create a dump of these repositories and the directories under which these projects will be imported in your repository.
> svnadmin dump -q /path/to/calc/repos > calc-dumpfile
> svnadmin dump -q /path/to/calendar/repos > calendar-dumpfile
> svnadmin dump -q /path/to/spreadsheet/repos > spreadsheet-dumpfile
> svn mkdir -m "Imported project roots" \
svn+ssh://<yourlogin>@scm.gforge.inria.fr/svnroot/<project_name>/calc \
svn+ssh://<yourlogin>@scm.gforge.inria.fr/svnroot/<project_name>/calendar \
svn+ssh://<yourlogin>@scm.gforge.inria.fr/svnroot/<project_name>/spreadsheet
Then, copy the dump file to your home directory on InriaGforge
> scp calc-dumpfile <yourlogin>@scm.gforge.inria.fr:/home/users/<yourlogin>/
> scp calendar-dumpfile <yourlogin>@scm.gforge.inria.fr:/home/users/<yourlogin>/
> scp spreadsheet-dumpfile <yourlogin>@scm.gforge.inria.fr:/home/users/<yourlogin>/
Finally, contact the InriaGForge admins in order to run such commands
$ svnadmin load /svnroot/<project_name> --parent-dir calc < /home/users/<yourlogin>/calc-dumpfile
$ svnadmin load /svnroot/<project_name> --parent-dir calendar < /home/users/<yourlogin>/calendar-dumpfile
$ svnadmin load /svnroot/<project_name> --parent-dir spreadsheet < /home/users/<yourlogin>/spreadsheet-dumpfile
You now have your three repositories under your project's repository on InriaGforge.
These warnings are generated by the procedure that connects commits to your CVS repository to the
-commits mailing list of your project. InriaGforge has generated an old format string for this command.
You therefore need to replace the format string of the loginfo file of your CVSROOT module :
$ cvs -d :ext:<yourlogin>@scm.gforge.inria.fr/cvsroot/<project_name> checkout CVSROOT
$ cd CVSROOT
$ vi loginfo #replace %S by %s in the last line
$ cvs commit -m "updated loginfo call to syncmail"
If you have followed ths configuration steps described in the
ssh for windows page mentionned in
How do I setup ssh (even on windows ?), you can use either
a graphical or a shell-based utility to access your cvs/svn repository.
To use the graphical utility, follow the steps described in our
tortoise page.
To use svn from a shell, you can follow these steps:
This is not doable using the admin pages. To do so, and especially to change from CVS to SVN, you need to contact the InriaGforge administrators by mail to help.et.gforge<AT>inria.fr.
Shapshot generation was disabled because it caused to big a load on the server because of the way
the snapshot was made on projects with to many branches. There is no generic way of making a snapshot
in a way that avoids the problems encoutered. Therefore, projects relying on snapshots should either use
the tarball that is generated (and available on the admin page of each project) or make a snapshot themselves.
A snapshot is nothing more than a tarball of the checkout of the complete repository made available each night.
You can program the same functionnality whith the scripts available here for cvs or svn.
The server is running subversion 1.4.2, some
more recent features of subversion may not be available.
Edit your subversion configuration file : ~/.subversions/servers and add in global section :
http-proxy-host = <your-proxy-server>
http-proxy-port = <your-proxy-server-port>
A hook script is a program triggered by some repository event, such as the creation of a new revision or the modification of an unversioned property.
On each subversion repository hosted on InriaGforge server, you find a directory named hooks, filled with templates for various repository hooks (such as pre-commit.tmpl). This directory hooks is located on /svnroot/myproject_unixname/hooks.
To access the content of this directory, check this FAQ entry.
By default, the post-commit hook is implemented for each subversion repository on InriaGforge in such a way that when the repository is modified after a commit, an email containing the diff is sent to the list myproject-commits.
For more information concerning the subversion hooks, consult Subversion hook related page.
If your subverson repository is corrupted (i.e. messages like "Svn diff too large, svn repository corrupted, ..."), follow this procedure :
- You must lock your repository in order to disable commit during the maintenance operation. For that, add a simple pre-commit hook script in your directory yourlogin@scm.gforge.inria.fr:/svnroot/<unix_project_name>/hooks/ with some lines like :
#!/bin/sh
echo "Repository in maintenance, please retry later"
exit 1
nb: your script name must be pre-commit and executable.
- Retrieve the repository on your local machine with command : scp -r yourlogin@scm.gforge.inria.fr:/svnroot/<unix_project_name> /tmp/
- Check your repository : svnadmin verify /tmp/<unix_project_name>
- If the verify process failed on revision n, try the following command on revision n and n+1: fsfsverify -f /tmp/<unix_project_name>/db/revs/<n and n+1>
And follow the instructions shown when the command ends. You may need to use the command fsfsverify -f several times.
- When the command fsfsverify seems ok, then recheck your repository : svnadmin verify /tmp/<unix_project_name> and/or test a checkout : svn co file:///tmp/<unix_project_name> mytest
- If it is ok then push your repository back on InriaGforge server using : scp -r /tmp/<unix_project_name>/* youlogin@scm.gforge.inria.fr:/svnroot/<unix_project_name>/
or send us an email at help.et.gforge<at>inria.fr
- Remove the pre-commit hook
This kind of problem can occur when commiting large binary files. A best practice for these files (pdf, doc,code compiled, or release) is to use the feature "file release system" provided by the forge.
By default each project on InriaGforge is provided with a mailing-list : project_name-commits.
When the repository of a project on InriaGforge is modified after a commit, an email containing the diff is sent to the list myproject-commits. This is done via a post-commit hook mechanism.
See this entry for more information about this hook.
If you want to be notified by mail, you need to subscribe to the project_name-commits list. To do so :
- Select the "Lists" tab
- You will find a table with the lists available for your project.
Retrieve the line for the list project_name-commits, and click on the link "Subscribe/Unsubscribe/Preferences"
- You will access to the mailman page dedicated to the list.
Fill the form shown at paragrah "Subscribe to project-name-commits".
The administrator of the list (which address is shown at the end of the page) will receive
your subcription demand.
Since 04 December 2008, the repository URL on InriaGforge server are located within scm.gforge.inria.fr domain name.
To be sure your own copy of a InriaGforge project repository is ok with this configuration :
Rem : if you are using CVS, you must perform the same kinds of checks.
To be able to:
- import your previous cvs or svn history,
- checkin a modification to the cvs or the svn repository,
- modify the project homepage,
- upload files to your private homedir
you need to setup an ssh connection between your machine and the gforge
server.
On Linux:
- An ssh client should already be installed on your machine and
should be accessible from the command line, as the "ssh" command. If not,
contact your system administrator.
- Generate a pair of rsa public/private keys with the ssh-keygen command:
ssh-keygen -t rsa (make sure you enter a lengthy passphrase, ie non null, when asked to).
- Copy your public key in an easy-to access file: cp ~/.ssh/id_rsa.pub ~.
- Paste your public key in the gforge website. To do this, you need to go to
your account and then go to the
Account maintainance tab. At the
bottom of the Account maintainance tab,
you should see a Shell Account Information section which contains an
[Edit keys] link.
Paste your public key(s) in the empty field below and click the Update
button.
On Windows, consult the ssh for windows page.
A common problem is that the Shell Account Information field does not
appear in your account page. This usually happens because you do not belong to any
gforge project. To correct this problem, either create your own project first
or request the project admin of the project you want to join to add you to the list
of the project's contributors.
Please, be aware that uploading your ssh public key on the server will not allow you
to connect to the server immediately through ssh. To do so, you will need to wait at most
24h. If your connection is impossible 24h later, please, contact the server
administrators.
A private project is a project that only exists for those who know that it has
been created and that can only be seen by the people that are registered as members of
this project. All members of a project have access to the source control Manager (SCM)
and to the webspace of the project.
A public project appears in the list of project hosted on the forge. Anybody
can find it using the search function, the project tree or a search engine and can browse
all public items of the project. But a public project does not necessarily mean that all
items of the project are public. The visibility of each item can be controlled item by
item. For example, you could have a public tracker for bugs, a private tracker for security
problems, and anonymous access to the source. The visibility of each item is controlled by
the admin link that is accessible to the project's admins on the page showing the item.
In all cases, only registered members of the project can change the web pages of the
project or its source code.
Project visibility is a project attribute chosen at the start of the life of a
project. Project administrators can change the visibility of their project by changing
the properties of the Observer role.
This can be done in the project admin pages, on the right column, where you should find
button named edit observer. The project priviledges section enables an administrator to
change the visibility of a project.
You should be aware that changing the visibility of a project does not change the
visibility of the different elements of the forge you are using. After having
made a project public, you will need to evaluate if you want to change the
visibility of any other element (eg. your cvs repository or your bug tracking tools).
The key to controlling access to the different parts of your project
on InriaGforge is the admin page of your project.
On the right of this page, each member of your project is given a
role, and to each role, access rights are associated. You can change
them by using the edit role part of the page.
A special role is the observer role : this is the role of people that
are not member of your project. By editing the observer role (edit
observer button, at the bottom of the project member list) you can
control access by anonymous users.
NB : Due to availability of both protocols (https and svn+ssh), restricting access to a Subversion subdirectory for somes users (among those participating in the whole project) isn't possible.
Creating a private project is the only way to gain this feature.
Some projects enable anonymous users to post issues on the trackers or forums
they run, for reporting for example. Some spammer are using this
setting for advertising using the trackers or forums, either by posting new
issues, or by commenting open issues.
InriaGforge hasn't got any technical mesures in place to prevent
that kind of spam. Therefore, if your project suffers from this, you
should change the access rights of all your trackers or forums to prevent
anonymous posting, by editing the observer role.
I created the project and/or I am an admin of a project but my normal gforge
password does not allow me to access the admin web interface of the mailing-lists.
This is normal. The password used to control access to the mailing-lists admin web
interface is different from your normal gforge account. This different password has
been emailed to all the admins of the project at the time the mailing-list was created.
The Subject of the email was
InriaGforge New Mailing List. It contained the password used to access to the
admin url:
http://lists.gforge.inria.fr/mailman/admin/your-mailing-list
If you lose/forget the password of the mailing-list administrator, you need to send an email to the administrators of the InriaGforge (help.et.gforge<AT>inria.fr) to ask the password of the list to be reset.
If the mailing-list is of the type myproject-commits, you should verify if you keep the mail sent at the time the mailing-list was created (see item above).
To do this, you need to be the mailing-list administrator. Go to:
http://lists.gforge.inria.fr/mailman/admin/your-mailing-list. To be able to log
successfully, you need your special mailing-list administration password. For information
on this password, see I cannot access the admin interface for the mailing-lists.
- Log into the administrative interface of your list
- Go to privacy options
- Go to the sender filter
- Find the Should messages from non-members, which are automatically discarded, be forwarded to the list moderator? line and answer No.
- Find the Action to take for postings from non-members for which no
explicit action is defined line and answer Discard.
- Save your changes
To do this, you need to be the mailing-list administrator. Go to:
http://lists.gforge.inria.fr/mailman/admin/your-mailing-list. To be able to log
successfully, you need your special mailing-list administration password. For information
on this password, see I cannot access the admin interface for the mailing-lists.
- Log into the administrative interface of your list
- Go to privacy options
- Go to the sender filter
- Find the List of non-member addresses whose
postings should be automatically accepted line and add something like (example from the default settings)
^.*@users.gforge.inria.fr
^.*@inria.fr
^.*@irisa.fr
^.*@inrialpes.fr
^.*@loria.fr
^.*@sophia.inria.fr
- Save your changes
On INRIA Gforge, each mailing-list name is of the form :
- <project_name>-suffixname@lists.gforge.inria.fr
To know what kind of suffixname is allowed, see this FAQ entry
If you need to add a member to the list that is already registered on INRIA Gforge, you can use the address <userlogin>@users.gforge.inria.fr.
This will refer automatically to the email address the user has given when registered on INRIA Gforge.
The web hosted pages for a projet on InriaGforge are located under host scm.gforge.inria.fr, and directory /home/groups/<project_name>/htdocs/.
By default, a index.php file is created for each project when the project has been registrated on the InriaGforge.
As you can not access to the server scm.gforge.inria.fr directly through ssh, you must use the commands : sftp, scp, or rsync.
To list the files, you can use sftp:
$ sftp <yourlogin>@scm.gforge.inria.fr:/home/groups/<project_name>/htdocs/
sftp> ls
sftp> exit
In order to modify the web hosted pages, you can use rsync to retrieve the files already hosted at scm.gforge.inria.fr:/home/groups/<project_name>/htdocs/ :
$ rsync -avz <yourlogin>@scm.gforge.inria.fr:/home/groups/<project_name>/htdocs/ <localpath>
Note: The parameters proposed below for rsync ensure that symbolic links, devices, attributes, permissions, ownerships, etc. are preserved in the transfer.
Modify the files locally on your machine, then send back the modified pages to scm.gforge.inria.fr:/home/groups/<project_name>/htdocs/ :
$ rsync -av <localpath>/ <yourlogin>@scm.gforge.inria.fr:/home/groups/<project_name>/htdocs
If you have trouble with the file permissions, once the files are back to the InriaGforge server, you can use sftp to modify them.
$ sftp <yourlogin>@scm.gforge.inria.fr:/home/groups/<project_name>/htdocs/
sftp> ls
sftp> chmod o+r filestobemodified
sftp> exit
You may check also this FAQ entry explaining why the owner of the files on your site must be to nobody_<project_name>
Yes. You can find an access log file under /home/groups/<project_name>/log and a html file containing information generated by
awstats under /home/groups/<project_name>/htdocs/log/. You can visualize the generated statistics using the URL http://<project_name>.gforge.inria.fr/log/.
Yes. Apache honors the .htaccess files that you place in the file hierarchy of your projects (files under /home/groups/<project_name>/htdocs/). You can therefore implement access protection using .htpasswd. Please refer to the apache documentation to implement this.
Yes. We have enabled php for project's webspace. Nevertheless, the primary reason php is installed on the webserver is to support the web interface of InriaGforge. Therefore, php.ini and the php version installed are configured to match InriaGforge's needs. If a security warning imposes changes on the configuration, we will act without notice to project admins. If the change is the result of a planned upgrade, project admins will receive advance notice so that they can plan for the upgrade.
To secure the server, all php scripts used by a project are run with
suPhp, which runs the scripts as the owner of the php file. To ensure
a badly written php script does not compromise to much data, a regular
script changes the owner of each php file to
nobody_<project_name> automatically. Therefore, if your php
script is insecure, an attacker would not gain access to the source
code repository nor to data of other projects. Nevertheless, you must
be carefull to allow further modifications to your script by giving
write access to php files to the group:
$ sftp <yourlogin>@scm.gforge.inria.fr:/home/groups/<project_name>/htdocs/
sftp> cd path_where_phpfile_installed
sftp> chmod g+w myfile.php
sftp> exit
More advanced users can use umask to ensure this is done automatically.
Some projects have all their files owned by
nobody_<project_name>. This is the result of a buggy version of
the regular script that changes the owner of .php files. Please
contact the site administrators to have this corrected if you need to
change the files and you don't have the correct access rights to do this.
No. The database server on InriaGforge has for only purpose to host InriaGforge's data. If you need a database backend for your project's webspace, please use other ressources.
Change the home page (file index.php) hosted by gforge.
Put the following HTML code between HEAD tags :
<meta HTTP-EQUIV="REFRESH" content="0; url=http://myotherserver/myproject">
This happens if you try to upload a large documentation file. Unfortunatly,
the exact file size limit is unknown and depends on the content of the file
itself. Furthermore, no error message is displayed to explain that the submission
failed because the file is too big.
To workaround this problem, you can upload your documentation to your web area
and then fill in the OR specify an outside URL where the file will be referenced :
field in the documentation submission form to point to that uploaded file with something
like: http://yourproject.gforge.inria.fr/yourfile.ps
This workaround suffers from the fact that the uploaded documentation file will
be publicly accessible to all, even for private projects, because it will be served by the
web server with no access control.
To delete a document file uploaded in the docs area (see "Docs" tab):
- Click on "Admin" link at the top left of the page
- Select either the document if it appears or the document group onto which the document has been added
- Once the document as been selected, you are shown a page given information about that uploaded document : its name, its description, its status, ...
- Click on the link "Permanently delete this document" located at the bottom of the page.
If you see no "Admin" link, your role on the project does not allow you to delete a document. So contact a member of your project who is "Admin" to do that or to modify your role to be allowed to. For more information about the roles, see this FAQ entry.
When you create a new project, when you upload a new ssh key,
when you create a new mailing-list, you might notice that the results
of these operations are not immediate. Even after a new project has been created, browsing the
cvs or subversion repository and accessing the web space
are not immediate. Many operations (the above list is not
exhaustive) can take up to 24hrs to complete.
This happens because the server records operations and only periodically
performs them.
If you are really in a hurry, you can send an email to
help.et.gforge<AT>inria.fr to ask
for a special server update. Otherwise, we ask you to be patient and wait for the
server to complete these tasks on its own which will improve its
reliability.
You might want a tracker or a forum to send mails to a mailing list, for example so that any new bug submission is announced in the developper mailing list.
First you need to be a member whom role allows to administrate the tracker or the forum. Then you can access to the "Admin" page relative to the tracker, or forum. Once on the "Admin" page :
- For tracker, you need to :
- click to the "Update preferences"
- then fill the "Send email on new submission to address" field with the relevant list address. If you want to use a list created via InriaGforge, see how to name the list FAQ entry.
- For forum, you need to :
- click on the forum name of interest
- fill the "Email All Posts To" field with the relevant list address. If you want to use a list created via InriaGforge, see how to name the list FAQ entry.
The mails coming from the tracker or the forum are set such as the sender is :
- For a tracker : projectname-trackername@gforge.inria.fr
- For a forum : projectname-forumname@gforge.inria.fr
So you need to modify the configuration of the list such as it accepts mails coming from this kinder of sender.
To do so, see the How can I make my mailing-lists automatically accept mails from some domains ? entry.
The list manager may complain that the message coming from a tracker or forum was not an explicit destination and may reject it. To solve this, you have to modifiy the mailing list configuration. The option you are looking
for appears under Privacy Options/Recipient filters. You should set require_explicit_destination to no.
The front page presents InriaGforge Statistics to all the visitors.
On top of that, on the default page of each project displays an Activity
Percentile for the project. These statistics don't always seem right. Here
is a list of reasons they might not show expected numbers.
- The number of hosted projects seems low: this is because only public
project are counted here. Better stats are available from InriaGforge's admins.
- There seems to be no correlation between the box displaying the number of
downloads and the one displaying the most active projects. This is because the
first box is cumulative, whereas the second only takes into account the previous week.
- There seems to be no relation between the activity of a project and the
percentile displayed on InriaGforge. This is because the percentile is computed
from incomplete information. In particular, projects using a subversion repository
don't have their repository activity taken into account whereas projects using a
cvs repository do. This should change during the next upgrade cycle for the software
behind InriaGforge, planned in 2006. To be a bit more precise, activity percentile is
computed from
- Activity in the project's forums
- Activity on the project's task manager
- Activity on the project's bug, tech support and patch trackers
- Number of downloads
- Number of released files
- Activity in the cvs repository
Beware that the percentile reflects only the rank of the project regarding its activity
computed as explained above.
If N projects have an activity (i.e. there are downloads, releases or activity in forums, etc.),
then the "most active" project have an activity of 100%, the second project has (100-(1/N))%,
the third has (100-(2/N))%, etc. In general project with rank M has an activity percentile
of (100-(M-1)/N)%. Only public projects are displayed in the list active projects.
If you have followed ths configuration steps described in the
webpage mentionned in
How do I setup ssh (even on windows ?), you can use either
a graphical or a shell-based utility to access your cvs/svn repository.
To use the graphical utility, follow the steps described in our
tortoise page.
To use svn from a shell, you can follow these steps:
- Download a binary version of subversion from
there
or, if it does not work, from there.
If you do not have administrator privileges on your machine, ask your system administrator to do it
for you.
- Start the pageant.exe utility which comes with putty. This program installs a small icon
(a computer screen with a hat) in your panel notification area located at the bottom right of
your screen. Right click on this icon and select the Add key item. In the file
selection dialog which pops up, select the private key file you saved during the ssh configuration
as described in How do I setup ssh (even on windows ?).
- Open a terminal, go to the directory you want to store your files in. Set the SVN_SSH environment
variable with this command: set SVN_SSH=plink.exe and then run this subversion command:
svn co svn+ssh://<your_username>@scm.gforge.inria.fr:/svn/<your_project_name>
To be able to :
- Manage your ssh connection with Eclipse
- Manage a Inria Gforge CVS depository with Eclipse
Consult the HowTo configure Eclipse page.
Because of predefined reserved names on gforge architecture, when naming your forums or mailing-lists, please AVOID theses words :
- For Forums:
- For Mailing-lists:
- projectname-admin
- projectname-bounces
- projectname-request
- projectname-subscribe
- projectname-confirm
- projectname-join
- projectname-leave
- projectname-owner
- projectname-unsubscribe
- projectname-post
A Wiki plugin is available for projects on the Inria forge and it is based on PhpWiki.
By default this plugin is not activated at the creation of a project.
To activate this plugin, as an admin of a project, you need to :
- Go to the "Admin" tab
- Click on "Edit Public Info" link
- Select "Wiki Plugin" box within the "Active Feature" paragraph
- Click on the "Update" button at the end of the page
- Return to the "Summary" tab
- Then you will notice a "Wiki" tab
In the "Wiki Plugin" page, you will find links to pages explaining how to use this wiki (eg. the text coding rules).
See this FAQ entry.
See this FAQ entry.
To delete spammed message or unwanted message from a forum, first you need to be a member whom role allows to administrate the forum.
If so, follow these steps:
- From the "Forums" tab, select the forum where the unwanted message has been added
- Select the topic message to be deleted
- Click on the link which name is the subject message to be deleted (below the line beginning with "By:")
- You will get a page where the content of the message is in a box which title is "Message" followed by a number : the message identifier
- Note this identifier
- Click on the "Delete" link at the top of this page
- Enter the identifier and click on the "Delete" button
Depending on feedback from our users, default settings for newly created projects evolve over time. This section of the FAQ holds a list of topics usefull to project admins who requested creation of their project before some of the settings evolved. You can still discover usefull information in this section, so it is kept as a reference.
By default, mailing lists request moderation for messages sent using e-mail adresses
that are not subscribed to the list. At the same time, message generated by cvs or svn
during commit or import operations are sent using an adress in the form
<yourlogin>@users.gforge.inria.fr. To avoid to have to moderate these messages, it is
possible to whitelist all messages sent from the users.gforge.inria.fr domain. To do this,
you need to :
- Log into the administrative interface of your list
- Go to privacy options
- Go to the sender filter
- Add
^.*@users.gforge.inria.fr to the list of non-member addresses whose
postings should be automatically accepted
- Save your changes
| 
