Julia port

[LaurentMeesseman]

Hi,

I started working on a pure Julia port of Timefold as an educational excercise, but I realized it may be more valuable if I would (ultimately) publish it. However, despite several years of hobby level programming experience, I've never coded beyond my own computer and I'm a complete noob regarding GitHub and in particular licensing and other "repo netiquette".

My idea is to have a functionally near-perfect port of Java (including the good, the bad and the ugly; of course excluding the Enterprise functionality) but using Julia primitives and targeting the Julia ecosystem. I would maintain the port myself, in my spare time. I believe that restricting myself to just copying the Java functionality will be sufficient to keep the maintenance feasible.
Given that it's a complete, pure Julia port (as opposed to your Python port) and given that you wouldn't have the capacity to take responsibility for maintenance (I suppose), I would create a new repo rather creating a PR to this repo.

Assuming you would support the idea of a Julia port, I still have some questions.

• I suppose creating a new repo would be better suited than forking your repo, is that correct?
• Can I just call the package Timefold.jl or are there some legal implications?
• How should I draft the license?
• How should I draft the readme file? Can/should I just shortly present that it's a Julia port and refer to your GitHub repo and your website for more information? Should I avoid copying too much from your docs to avoid giving the false impression that it's managed by you, or is that as such not a problem?
• Any other pitfalls I should be aware of?

What's your idea? Should I continue this endeavour?

[triceo]

Hi @LaurentMeesseman!

Your request is unusual, and I appreciate you bringing it to us first. We'll discuss it internally and get back to you - please understand that it may take us a little while to reach conclusions, as this is a situation we never really considered and we don't yet have a position on.