In case you all weren't following https://issues.apache.org/jira/browse/INFRA-23505, keep reading for the backstory
Action required: if you have pulled from the juddi-scout git repo since 2019, you'll want to stash or backup any changes that you've made (if any), and do a clean check out to a new folder and discard the old one. Otherwise, please disregard Backstory. I support a number of open source projects. I think at one point, while using sourcetree (no endorsement implied), i had inadvertently added a remote endpoint for an unrelated project to my local checkout of juddi-scout, then pulled in master. The result was a mess and IIRC, i took the action to deal with it later. Fast forward to a few days ago...a ASF INFRA bot reported that my gpg public key was not in either juddi nor juddi-scout's KEYS file. So i added it, committed and pushed without thinking. Thus now the juddi-scout git story is polluted with unrelated, non-ASF source code. Whoops The ASF INFRA team apparently keeps backups and has restored the repo back to the last commit in 2019.
