Hey, that's way cool! I have no experience on this, so can't comment on pitfalls (other than that I don't see any).

you might want to ask about ownership. It might or might not matter to you

I mean even if it's oss, right now you have full control on the repository (and its collaborators management)

not only that but also about what you do with potential contributions : ex an employee of the member org could one day push to get a feature you really don't want included, I suppose you need to think about these cases

Those are valid points, thanks! I am pretty sure that ownership will be with the company, if it is the official library. They have a good track record of integrating other libraries, e.g. C# and Go, which also started out as independent libs. I believe the maintainer of the C# lib joined them full time, and the creator of the Go lib still makes contributions to it. The OSS decisions they made in the last months all seemed reasonable to me, and I know they have employees who worked with Clojure in the past (and I suspect the suggestion to move the Clojure lib over came from one of them)

It depends also if you’re handing over or if you still plan to work on this.

And if you ever want to get paid for OSS work

Finally the optics of a solo dev working on it vs a company

> it takes the maintenance-pressure off of me How come? Is it part of the agreement somehow?

Did you discuss any kind of sponsership from the company for your work going forward? I think that would be in order, if the ownership is going to them.

I don’t plan to get paid for the work. My main goal for this wrapper was to make it easier to use this library in Clojure (also for our company, we use it heavily). Currently I am the solo maintainer, but the API is “finished” as long as the Java version does not provide heaps of new methods, and they don’t plan that right now. Every 3-4 months I update the transient dependencies, run the integration- and regressiontests in the pipeline and push a new version to Clojars, that’s about it. If they take ownership of the library, I can still contribute as an Open Source contributor, but of course I cannot decide on my own what goes in, what does not. On the other hand, I don’t have to do the upgrades and don’t have to make sure that it is on par with the features of the Java library, the responsibility switches over to them. People who are interested in using the lib from Clojure can then use the official wrapper and trust the source, and on their official website everything will be mentioned, so devs will find the library quicker. It just seems like the Clojure devs would benefit from this decision, which would be enough for me.

Makes sense!

If they want ownership, they should buy it from you Depending on the exact license, they may need permission from all past contributors to relicense It should also be clear that if ownership is transferred you are no longer accountable for the library, "this program is provided as is" etc

oh, that's a good idea!

🍻 but imagine clinking coffee cups instead.

it's coffee o'clock somewhere in the world!

Let's celebrate that... With a cup of coffee.

Is that a particular fractal in your profile pic, btw?

I think I wrote it in python about a decade ago. I don't think I still have the code.

It's probably not distantly related to a Julia set.

Thought it looked a bit Juliaish 🤓

Yeah, it has threefold symmetry though, which makes me unsure...

I like to plot fractals when I learn a new language - its a great way to get to grips with some of the fundamentals of a language while also exploring their graphics library(ies) a bit.

That's a nice approach! Did you do any with Clojure?

I have, although it's from a time before I changed my name: https://youtu.be/zP1qStsGlFE

Thanks! I’ll have to look when I get the chance and learn something 🤓 I dabble in generative art.

oh nice. me too. do you have any examples you care to share?

Sure. Here's a couple

I mean, I'm mostly exploring techniques, still, so it's not very "deep" art-wise. On the contrary, most of what I've done feels very shallow, in my own opinion. Needs a splash of recursion 😄

What’re you doing?

I really like the second and third of those.

Those are great!

The flowery one has a lovely composition to it, colorwise and patternwise.

I find the flowy line segments one very interesting visually as well as from a technical perspective. I’m not very well versed in efficient collision detection that I assume you must be employing here. Also, I wonder if you get consistently interesting output when it comes to the longer lines; in particular, the ones that loop back pique my curiosity, as someone who’s mainly used Perlin noise to control directional flow.

I dig the second and third of mine as well. I've done many renderings of variations of that algorithm. Here are a couple more

Finally getting around to watching your presentation. I loved the Henon Attractor joke, that came out of left field 😄