tenacityteam/tenacity-legacy

Start work on infrastructure

Open

#119 opened on Jul 7, 2021

View on GitHub
 (20 comments) (8 reactions) (0 assignees)C++ (6,921 stars) (275 forks)batch import
documentationenhancementhelp wanted

Description

EDIT: I was out of the loop, work is bieng discussed and done on: Libera IRC: #tenacity
Matrix: #tenacity:libera.chat

Issues:

  1. Currently there is no place where someone new, wanting to contribute to the project, can get up to speed on the progress.
  2. There is no "quick-start guide" for someone who would just like to install Tenacity and be on their way.

Now, I know this project is still in it its very early stages, and you may think its too premature to start work on the forums and guides, but in reality, the support and streamlined installation process is just as important as the software itself.

In the end, the only audacity fork that will survive is the one that can get out of early development and onto the majority of computers, the one which can be installed by the largest amount of people. It will only be then that linux distro maintainers will consider adding Tenacity to their official repos.

My proposal:

  • Separate teams and leadership for the software and infrastructure teams, the latter managing the website, hosting, IRC chat rooms and other sysadmin stuff.

  • Creation of an easy to navigate website Ideal: Keepassxc

  • Creation of dedicated forum or well-moderated subreddit, and IRC for general discussion and support. Ideal: KDE forum , KDE Subreddit , Arch IRC

  • Simultaneous work on Tenacity and the infrastructure so that the first release can be smooth and successful.

Suggested task list:

  • Creation of tenacityteam.github.io repo which will be served on tenacityaudio.org
  • Creation of tenacity-branding repo where contributors can discuss logo ideas and colors.
  • Appointing of infrastructure team.

Contributor guide

Tech stack
None
Domain
infrastructuredocumentation
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
website developmentforum setupIRC management
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The issue proposes creating infrastructure (website, forums, IRC, branding) for the Tenacity project. It has 20 comments; review those for discussion and any progress. The repository is deprecated; the active project is now on Codeberg. Look at the current infrastructure there or ask in the community channels (IRC/Matrix) for status.
Start work on infrastructure · tenacityteam/tenacity-legacy#119 | Good First Issue