On Sat, 21 Jun 2025 at 11:03, Hervé Boutemy <hbout...@apache.org> wrote:
> thanks for leading that retirement, that permits to stress test our > instructions against new eyes > > yes, after generation of the .yaml, asf-site branch being updated but not > the > web server is strange: I don't know if it was just a accidental hiccup or > if > there is a recurring edge case based on the way the content is created > We'll need to share the next time: the good news is that any manual update > seems to solve the issue > > on informing users vs dev: in fact, the spirit is there, it just has to be > adjusted based on the reality of effective mailing lists of the retiring > project, as it varies, and we avoided in the past creating too long > explanations > > on interpreting what level of communication is considered sufficient, it's > really up to the Attic retirement lead to make his own decision, and just > update the Jira issue to point to the message(s) he considered ok. > Again, simple instructions to avoid complex reading. > > on CSP: you're the expert, I hope this is a transient check that won't be > necessary in the future > Of the 103 websites that used proscribe analytics in Jan 2025 there are now only 4 projects that have not resolved this and I'm still working to get those last few resolved. With my privacy hat on, its on my TODO list to work through the CSP issues for apache projects. In most cases it doesn't really matter if they resolved (its a "nice to have") - which is the case here for jclouds (their website looks fine, just fonts being blocked). So it is a transient issue and something I'm prepared to work on (with both Privacy & Attic hats) - but I don't think its a big issue and not something the Attic needs to include in its process. > my key concern is the new Social Media aspect: > IMHO, the Attic retirement lead needs to contact the retiring PMC to ask > if > there is any social media to take action on. > I've just done that. > and while at it propose them to participate to the other aspects of the > retirement > I've just done that > > WDYT? > +1 > (and we'll need to find how to update our instructions to keep them simple > but > also help future retirements) > One thing I did was scan through the private@jclouds mailing list and I found a Twitter/X.com account (and an AWS account) - so that might be something to put in the process? Niall > Regards, > > Hervé > > Le samedi 21 juin 2025, 11:19:17 CEST Niall Pemberton a écrit : > > I generated the jclouds YAML file using the retire.rb script (thanks > > Sebb!!). > > > > Although github had the changes and the asf-site & cwiki-retired branches > > were updated, the changes were not reflected in the website & no email > > notifications came to the commits list. I made a small change to > > the project-templates-layout.html which did result in an email > notification > > AND the website changes were then visible (so looks like the commit > adding > > the jclouds YAML was lost). > > > > project-templates-layout.html said "Inform Dev" but our process pages say > > "Inform Users" - so I've corrected the template. > > > > The users had been notified about the resolution submitted to the board, > so > > I adapted the template text and sent the following email in response to > > that notification to the jclouds user list: > > https://lists.apache.org/thread/7ft2411fk8tvf7vmyjn8smxgtjhm3nsh > > SInce this is the 1st retirement I've been involved with, I hope thats > OK, > > but let me know if something different should be done. > > > > A note on CSP issues: > > 1) Google Analytics were removed from the jclouds site in March 2025 - so > > not an issue > > 2) The only other CSP issues are Google Fonts - the website looks fine, > but > > there would need to be local copies of Google Fonts to remove that issue > > > > Niall > > > > >
