I have had one-on-one interviews with individuals who have, or have had, senior-level responsibility for the Newsletter. In addition, I've had a chance to talk with three other individuals who have had a history of working on newsletters.
This is a summary of what I've discovered and what I'd suggest we do.
The Newsletter is an information driver. This is as opposed to a website, which is a repository, and a journal/magazine (such as TIP) which is an official record. The way the Newsletter drives information is by pushing it out to readers.
Based on my conversations with others, the manner in which information is pushed out can be both managed (essentially like it is now -- it's prepared by a content manager and then sent out) and elected. In this mode, the user can elect to receive information feeds via RSS (the little orange square at the top-right under the tool bar). The rights to information need to be managed by the organization through the newsletter function, but my committee members believe this is readily achievable.
The next issue is -- what is sent? The two most obvious answers would be "deadlines and headlines." These are managed by the organization. Beyond those, the RSS feeds allow the user to select content-oriented topics to be updated on a continual basis by the content originator. Also, we believe that what can be sent/updated should include: paragraphs about works in progress (like the old "validity information exchange" of PPsych), and dialogues. The dialogues can be messages (e.g., an announcement from an editor of JAP about a need for reviewers), or even video links a la YouTube.
In all, the goal of the Newsletter is to engage reader/members with the organization on a "real time" basis without bombarding them.
The individuals I've spoken with who have indicated an affirmative interest in being on the committee include Zack Horn and Charles Handler. These are two dynamic and experienced individuals, and their efforts to improve the Newsletter will incite others to want to join.
Please let me know what you think and if the ideas indicated here -- especially feeds -- are to your liking, we'll begin working on ways to implement them.