On 21/07/2017 22:28, Scott Kostyshak wrote:
I support the suggestion to create such a document and suppose to make it
a section in "Development.lyx":
+ bundled with other project policies and developer documentation
+ write access for all developers
+ we can use LyX's version control for to-be-reviewed parts and diverging
opinions/comments
+1
Development.lyx does not have a rigorous structure. If anyone is
interested in writing something more formal, when we can at reference
that file from within Development.lyx.
I support the idea as well, and I'm interested in contributing to it.
As a starting point for the needauth stuff, I had put a recap of the problem
and motivations within this TT:
http://www.lyx.org/trac/ticket/10481
and, just as a reminder, the shell-escape was one of the mentioned use-cases,
albeit not the very one under my hands at that moment.
I'd suggest not to create a .lyx document, but rather start from a wiki page
under
https://wiki.lyx.org/Devel/Devel
with a recap of the current status and exchanged ideas, and pointers to the
Trac TTs tracking TODOs which we agreed upon.
My2c,
T.
