Christian Buhtz

In relation to #85 I'm not well experienced packaging *big* projects but *small* ones. In #85 you also stated that you are not well experienced with packaing. Because of that...

I would say this is against "torrent netiquete". This is a feature that shouldn't be implemented. But this is just my opinion. Can you please describe more detailed a use-case...

Sorry, this doesn't answer my question which was "what the difference is between dirty and clean whitespaces". I have understand how your package treat that two types of whitespaces. But...

> f the whitespace is already clean, then the whitespace is considered to be clean. If the whitespace is not already clean, then it is considered to be dirty. But...

IMHO the problem with this Issue is that it is to "meta". It describe multiple problems and approaches. The problems and working packages should be atomized and described in separate...

> There is a single problem in this issue: Provide a better interface for editing flags That is a wish or goal not a "problem". You really should do more...

Thanks for explaining. You should mention in your documents what Angular is. Not all readers know it. Just use the term "the example project Angular" instead of just "Angular". I...

Not sure if this is a "Good First Issue" because it needs a lot of internal and deeper knowledge about the development process. > * a centralized entry point for...

OK. Also see the need for improvement of the docu but don't have a concrete solution in mind. Most of my modifications of the docu comes from my own use...

The "user-callback" script docu will be integrated in the manual (see #1659) if our docu migrated to MkDocs (PR #1738). The rest of the "docu" you list in your initial...