If you'd like to make a suggestion for changes to the community Web site, here's the process to follow:
Post Your Suggestion in the "Community Business > Suggestion Box" Sub-Forum
Only registered, logged-in users may post. Please post concise, yet descriptive suggestions. Explain how your suggestion would benefit the community as a whole. You can only create new suggestions - you are not able to reply to posted suggestions (we don't need "I second that" posts in order for something to be considered).
The Advisory Committee Discusses Your Suggestion
This discussion happens offline in a private mailing list. If you're interested in being a part of the discussion, you'll need to be invited to join the Advisory Committee. The Committee Chair is responsible for issuing these invitations, and will usually extend them to active members of this Community - meaning you need to contribute in order to become part of the Committee.
The Advisory Committee Posts a "Request for Comments"
If the Committee decided to go forward with your suggestion, or some variation of it, a "Request for Comments" post is made in the "Community Business" forum by a member of the Committee. This "RFC" allows all community members to offer their feedback. The Committee may decide to revise their proposal (resulting in a new RFC posting), withdraw it, or go forward with it. The Request for Comment period is 14 days unless the Committee specifies a longer period in the RFC posting. Note that any user may reply to an RFC, but only the Committee may create new RFC postings.
The Committee Presents the Proposal to the Community Director
Approved, finalized proposals are presented to the Community Director for implementation. Proposals which will require some kind of long-term maintenance must also include provisions for that maintenance, such as the name of a volunteer who will be initially responsible for that maintenance. Proposals which require a monetary expenditure must first go to the Board of the PowerShell Business League, which funds the community Web site. Provided the proposal is capable of being implemented, the Director will implement it.
Okay... now some background...
Wow, this may seem like quite a process, especially for a simple change. Let's take the "Remember my logon" checkbox, which appears on the community's logon page. That may seem like a fairly standard, simple thing - but turning it on when the community first started resulted in me (the Director) receiving around 30 e-mails from people who were angry that the site was issuing permanent cookies with no explanation (the checkbox itself was apparently explanation enough). So... while I've always been happy to implement good ideas, I can't make these decisions unilaterally. The Committee operates independently and autonomously, and their discussion combined with an open comment period will help ensure that everyone interested in having a say, has that opportunity. It's my expectation that batches of "smaller" proposals will be rolled up into a single (monthly?) RFC, just to help cut down on traffic and to help manage the community's stability - I don't want a change-a-day any more than your boss wants constant change in, say, your Active Directory configuration. Hopefully this process will provide fair, objective, and balanced opportunities for everyone to have a say in how the community grows!
|