Perhaps they should ask Copilot how their templating system works.

My line of business is entirely a Microsoft shop so everything we’ve ever written has been for MSSQL.

That being said, I can understand the benefits of having a choice in backend. For example, for our Zabbix deployment some engineer just installed mariadb+zabbix on a server and called it a day. This has caused us no end of troubles (ibdata misconfigured, undo files too small, etc). After the last time I had to rebuild it due to undo file corruption I swore that if it broke again I was switching to postgres. So far knocks on wood we haven’t had any major issues. We’re still looking into and planning for a postgres migration but we’re hoping to hold out for a little longer prep time.

Maybe I should contribute a MSSQL engine for Zabbix so I can move it to a platform I’m more comfortable with. ;)

IANAL, but this is likely a legal gray area regarding software licenses, especially if you read the AGPL code prior to writing your library. Companies that do this sort of thing professionally have a/b teams that don’t speak to each other (one reads and generates design documents, the other uses those design documents to write a new library) to prevent a lawsuit for violating licensing terms. They can claim that the developers writing the library didn’t copy any code from the source library.

As for the typedef, it’s most likely considered a public definition document. I would think it would be like a public C# interface, where it’s only the method declarations and expected parameters and the actual implementation is not included at all.

If you’re considering publishing this or using it commercially you should definitely consult a lawyer that specializes in copyright.

One of my system engineers started using TFS a few weeks ago. All he knows how to do is click Sync Changes in vscode and call me if there’s a problem.