These are just my ideas by the way.
The advisory board should probably borrow some elements of the democratic system (employed in the US for example). Each forum that has a team elects its representatives possibly even based on number of active members or production. So 1 rep per 400 active folding members or whatever. The team can manage their own election process but as a guideline they run for reelection every six months or once a year. The team reps then advise the president, vp, and sec of the results and those users are added to the forum. The president vp and sec are elected out of the group of people sent by their teams by the people on the advisory board. If two of those three people agree on punishment for one of the members of the board or of the folding community as a whole that punishment is carried out. Also as an advisory board the whole board could vote to punish someone specific or enact a vote of no confidence in any of their leaders and overrule a bad decision made by the top. The top leaders are always accountable to the board as a whole. The decisions they make will be reviewed by the board as a whole and reversed if the board votes it to be so. The leaders would then be wise to act in a way that is most appropriate or face the board overruling them and possibly kicking them out of office. The board can kick someone off the board and ask the team to elect someone else. If the team elects the same person again then the board should work with that person to help them understand how things work and do their best to work with that individual. The teams should also understand that if a person is kicked off the board the reasons should be posted on the new election posting if that person runs again.
The advisory board would make and publish rules for the community to follow. They would punish those who ignore the rules. They would hopefully get support from the backend server management people to help detect those that break the rules.
I would think everything given to the advisory board would be public domain people who are beta testers and on the board would have to keep these separate. Their meeting notes should be made public once a month if not immediately available. Realizing that certain things can't be made immediately available like punishment discussions. The only exception to the rule that everything is made available could be cheating detection algorithms.
The board can run on a forum and that forum should have Vijay P and people that work for him as a mod. The only other mods should be the 3 elected leaders of the board.
The forums should be read only for the public (my opinion) but have a closed off section for punishments that gets published later and a cheating algorithm section that doesn't (again this depends but just the way I see it).
Vijay and his team should be allowed input to this forum as a whole so that their voice can be heard if they see fit.
As has been stated up higher this forum should focus on solutions not complaining. Topics should be focused so as to preserve the time of the members and to allow Vijay and his team the ability to get an overview of what is going on quickly.
Points assignment may at some point be handed to the board but I think we would be best at starting with getting things in place and working first.
The advisory board should probably borrow some elements of the democratic system (employed in the US for example). Each forum that has a team elects its representatives possibly even based on number of active members or production. So 1 rep per 400 active folding members or whatever. The team can manage their own election process but as a guideline they run for reelection every six months or once a year. The team reps then advise the president, vp, and sec of the results and those users are added to the forum. The president vp and sec are elected out of the group of people sent by their teams by the people on the advisory board. If two of those three people agree on punishment for one of the members of the board or of the folding community as a whole that punishment is carried out. Also as an advisory board the whole board could vote to punish someone specific or enact a vote of no confidence in any of their leaders and overrule a bad decision made by the top. The top leaders are always accountable to the board as a whole. The decisions they make will be reviewed by the board as a whole and reversed if the board votes it to be so. The leaders would then be wise to act in a way that is most appropriate or face the board overruling them and possibly kicking them out of office. The board can kick someone off the board and ask the team to elect someone else. If the team elects the same person again then the board should work with that person to help them understand how things work and do their best to work with that individual. The teams should also understand that if a person is kicked off the board the reasons should be posted on the new election posting if that person runs again.
The advisory board would make and publish rules for the community to follow. They would punish those who ignore the rules. They would hopefully get support from the backend server management people to help detect those that break the rules.
I would think everything given to the advisory board would be public domain people who are beta testers and on the board would have to keep these separate. Their meeting notes should be made public once a month if not immediately available. Realizing that certain things can't be made immediately available like punishment discussions. The only exception to the rule that everything is made available could be cheating detection algorithms.
The board can run on a forum and that forum should have Vijay P and people that work for him as a mod. The only other mods should be the 3 elected leaders of the board.
The forums should be read only for the public (my opinion) but have a closed off section for punishments that gets published later and a cheating algorithm section that doesn't (again this depends but just the way I see it).
Vijay and his team should be allowed input to this forum as a whole so that their voice can be heard if they see fit.
As has been stated up higher this forum should focus on solutions not complaining. Topics should be focused so as to preserve the time of the members and to allow Vijay and his team the ability to get an overview of what is going on quickly.
Points assignment may at some point be handed to the board but I think we would be best at starting with getting things in place and working first.
Last edited: