[Imc-leeds] common grounds - snapshot

Wed May 7 06:31:41 PDT 2003

Thanks a lot.
----- Original Message -----
From: ionnek <ionnek@gmx.net>
To: <imc-leeds@lists.indymedia.org>
Sent: Tuesday, May 06, 2003 10:00 PM
Subject: [Imc-leeds] common grounds - snapshot


> hi leeds,
> just read that you're planning a meeting, so thought in case you haven't
> seen this guide through the indyjungle, I send it.
> There is a "virtual" meeting this friday evening on irc, #uk - maybe some
> of you have time to join in? Details are either on  [imc-uk-process or
> imc-uk-network].
>
> good luck with your meeting!
> ionnek
>
> ----
> please note: this snapshot from 29 Apr 2003 is an effort to to describe
the
> present shared working practices on uk.indymedia.org and the development
of
> the new IMC UK mir site - i.e. the consensus that we have developed over
> the past few weeks/months.
> An introduction to the document is archived at
>
http://lists.indymedia.org/mailman/public/imc-uk-process/2003-April/001145.h
tml
> .
>
> ---
>
> WORKING PRACTICES ON uk.indymedia.org/ mir
> ...in a nutshell:
> uk.indymedia.org is a DIY project based on collaboration of a network. If
> you want something done, read the manual (scattered across lists and
twiki)
> and go ahead - sometimes this just involves "doing it", sometimes you'll
> need to make a proposal to the appropriate list. Sometimes you might not
be
> able to "do it yourself" - in that case you'll have to convince someone
> else to do it for you. If you have a problem with the documentation of any
> aspect of imc, improve it or find someone to do the job. Same goes for the
> functionality or aesthetics of the site and for the communication within
> the network.
> uk.indymedia.org is a collaborative project of local imc groups who agree
> on some basic common grounds. Participation involves taking responsibility
> for shared tasks and gives each group access to the knowledge and
resources
> of other groups. Transparency is crucial - especially on the tech side.
> uk.indymedia.org is run by volunteers. A part from agreed shared tasks,
> everything relies on the motivation of individuals or groups - a good
> reason to maintain a spirit of solidarity and support in our
communication.
>
> LONG VERSION
>
> I. historical bits
>
> Since a few months, imc uk has kicked off as a network.
> In the first years, imc uk was mainly maintained by a group in London - we
> simply could not find other imc groups in the uk who were willing to join
> in. Then the network slowly started to build. Bristol set up their
separate
> website, Scotland is working on one. Imc uk temporarily hosted imc ireland
> while they were setting up their separate site. Manchester and Scottland
> asked for subsections on the UK page. We started to have network meetings.
> Lancester, Sheffield and Leeds joined in. Oxford and Cambridge applied for
> imc lists. The contact page was updated to include new groups
>
[http://lists.indymedia.org/mailman/public/imc-uk-network/2003-March/000253.
html].
>
> Several groups started to share "housekeeping duties" like newswire
> cleaning, the editorial guidelines were updated
>
[http://lists.indymedia.org/mailman/public/imc-uk-process/2003-March/001105.
html].
> (...add more to
> http://docs.indymedia.org/view/Local/UkMirAboutDraft)
>
> II. Migration to MIR - a collaborative project
>
> The first major project of the imc - United Kollective network is the
> migration to mir. This is much more than just a change of software. It is
> the outcome of a years long process to establish imc uk as a network of
> local imc groups who work together on a shared website, to build a
platform
> where people from all over the country can share information/news.
> The final deadline of the migration, the looks of the site, and the way we
> set up the admin depends on the input of each imc group.
> The development of the MIR site works a bit like opensource software
> developing, very pragmatic. Some people do things, then it's wait and see
> if others take them up.
> At the same time, imc uk has elements of a more structured, collective
> approach, because there are some things that we have to find consensus
about.
>
> Example: A while ago, Oxford made a proposal about a shared colour scheme
> on regional pages.
>
http://lists.indymedia.org/mailman/public/imc-uk-tech/2003-April/000864.html
> It was possible that regional groups go for one of the existing designs.
It
> was also possible that some groups come up with their own design. We could
> choose to leave this decision to local groups, or we could try to find a
> firm consensus about the colour scheme. This would probably have taken a
> while, until all existing imc groups have discussed amongst themselves,
> decided and come to an agreement with each other. So it was a matter of
> finding a balance between motivation/autonomy on one side and
> "branding"/functionality on the other. In this example, a solution for the
> proposal was found on the tech list, without activating the entire
> decision-making machinery.
>
> III. uk.indymedia.org Communication tools
>
> The consensus process is non-hierarchical, there is no formal
> decision-making body of delegates. But some communication tools for
sharing
> knowledge, discussion and decisionmaking have developed. Generally, things
> are being discussed in a variety of communication channels, before they
> come up as a proposal.
>
> /1 face to face meetings
> Although we are using a variety of electronic communication channels,
local
> imc groups rely on face to face meetings in intervals that suit them,
> mostly announced on their publicly archived imc list. If they don't get
> round to publicly announce their regular f2f meetings, they make sure to
> also hold open and public meetings (more...)
>
> /2 Lists
> Every local imc group currently liaises with some uk lists:
> [imc-uk-network] for information, [imc-uk-process] for discussion,
> developing proposals etc, [imc-uk-tech] to sort out how to do things.
> If things go well, consensus emerges from [imc-uk-process]. If it doesn't,
> things can be further discussed or eventually be brought to a face-to-face
> network meeting.
> The migration to mir, for example, has been "in the air" for more than a
> year, but it gathered momentum when a critical mass of imc groups agreed
to
> it at the Lancester network meeting.
> Every imc worldwide is committed to be in touch with some global imc
lists.
> Reports from global lists are fed to [imc-uk-process]. Sometimes, global
> lists are asking for feedback.
> It is important to be aware that silence on the lists is generally read as
> agreement. When a proposal goes up and nobody objects or amends, it is
> usually assumed that it can go ahead. But again, this is not a fixed rule.
> If I propose tomorrow to close down imc uk, silence might simply mean that
> people assume that I'm mad.
>
> /3 Network Meeting
> Every local imc group can propose a f2f network meeting. If a critical
mass
> of local groups agrees that a network meeting is needed or that it would
be
> fun, time and place are being sorted. Probably, the network meetings
> generate the most firm decisions, people tend to stick what they say at
f2f
> meetings. Minutes are being published on [imc-uk-network].
>
> /4 irc (internet relay chat)
> The channels on Irc.indymedia.org is helpful to discuss things, establish
> common grounds, work out how to proceed, share infos, knowledge and
> resources. Irc logs are being archived on the appropriate list. Irc is a
> forum to sort out practical details, to coordinate working groups, to
share
> skills and knowledge. While major proposals often develop on irc. But irc
> is not a decision making channel, because so far, only few imc uk'ers use
it.
>
> /5 twiki
> imc uk uses the indymedia twiki on [docs.indymedia.org]. Twiki is a piece
> of opensource server software that allows users to freely create and edit
> Web page content using any Web browser. Everybody can register on the
twiki
> and start using it.
> A special site has been set up for the migration to mir:
> http://docs.indymedia.org/view/Local/MovingToMir
> At the moment, it's mainly used to document the move to mir - links to
> discussions the the email lists or irc logs, tools for the development of
> the site and regional pages, documentation of technical and admin details.
> Hopefully, it will develop into a manual for admin, customising local
> sites, coding and the new imc process. Like irc, twiki is not a decision
> making body, because not many imc uk'ers are using it so far.
>
> IV. Shared tasks
>
> imc uk has developed a supportive attitude. People help each other out
with
> major and minor questions, and generally respect each others work and
> listen to each others points of views.
> Some tasks are shared between all local imc groups who work on
> uk.indymedia.org:
>
> /1 crucial from the beginning: liaising with 3 uk lists: [imc-uk-network],
> [imc-uk-process], [imc-uk-tech].
>
> /2 liaising with global lists:
> Every imc worldwide is committed to be in touch with some global imc
lists:
> [imc-finance], [imc- process], [imc-communication], [new-imc].
(complete??)
> There are a few other useful lists, like [imc europe].
> Since imc uk is a network, we can share this workload between the local
> groups. Each group should be prepared to take on a global list for some
> time and occasionally forward reports from those lists to
[imc-uk-process].
> Sometimes, global lists are asking for feedback.
>
> /3 list admin:
> The administration of the shared [imc-uk] lists rotates within the local
> imc uk groups, both to share the workload and to make sure that power is
> decentralised. Presently, the network uses mainly [imc-uk-network],
> [imc-uk-process], [imc-uk-features], [imc-uk-tech].
>
> /4 newswire cleaning
> Presently, on the imc uk active site, every newswire posting goes straight
> to the frontpage. Admins from local imc groups then screen the newswire
and
> hide postings if necessary according to the editorial guidelines. With the
> new MIR side, we have the option to use different models (dutch model,
> german model).
> Example: In imc-germany, every posting goes to the "open posting newswire"
> which is NOT on the front page. Moderators screen the open newswire, and
> "promote" postings, either to the frontpage newswire, or to one of the
> topics, or to a "feature" (middle column). Some postings are hidden.
> The main point is that all regional pages on imc uk mir will continue to
> share one database for newswire postings, i.e. the regional imcs will have
> to take responsibility to look after the main newswire, not only after
> their own.
>
> /5 features:
> Presently, features for the imc uk middle column on the active site are
> being proposed on [imc-uk-features]. All local imc groups are responsible
> to look after the uk middle column.
> On the IMC UK Mir page, each imc group with their own site will produce
> their own features. In addition, the startpage of uk.indymedia.org will
> also have features. We haven't discussed yet how these will be generated.
> Options are:
> - to generate them automatically from the local middle columns (needs a
> tech to implement).
> - to generate them manually, for expl by a dedicated startpage features
> group, a dedicated list, individuals or a mix of all.
>
> V. Setting up a regional page on IMC UK mir
>
> To run a regional page on IMC UK mir means to be part of a network. Each
> local imc group that runs a regional page on IMC UK mir positions itself
on
> the common grounds of the uk network, agrees to the "principles of unity"
> and takes on some of the shared tasks. The following paragraphs refer to
> those groups who are working on the uk.indymedia.org site - I assume that
> separate sites like Bristol have their own process.
> uk.indymedia.org sometimes offers emerging imcs a temporary subpage, while
> they are preparing their own site. Imc ireland is an example from the
past,
> imc scotland is an example for the present. The degree of involvement in
> shared tasks and communication is being negotiated as things emerge,
> depending on specific situations.
>
> /1 common grounds
> * Agree with the UK Mission statement
> At the moment, we are using the old imc uk mission statement. A proposal
to
> work on it has been made on
>
[http://lists.indymedia.org/mailman/public/imc-uk-network/2003-March/000254.
html]
> on march 26. A draft on the twiki includes all the changes that have been
> suggested in response to this proposal
> [http://docs.indymedia.org/view/Local/UkMirMsDraft]
> * Agree with the current Working practices of the site [link]
> The paragraphs on communication (III) and shared tasks (IV) sum up some of
> the current working practices of uk.indymedia.org. It would be good to
work
> on and discuss a document which can be approved by the uk.indymedia.org
> network.
> * Agree in Spirit to the "Principles of unity" [link]
> The global indymedia community shares a set of "principles of unity", I'm
> sending them in a separate mail. For the UK, these could be re-written to
> be a bit more user friendly!
> * Have open and public meetings
> This is to make sure that indymedia uk has a presence outside the virtual
> world of digital communication channels, to encourage local participation,
> transparency and face to face contact. (...more?)
> * Participate in outreach of uk.indymedia.org to local groups, encouraging
> more people to understand and use the site.
>
> 2/ steps towards a regional site on uk.indymedia.org
> * make sure you have enough people to run the regional page - and to keep
> in touch with the uk network. Please be aware that imc is a global
network,
> i.e. every imc group should keep track of what's happening there.
> * tell the process list that you are interested. Somebody will get back to
> you.
> * customise your regional page. Manuals and documentation are on a twiki
> page [http://docs.indymedia.org/view/Local/MovingToMir] - incomplete but
> better than nothing. Check also mir.indymedia.org. When you've RTM and get
> stuck, you can get more tech help on [imc-uk-tech]. There are also regular
> uk irc meetings, and it's helpful to hang out with the global mir coders
on
> their irc or check their list [mir-coders]
> * if you want your local imc group listed on the global linklist of all
> imcs, i.e. have your own localgroup@indymedia.org URL, you have to go
> through the new imc process via the global [new-imc] list. More info on
the
> new imc process here: [http://docs.indymedia.org/view/Global/NewImcHowTo]
> We are thinking of moving this process to the UK, so that you don't need
to
> go through the global lists, but this is only at the beginnings.
>
> 3/ principles of unity
> Tony proposes to amend the global "principles of unity" for the UK - here
> is his draft:
> [1] Indymedia UK Network is based on principles of equality, and local
> decentralisation, made up of self-organised autonomous collectives that
> recognise the importance of developing a union of networks.
> [2] IMC-uk considers open exchange of and open access to information a
> prerequisite to the building of a free and just society.
> [3] Contributers and readers can use the open web based publishing to
> express their views freely, based on the trust and aderhence to the
> Editorial guidlines.
> [4] Indymedia is a non-profit network
> [5] IMC-uk recognises the importance of process to social change and is
> committed to the development of non-hierarchical and anti-authoritarian
> organising.
> [6] IMC-uk is committed to the priciple of Consensus decision making and
> the development of a participatory democratic process that is transparent
> to its members.
> [7] IMC-uk is commited to sharing of resouces including skills, knowledge
> and equipment where possible.
> [8] ....
> The current global draft for principles of unity is included in an email:
> http://lists.indymedia.org/mailman/public/new-imc/2001-May/000159.html
>
> _______________________________________________
> Imc-leeds mailing list
> Imc-leeds@lists.indymedia.org
> http://lists.indymedia.org/mailman/listinfo/imc-leeds