Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 931
    • Issues 931
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #18052

Closed
Open
Created Dec 07, 2020 by intrigeri@intrigeriMaintainer

Document how users can add IRC support back themselves

Parent issue: #8573

Once we drop Pidgin, likely its replacement won't support IRC.

On #15816 (closed) we reached the conclusion that it was OK to drop IRC support by default, but we should smooth a bit the transition, in order to lower the noise this will create, and ease the pain on Help Desk.

We could:

  • Keep the Pidgin configuration in our image
  • Drop the Pidgin persistence feature: otherwise it's visible to everybody and we need to keep the corresponding doc
  • Document a way to add and configure Pidgin in a persistent manner
    • Install via Additional Software
    • Make ~/.purple persistent, e.g. by adding a line to persistence.conf or via dotfiles

For the discussion that lead there initially, see #15816 (closed).

Edited Dec 07, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking