> A group of long time users might be assembled to aid with the process. > Registration date could be a measure of trust in this case. You may think of > them as trusted users
I believe the risk here would be the creation of a black market of older accounts, especially if the AUR grows in popularity, so there would still need to be some sort of application process. On Tuesday, August 11th, 2026 at 4:44 PM, Marcin Wieczorek <[email protected]> wrote: > I'm happy to hear that there are new features implemented. Is this going to > be a burden for Package Maintainers? You might consider offloading the work > of adoption acceptance to regular users. Iirc the matter has been discussed > here. A group of long time users might be assembled to aid with the process. > Registration date could be a measure of trust in this case. You may think of > them as trusted users... Pun intended. > > Best regards > Marcin Wieczorek > > On August 11, 2026 1:16:45 PM GMT+02:00, Leonidas Spyropoulos > <[email protected]> wrote: > >Hello, > > > >aurweb v6.5.0 is now deployed on aur.archlinux.org. > > > >- SSH/git push access is re-enabled along with adoption. > >- Registration remains closed for now. > > > >Two changes affect users: > > > >Package adoption now requires review. Adopting an orphan, whether from > >the web interface or via `ssh [email protected] adopt <pkgbase>`, > >files an adoption request rather than transferring maintainership > >immediately. A Package Maintainer must grant it. Only one request can be > >pending per package base, and requests nobody acts on are rejected > >automatically after 14 days. > > > >Most (real) users remain unaffected but unverified accounts are sent a > >warning after 7 days and removed after 14. Verifying your address at any > >time stops this. This cleanup is a preparation for SSO interation when > >eventually comes along with fighting malicous / spam accounts. > > > >Thanks, > > >
