-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
[9.0] information_security_manual #97
Conversation
Information Security Management System Manual | ||
============================================= | ||
|
||
This module was written to provide an Information Security Manual Template. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This module provides an Information Security Manual Template.
7b1c597
to
b9130c9
Compare
b9130c9
to
f0c2698
Compare
👍 |
Contributors | ||
------------ | ||
|
||
* Odoo SA <info@odoo.com> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really?
1/ The module named should be prefixed with |
@dreispt |
You could use a shorter name; |
@dreispt I think infosec is bad for SEO and yes, you missed the content of the category which hasn't changed: |
I still still we should have the module area prefix. I'm sure you can come up with a shorter module name. |
@max3903 Since "infosec" is quite a specific keyword, what about |
…manual [REN] Rename module and fix formatting
@dreispt ping! |
👍 |
[9.0] information_security_manual
No description provided.