This is troubling. We've been repeatedly told by mnphysicist that breaking this or that rule will reult in an infraction, except perhaps in the case of a first offense. Yet if someone can gain no information as to what decision was made, the reasoning behind it, or how one stands in the process, then there is no chance to learn from the first offense. That person remains no less vulnerable to an infraction than previously.
I agree, and we need a way in which to do this. The first step is getting the reported member access to the report thread, so they can interact with staff. That helps one member, but doesn't help the membership as a whole. We do need a way to deseminate the finer points of rule application so all can benefit. How to do so with the constraints we are under is tricky, but it is something we are looking at.
I have to ask, is the policy disseminating pocess on this board meant to keep the membership well informed or not? I can imagine reasons why it might not be.
We need a way to do so, if we don't members are operating in the dark, and thats going to cause no small amount of problems, if not now, in 6 months it certainly will. Things build over time... no one needs those problems.
It seems to me that keeping the membership less informed than ever before is being accomplished, whether or not that is intentional. Rules and sub-rules and interpretations of rules, and even infractionable non-rules (see 'words that', re cursing) are scattered here and there. Stickied Announced rules have been changed, yet the changed rule remains unstickied, as this particular thread evidences.
Our policy folks are on other projects at the moment, this information will be published in such a way that its easy to reference. Same with the removal of dated or change information. Hopefully this will be cleaned up by the end of the year.
People complain staff do not answer PMs. People complain of posts removed without notification. People complain reports are not being acted on at all.
Guilty as charged as far as PM's go. I do not get to all of them, as there is not enough time in a day. It is something we are looking into as well.
I made a (rare: my second in a year) report myself yesterday, regarding a link that could be very damaging to CF's reputation. Except for a Chrisbot response, nothing's been done.
Send the admin of the area a PM, and if you don't get a response in 3 days, send one to me, with the word Urgent in the title.
All we hear in response is how busy staff are - but if so, what exactly are they busy doing, as they don't appear to be spending much time responding to members, privately or publicly. The few staff who do respond do so in limited fashion:
I think its a matter of rapid change at all levels. Staff are having difficulty keeping up. We should be out here more.
Can staff not understand that appearances are everything where secrecy is the norm?
This is a good point, and one I very much agree with. How to handle it will take some thought.
This has little or nothing to do with coding. This is a policy and implementation issue.
The coding part is a secondary aspect, but an integral one, when it comes to some policy issues. Its difficult from a scheduling point of view. If we wait to announce until the coding is done, folks get blind sided. If we announce before hand, and something breaks, which happened on private reports, then we raise expectations, only to dash them. This is an ongoing issue with almost every intensely resource constrained software project, where the same coders are supporting old code, concurrently with rolling out new features.
And Ron, brother... if you're really the only coder, then I heartily apologize for everything I've mumbled about you under my breath....
I'm an assembly language guy, and my php knowledge is limited, so I don't code on CF (although it may be possible that the electronics in the server are benefiting from some of my code, although its been a while since I did my last fab tool design work)
We do have a main coder guy, and he is amazing, but there is only so much time in a day, and keeping the site up has to come ahead of the other issues. For reference, there are still some dangling issues relating to the domain change, there is also the issue with the SS ads code breaking causing ads to be shown where there ought not to be any, plus we have some internal database issues. These need to come ahead of the report coding effort. You can go back to mumbling now
