Difference between revisions of "Organising a campaign"
m (→2. Don't try to be the owner: Category:Campaigning) |
(Related pages on {{SITENAME}}== * Current events * Formulating arguments * Let's avoid the term "Intellectual property" * Making leaflets * Why focus only on software * [[Duds and) |
||
| Line 1: | Line 1: | ||
| − | Previous and existing | + | Previous and existing campaigns against software patents provide good examples for '''campaign organising'''. |
| − | == | + | ==Building a large consortium== |
| − | |||
| − | |||
| − | |||
===1. Broad coalition=== | ===1. Broad coalition=== | ||
| Line 21: | Line 18: | ||
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. | 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. | ||
| + | ==Related pages on {{SITENAME}}== | ||
| + | * [[Current events]] | ||
| + | * [[Formulating arguments]] | ||
| + | * [[Let's avoid the term "Intellectual property"]] | ||
| + | * [[Making leaflets]] | ||
| + | * [[Why focus only on software]] | ||
| + | * [[Duds and non-solutions]] | ||
| + | * [[Campaigns to avoid patented ideas]] | ||
| + | * [[Analogies]] | ||
| + | * [[Why tech groups should be involved]] | ||
| + | * [[Why free software groups should be involved]] | ||
| + | * [[Why consumer organisations should be involved]] | ||
| + | * [[Why SME unions should be involved]] | ||
| + | |||
| + | |||
| + | {{page footer}} | ||
[[Category:Campaigning]] | [[Category:Campaigning]] | ||
Revision as of 03:37, 21 February 2010
Previous and existing campaigns against software patents provide good examples for campaign organising.
Contents
Building a large consortium
1. Broad coalition
There are many categories of organisations that should be against software patents.
- Why SME unions should be involved
- Why consumer organisations should be involved
- Why tech groups should be involved
- Why free software groups should be involved
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.
Related pages on ESP Wiki
- Current events
- Formulating arguments
- Let's avoid the term "Intellectual property"
- Making leaflets
- Why focus only on software
- Duds and non-solutions
- Campaigns to avoid patented ideas
- Analogies
- Why tech groups should be involved
- Why free software groups should be involved
- Why consumer organisations should be involved
- Why SME unions should be involved
