FWIW, I wouldn't consider pd-iem a fork, either. IMO, adding a bunch of plugins doesn't qualify as a fork. I think a better word would be "distro". Actually, that's how the project describes itself:

"is a Pure Data libraries distribution for plain Pure Data (Pd-vanilla), focussed on (but not limited to) IEM libraries."

Of course, there is no universal definition of "fork" and lots of grey areas with great potential for infinite bike shedding.

On 10/6/21 2:33 AM, Alexandre Torres Porres wrote:

Em ter., 5 de out. de 2021 às 19:12, IOhannes m zmölnig <zmoelnig@iem.at>
escreveu:

so what's you definition of a "fork"?

A modification of the source code to reflect different features. If I

but the "pd-iem" has all kinds of different features, e.g. you do do image processing and matrix processing and what not.
it doesn't change the source code of the implementation of `osc~` though (but iirc, neither did DesireData, Pd-Devel or PurrData).

so where does "modification of the source code" start?
how is modifying a line of code in a git-repository different from monkey-patching interpreted functions at runtime?
what's the role of dynamic extensions ("externals") in this context?

mgfdrs
IOhannes

_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list