-
Notifications
You must be signed in to change notification settings - Fork 2
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
Get feedback from participants from onboarding / application : https://github.com/baloise-incubator/ #257
Comments
The agreement is quite extensive and I was wondering whether we might shorten it: the longer the less it will be read. |
The document has many links/ URLs/ references: reading it always forces you to either follow a link or keep on reading. I guess I would prefer for internal links a separate "(see chapter , )" and for external links (see <external reference)". |
Explanations and demands are cool - I was actually wondering, whether some checks can be done automatically such as "no passwords/ secrets" or avoiding "personal/ personalized data" being plugged in as hooks? |
We might add ArchUnit in the template to avoid referencing internal infrastructure? |
I got the impression that some topics are redundant in the document such as "get a review". I would rather leave it at one central location, i.e. where we describe the process. |
Chapter 4.1: a brief description of roles would be nice |
Figure 4: I guess the license name is missing in the caption |
Chapter 1.1; could not really get heading vs contents ;) |
As far as I can remember there does exist a certain set of rules for headings in English (i.e. most words start with a capital letter). |
Chapter 2: do you really have to repeat "open source" in any title? I guess that is what the whole document is about. |
Conclusion: i like the contents of the document very much - or even better: the attitude it provides. |
From
The text was updated successfully, but these errors were encountered: