Re: Request access issue management

Jonas Hahnfeld via bug-lilypond <[email protected]>
Newsgroups gmane.comp.gnu.lilypond.bugs
Message-ID <[email protected]>
On Sun, 2022-07-17 at 20:32 +0200, Jean Abou Samra wrote:
> Le 17/07/2022 à 20:26, Paulo Matos a écrit :
> > Hi,
> > 
> > As described in:
> > https://lilypond.org/doc/v2.23/Documentation/contributor/introduction-to-issues
> > 
> > My gitlab nick is pmatos, so I can be given appropriate permissions to
> > manage issues. I have also already requests access to the lilypond
> > group.
> 
> SGTM. CCing Jonas (I'm not sure if he follows this list).

(Let's say that I'm subscribed; by the time I come to read the new
messages they are usually already taken care of 😄 but GitLab finally
listened and I even got a notification that somebody requested access,
which is a lot better than me checking manually every n weeks and not
coming back to people in time...)

> I guess the appropriate permission level for a newbie wanting
> to help with triaging issues would be Reporter?

Yes, done. You should be able to assign issues and change labels. For
bigger changes, such as reorganizing labels, please ask on the mailing
list first 🙂

> Thanks for offering to help!

Indeed, thanks!

Jonas

_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEXw/5YGpL6H9VOgO2kcnDPSxhrNsFAmLVePsACgkQkcnDPSxh
rNsqOwf7B/BQsyysBnaUKdDgYHY2t5xMyCC9jkfJXfzioXaSFEJ2bAm6X4saYwr2
ClHq4RGcDIZGNSjSz4aQjme0B/8DGskjGxpdkfNCQCEJ3dhzvWOSfxFIhvb/sP9s
vQzGMgan7670U0tC6VZhvHS484Qr/xGMGgWruakcFPNOZQ1DikaVO7ho3gwKY9xH
9+8B32bVz495eIlYP0BoQJK1x8/ejs8qbNoXD64P2G6aHxh0gy2JHt/fiPiQbpVb
OUf2Hg52lFcm8hqRMe9k9jtXgNK1p4tWKLiZ+tDJQlKu3BXX9wFxfP3OQGLx5gl/
VPq/QMOAo8riDEOXf+O0dZ+Vqbf7LA==
=+e4X
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.