Skip to content

Developer documentation overhaul#16561

Merged
pllim merged 52 commits into
astropy:mainfrom
taldcroft:doc-dev-quickstart
Jul 1, 2024
Merged

Developer documentation overhaul#16561
pllim merged 52 commits into
astropy:mainfrom
taldcroft:doc-dev-quickstart

Conversation

@taldcroft

@taldcroft taldcroft commented Jun 14, 2024

Copy link
Copy Markdown
Member

Description

This pull request is to make the developer documentation more accessible to newcomers and more useable by maintainers. The current docs contain a lot of information but are not well-organized and contain a lot of repetition.

It reflects an approach that sometimes "less is more", so some material was cut (notably detailed documentation on how to use two virtualenv managers), but for the most part it keeps all substantive material while cutting repetitions.

There are a lot of commits and most of them are useless individually, so this should definitely be squash-merged. There are a couple of commits that could be controversial and are meaningful.

Fixes #11621

See also:

  • By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

  • Do the proposed changes actually accomplish desired goals?
  • Do the proposed changes follow the Astropy coding guidelines?
  • Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
  • Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
  • Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
  • Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
  • Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
  • Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
  • At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

@github-actions

Copy link
Copy Markdown
Contributor

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

@neutrinoceros

Copy link
Copy Markdown
Contributor

Is there an issue for this??

I found two related issues:

@pllim pllim added this to the v7.0.0 milestone Jun 14, 2024
@taldcroft

Copy link
Copy Markdown
Member Author

RTD is now passing so you can look at the new docs.

@hamogu

hamogu commented Jun 14, 2024

Copy link
Copy Markdown
Member

I can't put a comment on it because this line is not yet changed, but I would also do away with astropy.test in favor of recommending to run pytest directly (https://github.com/astropy/astropy/pull/16561/files#diff-3082c98617b79c67603d9ef61bad41ef94d24d19a948af26eb52ca8ace968a97L368). Keep it simple by recommending one and only one way of doing it and we have #16208 open to remove astropy.test() anyway.

@taldcroft

Copy link
Copy Markdown
Member Author

I can't put a comment on it because this line is not yet changed, but I would also do away with astropy.test in favor of recommending to run pytest directly

I had not appreciated this was technically possible for an installed package. But definitely 👍 on removing astropy.test() from the docs, will do (in coordination with #16208).

@mhvk mhvk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@taldcroft - so far, I've just gone over the new quickstart guide - which I like very much! But of course some comments (mostly small).

Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst

@eerovaher eerovaher left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a look at the text that is present, I didn't think too much about what is missing but should be included.

Comment thread docs/development/index.rst Outdated
Comment thread docs/development/index.rst
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/testguide.rst Outdated
Comment thread docs/development/testguide.rst Outdated
Comment thread docs/development/testguide.rst
Comment thread docs/development/testguide.rst Outdated
Comment thread docs/development/testguide.rst
@taldcroft

Copy link
Copy Markdown
Member Author

Thanks for the comments folks! I got through many but not all of them, but I'll keep on plugging (hopefully over the next few days).

@taldcroft taldcroft force-pushed the doc-dev-quickstart branch from a624a4c to 1a590aa Compare June 21, 2024 19:25
@taldcroft taldcroft marked this pull request as ready for review June 21, 2024 19:25
@taldcroft taldcroft requested review from eerovaher, hamogu and mhvk June 21, 2024 19:38
@taldcroft

Copy link
Copy Markdown
Member Author

All -- I think that I have addressed or at least responded to every comment. I think this is in good enough shape now that I have made it a Pull Request (not draft).

@neutrinoceros

Copy link
Copy Markdown
Contributor

I'm going to review this today. For now, I just want to put a note that #16601 revealed an oversight in our dev docs. Fetching tags is necessary to first build and test astropy locally, and the information is there, but isn't presented as something you should do from the get go when you're getting started. Maybe you've already addressed this point (in which case I'll come back and hide this reply), but I wanted to make sure we addressed it too as part of the overhaul.

@neutrinoceros neutrinoceros left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some general level questions:

  1. why were some files from docs/development/workflow moved, but not all ?
  2. why replacing git checkout with git switch everywhere ? (this is a genuine question, I learned git before git switch was a thing and never really bothered migrating my muscle memory)

Comment thread docs/development/quickstart.rst
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst
Comment thread docs/development/quickstart.rst
Comment thread docs/development/quickstart.rst
Comment thread docs/development/maintainers/maintaining.rst Outdated
Comment thread docs/development/maintainers/maintaining.rst Outdated
Comment thread docs/development/maintainers/maintaining.rst Outdated
Comment thread docs/development/maintainers/maintaining.rst Outdated
Comment thread docs/development/maintainers/maintaining.rst Outdated
@pllim

This comment was marked as resolved.

@taldcroft taldcroft force-pushed the doc-dev-quickstart branch from 3621a4a to 33d8966 Compare June 25, 2024 16:56
@taldcroft

Copy link
Copy Markdown
Member Author

@pllim - rebased!

@dhomeier dhomeier left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for undertaking this, this should point new contributors to a much clearer path!
I just had time for reading through the quickstart and core workflow sections, only a few suggestions for potential improvements.

Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst Outdated
Comment thread docs/development/quickstart.rst Outdated

@pllim pllim left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here is the rest of my review. Since you said contents update largely is out of scope, I focused only on the stuff not inside development this time.

Comment thread docs/index.rst
index_getting_started
index_user_docs
index_dev
development/index

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there was a reason why we made the index at top level (index_dev) vs development/index but I don't remember why now. @saimn , do you remember?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just going to xref #14867 here in case we need to revert this particular change in the future.

Comment thread docs/development/index.rst
Comment thread docs/install.rst Outdated
Comment thread docs/install.rst
Comment thread docs/known_issues.rst
Comment thread docs/whatsnew/7.0.rst
@taldcroft

Copy link
Copy Markdown
Member Author

OK, I think I have addressed all review comments. There are some other PR's being blocked by this, so maybe it is time to merge this and start fresh with any other minor cleanups?

@taldcroft

Copy link
Copy Markdown
Member Author

@pllim - are you OK with merging now? I see 👍 from a few others that have reviewed.

@pllim

pllim commented Jul 1, 2024

Copy link
Copy Markdown
Member

There is an edited comment from @dhomeier saying that git switch is experimental at #16561 (comment) . Should we be recommending experimental Git command?

@pllim

pllim commented Jul 1, 2024

Copy link
Copy Markdown
Member

devdeps failures are unrelated.

@taldcroft

Copy link
Copy Markdown
Member Author

There is an edited comment from @dhomeier saying that git switch is experimental at #16561 (comment) . Should we be recommending experimental Git command?

Git switch was released in 2.23 almost 5 years ago. I'm not sure why they have not removed the "experimental" comment, but I don't think it is credible that they would now drop or make big changes to git switch.

@pllim

pllim commented Jul 1, 2024

Copy link
Copy Markdown
Member

Oh... ok then. Are you okay with "Squash and Merge"? 🚀

@taldcroft

Copy link
Copy Markdown
Member Author

Oh... ok then. Are you okay with "Squash and Merge"? 🚀

For sure squash and merge. There is no value in all the intermediate commits and LOTS of churn!

@pllim pllim merged commit 875b80c into astropy:main Jul 1, 2024
@pllim

pllim commented Jul 1, 2024

Copy link
Copy Markdown
Member

Done. Thanks!!!

@mhvk

mhvk commented Jul 2, 2024

Copy link
Copy Markdown
Contributor

Thanks! So nice to have clearer devdocs!!

d-giles referenced this pull request in d-giles/astropy-abdufork Jul 26, 2024
* Remove coding guide info for emacs

* Add a copy of pandas development docs

* Add pandas-based development docs to index

* Remove a codespell false positive

* Remove {{header}} from pd-based docs

* Replace pandas with astropy

* Touch-ups on contributing.rst

* Bring the pandas files into the main dev dir

* Remove contributing different ways (superseded)

* Remove non-applicable pandas content

* Update git_edit_workflow_examples

* Put tox into dev_all

* Remove pandas contributing codebase

* More tweaks to testing guide

* First pass at the documentation guide

* Remove pandas contributing_documentation

* Remove pandas doc files part duex

* Move git_resources out of workflow

* Make one quickstart doc

* Move the remaining bits from workflow dir

* Remove building and virtual_pythons docs

* Change target links to anonymous

* Remove doc refs to `astropy.test()`; replace w/ pytest

* Respond to review comments

* Apply suggestions from code review

Co-authored-by: Eero Vaher <eero.vaher@gmail.com>

* Address more review comments

* More comments; use git switch in non-maintainer docs

* Fix typo in git switch command

* Apply suggestions from code review

Co-authored-by: Clément Robert <cr52@protonmail.com>
Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com>

* More updates and review comments

* Add What's New and changelog entries

* Update docs/development/quickstart.rst

Co-authored-by: Derek Homeier <709020+dhomeier@users.noreply.github.com>

* Address more review comments

* Move is_development statement for clarity

* Other various updated related to dev docs

---------

Co-authored-by: Eero Vaher <eero.vaher@gmail.com>
Co-authored-by: Clément Robert <cr52@protonmail.com>
Co-authored-by: P. L. Lim <2090236+pllim@users.noreply.github.com>
Co-authored-by: Derek Homeier <709020+dhomeier@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Development docs reorganization

8 participants