Differences between revisions 81 and 82
Revision 81 as of 2017-09-17 08:47:33
Size: 9281
Editor: ?formorer
Comment:
Revision 82 as of 2017-09-17 08:49:01
Size: 9308
Editor: ?formorer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

<<TableOfContents()>>
Line 40: Line 43:
There isn't a replacmemtn planned for mailinglists. There isn't a replacement planned for mailinglists.

Translation(s): English - Français - Italiano - ?Russian

(!) ?Discussion


What is Alioth?

Alioth is broken, and there is nobody around to fix it. Don't ask the remaining people who give it life support to implement fixes and changes. There may eventually be replacements for some parts of it, but that is not now (2017-08). Please subscribe to debian-devel-announce for updates.

Alioth.debian.org is a Debian server running FusionForge (used to be GForge). It's much like sourceforge or savannah but it's a service for Debian Developers and all other kinds of contributors together.

Benefits of registering an account on Alioth

An Alioth account provides several benefits:

  • It can be used to access many Debian projects resources as a single sign-on provider
  • It makes it possible for contributors activity to be tracked and shared on the Debian contributors list, even when using different email addresses across several official and unofficial projects (wiki, forums, packaging, etc.)

  • It provides an email alias <loginname@users.alioth.debian.org>

  • It doesn't require going through any specific process or approval, making the barrier to entry very low for any first-time contributors.

News

Deprecation of Alioth

Alioth was deprecated and will vanish with the wheezy EOL. Please read the hints below about specific Alioth services.

Mailinglists

There isn't a replacement planned for mailinglists.

Moving lists to lists.debian.org

Some mailing lists that were formerly hosted on Alioth may be eligible for being hosted on lists.debian.org. The lists eligible for migration must follow the requirements outlined on the "How to ask a mailing list" guide. The process is also the same as outlined on the guide.

The following kind of lists are probably acceptable for lists.debian.org:

  • The list is expected to be useful, to have a purpose and an audience.
  • Public discussion or support lists are probably OK.
  • Commit or bug notifications lists are not OK. You should use the dedicated features of gitlab instead. If you're interested in a package's bug, you're expected to subscribe to it using the BTS features.

Short version: file a bug on the pseudo-package lists.debian.org with the severity 'wishlist', with the following information:

  • List Name
  • Rationale (why do you need this list, stating that you had one on Alioth is not enough!)
  • Short Description (for display in list indices)
  • Long Description (targeted to people that need to decide if they want to join)
  • Category

Lists migrated from Alioth are expected to be open, that is:

  • Open Subscription Policy (no closed lists)
  • Open Post Policy (anybody can post)
  • Open Archive
  • No moderation

If you do want the archive and/or the subscribers to be imported into your new mailing list, please:

  • on alioth, using your ssh access, run 'sudo /usr/local/bin/export-list <mailing_list_name>' to get gzipped tar archive (on stdout) containing:

    • mbox file of the archive
    • subscribers list in simple text file
  • import the resulting mbox file in your favorite e-mail reader and clean the spam,
  • attach the compressed archive and/or the list of subscribers to your request.

Also, please understand that the requirements and features for lists on lists.debian.org are not the same as for a mailing list on Alioth, and the listmaster might reject your request. Lists.debian.org is not supposed to replace all mailing lists and aliases on Alioth.

tracker.debian.org

Smaller teams and commit lists should move to the mail interface of tracker.debian.org.

Maintenance

Alioth has these administrators (IRC nick in parenthesis):

  • Alexander Wirt (formorer)
  • Roland Mas (Lo-lan-do)
  • Christian Bayle (chris38)
  • Stephen Gran (sgran)

They can all approve projects and have full administrative rights on all project if needed. They also have root rights on the machine.

They can be contacted via admin@alioth.debian.org. If you encounter a problem with alioth, you can file a support request on the siteadmin project. Sometimes, when you need to prod an administrator to do something, you can join #alioth on irc.debian.org (OFTC) ... they may help you.

Technical details

The machine hosting alioth.debian.org is running on moszumanska.debian.org. It is also hosting svn.debian.org, arch.debian.org, bzr.debian.org, darcs.debian.org, git.debian.org, and hg.debian.org. Those services are tightly related to Alioth since all the user accounts and the groups are taken from FusionForge database. This means that you can only create VCS repositories for existing alioth projects and that any member of that project will have access to the corresponding public repository.

All VCS repositories can be automatically created by FusionForge: enable “Source code management (SCM)” in your project (this can be done in the “Admin” tab, click on “Edit public infos”), then go the “Admin“ page in the “SCM” tab and there you can choose the type of SCM wanted. The repository will be automatically created by a cron job some hours later.

Alioth uses a modified version of FusionForge, see ?Alioth/FAQ#src to grab the dedicated bzr branch. Feel free to send us patches that apply to this tree if you want to get something fixed in a more timely fashion.

How can I help?

We tend to have a big number of support requests, please help us deal with those. Sometimes it requires a change to FusionForge, sometimes it only requires explanations to the submitter, you'll surely find something to do over there.

Other questions

Before asking an admin, please read the ?Alioth/FAQ.

  • Other wiki pages:
    • ?Alioth/FAQ -- Frequently Asked Questions

    • ?Alioth/SSH -- Information concerning SSH usage

    • ?Alioth/PackagingProject -- Using Alioth to maintain Debian packages

    • ?Alioth/Web -- Hosting web pages and/or web applications on Alioth

    • ?Alioth/ikiwiki -- How to use ikiwiki on Alioth

    • Concerning version control systems :
      • ?Alioth/Svn -- How to use Subversion on Alioth

      • ?Alioth/Git -- How to use git on Alioth

      • ?Alioth/Bzr -- How to use bzr on Alioth

      • ?Alioth/Hg -- How to use Mercurial on Alioth

      • ?Alioth/Arch -- How to use Arch/Baz on Alioth

      • ?Alioth/Darcs -- How to use darcs on Alioth

    • Alioth/OtherForges -- alternative software forges

  • External documentation


?CategoryAlioth | CategoryPermalink