You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
open individual issues for the technical aspects to be dicussed before writing things down?
comment inline in the tex file?
comment/review with a c&p PR with github's own tooling?
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:
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.
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: