Contributor Invite: Add Option to Set SuperUser Password for Mumble

About this Contributor Invite:

  • Task Area: Coding
  • Effort rating: 3/5
  • Skills required: Python, Django Views/Templates/Forms

Description of the Problem:

In the Mumble VoIP application, a “SuperUser” account can be used to manage channel and group permissions. But currently, there is not an option within FreedomBox’s UI to set SuperUser’s password for Mumble. Users need to manually retrieve or set the password.

What we ask of you:

Add an option in the Mumble app page to set SuperUser password. One can access these options after logging in with username ‘SuperUser’ with super user password. See Murmur Guide. To fix the problem, do the following:

  • Move MumbleAppView to views.py under the plinth/modules/mumble directory. See ssh as example.
  • Implement MumbleForm in forms.py and add a field to input the super user password. See ssh app as example. Label should be “Set SuperUser password”. Description for the form field should say “Optional. Leave this field blank to keep the current password. SuperUser password can be used to manage permissions in Mumble.”. Use this form in MumbleAppView.
  • Implement code for successful submission of the form. Implement an action script in actions/mumble. This action should set the password for mumble super user. See Mumble wiki page on setting the password. The operation should be run as ‘mumble-server’ user. Password should not be passed on the command line. Instead send it on standard input using -reasupw option.

Link to the issue in GitLab: https://salsa.debian.org/freedombox-team/plinth/issues/1680

How to claim this Contributor Invite :

Do you want to accept this invitation to contribute? If so, follow these steps:

  1. Comment on this forum post indicating that you would like to claim the invite. This will prevent multiple people from working on the same issue at the same time.
  2. Register an account with our GitLab instance and begin making your contributions on the GitLab issue page for this task. You can use the comment section of this forum post to ask questions, but the bulk of the development discussion should happen on GitLab.

Resources:

If you need help with this issue, please feel free to ask for it from members of our core team:

  • Sunil Mohan Adapa (@sunil): Lead Developer & Code Reviewer
  • Joseph Nuthalapati (@njoseph ): DevOps Engineer, Developer, & Code Reviewer
  • James Valleroy (@jvalleroy) : Release Manager, Developer, & Code Reviewer