On Wed, Jan 19, 2022 at 9:12 AM Gavin McDonald <gmcdon...@apache.org> wrote:
> On 2022/01/18 01:00:39 Bob Harner wrote: > > I agree too, Gavin's option is very good news. > > > > Ok everyone, shall I consider this approved and close everything out ? > I vote +1 to that. We can figure out any potential future glitches later, and yet this is way better than converting the whole site to a different tool. > > > On Mon, Jan 17, 2022, 4:56 PM Thiago H. de Paula Figueiredo < > > thiag...@gmail.com> wrote: > > > > > On Fri, Jan 14, 2022 at 9:15 AM Ben Weidig <b...@netzgut.net> wrote: > > > > > > > Hi Gavin, > > > > > > > > > > Hello, Gavin and Ben! > > > > > > > > > > that sounds great, thanks for the help! > > > > > > > > > > Agreed! Thanks! > > > > > > > > > > I'm not in the position to decide alone if this is the way to go > forward. > > > > What do the others think? > > > > IMO it's the best solution for now. > > > > > > > > > > I agree. > > > > > > > > > > I've looked (a little bit) into Pelican and exporting Confluence > data, > > > and > > > > it looked like A LOT of manual work, including the recreation of the > > > > current design. > > > > > > > > If there's still a need to switch CMS in the future, switching > without > > > the > > > > upcoming deadline and with a finished website-template might be more > > > > sensible. > > > > > > > > > > 100% agreed. It would be an awful lot of work better spent elsewhere > since > > > we now have an option to keep the current setup which has been serving > us > > > well. > > > > > > > > > > > > > > Cheers, > > > > Ben > > > > > > > > On Fri, Jan 14, 2022 at 12:25 PM Gavin McDonald < > gmcdon...@apache.org> > > > > wrote: > > > > > > > > > > > > > > > > > > > On 2022/01/14 10:31:54 Gavin McDonald wrote: > > > > > > Hello All, > > > > > > > > > > > > I believe I have a working solution that means you may continue > to > > > > > publish as you always have via the Confluence Wiki! > > > > > > > > > > > > CXF, Sanuario and couple of other use the same method and we have > > > > > converted them over successfully. > > > > > > > > > > > > I have created a new config file for you [1] and tested it [2] > and it > > > > > works fine for you also. > > > > > > I have not yet enabled the commit step for publishing as I > wanted you > > > > > guys to check the output and approve it for use. > > > > > > > > > > > > Feel free to commit a minor change to your cwiki and check the > output > > > > of > > > > > the next build [3] which runs and 11 minutes past each hour. > > > > > > > > > > > > (I added a temporary 'svn st' step for you to compare the output > is > > > as > > > > > expected.) > > > > > > > > > > Changed 'svn st' to 'svn di' to make it actually useful > > > > > > > > > > Gav... > > > > > > > > > > > > > > > > > Let me know how you get on. > > > > > > > > > > > > HTH > > > > > > > > > > > > Gav... > > > > > > > > > > > > [1] - > > > > > > > > > > > > > https://svn.apache.org/repos/infra/infrastructure/buildbot2/projects/tapestry.py > > > > > > [2] - https://ci2.apache.org/#/builders/77/builds/361 > > > > > > [3] - https://ci2.apache.org/#/builders/77 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2022/01/13 18:29:34 "Thiago H. de Paula Figueiredo" wrote: > > > > > > > Hello, Ben! > > > > > > > > > > > > > > Have you been able to do the content conversion and import? I'm > > > > afraid > > > > > I > > > > > > > still need to write a bit of stuff for the 5.8.0 release. Once > > > that's > > > > > done, > > > > > > > I want to help you with the process. > > > > > > > > > > > > > > Cheers! > > > > > > > > > > > > > > On Fri, Dec 31, 2021 at 8:43 AM Ben Weidig <b...@netzgut.net> > > > wrote: > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > I've looked into the general problem, and it seems to be > that the > > > > > favored > > > > > > > > new way for a project website is the Pelican > > > static-site-generator > > > > > with > > > > > > > > buildbot. > > > > > > > > At least it's the one most mentioned: > > > > > > > > > > > > > > > > * https://infra.apache.org/project-site.html > > > > > > > > * > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS > > > > > > > > > > > > > > > > I've used Jekyll in the past and now Hugo for personal stuff. > > > > > > > > Most likely, there'll be some customizations needed, but in > the > > > > end, > > > > > it > > > > > > > > shouldn't matter what language is behind the SSG. > > > > > > > > > > > > > > > > > > > > > > > > So the first step would be deciding which software to use and > > > > > getting INFRA > > > > > > > > involved in setting it up. > > > > > > > > > > > > > > > > Next, building a template to reflect the Tapestry design. > > > > > > > > There's an ASF-template that could be used as a starting > point. > > > > > > > > > > > > > > > > https://infra.apache.org/asf-pelican.html > > > > > > > > > > > > > > > > > > > > > > > > I've exported the Confluence content as XML to look at the > data, > > > > and > > > > > it's a > > > > > > > > single XML file with ~ 1.5 million lines... > > > > > > > > Transferring it will be cumbersome, but hopefully, a > converter > > > can > > > > > be used, > > > > > > > > maybe something like > > > > > > > > > > > > > > > > > https://gist.github.com/grugnog/2e6ee420707a8196951956cf4dbf6e91 > > > > > > > > > > > > > > > > > > > > > > > > Another critical point is a stable URL structure, so Google > will > > > > > still have > > > > > > > > the same content with the same URL in its index. > > > > > > > > Hopefully, 301 rewrites can be done with htaccess files. > > > > > > > > > > > > > > > > I'll check out content conversion and import into a SSG in > the > > > > first > > > > > week > > > > > > > > of January. > > > > > > > > > > > > > > > > Cheers and a happy new year! > > > > > > > > Ben > > > > > > > > > > > > > > > > On Thu, Dec 30, 2021 at 5:02 PM Gavin McDonald < > > > > gmcdon...@apache.org > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Although the ticket quoted below was fixed, we still need > to > > > move > > > > > you > > > > > > > > away > > > > > > > > > from using the CMS - and that means migrating your job off > of > > > the > > > > > CMS > > > > > > > > Slave > > > > > > > > > at ci.apache.org, it means migrating you away from using > > > > > tapestry.conf > > > > > > > > > file and it means moving you away from using built in CMS > > > tooling > > > > > like > > > > > > > > > build_external.pl . > > > > > > > > > > > > > > > > > > I have created a new ticket > > > > > > > > > https://issues.apache.org/jira/browse/INFRA-22684 > > > > > > > > > > > > > > > > > > Do not ignore this email or the jira ticket, the CMS WILL > BE > > > > > TURNED OFF > > > > > > > > > January 31st so you must act now, so testing and > enhancements > > > can > > > > > happen. > > > > > > > > > > > > > > > > > > Gav... > > > > > > > > > > > > > > > > > > > > > > > > > > > On 2021/09/16 15:56:50 Gavin McDonald wrote: > > > > > > > > > > Hi All, > > > > > > > > > > > > > > > > > > > > As you should be aware by now, the CMS is deprecated and > > > going > > > > > away. > > > > > > > > > > You are one of the last remaining projects still using > the > > > CMS > > > > > (in part > > > > > > > > > anyway) > > > > > > > > > > to publish your website. > > > > > > > > > > > > > > > > > > > > An Infra ticket ( > > > > > https://issues.apache.org/jira/browse/INFRA-22208) > > > > > > > > was > > > > > > > > > opened as > > > > > > > > > > your site no longer publishes. We will not be 'fixing' > the > > > > > problem that > > > > > > > > > currently exists > > > > > > > > > > but rather we want to get you off of the CMS and > publishing > > > > > using a > > > > > > > > > different method. > > > > > > > > > > > > > > > > > > > > Please liaise on the existing ticket above and we'll > help get > > > > you > > > > > > > > there. > > > > > > > > > > > > > > > > > > > > Thanks > > > > > > > > > > > > > > > > > > > > Gavin McDonald (ASF Infra) > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > To unsubscribe, e-mail: > dev-unsubscr...@tapestry.apache.org > > > > > > > > > > For additional commands, e-mail: > > > dev-h...@tapestry.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > To unsubscribe, e-mail: > dev-unsubscr...@tapestry.apache.org > > > > > > > > > For additional commands, e-mail: > dev-h...@tapestry.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Thiago > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > > > > > > For additional commands, e-mail: dev-h...@tapestry.apache.org > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > > > > > For additional commands, e-mail: dev-h...@tapestry.apache.org > > > > > > > > > > > > > > > > > > > > > > > -- > > > Thiago > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > -- Thiago
