Hello,<br><br>I want to note that even if we are not commenting on everything here your comments are being taken seriously and will be taken into account for the planning of future events. So I invite everyone to write down your impressions of the weekend so we can learn from mistakes and make things better the next time!<br>
<br>Greetings,<br>Jerry<br><br>P.S. I know the focus has been on the negative parts of the conference, but if you found anything positive, please also point out those parts of the weekend :)<br><br><div class="gmail_quote">
On Tue, Apr 20, 2010 at 11:53 PM, Andrew Norton <span dir="ltr"><<a href="mailto:ktetch@gmail.com">ktetch@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div class="im">On 4/20/2010 4:43 PM, Ole Husgaard wrote:<br>
> Hi,<br>
><br>
> I think everybody who went to the conference agrees that there were a<br>
> lot of problems. Now is the time to evaluate: What went wrong, and how<br>
> can we make it better next time? How can we make PPI better? How can we<br>
> make the PPI statutes better?<br>
<br>
</div>1) I think the key thing was that things were set up before the event.<br>
There wasn't a final draft of the statutes until the day of the<br>
conference, even though as recently as the Monday before, they were<br>
promised (at the coreteam meeting) to be done by the 13th. Without<br>
knowing exactly what was being voted, there was no way to debate and<br>
*think* about the statutes before being asked to vote on them. If we had<br>
all recieved a first draft, say 3 weeks beforehand, with another week<br>
for any alterations, amendments and counter-proposed statutes to be sent<br>
in, then a complete set of statutes, some with multiple proposals would<br>
have been released in plenty of time for parties to discuss and debate them.<br>
<br>
2) There was also some question over voting. As someone else explained<br>
earlier, many people are unfamiliar with how the voting system worked (I<br>
am not one of them, and for the record, while I was a candidate, I don't<br>
have an issue with the result, only concerns over the process). If<br>
people don't know how the system interprets their votes and uses them to<br>
determine the result, then how they voted may not be reflected in the<br>
actual results their votes generate. Personally, I don't feel this<br>
voting system is the best for this task, as it places excessive<br>
influence on 'first choice', when it was more a case of 'pick four'.<br>
This system is more appropriate when either a) the candidates have very<br>
differing policies or b) when there is a large number of voters. When<br>
there are 20-30 voters, 8 candidates for 4 positions, it doesn't work so<br>
well. The flaw is that if a candidate gets a lot of 2nd and 3rd place<br>
choices, but little/few first place votes, they can be eliminated, even<br>
if the majority feels them capable of holding one of the seats.<br>
<br>
3) The third issue is the schedule itself. The event was held in Europe,<br>
and was (with exceptions for the weather) fairly accessable for the<br>
european parties. It was extremely inaccessable, physically, for the<br>
non-European party delegates. The issue then becomes one of timing. With<br>
the vast majority of the 'local' party reps in attendance, and those<br>
distant doing so remotely, the timings were most convenient for the<br>
local parties. The 9am start is very handy for those in Brussles, but if<br>
you're in the Americas, it's anywhere between 4am and midnight making it<br>
already difficult to attend. A later start would have been preferable<br>
for the north, south and Central american party perspectives (although<br>
it would have meant it was a later start for the Australian and NZ party<br>
reps, who were 8-11 hours ahead of the conference). however, the timing<br>
issue could mainly be defeated with point 1, as they could have 'postal<br>
voted'. Timetables for future events should take into consideration that<br>
PPI is not just a local or regional thing, but a worldwide thing.<br>
<br>
4) sticking to the schedule. This was one of the most annoying ones as a<br>
remote viewer. A 10 or 15 minute break went on for close to 40, and<br>
nothing was said. An hour later, there was another quick break, that<br>
lasted for at least twice as long as it was supposed to. It was rather<br>
unfair to the remotes again. If a 10 minute break was called, and the<br>
physical delegeates were ready to go after 10 mins, but none of the<br>
remote ones were, would the break have continues, or would the event<br>
have resumed? I think the latter. If a 10 minute break is called, then<br>
it should be a 10 minute break only, if there are no physical delegates<br>
present when the meeting restarts, that's their problem, just as it was<br>
the remote delegates problem if they were not physically at their<br>
keyboards throughout.<br>
<br>
5) remote delegate participation. This was overall a big problem. The<br>
ability to participate for remote delegates was poor. I know the best<br>
was done, but it was very hard for a remote delegate to make an<br>
alternate proposal, unlike a physical one. The best comparison is that<br>
of a 'TV phone-in-poll', a bit like Big Brother (Ha!). The problems were<br>
best shown when the camera was knocked on Saturday, leaving it pointing<br>
upwards. It took a while before whoever could fix it did. I even<br>
messaged one of the 3 at the front, saying that the camera needed to be<br>
fixed, and he replied "not my problem...". It wouldn't have taken but a<br>
few seconds to say 'hold on a second, can someone back there fix the<br>
camera, it's been knocked out of place... ok great, please continue'.<br>
This camera was not just the only way remote delegates had to<br>
participate, but it was also the permanent record of the conference<br>
(minutes and transcripts can be derived from the video, video can't be<br>
derived from transcripts)<br>
<br>
6) Funding. This was, again, a kick in the teeth for many. That those<br>
with the cheapest travelling costs, were getting it subsidised by<br>
another body, while those with vastly more expensive travel were not. If<br>
the finding was something that was discovered after the date+place had<br>
been set, that would be one thing, but when these things are set<br>
specifically for this in mind, it's quite another. This is after all the<br>
5th meeting, and it's the 5th one in Europe (Vienna, Berlin, Uppsala,<br>
Helsinki and now Brussels) it means that every single meeting has been<br>
'cheap' to attend for EU parties, and expensive for the rest. Hopefully<br>
the next one will NOT be in the EU/Europe (or funding for non-European<br>
parties to help them physically participate be found).<br>
<br>
That's the main ones off the top of my head. There may be more.<br>
<br>
Andrew<br>
<div class="im"><br>
<br>
><br>
> When evaluating it is useful to look at the arguments of people<br>
> dissenting. The Swedes were dissenting, and one of the Swedes attending<br>
> the conference (though not as a delegate) wrote an interesting blog<br>
> entry in English, which I hope you want to read and perhaps comment on:<br>
> <a href="http://schonning.wordpress.com/2010/04/20/controversies-in-the-ppi-conference/" target="_blank">http://schonning.wordpress.com/2010/04/20/controversies-in-the-ppi-conference/</a><br>
><br>
> Best Regards,<br>
><br>
> Ole Husgaard.<br>
><br>
> ____________________________________________________<br>
> Pirate Parties International - General Talk<br>
> <a href="mailto:pp.international.general@lists.pirateweb.net">pp.international.general@lists.pirateweb.net</a><br>
> <a href="http://lists.pirateweb.net/mailman/listinfo/pp.international.general" target="_blank">http://lists.pirateweb.net/mailman/listinfo/pp.international.general</a><br>
<br>
</div>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.10 (MingW32)<br>
<div class="im">Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>
</div>iQEcBAEBAgAGBQJLziJkAAoJECjjuYTW3X5HmWYH/RCVyDUeWMHM55Qe2qN2SwPY<br>
uC1YuXHzQGF6Ad0sCuUf4dC28Jm/SLQSy2bGq1uwoluQxDFF4YGHyTZOkYj2W1G1<br>
pU0GqOASZ4cacCFqusigyUZdkFlkXUt3cSGReGK2JiAlfPx9IRoa0jys8Nk05gus<br>
GY+vG28oEYpkx7LtR+cYz0E11InjPJr5iHnGNVmeSxfdIW4rHlrzkm/V5SdkElkB<br>
qgAuUUHrBookG/K/aB99DstALOs27eyWiq+VD/+FtoHDKLkz9CnGfMRXkcB/Arra<br>
wWDbtLvFPxNMAC38La9PbbXwYF+2N0g5TpbvKSUvjyl9moQicty0RuD+CLRIPOE=<br>
=3Wo+<br>
-----END PGP SIGNATURE-----<br>
<div><div></div><div class="h5">____________________________________________________<br>
Pirate Parties International - General Talk<br>
<a href="mailto:pp.international.general@lists.pirateweb.net">pp.international.general@lists.pirateweb.net</a><br>
<a href="http://lists.pirateweb.net/mailman/listinfo/pp.international.general" target="_blank">http://lists.pirateweb.net/mailman/listinfo/pp.international.general</a><br>
</div></div></blockquote></div><div style="margin: 2em 0pt;" name="sig_654775721b">Weyer Jerry<br>
PPI Co-Chairman<br></div><br>