You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/08/24 17:17:18 UTC
[GitHub] [pulsar-site] tisonkun opened a new issue, #175: Remove all content before sync
tisonkun opened a new issue, #175:
URL: https://github.com/apache/pulsar-site/issues/175
@urfreespace @Anonymitaet Otherwise, we can suffer from some files deleted from upstream but still remain in this repo.
--
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: dev-unsubscribe@pulsar.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] Anonymitaet commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
Anonymitaet commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1255708849
@tisonkun
Suggest keeping all docs in the `Pulsar` repo, there was a similar discussion showing the benefits of this way.
https://lists.apache.org/thread/mf2xwntfgn84dq78ksqv22jk3drq6xb3
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
tisonkun commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1233636692
@urfreespace please reopen this issue. This issue is aimed at improving the sync workflow. The two related issues are manually workaround this issue.
I may have time to work on this issue this month. Or if you think we can postpone this work, please close as not plan - it is just not completed yet, anyway.
--
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: dev-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
michaeljmarshall commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1255754133
> If I get it right, in the mail thread linked your preference is keeping the "current" (unreleased) document in the main repo?
I think it is helpful to keep docs that are manually maintained in the apache/pulsar repo. Once a version is no longer supported, I don't think we need those docs in the apache/pulsar repo since the version itself is not getting updated.
> Keep released versioned document, especially still retain those like "version-2.1.0-incubating", "version-2.1.1-incubating" really help?
I support removing these docs from the apache/pulsar repo, and probably from the website, but I am not sure. One of my biggest problems with the old docs is that I still get served them by search engines above more recent docs. We definitely want users to find recent documentation.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
tisonkun commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1233759385
Since docs are versioned, it should not be a big deal. If we'd like to retain the link, we set up a redirection.
--
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: dev-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
tisonkun commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1233759015
@michaeljmarshall then it's an issue about the source of truth. If we retain those content, how can we remove it from the main repo?
The original purpose of this issue is to avoid dangling content under `docs` folder, I may narrow the scope there, though.
--
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: dev-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun closed issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
tisonkun closed issue #175: Remove all content before sync
URL: https://github.com/apache/pulsar-site/issues/175
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
michaeljmarshall commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1233756878
I think this kind of change will break certain links that I left in place a couple months ago. For example, many of the SNAPSHOT links here https://pulsar.apache.org/api/client/ will go away. I think it is fine to get rid of them if we are ready to do it, but I was slightly worried that users would have saved links to those endpoints, so I didn't remove them.
--
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: dev-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
tisonkun commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1255758382
> that are manually maintained
Good point. I will come up with a proposal to describe this topic in details. It's actually coupled with how we perform patch releases and how to maintain those versioned docs.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] urfreespace closed issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
urfreespace closed issue #175: Remove all content before sync
URL: https://github.com/apache/pulsar-site/issues/175
--
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: dev-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
tisonkun commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1255728679
@Anonymitaet Thanks for your information.
@michaeljmarshall If I get it right, in the mail thread linked your preference is keeping the "current" (unreleased) document in the main repo? Keep released versioned document, especially still retain those like "version-2.1.0-incubating", "version-2.1.1-incubating" really help?
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] tisonkun commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
tisonkun commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1255165828
Closed. I'm going to propose a solution by retaining only the unreleased document on the main repo.
--
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: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [pulsar-site] michaeljmarshall commented on issue #175: Remove all content before sync
Posted by GitBox <gi...@apache.org>.
michaeljmarshall commented on issue #175:
URL: https://github.com/apache/pulsar-site/issues/175#issuecomment-1233763774
That is a fair point about the source of truth. Maybe we just need to have a landing page? In the case of the API docs, the old content wasn't even based on released versions of Pulsar, so its value is questionable, anyway.
--
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: dev-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org