Julia port #1299
Replies: 4 comments
-
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. |
Beta Was this translation helpful? Give feedback.
-
This is a great idea. We welcome community contributions in the Timefold ecosystem, such extensions, tools, connectors, clients and ports to other programming languages too. Our internal discussion was purely around the use of the Timefold brand - as we want to avoid brand reputation harm if code we don't maintain has issues. With that in mind, we would like to ask you to use "TimefoldX" instead of "Timefold" to clearly make the distinction. Especially in benchmarks that distinction is important.
Yes
Please use timefoldx.jl instead.
Timefold-solver is Apache License. The easiest is to reuse that.
Yes
Not a problem, as long as you clearly mention at the start that it's a port of timefold with a link.
It' a lot of work, but it's fun :) |
Beta Was this translation helpful? Give feedback.
-
Note that there is also a C sharp port of Timefold by a community user, by @fredjekrueger : Maybe he knows a bit more about the pitfalls |
Beta Was this translation helpful? Give feedback.
-
Thanks for the support! I'll let you know when I have the first version (within a few months probably). |
Beta Was this translation helpful? Give feedback.
-
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.
Timefold.jl
or are there some legal implications?What's your idea? Should I continue this endeavour?
Beta Was this translation helpful? Give feedback.
All reactions