At this stage, I propose we set a policy of not doing detailed reports to the Quarto issue tracker when we have problems with Quarto - on the basis that we will likely waste both their time and ours. Let's therefore set a policy of noting the problems, and working around them. So, we put up an issue here on our tracker, with the problem, and record the workaround. We can also do searches on the Quarto issue tracker and cross-reference in case our experience is useful to them.
This is a proposal for a policy in dealing with Quarto build errors or features we would like.
Up until now, we (well I) have been careful to report bugs on the Quarto issue tracker.
However, the last few reports have been vexatious, for the Quarto team, and for me - especially https://github.com/quarto-dev/quarto-cli/issues/7291 .
At this stage, I propose we set a policy of not doing detailed reports to the Quarto issue tracker when we have problems with Quarto - on the basis that we will likely waste both their time and ours. Let's therefore set a policy of noting the problems, and working around them. So, we put up an issue here on our tracker, with the problem, and record the workaround. We can also do searches on the Quarto issue tracker and cross-reference in case our experience is useful to them.
Any thoughts?