en.swpat.org is a wiki.   You can edit it.   May contain statements End Software Patents does not endorse.

November 2014: About Microsoft’s patent licence for .NET core

SitemapCountriesWhy abolish?Law proposalsStudiesCase lawPatent office case lawLawsuits

Organising a campaign

From en.swpat.org
Revision as of 16:04, 25 March 2012 by Ciaran (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Previous and existing campaigns against software patents provide good examples for campaign organising.


[edit] Building a large consortium

[edit] 1. Broad coalition

There are many categories of organisations that should be against software patents.

[edit] 2. Don't try to be the owner

Most organisations don't like taking orders and don't like other people speaking on their behalf. Taking positions involves risks, so most organisations prefer to keep control of their own position on issues such as software patents.

Creating a relationship is good, and having communication channels is good. Trying to install yourself as an umbrella organisation is usually not very attractive.

Some organisations will even go as far as to refuse communication. Maybe this is because a department wants to take full credit within their organisation for the work done on this topic. Whatever the reason, remember that the important thing is to ensure that this organisation knows why and how to push for anti-swpat laws. You can do this with one-way communication tools such as websites. They can read the website, use all the info, and take all the credit.

[edit] Related pages on en.swpat.org

Formulating policy:

Making materials:


[edit] External links

This wiki is part of the End Software Patents (ESP) campaign (donate). For more information, see:
>> endsoftwarepatents.org (Main ESP website) <<
>> endsoftwarepatents.org/news (News) <<

This wiki is publicly editable. (See: en.swpat.org:About) It's a pool of information, not a statement of ESP's views or policies, so no permission is required. Add your knowledge! (See: Help:How to make a good contribution)