Hi Nikolaus, > > There are so many Cambridge debating society tricks in your response I > > don't know where to start :) > > Starting your response like that is impolite and implies an assumption > of bad faith. It just makes me read the rest of your message with more > scepticism.
What is polite depends on your cultural background, at least as long as you are not cursing or attacking somebody personally, but just sticking to commenting on the topic or what was written in the message you respond to. In my culture being frank and stating your true opinion is considered honest and polite, while omitting relevant facts is considered not just impolite, but borderline lying, especially if knowledge of those facts likely changes how people view the whole original argument. What Sean did argumenting that using the new Git-Tag-Info by other tools than tag2upload is explicitly forbidden by Debian Policy, without sharing that he wrote that section himself and published a new Policy version putting it into effect the very same day is in my culture very impolite. My comment was to express that I feel that Ian is doing similar tricks, but at a rate and a level of sophistication that piercing through the arguments becomes way more challenging. I already got some private emails from people who agree they see the same pattern, so even though I didn't pinpoint everything others can see what is happening. > > Debian is actually one of the few distros that is attempting to have > > workflows based on importing upstream git repos. Debian currently has > > two competing popular systems for doing this: git-buildpackage and > > dgit. > > This statement reveals, even for a casual observer like me, such a > fundamental misunderstanding that, in my opinion, it disqualifies you > from this discussion. Which of the two points above you feel is not true and you would like to have evidence on? The fact that Debian is one of the few in trying to import full upstream git histories, or that dgit and git-buildpackage are the main tools in Debian for it? I have been researching, documenting and enhancing packaging workflows long enough that I think I understand them pretty well both across different package types and teams inside Debian, as well as outside Debian in various Linux distros, Homebrew and many more. If you are asking for evidence to substantiate something I am happy to provide, but I would prefer to focus effort only on aspects that are disputed and actually need more evidence.
