<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-postmall17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=SV link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I agree with all the thanks Michael – Txs for the work you’ve
done already!<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Sound like a great proposal to me, even if I cannot make a technical
evaluation I trust you and others on the list to have that competence.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I think the Swedish OSI might have some kronor to put into this
transition/maintenance. Let me know and I’ll put a proposal forward to our
board.<br>
Best regards<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thomas<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Från:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> OSLIST
[mailto:OSLIST@LISTSERV.BOISESTATE.EDU] <b>För </b>Michael Herman<br>
<b>Skickat:</b> den 19 augusti 2010 19:38<br>
<b>Till:</b> OSLIST@LISTSERV.BOISESTATE.EDU<br>
<b>Ämne:</b> the future of the oslist -- news and a proposal<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>hello all, a bit of very important news and a proposal for
the future of the oslist.<br>
<br>
the oslist -- in it's current form -- will cease to exist within the next
year. i have been in contact with our boise state hosts and with the
makers of the software that drives our list and archives. i've developed
a bit of a work-around plan (working around paying the software company or
anyone else large sums of money annually to run the future of the list).
the softward company has confirmed for me that this (rather non-standard use of
their software) is indeed technically feasible. another nice thing about
it is that it makes the oslist structure look even more like what we do in open
space meetings. <br>
<br>
the oslist at boise state is done as of june 30th 2011, they are cancelling
their license and migrating all university groups to googlegroups. on
that date, oslist will disappear, unless we do something to move it. <br>
<br>
IF we can find another organization to host us as bsu has, then we can (pay
someone to) migrate our archive and user list and go on our merry way, subject
again to the whims of their IT department.<br>
<br>
IF, instead, we choose to fund our own implementation of the listserv (brand
name) software, we can migrate our archives and continue our conversation.<br>
<br>
ALTERNATIVELY, or more creatively... we can contract with l-soft directly to
set-up and maintain our archive, control that for ourselves going forward, AND
set it up in a way that would add to the archive going forward any postings
from any other email list, like germany, europe, australia, uk, etc.
what's more, this turns out to be the cheapest option, because we only need to
pay for listserv software for the archiving function, rather than for a
full-blown list that will deliver to 700 people at a cost of almost $2 for
EVERY message sent to the list (this assumes we would pay for the service
rather than license and run this for ourselves. harrison is fond of
saying that we have done all this without a marketing department. why add
an IT department now?) this is my suggestion.<br>
<br>
and this is what i'm proposing (offering) to do now:<br>
<br>
1. migrate all of our members to a new oslist at googlegroups (yes,
googlegroups. people who pay attention to such things seem to prefer the
functionality there and since our list is public anyway, there are no issues
with privacy and control of content. but we will also archive in two
other places, a gmail account AND a listserv system that will keep adding all
new posts to the old listserv archive.)<br>
<br>
2. migrate the archive (12 years, i think, and on our way to 29,000 messages)
to a new list that will have only one member account. <br>
<br>
3. make that one member account (<a href="mailto:oslist@gmail.com">oslist@gmail.com</a>,
for instance) a member of the new <a href="mailto:oslist@googlegroups.com">oslist@googlegroups.com</a>
AND any other lists around the world. THEN set that member account to
forward everything it receives to the migrated archive. so other lists
become like breakouts and the oslist archive a global community record wall of
what's happening.<br>
<br>
it this way, we achieve: <br>
<br>
1. a new, free, and durable oslist at googlegroups, with all the bells and
whistles there<br>
2. the survival of the 29,000-message archive in publicly-searchable
perpetuity, hosted by l-soft (makers of listserv software)<br>
3. the addition of all new oslist and other list postings to the central
archive<br>
<br>
what does it cost?<br>
<br>
1. continuing the oslist conversation in a new googlegroups oslist account
costs nothing.<br>
2. forwarding to the archive of all os community list mail from any list, costs
nothing<br>
3. migration of the oslist archive and setup of new archive list function costs
$500<br>
4. the cost of maintaining the archive would be $500 per year<br>
<br>
i'd expect that $500 is fundable through donations and could easily be handled
in the normal course of business and budgeting of the osi-usa. i assume
it's better to have a legal entity with a standing bank account take
responsibility for it, rather than an individual or loose group of
colleagues. but i'll leave it to osi-usa or another group to say they'll
take this on.<br>
<br>
i *think* that any other solution to this results in one or more of the
following... loss of the archives, costs that run to $3000 or $4000 annually
(and are totally variable based on list size), reliance on volunteer community
members to be our global IT department, additional cost of paying community
members to admin the system, reliance on the goodwill of some other
organization (which might be generous initially but could pull the plug with
less warning than we've been given now), no ability to archive many lists in
our one online record. <br>
<br>
i will check with boise state to confirm their support for our migration.
i'm told by l-soft that migrating the archive to a new location/list is pretty
simple stuff. <br>
<br>
i'm willing to implement this, but not fund it. i'd like at least four
others to sign on as stewards of the shift. more would be fine. and
i hope osi-usa will be the official steward for donations/funding matters.<br>
<br>
i don't have time right now to discuss this with 700 subscribers. i'm
just one guy, one list member. this is just my personal recommendation
and proposal. BUT... if there are concerns about any of this, i'm glad to
try to keep up with clarifying questions. <br>
<br>
if you think this is a good way to proceed, please say so. if you have
something to contribute to the process (time, attention, money, etc) please say
so. if you have concerns, let's hear them, too -- BUT if you think we
shouldn't do something in this proposal, then bring your own suggestions and
proposals for what we should do instead, making sure that the solution as
modified (or replaced) is still complete (technically, financially,
etc.). <br>
<br>
since we don't have anything to discuss about IF we should move or really even
WHEN we should move, the only question is HOW to preserve the archive and WHERE
to continue the main conversation. <br>
<br>
ideally, this would all happen when things quiet down a bit at the end of the
year, mid- to late-december. that's when i would be most able to support
these things. anyone else could do it sooner or later, but i do think
that distinguishing our two tasks, maintaining the archive AND continuing the
conversation, is a valuable way to think about this now.<br>
<br>
what can you contribute to this (new) beginning?<br>
<br>
m<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br clear=all>
<br>
--<br>
<br>
Michael Herman<br>
Michael Herman Associates<br>
<br>
<a href="http://MichaelHerman.com">http://MichaelHerman.com</a><br>
<a href="http://RonanParkTrail.com">http://RonanParkTrail.com</a><br>
<a href="http://ManorNeighbors.com">http://ManorNeighbors.com</a><br>
<a href="http://ChicagoConservationCorps.org">http://ChicagoConservationCorps.org</a><br>
<a href="http://OpenSpaceWorld.org">http://OpenSpaceWorld.org</a><br>
<br>
312-280-7838 (mobile)<br>
<br>
<br>
* * ==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU ------------------------------ To subscribe,
unsubscribe, change your options, view the archives of
oslist@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html To learn about OpenSpaceEmailLists
and OSLIST FAQs: http://www.openspaceworld.org/oslist <o:p></o:p></p>
</div>
</body>
</html>
*
*
==========================================================
OSLIST@LISTSERV.BOISESTATE.EDU
------------------------------
To subscribe, unsubscribe, change your options,
view the archives of oslist@listserv.boisestate.edu:
http://listserv.boisestate.edu/archives/oslist.html
To learn about OpenSpaceEmailLists and OSLIST FAQs:
http://www.openspaceworld.org/oslist