Re: website migration
Hi Rick, thanks for reviewing. I fixed the link you mentioned. Til On 24/01/2022 19:22, Rick Hillegas wrote: Moving this discussion to the general list, as Craig recommended. Thanks for doing all of this work, Til. I have checked out and built the top level db site according to your instructions. I manually followed all of the links but did not exhaustively try out the mailing list subscriptions. I only reviewed the site for the internal consistency of the links. I did not review any of the content for correctness--that seems to be outside the scope and deadline of this effort. I found only one issue: On db-site/target/site/communication.html : The third paragraph mentions a "[Mailing List](mail.html)" page. That link needs to be filled in. Perhaps a pointer to db-site/target/site/mail.html Thanks, -Rick On 1/20/22 12:13 PM, Tilmann wrote: Hi Rick, yes, the link is wrong, I fixed it. (I copied it from the original website, where it is also wrong, it seems the apache.org/foundation section has changed). If you want to preview the website it is best if you follow the instructions in the README.md (I updated them a bit): * check out the repository to a local workspace * run "mvn clean compile" * browse the html files created locally in target/site/index.html Best, Til On 19/01/2022 18:49, Bouschen, Michael wrote: Hi Rick, just my 0.02$ Thanks, Craig. I started reviewing the website source at https://github.com/apache/db-site/blob/main/src/main/asciidoc/index.adoc I was not able to get very far. o Under "Apache Software Foundation", the "license" link takes the user to a "Not Found The requested URL was not found on this server." page. I think this link points to the wrong site https://www.apache.org/foundation/license-FAQ.html, it should be https://www.apache.org/licenses/ instead. o Under "More Information", the "DB Project Guidelines", "DB Subproject Proposals", and "Contacting Us" links are all dead. That is, they take the user to github-generated 404 errors. These links point to generated html sites of the corresponding adoc sources, e.g. https://github.com/apache/db-site/blob/main/src/main/asciidoc/guidelines.html for "DB Project Guidelines". These links do not work with the adoc sources. Once the site is shipped the link is correct. If you want to see it within github just replace ".html" by ".adoc" in the url of the browser window showing the 404 error, then it show the corresponding adoc source. Regards Michael Is it premature to review the website source? I don't know how to proceed with the proofreading task. Thanks, -Rick On 1/18/22 10:57 AM, Craig Russell wrote: Here you go: https://github.com/apache/db-site Craig On Jan 18, 2022, at 9:57 AM, Rick Hillegas wrote: Thanks, Til. I don't normally use github. Can you give us the full url to the github site? On 1/17/22 12:09 PM, Tilmann wrote: On 17/01/2022 19:39, Rick Hillegas wrote: If I understand Gavin's 2022-01-06 comment on https://issues.apache.org/jira/browse/INFRA-21381, he has volunteered to "svn mv" all generated website output from https://svn.apache.org/repos/infra/websites/production/db to https://svn.apache.org/repos/infra/sites In the meantime, Til has volunteered to convert the parent db site content into a markdown format, whose pages can then be checked into a github repository. This port to markdown was a spur of the moment thing. Also, people may prefer the old html look over the new style. I don't mind, just let me know of the old version is preferred. For now, I checked everything in into apache/db-site on GitHub. To look at the new site follow the instructions in the beginning of the README. What remains to be done? The following occur to me: 1) Individual db projects need to update their processes so that generated website output is checked into Gavin's target svn repo at https://svn.apache.org/repos/infra/sites rather than into https://svn.apache.org/repos/infra/websites/production/db Gavin doesn't need to worry about this piece and each project can tackle the task whenever it makes sense to them. 2) Some processes need to be documented for how we will edit Til's markdown in the future and generate/checkin the production website from the edited markdown. 3) Some proof-reading of Til's markdown will be needed. In particular, we will need to make sure that links point into pages under https://svn.apache.org/repos/infra/site I can do (1) for Derby. I can also help out with the proof-reading. What else needs to be done? I put some more items into the README in apache/db-site. It basically relates to getting the settings right and the builds triggered/working. I am not quite sure what the settings need to be. Also, we need to decide on mailing lists where we send notifications. Cheers, Til Thanks, -Rick On 1/16/22 10:57 PM, Gavin McDonald wrote: On 2022/01/16 16:57:49 Tilmann wrote: Hi, I am not sure about the mailing list, I couldn't see a [email protected]
Re: website migration
Moving this discussion to the general list, as Craig recommended. Thanks for doing all of this work, Til. I have checked out and built the top level db site according to your instructions. I manually followed all of the links but did not exhaustively try out the mailing list subscriptions. I only reviewed the site for the internal consistency of the links. I did not review any of the content for correctness--that seems to be outside the scope and deadline of this effort. I found only one issue: On db-site/target/site/communication.html : The third paragraph mentions a "[Mailing List](mail.html)" page. That link needs to be filled in. Perhaps a pointer to db-site/target/site/mail.html Thanks, -Rick On 1/20/22 12:13 PM, Tilmann wrote: Hi Rick, yes, the link is wrong, I fixed it. (I copied it from the original website, where it is also wrong, it seems the apache.org/foundation section has changed). If you want to preview the website it is best if you follow the instructions in the README.md (I updated them a bit): * check out the repository to a local workspace * run "mvn clean compile" * browse the html files created locally in target/site/index.html Best, Til On 19/01/2022 18:49, Bouschen, Michael wrote: Hi Rick, just my 0.02$ Thanks, Craig. I started reviewing the website source at https://github.com/apache/db-site/blob/main/src/main/asciidoc/index.adoc I was not able to get very far. o Under "Apache Software Foundation", the "license" link takes the user to a "Not Found The requested URL was not found on this server." page. I think this link points to the wrong site https://www.apache.org/foundation/license-FAQ.html, it should be https://www.apache.org/licenses/ instead. o Under "More Information", the "DB Project Guidelines", "DB Subproject Proposals", and "Contacting Us" links are all dead. That is, they take the user to github-generated 404 errors. These links point to generated html sites of the corresponding adoc sources, e.g. https://github.com/apache/db-site/blob/main/src/main/asciidoc/guidelines.html for "DB Project Guidelines". These links do not work with the adoc sources. Once the site is shipped the link is correct. If you want to see it within github just replace ".html" by ".adoc" in the url of the browser window showing the 404 error, then it show the corresponding adoc source. Regards Michael Is it premature to review the website source? I don't know how to proceed with the proofreading task. Thanks, -Rick On 1/18/22 10:57 AM, Craig Russell wrote: Here you go: https://github.com/apache/db-site Craig On Jan 18, 2022, at 9:57 AM, Rick Hillegas wrote: Thanks, Til. I don't normally use github. Can you give us the full url to the github site? On 1/17/22 12:09 PM, Tilmann wrote: On 17/01/2022 19:39, Rick Hillegas wrote: If I understand Gavin's 2022-01-06 comment on https://issues.apache.org/jira/browse/INFRA-21381, he has volunteered to "svn mv" all generated website output from https://svn.apache.org/repos/infra/websites/production/db to https://svn.apache.org/repos/infra/sites In the meantime, Til has volunteered to convert the parent db site content into a markdown format, whose pages can then be checked into a github repository. This port to markdown was a spur of the moment thing. Also, people may prefer the old html look over the new style. I don't mind, just let me know of the old version is preferred. For now, I checked everything in into apache/db-site on GitHub. To look at the new site follow the instructions in the beginning of the README. What remains to be done? The following occur to me: 1) Individual db projects need to update their processes so that generated website output is checked into Gavin's target svn repo at https://svn.apache.org/repos/infra/sites rather than into https://svn.apache.org/repos/infra/websites/production/db Gavin doesn't need to worry about this piece and each project can tackle the task whenever it makes sense to them. 2) Some processes need to be documented for how we will edit Til's markdown in the future and generate/checkin the production website from the edited markdown. 3) Some proof-reading of Til's markdown will be needed. In particular, we will need to make sure that links point into pages under https://svn.apache.org/repos/infra/site I can do (1) for Derby. I can also help out with the proof-reading. What else needs to be done? I put some more items into the README in apache/db-site. It basically relates to getting the settings right and the builds triggered/working. I am not quite sure what the settings need to be. Also, we need to decide on mailing lists where we send notifications. Cheers, Til Thanks, -Rick On 1/16/22 10:57 PM, Gavin McDonald wrote: On 2022/01/16 16:57:49 Tilmann wrote: Hi, I am not sure about the mailing list, I couldn't see a [email protected] or similar...? I started migrating the website to GitHub. The idea is to use the same approach/
