Hi

The use of tools to assist developers is growing and will
continue to grow. Its not going away.
And what one can and cannot do with these tools will evolve

I dont think i understand the thought process behind this policy.
Licenses need to be complied to, code needs to be of good quality.

If a tool can help with that, you use it, if not you dont.
If you dont know, you try.

I think we should ensure that (static copies) of our bug tracker,
mailing list archieve and git repository are accessible to these tools.
Otherwise we will see more
* ddos by the tools trying to bypass restrictions
    [you know, the developer saying "search this",
     the tool replying with "its behind anubis",
     the developer asking "what can i do?"
     teh tool producing a script that ddos us becuase
     "bypassing restrictions" directs teh LLM to mallicious
     scripts, thats just the context in which "bypassing restrictions" occurs]

* code generators incorporating code from outside that is incompatibly licensed
    If a code generator can see all our code it should preferably use it
    if it can see none of it, it will use forums and random bits of code
    off the internet. Not all of which is LGPL compatible
    so again, IMHO if you are afraid of license issues the very first thing to
    do is ensure our code and coding docs are accessible to the tools
    generating code

* generally tools being less usefull as they have less ffmpeg specific
  context

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Whats the most studid thing your enemy could do ? Blow himself up
Whats the most studid thing you could do ? Give up your rights and
freedom because your enemy blew himself up.