Article Post

Maybe you have notice but pretty much all our content on the site is open to everyone.  We have a few exceptions only dealing with assets and financial issues that members can not see.

Asset are available based on rank this is to stop member from joining us and pulling all of our resource and leaving which has happen many times before this solution was thought of by one of our members.

As far as financial part this is up to me (James Fleming) so its locked down just for lead producer since I handle all of it.

Now as far as the project goes their is not one part that is locked down in any since.  The whole team can see every part that member contribute as a team I think this is important to help everyone know what is being worked on, and what is done.

For leadership their is member stuff that is locked down that non lead members don't need to see.  Such as having their address or seeing the conduct notes the automation system puts on their record when it makes an adjustment to their account

So basically the point of all of this is we want as much information out for the general population of Thou Curator so that information is not having to be repeat and everyone see what is going on and the conversation on the subject.  You never know when someone might have and idea or comment about the subject being discussed that might set a motion in order that changes the ideology of our direction.

I can't tell ya how many times a member not in programming has made a comment about something that has made me change the logic or presentation layer of a project not only in game development but also in business applications.  All of our members should be heard and an attempt to at least try to disprove their thoughts so as to have a logical reason why we do things a certain way.

It is important for us to use the liaison area at the top of content and the kanban forum section when working with agenda's so information is kept in the public view.  We have a lot of resource for this reason forum, kanban, content conversation, blogs, and wikis for this purpose.

Private Messages (PM) should only be used when our project is not the subject and personal reason if needed to allow the member to express a concern they are having that he / she does not want other members to know about for whatever reason.  But when this type of situation happens the content of the PM should be re-established to the members view if relative for directions of or team.