Dan,<div>I attached two PDFs showing the changes to the blog I had in mind. They are attached again.</div><div><br></div><div>This thread began as a discussion of the mailing list policy. I drafted a sample. I got feedback. I incorporated feedback. You asked for more context for how these revisions would be integrated into the pages so I drafted a mock-up and attached them. They are not final. They are just an attempt to show you what I had in mind. That's why this is all on this thread and this list.</div>
<div><br></div><div>I agree that this isn't a conversation that SHOULD be on this list but it does bring up the need for a discussion that does perhaps belong on this list. And you allude to it in your last message when you say:</div>
<div><br></div><div>"I'm not sure if there is an Evergreen infrastructure team at this point, but between the web site and git servers and blog and mailing lists and wiki (and updates required for a number of those), it probably makes</div>
sense for it to have some recognizable structure to enable people to get involved with the effort - at least on a wiki page and/or mailing list discussion, to begin with."<div><br></div><div>I suggest that there is in fact an infrastructure team and it was founded as the Communication Committee and has evolved into what we call the Web Team. We undertook a very thorough assessment of the infrastructure and communication needs of the Evergreen community and developed some recommendations. See
<a href="http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam:webplan:2011">http://www.evergreen-ils.org/dokuwiki/doku.php?id=webteam:webplan:2011</a> for the documentation of all that work. Since then, we've tried to make incremental changes to get closer to what we learned the community wanted/needed. We've been minimally successful.</div>
<div><br></div><div>I think it is time we define areas of responsibility for parts of the "Evergreen online ecosystem" rather than continuing to rely on the few people who have traditionally been responsible. The Web Team has talked about the identifying content owners for areas of the 'ecosystem' and we will incorporate that idea into our Drupal demo site, but I think we could make some moves in that direction on the existing site. </div>
<div><br></div><div>To begin with, let's make it explicit how it works now getting answers to the following questions. </div><div><ul><li>Who is in charge of making decisions about what is on the Evergreen website (e.g. the home page and blog areas) </li>
<li>Who actually can make changes? </li><li>What mechanism is used to determine when a change should be made?</li></ul></div><div>Maybe if we understand better how it works now, we can make some decisions about how we want it to work.</div>
<div><br></div><div>Lori</div><div><div><br></div><div><div><div><br></div><div><br></div></div>
<br><br><div class="gmail_quote">On Thu, Jun 7, 2012 at 9:36 AM, Dan Scott <span dir="ltr"><<a href="mailto:dan@coffeecode.net" target="_blank">dan@coffeecode.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Thu, Jun 07, 2012 at 04:25:55PM +0000, Lori Bowen Ayre wrote:<br>
> Trying to keep this going....Got one +1 and no objections to the proposed<br>
> changes to the Communicate and Mailing List pages so I will proceed.<br>
<br>
</div>Sorry. Your proposal had "To contribute to the wiki ???", you're<br>
proceeding with that?<br>
<div><br>
> Can we get Alexey privileges to make changes to the blog? He is a very<br>
> experience web developer. Maybe I could put him in touch with Chris Sharp<br>
> to discuss protocols and things? We'd like to be able to implement these<br>
> things and not have to put additional pressure on Chris.<br>
<br>
</div>What changes to the blog do Alexey / you have in mind?<br>
<br>
Going through the Oversight Board seems like the wrong avenue for<br>
getting someone access to Evergreen infrastructure at this point, in any<br>
case. I would suggest that Alexey propose whatever changes he wants to<br>
make on -general and see if anyone wants to make those changes or offer<br>
him access.<br>
<br>
I'm not sure if there is an Evergreen infrastructure team at this point,<br>
but between the web site and git servers and blog and mailing lists and<br>
wiki (and updates required for a number of those), it probably makes<br>
sense for it to have some recognizable structure to enable people to get<br>
involved with the effort - at least on a wiki page and/or mailing list<br>
discussion, to begin with.<br>
</blockquote></div><br></div>
</div>