[Slackbuilds-users] [hplip-plugin] updated without my say-so, by someone who used my name and email.

[Willy Sudiarto Raharjo]

>        I  wonder if  current SlackBuild.org  policy
>  allows  individual maintainers  to sign  their own
>  updates, by optionally  including a signature file
>  in their  upload, which gets published  to the end
>  users just like any file in the SlackBuild.  Users
>  who want to be extra cautious can then validate it
>  to make sure nothing weird is happening.  Would my
>  updates be rejected if I do so?

During development cycle preparing for next SBo repo, we take everyone's work
in order to make the script works with latest snapshot of -current changes.
That will surely break the workflow if only certain people are allowed to
update a script.

>        At minimum, we  need email confirmation sent
>  to the maintainers' address when they make uploads
>  so that their identity is slightly confirmed.

Yes, this is the easiest way actually, but for now, send updates via
github/gitlab is the preferred solution without making any changes to the
current workflow. You might be given privileges to run the CI to test your own
scripts as well, so double benefits for active maintainers :)


--
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 870 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20260516/83cae1ef/attachment.asc>