Ma77Ball commented on PR #5000:
URL: https://github.com/apache/texera/pull/5000#issuecomment-4419458575

   @Yicong-Huang here is a report to help with the review of what is included 
in the docs: 
   
   
   # Wiki sync status all 23 pages
   
   Comparison between 
[`apache/texera.wiki`](https://github.com/apache/texera/wiki) and the `docs/` 
folder in this PR.
   
   Legend: ✅ in PR (present under `docs/`) · ❌ not in PR (with reason)
   
   ## ✅ In the PR (18)
   
   | # | Wiki page | Location in `docs/` |
   |---|---|---|
   | 1 | `Apache-License-header.md` | 
`contribution-guidelines/apache-license-header.md` |
   | 2 | 
`Build,-Run-and-Configure-micro‐services-in-local-development-environment.md` | 
`contribution-guidelines/micro-services-local-dev.md` |
   | 3 | `Create-Dataset,-upload-data-to-it-and-use-it-in-Workflow.md` | 
`tutorials/create-dataset-upload-data.md` |
   | 4 | `Guide-for-Developers.md` | 
`contribution-guidelines/guide-for-developers.md` |
   | 5 | `Guide-for-how-to-use-Texera.md` | 
`tutorials/guide-for-how-to-use-texera.md` |
   | 6 | `Guide-to-enable-the-LLM‐based-Texera-agent.md` | 
`tutorials/guide-to-enable-llm-agent.md` |
   | 7 | `Guide-to-Frontend-Development-(new-gui).md` | 
`contribution-guidelines/guide-to-frontend-development.md` |
   | 8 | `Guide-to-Implement-a-Java-Native-Operator.md` | 
`contribution-guidelines/guide-to-implement-java-operator.md` |
   | 9 | 
`Guide-to-Implement-a-Python-Native-Operator-(converting-from-a-Python-UDF).md` 
| `contribution-guidelines/guide-to-implement-python-operator.md` |
   | 10 | 
`Guide-to-launch-Lakekeeper-as-the-RESTCatalog-Service-for-Texera's-workflow-result-storage.md`
 | `tutorials/guide-to-launch-lakekeeper.md` |
   | 11 | `Guide-to-Use-a-Python-UDF.md` | 
`tutorials/guide-to-use-python-udf.md` |
   | 12 | `How-to-run-Texera-on-local-Kubernetes.md` | 
`getting-started/run-on-kubernetes.md` |
   | 13 | `Installing-Apache-Texera-using-Docker.md` | 
`getting-started/installing-using-docker.md` (updated this pass: added 
`ANTHROPIC_API_KEY` section + `--profile examples` in 
uninstall/troubleshooting) |
   | 14 | `Install-Texera.md` | `getting-started/install-texera.md` |
   | 15 | `Making-Contributions.md` | 
`contribution-guidelines/making-contributions.md` |
   | 16 | `Migrate-a-Jupyter-Notebook-to-a-Texera-Workflow.md` | 
`tutorials/migrate-jupyter-notebook.md` |
   | 17 | `Past-GUI-screenshots.md` | `getting-started/past-gui-screenshots.md` 
**(added this pass)** |
   | 18 | `[VOTE]-Release-Apache-Texera-(incubating)-Email-Template.md` | 
`contribution-guidelines/release-email-template.md` |
   
   ## ❌ Not in the PR (5)
   
   | # | Wiki page | Reason |
   |---|---|---|
   | 19 | `Installing-Texera-on-a-Single-Node.md` | Wiki file is 0 bytes empty 
placeholder, nothing to port. |
   | 20 | `temporary‐install‐using‐docker‐compose.md` | Overlaps with 
`installing-using-docker.md`. Unique bits (LLM API key, `--profile examples`) 
merged into entry #13 above. |
   | 21 | `Home.md` | GitHub wiki landing/link-hub page. Hugo builds the site 
landing from `_index.md` + `overview.md`, so a `Home.md` would be redundant. |
   | 22 | 
[`Deploying-Texera-on-Amazon-Web-Services(AWS).md`](https://github.com/apache/texera/wiki/Deploying-Texera-on-Amazon-Web-Services%28AWS%29)
 | Cloud-deployment guide. Still in development on the wiki; initially excluded 
from the diff for testing reasons. Defer porting until the wiki version is 
finalized. |
   | 23 | 
[`Deploying-Texera-on-Google-Cloud-Platform-(GCP).md`](https://github.com/apache/texera/wiki/Deploying-Texera-on-Google-Cloud-Platform-%28GCP%29)
 | Cloud-deployment guide. Still in development on the wiki; initially excluded 
from the diff for testing reasons. Defer porting until the wiki version is 
finalized. |
   
   ## Totals
   
   | Bucket | Count |
   |---|---|
   | Wiki pages compared | 23 |
   | ✅ In PR | 18 |
   | ❌ Not in PR (with reason) | 5 |


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to