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

Get feedback from participants from onboarding / application : https://github.com/baloise-incubator/ #257

Open
1 of 5 tasks
MarkusTiede opened this issue Aug 27, 2020 · 11 comments
Assignees
Labels
contribute https://baloise.github.io/open-source/docs/md/goals/uplift.html#contribute help-wanted impediment If this is not done it blocks uplifting

Comments

@MarkusTiede
Copy link
Member

MarkusTiede commented Aug 27, 2020

From

@MarkusTiede MarkusTiede self-assigned this Aug 27, 2020
@MarkusTiede MarkusTiede added impediment If this is not done it blocks uplifting contribute https://baloise.github.io/open-source/docs/md/goals/uplift.html#contribute labels Aug 27, 2020
@MarkusTiede MarkusTiede changed the title Get feedback from Arthur from first onboarding / application : https://github.com/baloise-incubator/org/pull/9 Get feedback from first participants from onboarding / application : https://github.com/baloise-incubator/ Sep 4, 2020
@ArthurNeudeck
Copy link

The agreement is quite extensive and I was wondering whether we might shorten it: the longer the less it will be read.

@ArthurNeudeck
Copy link

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)".

@ArthurNeudeck
Copy link

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?

@ArthurNeudeck
Copy link

We might add ArchUnit in the template to avoid referencing internal infrastructure?

@ArthurNeudeck
Copy link

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.

@ArthurNeudeck
Copy link

Chapter 4.1: a brief description of roles would be nice

@ArthurNeudeck
Copy link

Figure 4: I guess the license name is missing in the caption

@ArthurNeudeck
Copy link

Chapter 1.1; could not really get heading vs contents ;)

@ArthurNeudeck
Copy link

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).

@ArthurNeudeck
Copy link

Chapter 2: do you really have to repeat "open source" in any title? I guess that is what the whole document is about.

@ArthurNeudeck
Copy link

Conclusion: i like the contents of the document very much - or even better: the attitude it provides.
I asked myself whether it must be in a "list of guidelines" style or it might be a more process oriented way: you want to start open source? Here is what you need to do, what you need to take into concern, and who may assist you.
But: Definitely something I can and will sign and follow. Good work!

@MarkusTiede MarkusTiede changed the title Get feedback from first participants from onboarding / application : https://github.com/baloise-incubator/ Get feedback from participants from onboarding / application : https://github.com/baloise-incubator/ Feb 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribute https://baloise.github.io/open-source/docs/md/goals/uplift.html#contribute help-wanted impediment If this is not done it blocks uplifting
Projects
None yet
Development

No branches or pull requests

2 participants