Hi all,
Here's a quick recap of what I think are the essential bits of this
conversation:

- I've been at Luma for 14 years and I can safely say it's doing better
than ever (We're currently looking for TDs in LA and Melbourne, so go to
our site and apply).
- In the event that an earthquake destroyed Luma LA, and a brush fire took
out Luma Melbourne, PyMEL is open source, and there are a lot of capable
people out there who use and love it and would maintain it.
- Warranties aren't really a thing in the software game, because no one
wants to be sued for what a user *perceives* as failure.
- PyMEL has a BSD license, which is the most permissive open source
license.  There are absolutely no legal repercussions to using it.  It
doesn't matter if you use it to make truckloads of money or to cure cancer.
- We address outstanding issues and pull requests prior to every Maya
release, so there's a good rhythm to our releases, but there's no ground-up
rewrite on the way, because, frankly, it does what it aims to do pretty
damn well already.  If you want PyMEL performance to improve, be sure to
let Autodesk know that you'd like them to add the necessary hooks to avoid
converting objects to and from strings when working with maya.cmds.  Or use
C++.
- I find these conversations about executives kind of funny, because would
you rather have your issue go to Autodesk support or to us and the rest of
the PyMEL community?  Worst case scenario, you fix it yourself, which is
something that can't be said for the internals of Maya or their
menagerie of plugins.


chad.



On Tue, Jun 14, 2016 at 9:01 AM Paul Molodowitch <elron...@gmail.com> wrote:

> Oops - just noticed I had started to write that as a flat response, then
> decided to reformat it as an in-line response to quotes... and apparently
> forgot to delete the bit I wrote to start!  Apologies for the confusion /
> poor editing!
>
> ...and before any conspiracy theories get started - the hanging "we would
> love to have..." statement was going to read, "we would love to have a
> wider base of core contributors", but I dropped it when I rewrote
> because... well, what open source project wouldn't, and it didn't really
> add any useful information to the discussion.
>
> On Tue, Jun 14, 2016 at 8:53 AM Paul Molodowitch <elron...@gmail.com>
> wrote:
>
>> Well, if it makes anyone feel better, Luma is doing quite well at the
>> moment, and won't be going anywhere anytime soon!
>>
>> Having said that, though... we would love to have
>>
>>> It’s as much of a risk as it is depending on anything open source, I
>>> suppose…
>>>
>>> Sounds reasonable! But honestly I was thinking less about maintenance
>>> and such but more on legal consequences, guarantees etc….like some sort of
>>> (perceived)
>>> warranty you might be having with an *official* API !?….don’t know for
>>> what and how, but it seems like basic business logic to operate the thing
>>> you bought for lots
>>> of money according to manufactorer’s instructions to not lose any
>>> warranties/arguments!?​
>>>
>>  Not really sure what you're hoping for here. As far as I'm aware of,
>> Maya usage itself comes with no legal guarantees, so Pymel is no different
>> there.
>>
>> will continue to be maintained as long as Luma exists and is using Maya
>>>>>
>>>>> ..I hope this is not true. Studios come and go and studios find new
>>>>> solutions to solve their needs every day. When Luma goes something pops up
>>>>> to replace their need for Maya, I’d expect a set of volunteers to step in
>>>>> and continue to maintain it and provide updates.
>>>>>
>>>>> If not, then I’d worry.
>>>>>
>>>> Perhaps I should have said, "for at LEAST as long as".  On that note,
>> though - it may make people feel more comfortable to know that Luma is
>> currently doing quite well, and won't be going anywhere anytime soon!  If
>> something unforeseen DID happen, though, as Marcus notes, I'm sure we'd be
>> able to find some people willing to step in.
>>
>> - Paul
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Python Programming for Autodesk Maya" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to python_inside_maya+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/python_inside_maya/CAAssL7a4Pe8ta7cjtP7KYp%2BCg%2Bj2K26U28z3wtvX9MH-XyRd5w%40mail.gmail.com
> <https://groups.google.com/d/msgid/python_inside_maya/CAAssL7a4Pe8ta7cjtP7KYp%2BCg%2Bj2K26U28z3wtvX9MH-XyRd5w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to python_inside_maya+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/python_inside_maya/CAGq9Q7GnEfq2wZ%2BxfJ48xvnO7_QJq8_VdnqnLhRztCgGZLHUow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to