Group:FSF Community Team/Workflow

Workflow

Here's what should happen with most articles.

1. Somebody posts an article to the list.
2. People respond with actual reply text, or changes to text.
3. Somebody from FSF approves the responses (for now, this will change soon) and we send on behalf of the 'Team.
4. Any other discussions about our process is a process point (see below).

Message Types

Article

This is a proposal for an article we should respond to. When proposing an article, include:

• "Article:" in the subject
• The link
• Quick description of the source (if not obvious)
• Data or a subjective take on the source's popularity (why worth it?)
• Reason for response
• Proposed form of response? Comment? Email? (incl. links/addresses)
• Optional: a proposed response (see below).

Example:

Article: http://joetechblogger.net/posts/the_iphone_is_awesome/ 

Joetechblogger is a popular tech blog.  #78 on technorati, 12,345 
twitter followers (or: a widely-read Australian tech-blogger).

The iPhone is a serious threat to peoples' freedom, we should explain why.  
I propose we leave a comment in that post and write the author a friendly 
email (j@joetechblogger.net).
 

Response

This is a proposed response to an article. It should be a reply to the article thread. A response should be:

• A complete, actual written response
• In the form of an email, comment, or both as necessary.
• Something you would actually send, that would inform or persuade.

NOTE: If you want to suggest an improvement to somebody else's text, *always* include real proposed language that fits in their proposal. No ideas without real writing!

Example:

Hi Joe,

I realize the iPhone is a cool piece of hardware, but the software 
on it presents a real danger to society, and I think you have a duty 
to make your readers aware of this.

(reasons)

Thanks,
Holmes Wilson
FSF Community Team

Process Point

This is a wide open area for discussing our goals or how we're organizing ourselves. Anything is on the table, but please be concise and constructive, and avoid generating needless controversy or list traffic.

• Explain what problem you're trying to solve or what you're trying to achieve
• Include a simple, concrete actionable proposal that you could imagine getting done.
• The phrase "I propose that" should probably appear in your email.

NOTE: Every response to a process point should also include a proposal.

Introduction

See Introduction Letter (fill this in)