>> Unfortunately for our project we could use only managed code. And
>> that means that current implementation is not really fit our needs.
>> We are thinking about porting C++ code to C#.
No objections license-wise, however...
> If you fork the code, then all the maintenance burden for the fork
> falls on you. As future feature enhancements and bug fixes
> (including security problems!) come along, you will have to do all
> the work of recreating them in your fork.
>
> Are you ready to commit to such a thing? Or will your product fall
> further behind over time, vis-à-vis the original thing?
... these are valid concerns.
Werner
_______________________________________________
Freetype mailing list
Freetype@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
