I am imagining a small "yes you can study here" sort of a market.
A narrow market, but they can spend a lot. I'm more concerned
about being told I can't distribute my stuff than I am about the
University making money from it.
Since you put it that way, though, as far as the graphical environment,
I suppose that's no different than owning a program written in Java.
Our school's music director replied:
"UArts currently has no stated policy on copyright/patent ownership of
student or faculty work. One was being developed a few years ago, but
it has not been implemented (and that version actually had students and
faculty retaining all rights to their creations)."
(is it wrong to post his words?) He is devoted to understanding copyright, too.
Anyway, I take it any rule there is must be along the lines of the
poetry contest rule, where they are allowed one publishing but the
copyright never changes.
Thanks,
Chuckk
On 9/13/05, Greg Wilder <greg@gregwilder.com> wrote:
On Tue, 2005-09-13 at 13:33 -0400, Chuckk Hubbard wrote:
> But then someone told me today about some fine print clause somewhere
> that says University of the Arts owns anything someone creates while
> they're here.
I doubt *very* seriously if this is true.
> Luckily, since no one here understands either the tuning systems or
> the inner workings of a PD patch, them knowing what I had in mind
> doesn't help them if they don't actually have it.
And how would it help them anyway? What sort of market do you imagine
for what you're trying to create?
> So what I'm wondering is, is there such a thing as ownership with a PD
> patch?
PD is an graphical object oriented programming environment. If you
create a "patch" in PD, you're really building a unique program using
the PD objects and interface. While you can't "own" PD, I would think
that you can certainly claim ownership of your unique implementation of
the environment that PD provides.
Kinda like making music using Ardour or Hydrogen - you own the music,
even if you didn't create the original sound libraries and the program
code. Or better yet - you could think of it like coding inside an IDE.
Best,
Greg
--
"It is not when truth is dirty, but when it is shallow, that the lover of knowledge is reluctant to step into its waters."
-Friedrich Nietzsche, "Thus Spoke Zarathustra"