Blue Monkey
Archon Without Portfolio
That response does not address the issue of why it is here and not in site feedback or some other subforum devoted to sitewide issues. Such as the database. And policies that need to be appended to the forum rules / guidelines.Please read the OP. It is why we posted it in every C&C forum with links to here.
Is this a serious proposal? We designate or someone volunteers to search every thread in every subforum for permissions and attributions, download every single thing in the database, read all the read-mes & other text files, open all of the mods with ui elements to see if anything relevant is written there, check for things such as pcx files with authors' names in the unused parts of the image, collate that info & report back to staff?It would be very helpful if someone from that forum could put something together the details of what those permissions are/were so we can understand that.
Wouldn't it be simpler to address the general issue of grandfathering prior permission statements?
Once a policy is in place intentions won't have much impact. Won't even be known to most people affected by the policy. This policy specifically addresses intellectual property rights. In a contentious disagreement between some individual's intention and an explicit governing policy guess which wins.Our intentions are not to nullify anything.
Seriously?Perhaps you could expound upon this and provide some info via PM that would help us better understand the point you are trying to make?
What needs to be private about considering the difficulties inherent to links to other other sites, downloadable items from outside the CFC database and issues related to commercialization? These are not pure hypotheticals. Nor are they references to private situations. All have previously occurred at CFC in public view and will certainly occur again.
What needs to be private about pointing out that staf that are required to enforce a policy be familiar with its implications? One elementary example would be that the draft modiquette specifically states that we are meant to abide by any author's use of the creative commons license. So pointing out that staff will need to be familiar enough with the complete text of the many open-source licensing arrangements to enforce the related policies should be done only in private?
If key information is meant to be sent privately then discussion is effectively stifled. Can't comment on what we can't read. The whole idea of fragmenting this discussion to keep major parts of it private is appalling.
That's a pretty disingenuous response. The issue is not about the specific content of the policy but about how it will be enforced. Violations of any CFC policy are normally subject to actions such as formal warnings, infractions, elision by staff and banning. How will enforcement of this policy be reconciled with past practices?If everything on the site is open source, what would there be to infract?
