I think what we'll want to do is create a branch in our repo that is specifically for the website (they recommend "asf-site" as the branch. This assumes the new site can be compiled into static files via buildbot / Jenkins, if not we probably have to pre-process so that what is committed to git is what can go through buildbot/Jenkins or is already static.
I'm not familiar with the new site or how it's built, but if that all works, we should create that branch (or someone can create a PR and one of the committers can merge it) and then we should open a ticket with infrastructure team to finalize the configuration. I can help with merging a PR, or opening the ticket with infra if someone can get it to that stage -----Original Message----- From: Laimonas Simutis <[email protected]> Sent: Friday, January 18, 2019 6:09 AM To: [email protected] Subject: Re: New website - steps to get this launched This seems to have some good info: https://www.apache.org/dev/project-site I should have time to review and get back with more info in case no one else gets to it first. It seems that it's a matter of generating static files and placing it in the appropriate location in the repo so that apache servers can pick it up. Some of the trickier bits like downloads cgi, we can point to nuget for beta and the old downloads.cgi page for older bits until we get that straightened out. We can worry automating this as we go, let's get the site updated with manual generation if we have to and iterate on that. Shannon, once I setup my lucene env and reorient with the docs and repo migration that just happened, I can merge your PR. I just want to make sure we got the git locations right after the migration. Laimonas On Fri, Jan 18, 2019, 06:41 Shannon Deminick <[email protected] wrote: > Happy to host anywhere, only thing is that we need to follow the > Apache rules and from what I read it needs to be done by them unless > anyone knows differently? > > On Fri., 18 Jan. 2019, 20:50 George Kinsman <[email protected] > wrote: > > > Hi, any reason a simple GitHub pages wouldn't work? > > > > It's a static site built with Hugo so it just outputs html at the > > end of the day. It would then be linkable from the GitHub repo at > > lucenenet.github.io. It also means that changes to the site could be > > automatically published via GitHub action. > > > > Get Outlook for Android<https://aka.ms/ghei36> > > > > ________________________________ > > From: Itamar Syn-Hershko <[email protected]> > > Sent: Friday, January 18, 2019 8:21:46 AM > > To: [email protected] > > Subject: Re: New website - steps to get this launched > > > > Hi, I will gladly host the website on our cloud infra until all that > Apache > > infra is figured out > > > > On Fri, Jan 18, 2019, 2:06 AM Shannon Deminick <[email protected] > wrote: > > > > > Hi all, > > > > > > Revisiting this new website (and docs stuff) based on the last > > > thread > > > > > > > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist > s.apache.org%2Fthread.html%2F22c097a7c6eee169dfc80dbb1fc433c026b1806f8 > 25a599dcf426ed3%40%253Cdev.lucenenet.apache.org%253E&data=02%7C01% > 7C%7Cba9d6890dd854b430c4308d67d1e068f%7C84df9e7fe9f640afb435aaaaaaaaaa > aa%7C1%7C0%7C636833965245921546&sdata=H0pDk8xeImJTw1C9kN5eiPPxdxB1 > %2BwmVn%2FfxpJhBEyA%3D&reserved=0 > > > > > > Seems the consensus is to try to get this new site launched as a > > > start > to > > > try to promote a bit more development for this project. > > > > > > I've updated the GH PR with a task list for both the website and > > > docs including links, etc... : > > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > ub.com%2Fapache%2Flucenenet%2Fpull%2F206&data=02%7C01%7C%7Cba9d689 > 0dd854b430c4308d67d1e068f%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7 > C636833965245921546&sdata=ELEQ4H0CR3R54kAMxHAd8i08Y2AvkFiigYRBx53E > u5s%3D&reserved=0 > > > > > > (I should prob split the PR into 2 - one for website and one for > > > docs, > > but > > > can do that later) > > > > > > Most of the website tasks are very easy and is just filling in > > > content > > but > > > there are some interesting ones about hosting, branding, download > > > CGI > > page > > > (whether this is a strict requirement or not) > > > > > > Anyone have experience with the apache project site hosting, and > > > specifically using *gitpubsub* (since that seems to be the > > > simplest way > > to > > > host this) and how we can make the switch from what we have > > > currently > to > > > this new site? > > > > > > Anyone feel like figuring out what branding policies need to be > > > updated/fixed with the new site? > > > > > > Let me know if you have other comments about that task list > > > > > >
