-
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
adding remarks from my side #7
Comments
Hey @jerch I strongly opt for number 1 too. Also, we can have a call (Hangouts, Discord, ...) to clear thoughts straight out, and then create/comment-to tickets for documentation or as a form of todo items. (this is how we often do communication in our EF team, to retain openess). EDIT: p.s.: forgot to mention, I didn't work on the draft last days due to xmas/health related duties. I will slowly increase my work speed though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Christian, just got through your draft. Thats a really good start, but as you might have guessed I have several remarks both regarding the technical aspects as well as for the writing. Now I wonder how to start/contribute my thoughts here?
Several options come to my mind:
What would you prefer? I would tend to 1. and 3. (as 2. would clutter the tex file), but it is up to you.
The text was updated successfully, but these errors were encountered: