On 21/02/2022 22:15, Morag Brown wrote:
While I think most people on this mailing list can certainly share your frustrations with getting the toolflow to work, I think it's important to emphasize that this is an open collaboration that many contribute to without it strictly speaking being part of their critical work duties.
I certainly understand that and personally I have been trying to contribute by doing pull requests, trying to ask well formulated questions and sharing my successes and solutions. And I have done it outside of my work duties to support a project that I find important. So I have been there and done that.
As such, writing and maintaining documentation and testing toolflow functionality across all configurations of operating systems and software versions is difficult. However we do try our best at these things, and definitely try to help however we can whenever someone faces an issue that has either not been documented or even just not yet encountered by developers. The PRP stuff was presented at the 2021 CASPER conference, and has yet to make it's way into our docs. But as Jonathon has said, we do have a CASPER slack, with a PRP channel, and other channels where more help could potentially be found.
What I find very disturbing is that there seems to be a working solution that would have saved months of time and that is known to many but no-one cared to mention it before.
Is this a really an _open_ _collaboration_? Kaj -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/491ca6ed-b73d-cce9-f0c7-e1808b87d33b%40utu.fi.
