Constitution #3
|
@ -438,6 +438,36 @@ and spread our shared vision of a humane social order.
|
||||||
project group once it is formed after the ratification of this
|
project group once it is formed after the ratification of this
|
||||||
document.
|
document.
|
||||||
|
|
||||||
|
3. A project may elect a Producer from the project body to the term of
|
||||||
|
the project development cycle.
|
||||||
|
|
||||||
|
1. A Producer is responsible for the planning, procurement, and
|
||||||
Rissa marked this conversation as resolved
Outdated
|
|||||||
|
execution of a project.
|
||||||
|
|
||||||
|
2. A Producer is responsible for facilitating communication between
|
||||||
|
the Project Director and project body to define & refine
|
||||||
|
engineering, creative, and business requirements.
|
||||||
|
|
||||||
|
3. A Producer is responsible for negotiating a project schedule
|
||||||
|
with the project body, and coordinating the project body's labor
|
||||||
|
to ensure the project is completed in accordance with that
|
||||||
|
schedule.
|
||||||
|
|
||||||
|
4. A Producer is responsible for advocating for their project's
|
||||||
|
labor requirements to the Personnel Committee.
|
||||||
|
|
||||||
|
5. A Producer is responsible for advocating for their project's
|
||||||
|
material and technological requirements to the Infrastructure
|
||||||
|
Committee.
|
||||||
|
|
||||||
|
6. A Producer is responsible for advocating for their project's
|
||||||
|
financial requirements to the Treasurer.
|
||||||
|
|
||||||
|
7. A Producer is responsible for informing the greater collective
|
||||||
|
body on any decisions relating to the procurement of project
|
||||||
|
requirements.
|
||||||
|
|
||||||
|
|
||||||
## Article VIII. Collective Ownership
|
## Article VIII. Collective Ownership
|
||||||
|
|
||||||
### Sec 1. Collective Property
|
### Sec 1. Collective Property
|
||||||
|
|
Loading…
Reference in New Issue
I'm a little concerned about maintaining a division between personal IP and collective IP; I'm not suggesting that I want to retain rights to something used by the collective, but I don't want to accidentally, implicitly, transfer rights by offering an anecdote from a personal project during a brainstorming session. I'm not sure, however, that there's any cleaner way to deal with the issue than not to share such an anecdote.
I agree. I really hate the typical software company IP agreements -- y'know, where you get five lines to list every idea you've ever had, and everything else now legally belongs to your employer. I want to embed a policy of respecting individual members' lives outside the collective into the constitution, and that includes rights to personal IP. The idea with the Collective Property section is to establish a very permissive IP policy right from the start. To that end, I wouldn't be terribly opposed to making it more permissive -- I'll follow up with some ideas on that in the chat.
That said, the collective needs to own its own intellectual property, because we need to prepare the collective to exist as a legal entity within a legal system that believes in and enforces private ownership of intellectual property. That's why I think we need to assert in clear terms from the start that "something is owned by the Collective" and "something is collectively owned by the members of the collective body" are equivalent terms. Whenever we incorporate, we'll want an IP lawyer to look over this and tell me that I'm an idiot and all of this means nothing, then tell us how to actually write it.
(yes, I still think the entire idea of "intellectual property" is deeply puerile and idiotic. unfortunately we live in a world that is also puerile and idiotic and thinks ideas can be owned by people.)
How do you feel about the updated version as of
8ccb8ceb9b
?I suppose I should say something in addition to marking the conversation resolved. I think we've worked out my concerns; basically we're now asking to explicitly assign rights to the collective at the outset of related work.