falktx @falktx@mastodon.falktx.com

@unfa @hoergen @LuKaRo @be not everyone has enough leverage to do that. when you are in a real need of a job, you take whatever is available. it is a risky move, as companies will assume you dont care about them but are only there to "pass time working" until your real work comes. which is true most often than not, but it is something they do not like to be said out loud..

@hoergen @be you can still request for this to NOT be on the contract, which was exactly my case.

for reference, it was https://berlin.bewatec.com/about
you can still see me in some of those pics 😂

@unfa long-term it is cheaper too. so win-win :)

@be @LuKaRo @unfa It is worse when companies require this when employees work on FLOSS stuff outside of working hours. Some (as was the case of someone I know recently) do not even allow you to work on FLOSS while working for them... 😡

I am glad that I do not have to deal with any of this, would be infuriating otherwise. On my previous job I asked for 1 day free per week to do FLOSS development, they were quite okay with it. And now, well, the development is 99% in the open anyway :D

@unfa that is understandable.

FYI https://opensource.google.com/docs/patching/#common-rules has details on the whole subject.

A lot of FLOSS developers dislike google, and it is not just because their are a Advertising/Data-Collection company that happens to make products to spread their business.

@unfa please dont bump tickets that are now closed and discussed ended many months ago, that is not okay.

PS: I deleted the comment you just made

@LuKaRo @be @unfa every time I have seen google employees submit patches to stuff I maintain, it always comes with the caveat that the google name needs to be in the authors list (even though it is a company, not the real author)
see https://github.com/jackaudio/jack2/pull/348

you both are making good points, I am just very cautious when it comes to google stuff.

google has a terrible history when it comes to maintaining stuff https://killedbygoogle.com/

@unfa seems like the usual google thinking/acting like they own the place.

@unfa maybe phantomjs?

Yet another one of those monthly reports.
https://kx.studio/News/?action=view&url=kxstudio-monthly-report-january-2021

@be oh haha, no worries. I thought something was off.

In any case, related to what you said, I have cached builds too, not just the plugins but the libraries.
I used buildroot before, so took many design patterns from there.

A full rebuild takes around 1h (including plugins). Adding or updating a library will only build that specific library, same for plugins.

I am used to building stuff due to work on the kxstudio repos and use buildroot for my job. Your help is appreciated but all is fine.

@be why are you saying all these things to me? I am confused...

@schratze you need the dev builds, available in https://www.landoleet.org/

Initial/experimental LV2 just landed in latest reaper dev build, nice to finally see LV2 in a commercial DAW 😮 🎉

@be sounds good. the lv2 plugin already works as-is afaik, so it is really just making that part of the build process.
ping me when it gets merged, and I will quickly add it to PawPaw then.

@be the rubberband cmake one. https://github.com/breakfastquay/rubberband/pull/18

@be yeah, would be best if the project supported building it. is your cmake PR getting merged soon? if not, I can always hack around a quick makefile

@be that is amazing, nice work!

let me know if you need any plugin in particular, I will add it to PawPaw.