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

What do we really want in the README #2

Open
hmpf opened this issue Dec 7, 2022 · 1 comment
Open

What do we really want in the README #2

hmpf opened this issue Dec 7, 2022 · 1 comment

Comments

@hmpf
Copy link
Contributor

hmpf commented Dec 7, 2022

As is, the README is a good starting point, and we can start using the plugin without polishing it further. However, since it also is the only real place to document the plugin (docs/ would be overkill I feel) and it feels a bit too short and sweet I'll write down what I think would make it better, especially when we have a few more plugins in place.

  • Maybe a pointer to argus-server's docs about ticket plugins, and especially the list of other plugins, when we have that list!
  • Badges! Everything is better with badges. Makes the project look more mature than it is ;)
  • Mention that the settings talked about is the instance specific Django settings file
  • How to install
  • How to test
  • File-hierarchy and some comments pointing out the important bits, to make it easier for developers making their own plugins to understand what they need to focus on, for instance the requirements-*-files are generated by tox!

All of this should eventually go in the cookiecutter of course. And there should probably be a link to the cookiecutter, again, to make it easier for plugin-developers.

@hmpf
Copy link
Contributor Author

hmpf commented Dec 7, 2022

Ouah, we must also mention which RT version this is for as RT has changed quite a bit through the years. Once upon a time it only worked via email.

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

No branches or pull requests

1 participant