<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>[top-politics] Re: Definition of TOP - Systematization</title>
    <link>http://leparlement.org/Re_Definition_of_TOP_Systematization_19/vote.rss</link>
    <description>[top-politics] Re: Definition of TOP - Systematization</description>
    <item>
      <title>[top-politics] Re: Definition of TOP - Systematization</title>
      <vote>3</vote>
      <pubDate>2006-09-25 19:51:15+0200</pubDate>
      <link>http://leparlement.org/Re_Definition_of_TOP_Systematization_27/vote.rss</link>
      <comments>http://leparlement.org/Re_Definition_of_TOP_Systematization_27/vote.rss</comments>
      <dc:creator>Serge</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;Hey,&lt;/p&gt;
&lt;p&gt;First of all I agree with Gale that defining a system as &lt;span class="caps"&gt;TOP&lt;/span&gt; although
slightly redundant, leaves a lot less room for misinterpretation that
&amp;#8220;open system&amp;#8221; would, and remains concise enough to be acceptable.&lt;/p&gt;
&lt;p&gt;Secondly, is it right to say that we agree that the aim of this group
is for a &lt;span class="caps"&gt;TOP&lt;/span&gt; system allowing for such things as proxy voting, signal
amplification over noise (filters), etc to be implemented freely and
easily by any &lt;span class="caps"&gt;TOP&lt;/span&gt; organization wanting to?&lt;/p&gt;
&lt;p&gt;If yes, why don&amp;#8217;t we start try and get more developpers involved to
build on leparlement, defining the specifics of the software, and
testing it all the while through using leparlement as a platform for
discussion/decision/vote??&lt;/p&gt;
&lt;p&gt;&lt;a class="readMore" href="#" onclick="Element.hide(this); Element.removeClassName(this.parentNode.nextSibling, 'tooLarge'); return false;"&gt;Read more&amp;#8230; / Lire plus&amp;#8230;&lt;/a&gt;
&lt;div class="tooLarge"&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Serge&lt;/p&gt;
&lt;/div&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] The state of parlement</title>
      <vote>2</vote>
      <pubDate>2006-09-29 01:44:44+0200</pubDate>
      <link>http://leparlement.org/The_state_of_parlement/vote.rss</link>
      <comments>http://leparlement.org/The_state_of_parlement/vote.rss</comments>
      <dc:creator>echarp</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;On Tue, Sep 26, 2006 at 03:23:35AM -0000, Serge wrote:&lt;br/&gt;&lt;/p&gt;
&lt;p&gt;&amp;gt; We also would need to have a proposal at hand for what the system
&amp;gt; should be able of doing (Emmanuel do you have such a definition
&amp;gt; document?). Then again it&amp;#8217;s not like it needs to be all slick and
&amp;gt; pretty since these documents are openstanding, it is more to provide a
&amp;gt; reasonable amount of information and direction for people to catch up
&amp;gt; on the idea and decide if they are interested and want to participate.
&amp;gt; Once the starting elements are there, it&amp;#8217;s all about publicity. Talk
&amp;gt; on message boards forum, talk with political bloggers, email your
&amp;gt; address book about it, whatever you can think of to spread the
&amp;gt; word&amp;#8230;.&lt;/p&gt;
&lt;p&gt;I don&amp;#8217;t have much documents besides our discussions and
&lt;a href="http://leparlement.org"&gt;parlement&lt;/a&gt; itself. Somehow, there is also
&lt;a href="http://rubyforge.org/projects/parlement"&gt;rubyforge&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Basically, here are the already implemented features:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;threaded forum&lt;/li&gt;
	&lt;li&gt;&lt;span class="caps"&gt;RSS&lt;/span&gt; feed for latest posts &lt;strong&gt;and&lt;/strong&gt; most popular posts&lt;/li&gt;
	&lt;li&gt;login (optional password/email)&lt;/li&gt;
	&lt;li&gt;each post is also a forum&lt;/li&gt;
	&lt;li&gt;each post is also a mailing list&lt;/li&gt;
	&lt;li&gt;server replication (in real time by mail)&lt;/li&gt;
	&lt;li&gt;spam filtering (basic)&lt;/li&gt;
	&lt;li&gt;votes: -1, 0 or +1&lt;/li&gt;
&lt;/ul&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;a class="readMore" href="#" onclick="Element.hide(this.parentNode.parentNode); Element.removeClassName(this.parentNode.parentNode.nextSibling.nextSibling, 'tooLarge'); return false;"&gt;Read more&amp;#8230; / Lire plus&amp;#8230;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="tooLarge"&gt;
&lt;ul&gt;
	&lt;li&gt;avatars&lt;/li&gt;
	&lt;li&gt;personal display filter&lt;/li&gt;
	&lt;li&gt;posts can be positioned&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;a class="readMore" href="#" onclick="Element.hide(this); Element.removeClassName(this.parentNode.nextSibling, 'tooLarge'); return false;"&gt;Read more&amp;#8230; / Lire plus&amp;#8230;&lt;/a&gt;
&lt;div class="tooLarge"&gt;&lt;/p&gt;
&lt;p&gt;In the future:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;long posts shortened for display (tomorrow)&lt;/li&gt;
	&lt;li&gt;easy installation&lt;/li&gt;
	&lt;li&gt;electoral lists&lt;/li&gt;
	&lt;li&gt;&lt;span class="caps"&gt;PGP&lt;/span&gt; signatures&lt;/li&gt;
	&lt;li&gt;delegations&lt;/li&gt;
	&lt;li&gt;range votes&lt;/li&gt;
	&lt;li&gt;irc interaction&lt;/li&gt;
	&lt;li&gt;individual votes life span&lt;/li&gt;
	&lt;li&gt;web page updated in real time (chat)&lt;/li&gt;
	&lt;li&gt;voucher for anonymous pseudonym obtention&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are no roles, ranks, agendas, private settings, or obscured data.
Everything is transparent, but for passwords (which are recorded as
salted hashes and not replicated).&lt;/p&gt;
&lt;p&gt;Poll results will be calculated according to a given electoral list.
Which would thus act as a caucus of sorts. Anybody will be able to setup
any number of electoral lists.&lt;/p&gt;
&lt;p&gt;Anyone who has already posted to top-politics already has a parlement&amp;#8217;s
pseudo. It is the same as your mail&amp;#8217;s name. Me for example, it&amp;#8217;s
&amp;#8220;echarp&amp;#8221;. Don&amp;#8217;t hesitate to try it. You can, among other things, set up
your avatar ;)&lt;/p&gt;
&lt;p&gt;Come and have a talk on &lt;a href="http://VirtualMeetup.our-constitution.org"&gt;irc&lt;/a&gt;
(you need to have java on your machine).&lt;/p&gt;
&lt;p&gt;echarp &amp;#8211; &lt;a href="http://leparlement.org/irc"&gt;http://leparlement.org/irc&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/p&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: Definition of TOP - Systematization</title>
      <vote>2</vote>
      <pubDate>2006-09-19 15:41:32+0200</pubDate>
      <link>http://leparlement.org/Re_Definition_of_TOP_Systematization_21/vote.rss</link>
      <comments>http://leparlement.org/Re_Definition_of_TOP_Systematization_21/vote.rss</comments>
      <dc:creator>Serge</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;Hey,&lt;/p&gt;
&lt;p&gt;Your reply seems to show that a definition of transparency _ open _
public as separate parts would remain necessary, however close their
principle are could be useful. Using only the word open seems to have
triggered the misunderstanding that it would be a &amp;#8220;mindless&amp;#8221; opening,
while the transparency definition does state at this point that:
&amp;#8220;A transparent organization must ensure full, accurate, and timely
disclosure of actions and information. Its actions and their
justifications must remain intelligible and clear.&amp;#8221;&lt;/p&gt;
&lt;p&gt;Also I agree with your statement that delegable proxy can and should be
used to reduce noise etc, as has been discussed and agreed in previous
posts.&lt;/p&gt;
&lt;p&gt;regards,&lt;br/&gt;
Serge&lt;/p&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: The state of parlement</title>
      <vote>1</vote>
      <pubDate>2006-10-14 03:05:35+0200</pubDate>
      <link>http://leparlement.org/Re_The_state_of_parlement_2/vote.rss</link>
      <comments>http://leparlement.org/Re_The_state_of_parlement_2/vote.rss</comments>
      <dc:creator>illegale</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;+1&lt;/p&gt;
&lt;p&gt;This reminds me about compilating our recent intentions in order of
getting back to them when the time comes.&lt;/p&gt;
&lt;p&gt;&lt;span class="caps"&gt;ATB&lt;/span&gt;,&lt;br/&gt;
Gale&lt;/p&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: The state of parlement</title>
      <vote>1</vote>
      <pubDate>2006-10-14 03:03:28+0200</pubDate>
      <link>http://leparlement.org/Re_The_state_of_parlement_1/vote.rss</link>
      <comments>http://leparlement.org/Re_The_state_of_parlement_1/vote.rss</comments>
      <dc:creator>illegale</dc:creator>
      <description>&lt;p&gt;&lt;span&gt;+1 &amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&lt;/span&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: The state of parlement</title>
      <vote>1</vote>
      <pubDate>2006-10-11 15:17:02+0200</pubDate>
      <link>http://leparlement.org/Re_The_state_of_parlement/vote.rss</link>
      <comments>http://leparlement.org/Re_The_state_of_parlement/vote.rss</comments>
      <dc:creator>echarp</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;+1&lt;/p&gt;
&lt;p&gt;&amp;gt; I am copying your implemented features and planned additions on the
&amp;gt; wiki so we may try to find a synthetic vision of the features a system
&amp;gt; would need.&lt;/p&gt;
&lt;p&gt;Cool, definitely very cool!&lt;/p&gt;
&lt;p&gt;&amp;gt; Chiefly I&amp;#8217;d like to add that this needs to be as easy as possible to
&amp;gt; install and implement so as to raise the chance of organizations
&amp;gt; adopting it.&lt;/p&gt;
&lt;p&gt;&lt;a class="readMore" href="#" onclick="Element.hide(this); Element.removeClassName(this.parentNode.nextSibling, 'tooLarge'); return false;"&gt;Read more&amp;#8230; / Lire plus&amp;#8230;&lt;/a&gt;
&lt;div class="tooLarge"&gt;&lt;/p&gt;
&lt;p&gt;There are currently two dependencies: ruby on rails and PostgreSQL. The
only one bothering me is the DB. Anybody knows of a good ruby DB to
remove that dependency? (this would do the same trick as derby in a J2EE
project)&lt;/p&gt;
&lt;p&gt;&amp;gt; best regards,&lt;/p&gt;
&lt;p&gt;Thanks, take care&lt;/p&gt;
&lt;p&gt;echarp&lt;/p&gt;
&lt;/div&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: Definition of TOP - Systematization</title>
      <vote>1</vote>
      <pubDate>2006-10-06 16:14:43+0200</pubDate>
      <link>http://leparlement.org/Re_Definition_of_TOP_Systematization_45/vote.rss</link>
      <comments>http://leparlement.org/Re_Definition_of_TOP_Systematization_45/vote.rss</comments>
      <dc:creator>Markus Schatten</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;Dear Serge&lt;/p&gt;
&lt;p&gt;On Tuesday 19 September 2006 05:33, Serge wrote:&lt;br/&gt;&lt;/p&gt;
&lt;p&gt;&amp;gt; Dear Markus and members of the group,
&amp;gt;
&amp;gt; Most points seem valid, but I hope you won&amp;#8217;t take offense if I point
&amp;gt; out it&amp;#8217;s not a very engaging read.&lt;/p&gt;
&lt;p&gt;No offense at all ;-) It wasn&amp;#8217;t very engaging to write also, but it has to be 
done.&lt;/p&gt;
&lt;p&gt;&lt;a class="readMore" href="#" onclick="Element.hide(this); Element.removeClassName(this.parentNode.nextSibling, 'tooLarge'); return false;"&gt;Read more&amp;#8230; / Lire plus&amp;#8230;&lt;/a&gt;
&lt;div class="tooLarge"&gt;&lt;/p&gt;
&lt;p&gt;&amp;gt; I do believe that the medium is 
&amp;gt; (half) the message, and that for &lt;span class="caps"&gt;TOP&lt;/span&gt; to have any kind of traction with
&amp;gt; the public, its message must be absolutely as concise and clear as
&amp;gt; possible.&lt;/p&gt;
&lt;p&gt;I agree!&lt;/p&gt;
&lt;p&gt;+1&lt;/p&gt;
&lt;p&gt;&amp;gt;
&amp;gt; As you point out, and rightly so, my definition of &lt;span class="caps"&gt;TOP&lt;/span&gt; has elements
&amp;gt; missing. Surely some elements would need to be added, and others
&amp;gt; removed . However, expanding the level of detail beyond what consitutes
&amp;gt; the core of &lt;span class="caps"&gt;TOP&lt;/span&gt; for this introductory statement would be a mistake for
&amp;gt; two main reasons:
&amp;gt; &amp;#8211; While exceptions and numerous other things do need to be addressed,
&amp;gt; bundling everything in the same document will only make it unpalatable
&amp;gt; to anyone new to the discussion.
&amp;gt; &amp;#8211; While we can all agree on the fundamental meaning and goals of &lt;span class="caps"&gt;TOP&lt;/span&gt;
&amp;gt; politics, we need to be cautious about trying to include details from
&amp;gt; the start, as these details will probably be the points on which we
&amp;gt; disagree rather than the essentials &amp;#8211; and uselessly delay agreement on
&amp;gt; these essential points.&lt;/p&gt;
&lt;p&gt;I agree, this was an error of me to define everything in detail in only one 
document. But still, details have to be defined in special documents which 
should be referenced in the main one (so it should be understand that they 
are an integral part of it). Maybe we should take a law-writing approach e.g. 
use statements like &amp;#8220;this issue is defined in a special document&amp;#8221;, or &amp;#8220;if in 
doubt consult special elaboration&amp;#8221; etc.&lt;/p&gt;
&lt;p&gt;&amp;gt;
&amp;gt; Some posts raised the question of whether open and public are the same
&amp;gt; thing. I&amp;#8217;ll add that transparency is similar too. In my understanding,
&amp;gt; the three &lt;span class="caps"&gt;TOP&lt;/span&gt; principles are openness of contents (transparency),
&amp;gt; openness of structure (open), and openness of access (public). It is
&amp;gt; interesting to notice that controlling either information, system
&amp;gt; infrastructure, or access to a political system are widely used methods
&amp;gt; of hijacking of supposedly democratic gevernment systems. So how about
&amp;gt; creating a dedicated reference document for each of the three founding
&amp;gt; &lt;span class="caps"&gt;TOP&lt;/span&gt; principles? Or should we just see this as open politics, and not
&amp;gt; try to label rigidly the domains to which openness applies?
&amp;gt;&lt;/p&gt;
&lt;p&gt;This was allready been discused so I won&amp;#8217;t engage a new discussion here, but 
let me just tell that I like the pretty definition of &lt;span class="caps"&gt;TOP&lt;/span&gt; you stated ;-)&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;&amp;#8212; 
Markus Schatten, dipl. inf.&lt;br/&gt;
e-mail: &lt;a href="mailto:markus.schatten@foi.hr"&gt;markus.schatten@foi.hr&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://www.tiaktiv.hr"&gt;http://www.tiaktiv.hr&lt;/a&gt;&lt;/p&gt;
&lt;/div&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: Definition of TOP - Systematization</title>
      <vote>1</vote>
      <pubDate>2006-09-27 22:29:58+0200</pubDate>
      <link>http://leparlement.org/Re_Definition_of_TOP_Systematization_31/vote.rss</link>
      <comments>http://leparlement.org/Re_Definition_of_TOP_Systematization_31/vote.rss</comments>
      <dc:creator>illegale</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;Serge wrote:&lt;br/&gt;&lt;/p&gt;
&lt;p&gt;&amp;gt; Hey Gale,
&amp;gt;
&amp;gt; when you ask what we can do about that, I take &amp;#8220;that&amp;#8221; to mean &amp;#8220;If yes,
&amp;gt; why don&amp;#8217;t we start try and get more developpers involved to build on
&amp;gt; leparlement&amp;#8230;.&amp;#8221;. The answer I would have is pretty straightforward.
&amp;gt;
&amp;gt; For starters we need an accessible and compelling statement of
&amp;gt; intention (&lt;span class="caps"&gt;TOP&lt;/span&gt; definition).&lt;/p&gt;
&lt;p&gt;OK. That is the job we are doing right now.&lt;/p&gt;
&lt;p&gt;&amp;gt; We also would need to have a proposal at
&amp;gt; hand for what the system should be able of doing (Emmanuel do you have
&amp;gt; such a definition document?).&lt;/p&gt;
&lt;p&gt;&lt;a class="readMore" href="#" onclick="Element.hide(this); Element.removeClassName(this.parentNode.nextSibling, 'tooLarge'); return false;"&gt;Read more&amp;#8230; / Lire plus&amp;#8230;&lt;/a&gt;
&lt;div class="tooLarge"&gt;&lt;/p&gt;
&lt;p&gt;Indeed. People will need definition (is that right word?) of future
system in order of making people interested.&lt;/p&gt;
&lt;p&gt;&amp;gt; Then again it&amp;#8217;s not like it needs to be
&amp;gt; all slick and pretty since these documents are openstanding, it is more
&amp;gt; to provide a reasonable amount of information and direction for people
&amp;gt; to catch up on the idea and decide if they are interested and want to
&amp;gt; participate. Once the starting elements are there, it&amp;#8217;s all about
&amp;gt; publicity.&lt;/p&gt;
&lt;p&gt;So, you think we do not get too loud before first two things are
realised in satisfying manner? I do agree with this idea, as long as my
previous attempts of getting people interested withouth any &amp;#8220;catch&amp;#8221; is
actually far from satisfying experience. I believe we do indeed need to
have some &amp;#8220;product&amp;#8221; first.&lt;/p&gt;
&lt;p&gt;&amp;gt; Talk on message boards forum, talk with political bloggers,
&amp;gt; email your address book about it, whatever you can think of to spread
&amp;gt; the word&amp;#8230;.
&amp;gt;
&amp;gt; &lt;span class="caps"&gt;IMO&lt;/span&gt; it&amp;#8217;s not exactly easy to do, but it&amp;#8217;s really not that hard either,
&amp;gt; all it takes is to actually get the ball rolling.&lt;/p&gt;
&lt;p&gt;OK. &lt;br/&gt;
&lt;span class="caps"&gt;ATB&lt;/span&gt;,&lt;br/&gt;
Gale&lt;/p&gt;
&lt;p&gt;&amp;gt; 
&amp;gt; Regards,
&amp;gt; 
&amp;gt; Serge&lt;/p&gt;
&lt;/div&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: Definition of TOP - Systematization</title>
      <vote>1</vote>
      <pubDate>2006-09-26 10:35:57+0200</pubDate>
      <link>http://leparlement.org/Re_Definition_of_TOP_Systematization_30/vote.rss</link>
      <comments>http://leparlement.org/Re_Definition_of_TOP_Systematization_30/vote.rss</comments>
      <dc:creator>echarp</dc:creator>
      <description>&lt;p&gt;&lt;span&gt;+1 &amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&amp;#160;&lt;/span&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>[top-politics] Re: Definition of TOP - Systematization</title>
      <vote>1</vote>
      <pubDate>2006-09-26 05:23:35+0200</pubDate>
      <link>http://leparlement.org/Re_Definition_of_TOP_Systematization_29/vote.rss</link>
      <comments>http://leparlement.org/Re_Definition_of_TOP_Systematization_29/vote.rss</comments>
      <dc:creator>Serge</dc:creator>
      <description>&lt;p&gt;&lt;p&gt;Hey Gale,&lt;/p&gt;
&lt;p&gt;when you ask what we can do about that, I take &amp;#8220;that&amp;#8221; to mean &amp;#8220;If yes,
why don&amp;#8217;t we start try and get more developpers involved to build on
leparlement&amp;#8230;.&amp;#8221;. The answer I would have is pretty straightforward.&lt;/p&gt;
&lt;p&gt;For starters we need an accessible and compelling statement of
intention (&lt;span class="caps"&gt;TOP&lt;/span&gt; definition). We also would need to have a proposal at
hand for what the system should be able of doing (Emmanuel do you have
such a definition document?). Then again it&amp;#8217;s not like it needs to be
all slick and pretty since these documents are openstanding, it is more
to provide a reasonable amount of information and direction for people
to catch up on the idea and decide if they are interested and want to
participate. Once the starting elements are there, it&amp;#8217;s all about
publicity. Talk on message boards forum, talk with political bloggers,
email your address book about it, whatever you can think of to spread
the word&amp;#8230;.&lt;/p&gt;
&lt;p&gt;&lt;span class="caps"&gt;IMO&lt;/span&gt; it&amp;#8217;s not exactly easy to do, but it&amp;#8217;s really not that hard either,
all it takes is to actually get the ball rolling.&lt;/p&gt;
&lt;p&gt;&lt;a class="readMore" href="#" onclick="Element.hide(this); Element.removeClassName(this.parentNode.nextSibling, 'tooLarge'); return false;"&gt;Read more&amp;#8230; / Lire plus&amp;#8230;&lt;/a&gt;
&lt;div class="tooLarge"&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Serge&lt;/p&gt;
&lt;/div&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
