User:Larry Sanger

From Citizendium
Revision as of 13:08, 21 January 2008 by imported>Larry Sanger
Jump to navigation Jump to search
Lsanger02sm.jpg

Hi there! Larry Sanger here. I'm the Editor-in-Chief of the Citizendium. I am also currently, and temporarily, serving as Chair of the Editorial Council. If you have a question, I'll try to answer, but you might want to try the Forums first if I don't answer instantly. I'm happy to report that I'm extremely busy! You can join my shameful backlog of e-mail at sanger <at> citizendium <dot> org.

You can read more about me at my personal home page. I have a Ph.D. in Philosophy from Ohio State and a passion for Irish traditional music. I was born in the Seattle area and grew up in Anchorage, Alaska.

I do not claim any sort of editorship other than being Editor-in-Chief, I'm afraid, not even in philosophy or the Internet. I am too long out of doing any serious research. (Although this is changing!)

I've worked on many articles, but I wrote significant parts (or all) of: John Doherty (fiddler), philosophy, Ship of Theseus problem, and epistemology. None are done yet!

There's a CZ article about me which I have not edited.  ;-)

Citizendium 80x15.png <-- you can use this if you want

Status
Mon., Jan. 21: I'll be maintaining my to do list on this page.


Suggestion Box
Got a suggestion for me personally? I mean, you can use the Forums to make any suggestion, but if there is some big sweeping change or project or idea that probably ain't gonna happen if I don't get behind it, please let me know at Suggestion Box.
Sanger's Dashboard

Done

High priority one-off items

  • Catch up with e-mail (top top)
  • Restart Editorial Council already...
    • Submit revised resolution
  • Post call for technical partners
  • See if we can get that minor re-skinning done soon.
  • "Focus group"/weekly call...
  • Continue recruiting for CZ Honorary Board
  • Userinfo System
    • Fix little bug
    • Group status page for workgroups!

Policy and help pages

  • Quickly finish usable if not perfect versions of the various instructions home pages, and quickly if not perfectly update our introductory material, it's getting rather outdated
  • Finish work on various policy and instructions pages:
  • Write up some guidelines for editing policy documents: which details go in the document and which go on more specialized policy pages, who needs to be informed of changes, and that we should be linking to all (yes, all) policy pages via the homepages linked on CZ:Home

Recruitment

  • Citizendium advocates' guidelines
    • Encourage authors and editors to become advocates and spread the word; feel proud
    • Part of the recruitment ramp-up effort
    • Button to put on blog: "I power the Citizendium"

== Other plans (higher priority)

  • Public comments feature - MW plugin?

== Other plans (lower priority)

Workgroup launch strategy

  • "Ramp up editor participation"
  • See here and elsewhere for ideas on new approval system.
  • Add editor policy and relevant workgroup templates to all editor pages.
  • De-link inactive accounts
  • Procedure for adding workgroups, including breaking "Hobbies Workgroup" into a zillion subgroups
    • One possible condition: three editors request it, all of them having created at least three articles and having edited five articles.

Dispute resolution and governance

  • Add an important distinction: pulling rank in order to resolve a dispute vs. pulling rank in order to win an argument. The former, only, is permitted. -- Add this to CZ:The Editor Role and CZ:Dispute Resolution.
  • Referee/Judicial Board/democratic system discussion:
    • Respond to Gareth and Pat
  • Rethink and discuss various governance improvements, including: Personnel Manager, "job listings," Judicial Board policy, a central "proposals" page?
  • Constabulary
    • Finish drafting policy regarding entrance and exit from Constabulary (an element of sortition here?)
    • Hammer out policy about how new Constabulary policy is created
  • Write various Editor-in-Chief powers and constraints into rules
    • Veto power
    • Minor policymaking power (must be exercised before Council & Const.)
    • Ask Editorial Council and Constabulary to vet the rules about Editor-in-Chief powers and constraints
  • Hammer out author demotions policy--long anticipated, never acted on
  • Technical Committee

Recruitment Step 1

  • Create "one-off" job board
  • Request resignations from inactive members of Executive Committee, Constabulary, and Editorial Council
    • Follow up to nonreplies after a week (set reminder)
    • Actually remove people from various wiki lists and mailing lists
  • Accomplish separation of powers
    • Compile list of people who serve on more than one group
    • Send mail to all of them asking them to choose which group they want to remain on
    • Follow up to nonreplies after a week (set reminder)
    • Make decisions for any laggards (set reminder)
    • Actually remove people from various wiki lists and mailing lists
  • Do big management recruitment push
    • Create "job listings" page
    • E-mail lists when ready
  • "Jobs" to list include (be sure to specify which positions are pending approval):
    • Chair of the Editorial Council
    • Constables (6-10 new recruits)
    • Executive Committee (6-10 new recruits)
    • Executive Committee Secretary
    • Editorial Personnel Administrators (8-12 new recruits)
    • Chair of the Editorial Personnel Committee
    • Judicial Board members (3)
    • Personnel Manager
    • Project Coordinators: annotated Web links; annotated (non-Web) bibliography; categories (subtopics, supertopics, related topics); catalogs (almanac-type information in tabular form; see e.g. catalog of religions); gallery/multimedia; expert (curated) articles with bylines; debate guide; news summary; tutorials
  • Update CZ:Personnel with data about beginning and end of terms
  • Follow up on old volunteer offers

Recruitment Step 2

  • If possible, find a Personnel Manager first; work with this person to complete Step 2
  • Begin matching jobs to persons when applications begin dropping off
  • Work with current constables and Chief Constable to get new constables on board
  • Do the sortition to get new editors and authors on board
  • Select new Executive Committee members (from within set of general volunteers, and possibly others)
  • If necessary, use Craigslist and/or other sites for recruitment
  • Find new E.C. Chair
    • Solicit from within Council
    • If there are no replies (set reminder), solicit from outside Council
  • Create coder wiki page, to include: desired projects; "bounties" (solicit donations for particular software projects--domystuff.com?)
  • Assign authority to edit certain pages to certain specific individuals; track these assignments on CZ:Policy Outline

Implementation

  • The Big Subpage Move
  • Son of the Big Delete (eeee!)
  • Start the Big Invite
  • Nominate new Editorial Council members
  • Create new workgroups, finally
  • Add rules about the Editorial Personnel Committee and its Chair
  • Do "training" of new positions
  • When finished, make self rank-and-file member of Council & remove self from Constabulary
  • Establish Execute Committee meetings (conference call)
    • Settle upon technology
    • Settle upon time
    • Ask whether anyone will serve as Secretary
    • Set up new Executive Committee wiki page, containing reports/minutes
    • Decide whether to post these meeting reports to Citizendium-L

Other Tasks

  • Create Board of Advisors
    • Ask for nominations from Citizendium-L, Citizendium-Editors, Executive Committee, as well as the blog
    • Create criteria
    • Do further research into possible invitees
    • Make a master list of possible invitees
    • Approach each personally
  • Follow up on eBay thing
  • "Submit articles" button/address & process?
  • Move discussion from workgroup forum boards to workgroup mailing lists?
  • Follow up (write policy on and develop) "Cold Storage"
  • Establish a method to raise neutrality issues (and other issues of failure on the part of the editor to follow CZ policy)
  • Create a uniform dispute resolution mechanism, in the form of a vote on proposed issue.
  • Other quality checklists?
  • Open up stubs?
  • Start up weekly focus days? -- New article day, edit someone else's article day...
  • Put editor names on talk (or info) pages?
  • Popovers
  • A page for giving credit to "First Collaborators"
  • Move discipline-oriented discussion to mailing lists, shut down workgroup forums??
  • Ensure the Constabulary gets a policy about exiting members going
  • "Pop culture" subpages
  • Proof subpages
  • A better way to get programming support
  • Decide whether to use Flagged Revisions
  • Review system (see exec mail of Oct. 10)

Other people's to do, to follow up on

Who What Remind Absolute deadline
Lee Berger Eduzendium press release Jan. 18 None

Principles for our organizers' group

I've convened a small (six person) group of people who have committed to helping to organize various initiatives and generally "get stuff done." Call them organizers. We're going to talk on a regular basis and together drive a lot of new stuff forward in 2008. For my future reference (and theirs), here are some principles I have proposed for this group.

(1) Above all, what we need is maximum creativity, to achieve two goals: (a) precisely identify specific practical problems that need solving, and (b) propose specific practical solutions to those problems. No project I've ever been involved in has ever made headway without the principals constantly thinking up better practical solutions to practical problems.

(2) More specifically, our job is to organize activity. If we execute everything ourselves (individually or collectively), we are not doing our jobs. Our job is to organize and motivate others to do stuff. No doubt we will have to lead the way, and sometimes work hard in doing so. But we have to feel bold enough to call on others to help. This can be specific other known individuals, but more importantly is the power of "crowdsourcing" that is at the heart of wiki projects like CZ. We prioritize community initiatives and labor: what are the most important problems CZ faces, and needs to solve? I also welcome your help in prioritizing my own work.

(3) Our job is not to debate. Debate is great. Debate is necessary. But it is not our job. Our job is to do. Therefore, if we debate, we should debate only concerning what the best course of practical action should be. But even this debate should be kept to a minimum.

(4) Big important new initiatives do need discussion and approval. But once they're approved, go to town. Steve Ewen was given the green light to organize our image policies and resources, and he went to town--that is a perfect example of what I mean.

(5) We are not the Grand Overseers of the Citizendium. We are not The Cabal. So we do not make policy and we do not pass judgment on individuals. We are doers and organizers. If new policy is required for us to take some action, we consult the community and drive it through the proper bodies (if possible!).

(6) Our proceedings need not be particularly secret, except perhaps in very small cases...we could, if we wanted to, set up a mailing list for our group and make it open to read.

(7) We will report on our work to each other once or twice a week (we can decide later), and give each other advice and encouragement. If you stop acting for a time, you'll be dropped from the group. If some other person particularly distinguishes him or herself and would seem to fit in as a co-organizer, let's get that person into the group.

Userplan experiment


Citizendium Organization
CZ:Home | Workgroups | Personnel | Governance | Proposals | Recruitment | Contact | Donate | FAQ | Sitemap
How to Edit
Getting Started Organization Technical Help
Policies Content Policy
Welcome Page