Make all CDT discussions public record

In regards to this, I'm supporting releasing the threads once events are completed/polls close. Opening up the section for public view is stupid.

 

I don't see why it would be wrong for us to post the monthly check in thread publicly.


This way we have a summary of what has been done shown to the public without leaking anything and doing damage to the internals. +it helps people stay accountable.

 

Well if you want the public to attend your event you have to organize at least part of it in the public. If it's a contest or something that needs to have private answers, fine plan it in private but release it after the fact.

If you change the way you communicate based on whether you are in public or not you shouldn't be in the position to comment privately.

Syed said there was a lot of suggestions floating around in there. Can those be made public? Part of the reason I want the entire section is because I don't trust people to actually make things public. The default should be public, not private.

This doesn't solve the trust issue.

 

I don't see a problem with that as long as it doesn't interfere with anything the CDT has planned.

 

Make the CDT, PR, and Tech Core all one big "Community Building" squad that has different subsets and there can be a record keeper who releases the monthly updates/info of everything.

All in all yeah, make it public, take feedback, and force the teams to somehow work together for a common goal of success (isn't that what we're doing) so this doesn't turn into a pissing contest where people are trying to mark their territory.

 

I'd support the idea of an archivist who worked with all three teams to publically archive old threads. I'd still like as much as possible to happen in public rather than in private. The TCT will likely have a lot that can happen directly in public but we can figure that out as we get up to speed as a team.

 

As long as there's still a place for private information that may be sensitive then that's fine. My only real concern is ensuring the teams work together to fulfill the common goal of aiding Sythe's community

 

I completely agree there should be transparency. I see nothing wrong with releasing information to the public that isnt sensitive material.

 

We can have a public event archive yeah but the live threads should remain as is

 

This is being exaggerated to crazy levels. What is the point of the CDT existing if discussion is had or moved to the public before events become live?

 

Tell @Syed to stop leaking information, nothings been decided on the outcome of publicity yet.

The idea of having suggestions floating around in there is to determine what would be good, or pencil to paper ideas on what could happen. We then if necessary make these idea's public and ask the community what they would like to see with these ideas. Other times it is not possible to do so, because it could ruin the event etc. If you have these ideas immediately on show to the public, it wouldn't have the same effect. Like Tyler said, there are a lot of event planning which need to be hidden. So I don't support live events being open to public.

There are a few things I would not mind being public.

Applications; whether that be the sole application itself, or the voting as well - possibly just the application. I'm aware of there being a stigma regarding if a CDT member voted no or had negative reasons it could be a downer for the new applicants. I don't see why it wouldn't be unfair to show the community the reasons for why you wanted to join the CDT, what skills you have to offer, what has motivated you to apply.

I don't see why we can't make events which have finished be publicly archived; have the 'making-of' event#1. That way the whole community can see for themselves who participated where, how and what was done behind the scenes. Alongside the monthly check in thread. This would be a great way to receive feedback from the community if they can see what was done. I've

Some voting. events such as Monthly Graphics Competition, are open to public voting. I agree possibly in future we can have events which have entries such as photos could have public voting. - I don't see much wrong with this being a public voting. If entries are hidden, then the voting can be public, this way we minimize the whole idea of votes being based on a popularity contest.

This is so far what I can think of, off the top of my head.

 

With the exception of applications, voting on applications, and organization of events during that event, I don't see why not. Applications should be made private to respect the privacy of the user applying. If they want it public or don't mind, they're free to post it on the application thread imo. Voting on applications should be private for many of the reasons mentioned above. And an event is no fun if organized in the public. Many events, such as the halloween haunted houses would be no fun because the answers and structure of the event would be public for everyone participating to see, eliminating the fun of it.

But discussions I don't see why not. Infact, I'd love to see threads go up a month before december asking if anyone has any ideas for christmas events. I think that can get people really engaged to participate with the CDT, and can even help show the CDT some people who are encouraged and want to be apart of making these events. So really, almost nothing bad can come of it. If anything, it'll help the CDT grow and help make improved events that even more people in our community can enjoy.

 

Bump.

 

This can be done easily. Just as there is a "Discord Log" in the SF, logs of event discussions can be put out to the public. But making it live I don't think is a good idea, there's no point in having a team then.

A way to avoid that, would be discussing things with the community first before starting team discussion. I agree with Roary on this.

 

Butt (Bring up the thread)
Bump is incorrect as that means Bring up my post, this thread isnt mine so have to use Butt

 

We will be publishing all event threads after the events finish as soon as get a forum to do so

 

I like this. PR, CDT and TC should be made this way. Like this the PR, CDT and TC members also have a reason to do things quickly as people can see if you are slacking.

 

i think that's probably the best solution here. there's a good reason to keep active threads separate, and honestly most of them are boring anyway.

fwiw, i think the response to one poorly-managed CDT event being "ok, make it public" is an overreaction, but honestly now that CDT is a shell of its former self i dont really mind if its all made public.

quicker ≠ better

 

The poor event was just the catalyst of change, not the reason to change.

 

never said it was . in any case, i still think SS's approach makes the most sense