You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I clearly defined that the design docs which are not yet implemented shouldn't be visible on the docs page (or only on a separated page) (thanks @eyanghwx)
I clarified that we would like to be compatible with the existing practices (creating PDF with any method or create a wiki page should be accaptable) but I suggested to create a reference page with a summary and link. I think it addresses the possible formatting issues (thanks @arp7, what do you think about this approach?)
TL;DR:
Create a new jira + a new page under the docs/content/design folder for each new design docs
Either include the content of the design in the markdown file (recommended as it can be commented line by line) or include the link (to Apache Jira attachment or Apache Wiki)
…e subproject (apache#950)
* HDDS-1659. Define the process to add proposal/design docs to the Ozone subproject
* Remove Site improvements to display proposals
* adding license header
* clarify the support of the existing method
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We think that it would be more effective to collect all the design docs in one place and make it easier to review them by the community.
We propose to follow an approach where the proposals are committed to the hadoop-hdds/docs project and the review can be the same as a review of a PR
See: https://issues.apache.org/jira/browse/HDDS-1659