Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
jami-project
jami-project
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 177
    • Issues 177
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-projectjami-project
  • Issues
  • #200

Closed
Open
Opened Jan 20, 2016 by RingBot@RingBotOwner

Only use the mailing list for announcements and tell users to open issues on Tuleap at ring.cx

Issue generated from Tuleap's migration script. Originally submitted by: Ciro Santilli (cirosantilli)

https://ring.cx/en/documentation/how-to-contribute-to-the-ring-project says:

by subscribing to the mailing list (to report bugs, to receive some help or just to follow the development of project).

We already have the major bug tracker on tuleap, which is way more flexible, so let's tell users to open issues there instead. We could also give users the new post link directly, since I imagine not many people are familiar with tuleap.

Having two bug report methods means that everyone has to search things twice.

I also think that usage questions / feature requests should go to Tuleap as well for the same reasons.

This would leave the ML only for announcements, a feature which overlaps with a Twitter (what to do here this one is a tough choice. I'd keep just Twitter + blog posts).

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-project#200