Postgresql.org "Editor-in-Chief"
Responsibilities:
I. Writers List
	A. Solicit the PostgreSQL community and assemble a list of writers
		(in various languages) who are willing and capable of writing
		magazine and web articles and books.  The list should have:
		1. Contact info
		2. Subjects of expertise
		3. what kind of writing they're available for,
			 including paid, free, and postgresql internal
	B. Maintain the above list:
		1. Track changes to the above data;
		2. Note feedback from publishers, and remove people from
			the list if they get too many complaints;
		3. Periodically solicit to find additional writers.
	C. Publish the above list on the web or elsewhere if we decide
		to do so.
	D. Possibly admin a mailing list for PostgreSQL writers
	E. Coordinate this with the Speakers List (below)
II. Publishers List
	A. Solicit a list of Publishers seeking PostgreSQL material:
		1. Contact info
		2. Submissions requirements and publication style
		3. Compensation & copyright info
		4. What they're currently seeking
	B. Maintain contacts with publishers:
		1. keep a publicized e-mail where you accept requests
			from publishers;
		2. keep the above list updated
	C. Solicit writers for projects
		1. Solicit the writer's list for new projects;
		2. Help publishers with problem projects (e.g. writer
			vanishes and has to be replaced)
	D. Publish the above list on the web or elsewhere if we decide
		it's a good idea.
III. Advocacy Writing
	A. Solicit writers for work on brochures, web sites, and other
		advocacy material;
	B. Do or arrange editing/review for this material.
Time expected 4-6 hours per week, with about 30 hours to get things started


PostgreSQL.org "Master of Ceremonies"
I. Speakers List
	A. Solicit the PostgreSQL community and assemble a list of
		speakers (in several languages) who are capable of public
		speaking and interviews for PostgreSQL.
		1. Contact information, including several phone numbers
			and avail hours for interviewees
		2. Topics of expertise
		3. Types of speaking available (conventions, interviews,
			user groups) including paid & unpaid
		4. Location and willingness to travel
	B. Maintain the above list:
		1. Track changes to the above data;
		2. Note feedback,  and remove people from
			the list if they get too many complaints;
		3. Periodically solicit to find additional speakers.
	C. Publish the above list on the web or elsewhere if we decide to;
		if not, provide list & updates promptly to PR team
	D. Possibly admin a mailing list for PostgreSQL speakers;
	E. Coordinate this list with the Writers List, as it will include
		many of the same people (likely at least 50% overlap).
II. Staffing Events & Requests
	A. Keep track of conventions in the news, and actively solicit
		organizers for the inclusion of PostgreSQL speakers.
	B. Respond to requests from User Groups and Conventions and arrange
		speakers for these things, including arranging replacements.
	C. Respond to requests by speakers for travel funds and submit these
		proposals to the Advocacy core group (still being formed);
	D. Publicize events which have a PostgreSQL speaker within
		 the PostgreSQL community.
	E. Coordinate all this with the Regional Contacts.
Time expected: 4-6 hours per week, more at the beginning.



PostgreSQL Advocacy Regional Contacts
I. Regional Press
	A. Help arrange translation of press releases and other Advocacy
	   materials
	B. Maintain a list of local/regional/language press contacts
	C. Answer or forward questions from the local/regional/language press
	D. Work with the PostgreSQL "Master of Ceremonies" to staff interviews
		 in your area
	E. Keep up to date on PostgreSQL developments so that you can be
		knowlegable for the above, including participating actively
		on the pgsql-advocacy list.
II. Community Building
	A. Solicit users in your area/language
	B. Create and admin a mailing list when you have enough people.
	C. When you have even more people, add a web page and/or
		start a PostgreSQL user's group.
III. Community Liason
	A. Find user's groups, conventions, and other local events and groups
		which are related to PostgreSQL
	B. Work with the "Master of Ceremonies" to do PostgreSQL outreach
		to these groups and events.
Time expected: 5-12 hours per month.


Case Study Manager:
I. Locate and contact companies known to use PostgreSQL for case studies;
II. Respond to questions and interview these companies;
III. Draft case study reports based on the interviews;
IV. Obtain written authorizations from the participants to publish the
	studies;
V. Arrange/do final formatted versions of the studies in HTML and/or PDF.
Time expected: 4-12 hours per month, more initially.