[MG] Minimal start plan - inter-community network

[conseo]

Am Tuesday 31 May 2011 schrieb Michael Allan:
> Thomas von der Elbe wrote:
> > I think the 4 maps are good! At least I cannot think of anything
> > better.  Its a lot of added complexity though. Whats hard for me to
> > imagine beforehand is the navigation between them (especially in
> > combination with zooming). Maybe a lot depends on that navigation. I
> > hope, you have a clearer picture of that than I, Mike.
> 
> The links in the detailed view (d) can do that job.  Select an item in
> the communities map for example, and (d) will show links to:
> 
>   * Polls the community participates in
>   * People who are active members of the community
>   * Topics the community discusses
> 
> Or select an item in the poll map, and you get links to:
> 
>   * Communities that are participating in that poll
>   * People who are participating in that poll
>   * Topics that poll is about
> 
> And so on for the other map types (people and topics).  In addition,
> when the topics map is filtered to a specific set of keywords -
> usually those of a community, poll or person - then it will also
> provide links to:
> 
>   * Communities that discuss (some or all of) those topics
>   * Polls about those topics
>   * People interested in those topics
> 
> In those views, you'll see exactly how many keyords are matched by
> each item.  This will indicate (very roughly) how interested each
> person is in the community, or each community in the poll, and so
> forth.  We might generalize this matching trick to sets of other
> items, aside from topics.  So, for the active membership of a
> community, which is a set of people, you would see:
> 
>   * Communities in which (some or all of) those people participate
>   * Polls in which they participate
>   * Topics that interest them
> 
> So links will provide navigation from map to map, as well as the
> filtering (zooming) of each map.  The feed will be filtered to match.
> 
> > The plan sounds good, for sure.
> 
> I guess the social tasks (s) are what drive it.  We need to find
> people with fire under their butts, then go to work to keep them happy
> with the tools.  There's no other way forward I can see.  Rationale:
> http://metagovernment.org/pipermail/start_metagovernment.org/2011-May/00402
> 4.html

+1 Maybe you can add a "resources" map (for economical planning) to the 
agenda, I'll do it once my exams are over (I am still thinking about it, 
although I have little time for developing atm.) I have talked with Thomas 
about my ideas and maybe he can ellaborate on that as well a bit with me (the 
agenda and integration with the current ideas about social maps). I will open 
a different thread for that if you have time to discuss plans about it, Thomas.

conseo



> 
> > On Sat, 28 May 2011 16:55, Michael Allan wrote:
> > > I have a design and plan to propose.  Very roughly:
> > > 
> > > DESIGN
> > > ------
> > > 
> > > Four new maps for crossforum theatre: [1]
> > > 
> > >     i. Communities
> > >    
> > >    ii. People
> > >   
> > >   iii. Topics
> > >   
> > >    iv. Polls
> > > 
> > > The structure is the same for each map.  The map consists of three
> > > 
> > > main visual components, from top to bottom:
> > >    (d) Detailed view of selected item.
> > >    
> > >    (g) Graph of all items.
> > >    
> > >    (t) Table of all items.
> > > 
> > > (t) The table is the main component.  It lists each item in a paged
> > > viewport (page up/down to see all).  For example, the table in the
> > > community map will normally list all known communities.  The rows may
> > > be sorted according to any columnar value.  Clicking on the 'size'
> > > column in the community table, for example, will sort the rows by the
> > > number of community members (i.e. subscribers to mailing list, or
> > > whatever).  Clicking again reverses the order.
> > > 
> > > (g) The graph shows all items (x axis) and plots the value of the
> > > currently sorted column (y axis).  For example, you might see a bar
> > > graph of communities from the largest (left) to the smallest (right).
> > > Items in the graph are highlighted by events in the feed, of
> > > course. [2]
> > > 
> > > (d) The detailed view shows further details of the currently selected
> > > item.  It includes links to other maps and views.
> > > 
> > > The scoping of any map may be resticted to a single item from one of
> > > the other maps.  For example, you may restrict the community map to
> > > show only the communities of a particular person, topic or poll.  And
> > > so on for all combinations of the four maps.
> > > 
> > > By itself, this design does not meet all of the requirements [3].  But
> > > I think we can meet them by adding sub-views, mini-tools and other
> > > details to the basic design.  For example, to support lateral
> > > extension (M.1-3) we might add a 'crossforum membership' column in the
> > > community table that shows how many of your collaborators are members
> > > of each community [4].  Vitality and vital rank (F.iii.c, d) can be
> > > projected in a heads-up display over the graph component of the
> > > community map - though only for certain views/scopes - and these can
> > > be the views that are linked from the discussion medium (design
> > > problem 4).
> > > 
> > > PLAN
> > > ----
> > > 
> > > Most of these tasks can be done in parallel:  (t) tech (s) social
> > > 
> > >      1. (t) Add support for communities (S.1, 2) to the pollwiki.
> > >      
> > >      2. (s) Decide which topics and issues to seed.  Create the
> > >      
> > >             necessary community pages.  Plan seeding.
> > >      
> > >      3. (t) Code the forum harvesters for the key communities in the
> > >      
> > >             seeding plans (2).  If we have new developers, maybe they
> > >             could coordinate with C on this.
> > >      
> > >      4. (s) Organize outfit (H).
> > >      
> > >      5. (t) Code the new maps, beginning with the community map.
> > >      
> > >      6. (s) Execute seeding plans (2).
> > > 
> > > What do you think?
> > > 
> > > 
> > > NOTES
> > > -----
> > > 
> > >   [1] http://zelea.com/project/votorola/a/crossforum/theatrePlan.png
> > >   
> > >   [2] Items in the table are highlighted too, when they are visible in
> > >   
> > >       the viewport.
> > >   
> > >   [3]
> > >   http://metagovernment.org/wiki/User:Michael_Allan/Seeding_an_inter-c
> > >   ommunity_network
> > >   
> > >   [4] This would depend on the user listing his/her crossforum
> > >   
> > >       collaborators as a registration property.  You would then see the
> > >       degree of cross-membership only with regard to the people who
> > >       will actually collaborate with you in lateral ventures such as
> > >       delegation, nomination or colonization (maybe voters and
> > >       candidate by default).
> > >       
> > >       http://metagovernment.org/wiki/Template:Draft
> 
> _______________________________________________
> Start : a mailing list of the Metagovernment project
> http://www.metagovernment.org/
> Post to the list: Start at metagovernment.org
> Manage subscription:
> http://metagovernment.org/mailman/listinfo/start_metagovernment.org




Originally posted to the mailing list of the Metagovernment Project:
http://metagovernment.org/mailman/listinfo/start_metagovernment.org