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

Improve package readme #290

Open
thompson-tomo opened this issue Mar 29, 2024 · 1 comment · May be fixed by #291
Open

Improve package readme #290

thompson-tomo opened this issue Mar 29, 2024 · 1 comment · May be fixed by #291

Comments

@thompson-tomo
Copy link
Contributor

Summary

I wish for the base nuget package to have a more informative readme.

Details

The base nuget package should be using the same readme as the repo to make it as easy as possible for a user to get started with the package.

thompson-tomo added a commit to thompson-tomo/sdk-csharp that referenced this issue Mar 29, 2024
Signed-off-by: James Thompson <thompson.tomo@outlook.com>
@thompson-tomo thompson-tomo linked a pull request Mar 29, 2024 that will close this issue
@jskeet
Copy link
Contributor

jskeet commented Apr 2, 2024

I disagree with the premise here. I think a website readme and a package readme have different purposes. I can agree with the summary in this issue, but not the details.

I view a package readme as something which should:

  • Give enough information for the user to decide whether or not this is a useful package for them
  • Tell them where to find more information

A lot of the README doc at the moment really isn't aimed at the average NuGet consumer - it's about governance of CloudEvents etc.

I think we should have a dedicated NuGet-specific README instead, with:

  • A succinct summary of the package
  • A single example (and we'll need to think about how to choose that)
  • A link to the user guide
  • A link to the repo root

I think that would be more useful to a NuGet consumer than the current full README.

In an ideal world, we'd have a different example and summary for each package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants