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

Please expand the README.md #2730

Open
pvalena opened this issue Mar 4, 2024 · 5 comments
Open

Please expand the README.md #2730

pvalena opened this issue Mar 4, 2024 · 5 comments
Labels
code | no functional change "No Functional Change" intended. Patch should not change tmt's behavior in any way. code | trivial A simple patch - a couple of lines, an easy-to-understand change, a typo fix. documentation Improvements or additions to documentation good first issue Good for newcomers

Comments

@pvalena
Copy link
Collaborator

pvalena commented Mar 4, 2024

Please, at least add quick howto like Install (or links to it). And/Or a short example for usage (not a big block of text like there is).

This is quite usual (and welcoming) for upstream projects to have this in the README.md :).

@pvalena pvalena added documentation Improvements or additions to documentation code | no functional change "No Functional Change" intended. Patch should not change tmt's behavior in any way. code | trivial A simple patch - a couple of lines, an easy-to-understand change, a typo fix. good first issue Good for newcomers labels Mar 4, 2024
@BDFL669
Copy link

BDFL669 commented Mar 4, 2024

I'd be happy to help with this issue. Please assign it to me

@pvalena
Copy link
Collaborator Author

pvalena commented Mar 4, 2024

Glad to hear that! Please wait for the repo maintainers/owners to agree some changes are needed :).

@BDFL669
Copy link

BDFL669 commented Mar 4, 2024 via email

@LecrisUT
Copy link
Contributor

LecrisUT commented Mar 6, 2024

Worth considering:

  • Move the README content into docs/overview #2414 The contents of the README were moved recently to better support sphinx-specific decorators. But having a more shortened tl;dr version of that as a front-page is worth reconsidering
  • synchronization of README.md with index.md (example, see usage of <!-- SPHINX-START -->)
  • Badges? Many cool ones from https://shields.io/badges
  • What to include? Best discussed with the main developers, but some things I think would be nice
    • Purpose and goal of tmt. I view it as a tool to unify testing independent of CI environment
    • One simple test.fmf with the cli interface to trigger/CI environments that run it
    • Where to get in touch
    • Primary sponsors?

Anyway let's wait for more feedback from @lukaszachy @psss @thrix? Happy to review though.

@psss
Copy link
Collaborator

psss commented Mar 7, 2024

Yes, the original README content was moved because it has grown substantially and it did not make sense to maintain similar information on several places. I like the idea of providing a tldr version on the most essential commands. Perhaps, we could resolve this issue together with this one?

The same content could be submitted to the tldr command repository. Plus, in the README we could include a link to the installation instructions to help users get quickly started?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code | no functional change "No Functional Change" intended. Patch should not change tmt's behavior in any way. code | trivial A simple patch - a couple of lines, an easy-to-understand change, a typo fix. documentation Improvements or additions to documentation good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants