On Sat, 5 Apr 2025 at 11:04, Niall Pemberton <niall.pember...@gmail.com> wrote: > > On Sat, 5 Apr 2025 at 09:17, sebb <seb...@gmail.com> wrote: > > > On Sat, 5 Apr 2025 at 00:30, Niall Pemberton <niall.pember...@gmail.com> > > wrote: > > > > > > On Fri, 4 Apr 2025 at 00:41, sebb <seb...@gmail.com> wrote: > > > > > > > On Fri, 4 Apr 2025 at 00:23, Niall Pemberton < > > niall.pember...@gmail.com> > > > > wrote: > > > > > > > > > > How do we proceed with getting write access to the project websites > > using > > > > > Git (for ATTIC-234 & ATTIC-235)? Should I create an Infra ticket for > > > > this? > > > > > > > > > > Once they are R-W, I can create PRs for the changes. > > > > > > > > I think Infra need to be involved. > > > > > > > > However, auth might be a problem; I suspect it is automatically > > > > generated from the repo name. > > > > If so, it would probably require creating the appropriate LDAP groups > > > > and populating them. > > > > > > > > [Whereas SVN auth can be assigned as needed, so is simple to do.] > > > > > > > > I suggest you explain what needs to be done to the repos in case Infra > > > > have a simpler way of achieving what is required. > > > > e.g. they may find it easier to apply patch files themselves. > > > > > > > > Of course if they can grant Attic PMC RW access, that would simplify > > > > matters. > > > > > > > > > > Sorry Sebb, only just saw this as it had been marked as spam (gmail told > > me > > > when I sent a reply to the original). Anyway, I've created INFRA-26723 > > > > No problem. > > > > Note that at least some of the sites have other references that fall > > foul of the CSP. > > Fonts and CSS etc. These are not mentioned in the Jira, but I think > > they should be fixed (where not too difficult) before the repos are > > made read-only again. For example aurora cannot load bootstrap.css and > > that causes layout issues. > > > > I have the changes ready for Aurora & Trafodion rendering issues > (see ATTIC-235). For the rest, the remaining CSP issues are: > > Apex (Twitter & Search) > Archiva (fonts, images,search & youtube) > Bahir (fonts, sortable.js) > Hawq (img, JIRA issue list) > Metron (fonts) > Streams (img, Twitter) > Trafodion (fonts) > Usergrid (fonts) > > I wasn't planning on fixing the font issues (or any other issues) since > that doesn't seem to affect how it looks much. WDYT?
If the repo is writable, and fixing the fonts etc is not difficult, then I think it should be done. That seems to me to be more useful to the end user than fixing analysis references that are anyway blocked by the CSP (and don't usually cause site issues). I am happy to do at least some of the fonts/js/css. > Niall > > > > > > > > > > > > > > > Niall > > > > > > > > > > > > > > > > > > > > > > > Thanks > > > > > > > > > > Niall > > > > > > > > > > Below is the list of repositories: > > > > > > > > > > apex-site > > > > > archiva-web-content > > > > > aurora-website > > > > > bahir-website > > > > > hawq-site > > > > > metron > > > > > mxnet-site > > > > > polygene-website > > > > > streams > > > > > trafodion-site > > > > > usergrid > > > > > >
