>Yes, one of my Slackbuilds was apparently updated recently (by a bot >or something?) and it was said to be committed by my GitHub username >even though I had nothing to do with it. I don't have a problem with >automatic updates in some situations if this makes maintenance easier >for Willy and team, but I am not comfortable with being impersonated. >It shouldn't have my username on it if someone else did it.
I sometimes makes a direct changes to some scripts (not particularly on yours Dan, but in general), when i saw some security updates needed or the maintainers is MIA and i know it won't break things. But there are times when i thought it was a minor changes and turns out upstream made a *major* changes and i missed the ChangeLog, so it broke some other scripts. At least we could catch most of build failures asap with our CI, thanks to Andrew's work. Some were not catched because it built fine on CI, especially those bugs that were occurring during runtime, but we could find out when users starts reporting. So my suggestions for those who have knowledge on how to submit an updates via github/gitlab, please do so. At least we can tag your handler directly without having to check the submitter's email. It's easier when everyone is doing updates via github/gitlab and leave the submission form *only* for new scripts. -- Willy Sudiarto Raharjo
pgpAJQZyrudXb.pgp
Description: OpenPGP digital signature
_______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
