Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs cleanup #1279

Closed
1 of 3 tasks
Adirio opened this issue Jan 3, 2020 · 12 comments · Fixed by #1499
Closed
1 of 3 tasks

Docs cleanup #1279

Adirio opened this issue Jan 3, 2020 · 12 comments · Fixed by #1499
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@Adirio
Copy link
Contributor

Adirio commented Jan 3, 2020

The book needs to be cleaned up.

  • The files are not completely up-to-date and the tutorial should be followed step by step and checking the differences in the code as tracked in Review tutorial to ensure that it has not outdated code #1251
  • Is the folder /docs/book/src/migration/testdata being used for anything? It should be removed if it isn't. Why should we have a testdata folder that is the one used by the golden script inside one of the book chapters?
  • Several files related to the old documentation like migration from v0, gifs, or some files that look like the utils used for previous versions of the documentation before moving to the new book format are still found in this directory

/kind cleanup

@Adirio Adirio added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 3, 2020
@k8s-ci-robot k8s-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jan 3, 2020
@DirectXMan12
Copy link
Contributor

/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@DirectXMan12:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jan 7, 2020
@vnzongzna
Copy link

Hi, I would like to work on it.
/assign

@Adirio
Copy link
Contributor Author

Adirio commented Jan 8, 2020

@vaibhavk the first point should be pretty straightforward. Just follow the tutorial in a new project and doccument the differences in the file.

Second point requires to verify that the testdata directory is not used for anything, and remove it.

Third would require deep undestanding of the whole book creation process.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 7, 2020
@Adirio
Copy link
Contributor Author

Adirio commented Apr 22, 2020

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 22, 2020
@camilamacedo86
Copy link
Member

camilamacedo86 commented May 7, 2020

Hi @Adirio,

Following a few comments inline.

The files are not completely up-to-date and the tutorial should be followed step by step and checking the differences in the code as tracked in #1251

It shows a duplicate of #1251 so I think that can be removed from the scope of this issue. I mean the repo has another issue already to address the same. Also, the PR: https://github.com/kubernetes-sigs/kubebuilder/pull/1492/files probably address it.

Is the folder /docs/book/src/migration/testdata being used for anything? It should be removed if it isn't. Why should we have a testdata folder that is the one used by the golden script inside one of the book chapters?

The /docs/book/src/migration/testdata is used just in the migration guide to help users move forward from V1 to V2. Since V1 was deprecated to long and has no longer supported I think we could keep the migration guide to still having the info but remove the examples/testdata.

Several files related to the old documentation like migration from v0, gifs, or some files that look like the utils used for previous versions of the documentation before moving to the new book format are still found in this directory

I think the above would solve this one as well. WDYT?

@camilamacedo86
Copy link
Member

/assign @camilamacedo86

@Adirio
Copy link
Contributor Author

Adirio commented May 13, 2020

I listed them to remember we need to do it but I don't have enough knowledge of the inner workins of how the documentation is generated to really know if those files are being used somewhere or they aren't.

You are saying that the testdata folder is being used for something so I would say we should keep it as long as we keep the migration guide (as you can see, that point was a question because I didn't know if it was being used or not). So, IMHO, we should remove that point from the list here and not remove the testdata folder until we remove the migration guide (if we ever do that).

@camilamacedo86
Copy link
Member

camilamacedo86 commented May 13, 2020

HI @Adirio,

Sorry, may I could not clarify properly my thoughts. Following some comments

Regards 1th Item

Regards 2th Item

PS.: IMO we should not migrate to the migration guide. We can create new ones when/if is required. It is a doc that should exist with its steps as history. We just do not need to keep /docs/book/src/migration/testdata because it is not really adding value to the info, also v1 is deprecated/not supported and currently removed and no longer it would be updated. I mean the /docs/book/src/migration/testdata is not required for users to migrate their projects and follow up the steps at all.

Regards 3th Item

  • I understand that the 3th item of this list also could be solved with the above solution.

@Adirio
Copy link
Contributor Author

Adirio commented May 13, 2020

Yeah, I understood you correctly. What I mean is, if we have the migration guide (v1->v2) we keep the corresponding testdata folder, if we remove that guide we remove the folder.

And yes, the first point is tracked in another Issue, this is just a list of things that were needed. Things can be removed or marked as done once they get resolved.

@camilamacedo86
Copy link
Member

added all detailed reasons why in POV is quite safe to delete the example of a V1 project that is just used in the migration guide from V1 to V2 in the PR: #1499 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants