Skip to content

Move reporting a vulnerability documentation to contact page - #14610

Merged
codelipenghui merged 1 commit into
apache:masterfrom
michaeljmarshall:fix-security-docs
Mar 12, 2022
Merged

Move reporting a vulnerability documentation to contact page#14610
codelipenghui merged 1 commit into
apache:masterfrom
michaeljmarshall:fix-security-docs

Conversation

@michaeljmarshall

Copy link
Copy Markdown
Member

Motivation

The context for this PR is on the mailing list here: https://lists.apache.org/thread/l2hp7tq5fr0r1v4pg0lvkbxtqtwo81pq

Modifications

  • Move the reporting a vulnerability information to the "contact" pages.

Verifying this change

I was able to verify the changes for the old website, but not the new website (site2/website-next).

Does this pull request potentially affect one of the following parts:

This is only a documentation update.

Documentation

  • doc

This is an update to the docs.

@michaeljmarshall michaeljmarshall added the doc Your PR contains doc changes, no matter whether the changes are in markdown or code files. label Mar 8, 2022
@michaeljmarshall michaeljmarshall added this to the 2.11.0 milestone Mar 8, 2022
@michaeljmarshall michaeljmarshall self-assigned this Mar 8, 2022
@Anonymitaet

Copy link
Copy Markdown
Member

Hi @michaeljmarshall thanks for your contribution.

As I replied in ML, it makes more sense to place this info to https://pulsar-next.staged.apache.org/community#how-to-contribute, the original file is https://github.com/apache/pulsar-site/blob/main/site2/website-next/src/pages/community.js (@urfreespace please correct me if I'm wrong)

image

@michaeljmarshall

Copy link
Copy Markdown
Member Author

As I replied in ML, it makes more sense to place this info to https://pulsar-next.staged.apache.org/community#how-to-contribute, the original file is https://github.com/apache/pulsar-site/blob/main/site2/website-next/src/pages/community.js (@urfreespace please correct me if I'm wrong)

Hi @Anonymitaet, I replied to that thread on the mailing list noting that many of the sources you cited had the reporting a vulnerability information in the contact info, which was right next to the contributing info on those websites. Are we planning to drop the "contact" page for the new website? If so, that's fine. How long will we keep the old website? This PR does not affect the new website.

@michaeljmarshall

Copy link
Copy Markdown
Member Author

I removed the website-next updates since that directory was recently removed.

@codelipenghui
codelipenghui merged commit ce901d4 into apache:master Mar 12, 2022
@Anonymitaet

Anonymitaet commented Mar 15, 2022

Copy link
Copy Markdown
Member

Hi @michaeljmarshall
Thanks for your contribution. The changes in this PR are shown on the current Pulsar website (https://pulsar.apache.org/en/contact/).

For the new Pulsar website, could you please copy your changes to https://github.com/apache/pulsar-site/blob/main/site2/website-next/src/pages/community.js#L224 since we have a new design for the new Pulsar website, so that your changes will be shown on https://pulsar-next.staged.apache.org/community/#community, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc Your PR contains doc changes, no matter whether the changes are in markdown or code files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants