<div dir="ltr">On Sat, Jan 26, 2013 at 5:29 PM, Michael Allan <span dir="ltr"><<a href="mailto:mike@zelea.com" target="_blank">mike@zelea.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've been struggling with the planting part for a couple of days:<br>
<a href="http://zelea.com/w/User:Mike-ZeleaCom/G/p/vohall?oldid=6116#2._Grow_the_discussion" target="_blank">http://zelea.com/w/User:Mike-ZeleaCom/G/p/vohall?oldid=6116#2._Grow_the_discussion</a><br>
It's all wrong. I think I took the wrong approach. I finally<br>
realized my mistake. What I need first is to understand the practice<br>
in the leafy canopy, because that's what we need to *grow into*.<br>
<br>
I figure the basic unit of the canopy is a small group of 2-7 leaf<br>
drafters around a variant pipe.<br>
<br>
(+) (+)<br>
\ | (+)<br>
\ | /<br>
\ | /<br>
\ |/<br>
( )-----(+)<br>
|<br>
|<br>
<br>
They work on the draft in order to get it accepted in a patch relay.<br>
It's not just a question of passing it to the candidate below (as we<br>
originally thought), but rather to the entire branch or tree. Either<br>
a patch gets sunk pretty much everywhere it can possibly be applied<br>
(goes "wild"), or it goes nowhere. What follows from this?<br>
<br>
(a) The group doesn't need votes. That won't help in a patch relay.<br></blockquote><div><br></div><div style>[alex]<br>haha :-) That sounds funny.<br>If I decide to apply a patch, then this could be interpreted as giving my vote.<br>
It isnt necessary to model the giving of votes in an explicit way, its given implicitly, right?<br>At least that's how you sound<br>[/alex]</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
(b) They need *generally agreeable* content in the variant draft.<br>
There's no other way to get the patch accepted by the pipe<br>
minders downstream.<br>
<br>
(c) Win or lose, most of the members will eventually move on to<br>
other variants.<br>
<br>
(d) Groups are somewhat ad hoc. They don't always move as a unit,<br>
but may break up and reform in different combinations on<br>
different variants, depending on personal interest.<br></blockquote><div><br></div><div style>[alex]</div><div style>yes, this feels right</div><div style>[/alex]</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
So I'm thinking, maybe this is *also* how it starts? Differences at<br>
the earliest stage would be:<br>
<br>
(s) Not many groups, ofc. Initially there's just a single group<br>
working on a single variant in one of the component branches.<br>
<br>
(t) Almost no patches have been accepted yet. The text is small.<br>
<br>
(u) Every patch is pretty much guaranteed to be accepted. NOT GOOD<br>
<br>
I think (t) is an advantage, because it makes the text accessible.<br>
But (u) is a danger. It's unrealistic. We want a consensus that<br>
everyone affected can agree to, not just one group. So maybe this is<br>
where we connect with forums? We use them to:<br>
<br>
(f) Give us a quorum. We ask for an informal thumbs up/down on each<br>
patch relay. If the public doesn't like it, then we hold off.<br>
<br>
(g) Give us ideas for (b).<br>
<br>
Maybe this kind of "public consultation" would always be a good idea,<br>
even when the canopy was buzzing with activity. It feels like the<br>
right way to connect with a larger public. Of course, we might also<br>
expect to attract new users from forums. But we'd never have to push<br>
for that. All we'd really need is (f) and (g).<br></blockquote><div style><br>[alex]<br>by the way, your diagrams are hard to read, because somehow the font google mail uses often distorts them very much.<br><br>reagarding (f) and (g), i dont understand who that should look like in practice and all the examples i can make up dont feel right<br>
[/alex]<br><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Anyway, I wanted to share what I'm thinking before I try (once again)<br>
to diagram it. It may take a while.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Michael Allan<br>
<br>
Toronto, <a href="tel:%2B1%20416-699-9528" value="+14166999528">+1 416-699-9528</a><br>
<a href="http://zelea.com/" target="_blank">http://zelea.com/</a><br>
_______________________________________________<br>
Votorola mailing list<br>
<a href="mailto:Votorola@zelea.com">Votorola@zelea.com</a><br>
<a href="http://mail.zelea.com/mailman/listinfo/votorola" target="_blank">http://mail.zelea.com/mailman/listinfo/votorola</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div style="color:rgb(34,34,34);font-family:arial,sans-serif"><br>Best Regards / Mit freundlichen Grüßen</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">
***********************************************</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">Alexander Praetorius</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">Rappstraße 13</div>
<div style="color:rgb(34,34,34);font-family:arial,sans-serif">D - 60318 Frankfurt am Main</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">Germany</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">
<b>[skype] </b>alexander.praetorius</div><div style="color:rgb(34,34,34);font-family:arial,sans-serif"><b>[mail] </b><a href="mailto:alexander.praetorius@serapath.de" target="_blank">citizen@serapath.de</a></div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">
<b>[web] </b><a href="http://wiki.piratenpartei.de/Benutzer:Serapath" target="_blank">http://wiki.piratenpartei.de/Benutzer:Serapath</a> </div><div style="color:rgb(34,34,34);font-family:arial,sans-serif">***********************************************</div>
</div>
</div></div>