[3dprinter-general] Bug#742704: ImplicitCad in Debian

[Christopher Olah]

Hey Bas,

Presently, I no longer maintain ImplicitCAD. I've been pretty poor
about handling this. I put it out temporarily to work on some other
stuff and ended up getting pulled away. Now I work full time on
machine learning research. I just don't have the cycles to keep
another project in my head anymore. :/

In any case, right now there's no upstream for ImplicitCAD. I've
spoken to a few people who were interested in taking over maintenance,
but they haven't ended up doing so.

ImplicitCAD, unfortunately, has a bunch of rough corners. Mostly,
these deal with the computational costs of rendering objects at high
resolutions and rendering issues at low resolutions.

If you're interested, I'll try and pull together remaining interest in
ImplicitCAD and see if we can find a new maintainer. It'll need to
wait until after the NIPS submission deadline, though.

All the best,

Chris

On Fri, May 23, 2014 at 5:03 PM, Bas Wijnen <wijnen at debian.org> wrote:
> Hi,
>
> Someone requested that ImplicitCad be included in Debian.  I'd be the one doing
> that, and after checking it out, I must say I'm rather excited about it.  This
> has (almost ;-) [1]) all the features that I've been missing in OpenScad.
> However, there is a minor issue, which I hope you can help with:
>
> I don't know Haskell.  This means I would make sure the package builds right
> and that bug reports are handled (which means fixing the packaging or passing
> them to you); Debian's Haskell team has offered to help with the Haskell part,
> but they don't want to take over from you.
>
> So what it means is that we need you to continue responding to bug reports and
> fixing things when needed.  I really don't know how much work that is; I guess
> you know better.
>
> Normally I would just assume that you would do this, but it's been some time
> since you last pushed any changes to github, so I'm slightly worried that you
> may have abandoned the project.
>
> Can you please let me know the status?
>
> Thanks,
> Bas
>
> [1] The one feature which is not in either of them, as far as I could see, is
> the 3-D variant of "polygon offsetting": growing or shrinking an object.