EGM - No. 7 - Code of Conduct
Sam Toland
Public
Seen by 373
This thread is open to all Resonate members.
We need to have a Code of Conduct ready for adoption at our first General Meeting. It is quite an important little document as it:
(i) helps establish our common group culture
(ii) helps define what is not ok, and gives the team a way to deal with misconduct / inappropriate actions
@samtoland has started writing a list of requirements for the Code of Conduct - and is interested to knowing if anyone has an interest in contributing, feedbacking, brainstorming.
@samtoland feels we need to keep it simple, clear and concise - rather than try and proscribe everything.
Let's give some time for people to comment, feedback etc. and then @samtoland will draft a first draft of the code for review.
Examples
- Open Source Development
- Musicians Code
- Feel free to add examples!
Sam Toland Tue 19 Sep 2017 6:46PM
Few different things.
Communicating with each other
Acting honestly etc.
Behaviour on the service (not breaking copyright, ripping music)
Contributing as a volunteer
It's pretty catch-all - that's why I broke it down.
The importance of it (as a relatively urgent matter) is that we need a code of conduct to refer to in the event we need to discipline / suspend / expel a member. Hopefully not going to be an issue - but from experience it is crucial to have this in place before any issues arise.
Nacho Baigorria Wed 27 Sep 2017 7:40PM
We definitely need one as what we are building is a different compared to many other organizations. I can help brainstorming but not a lot of time to actually produce content.
Poll Created Tue 24 Oct 2017 4:41PM
Motion: Approve Code of Conduct Closed Thu 26 Oct 2017 8:02PM
Approved
[NOTE - ONLY 7 SIGNATORY MEMBERS MAY VOTE ON THIS PROPOSAL]
We approve the requirements list for the Code of Conduct and that this requirements list may serve as the Code of Conduct until a more complete document is finished.
We ask the Board to bring a more complete document to a General Meeting for approval.
Results
| Results | Option | % of points | Voters | |
|---|---|---|---|---|
|
|
Agree | 71.4% | 5 |
|
| Abstain | 28.6% | 2 |
|
|
| Disagree | 0.0% | 0 | ||
| Block | 0.0% | 0 | ||
| Undecided | 0% | 4 |
|
7 of 11 people have participated (63%)
Terry Tyldesley Thu 26 Oct 2017 9:06AM
I'm happy to approve it as a basic code. For the more complete document I suggest we make the wording in the Musicians Code around samples more definite and be strict from the very start. Released music and uploads to many other sales / streaming / radio / online publishing sites stipulate no samples / 100 % artists own work. In the code now "at some point in the future we may need to be ridiculously strict" indicates wiggle room and could complicate things.
Sam Toland Thu 26 Oct 2017 12:04PM
@terrytyldesley I think it would be very valuable for you to input into the next draft. I also think this is a key element of our engagement with our musician members... something you might be interested in facilitating :)
Stephanie Merchak Thu 26 Oct 2017 2:25PM
Regarding samples, I think it would be more fair to say "only royalty free samples. No samples at all is impossible, all DAWs come with libraries, some companies such as Novation bundle their hardware with sample libraries from companies like Loopmaster. Native Instruments sell Kontakt with instruments sample libraries... All these can be legally used by musicians and producers. Saying no samples would mean artists will have to get instrument players and record all the instruments every time they want to make a track. That's simply impossible.
Terry Tyldesley Thu 26 Oct 2017 2:27PM
Agree it needs to be more specifically worded in the new version.
Peter Harris Thu 26 Oct 2017 6:25PM
Changed the language Steph, want to have a look?
Stephanie Merchak Thu 26 Oct 2017 6:45PM
Yes, much better that way.
Patrick · Tue 19 Sep 2017 5:39PM
Seems like we need a template. Not sure what conduct we are referring to. Is it how people communicate with each other or something else?