secondlife / secondlife/viewer

Ability to rename a group

Open
#4,377 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement team:viewer
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Summary

Allow group owners to rename groups. This will allow users to address changes to their group purpose, branding, and generally provide greater flexibility for group social features and identity.

User Stories

As a Group Owner, I want to:

  • Rename my group so that its name accurately reflects its current purpose or branding.
  • See an input field within the group floater where I can enter a new name for my group.
  • Receive clear feedback if the new group name I choose is already in use, contains inappropriate terms, or does not meet length requirements.

As a Second Life Resident, I want to:

  • See updated group names in the Group Finder, my profile, and other UI elements where group names are displayed, so that I can easily identify and interact with groups.

Requirements & Validation

  • UI Placement: A new input field for the group name will be added to the existing group floater UI.
  • Permissions: Only group owners (or roles with equivalent permissions) can initiate a group rename.
  • Uniqueness: The new group name must not already be in use by another group.
  • Content Policy: The new group name must not contain inappropriate terms and must adhere to the Second Life Terms of Service (ToS).
  • Length Constraints:
    • Minimum length: To be determined (e.g., 3 characters).
    • Maximum length: To be determined (e.g., 50 characters).
  • Cooldown Period: A group can only be renamed once every 7 days. This cooldown applies from the time of the last successful rename.

Questions

  • Should it cost L$ to change a group's name?
  • How should validation errors be presented? In a tooltip? (See "Validation States" section under Mockups for a proposal)

Mockups

Image

A new group name input field added under the "Group" section of the floater.

✅ Validation States Image Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start by locating the existing group floater UI and group-name handling in the viewer, then trace how group permissions and updates are represented. Done requires an agreed design and implementation for renaming, validation, cooldowns, and updated names across the listed UI surfaces; the open cost and validation questions need decisions first.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.