This is a list of our stakeholders (based on earlier team contributions)

1. Shortlist of key stakeholders

1.1. Project staff (Academic, Administrative, Technical)

1.2. Strategic projects (Sakai, OpenCast, Wookie, WebPA etc)

1.3. JISC

1.4. Academic software authors

1.5. RSCs

1.6. External developers

1.7. Knowledge transfer staff

1.8. Learners of open source development (students, work-based)

1.9. e-Research/ Research Infrastructure developments (incl. e-Research South consortium)

2. Stakeholder categories by sector

2.1. Academic

Academic - Teaching and research: People holding teaching or research posts
Academic - students: Undergraduate and postgraduate students
Academic - Managerial/Administrative: People holding managerial or administrative posts in educational institutions, or holding such posts within specific projects; this could includes staff dealing with legal issues, or issues of intellectual property exploitation, for example.
Academic - Technical Managerial: People holding high-level roles which are either technical or directly connected to a technical department, project, or activity. Such roles may mix a technical aspect with a strategic, advisory, managerial or administrative aspect; for example, project manager of a technical project, head of ICT, software engineer, etc.
Academic - Technical: People holding directly technical roles within either academic institutions or specific projects; for example, IT support staff, or developers.
Academic - Affiliated Bodies: people working for bodies within the UK educational system, which are not themselves educational institutions; for examples, JISC, the Science and Technology Facilities Council, the National Centre for Text Mining, technology

transfer units, BECTA, etc. The sub-categories of "technical managerial", "technical", and "managerial administrative" would apply here as well.

2.2. Private Sector

People working for private sector companies, as consultants, and so on. People in this category who attend OSS Watch events are often doing work for the education sector. In future, OSS Watch may accept attendees with no educational connections at all, for a fee. The sub-categories of "technical managerial" and "technical" would apply here as well.

2.3. Peers

Representatives of organisations or companies with interests and expertise in open source software, who may attend in an observational role. They may have an interest in how OSS Watch conducts its events; they will not usually be attending to learn, as their expertise may be similar or greater than OSS Watch's. Examples would be staff from the Open Source Consortium and Red Hat Ltd.

2.4. Non-UK

One of OSS Watch's past events for which a delegate list is still available featured a number of attendees from outside the UK.
Some previous events have involved members of Libresoft in connection with the Universidad Rey Juan Carlos.

3. Stakeholder categories by role

3.1. Academic

As before, these are academic staff or students.

3.2. Senior Technical/Technical Managers/Strategic and Advisory

People with either senior, and somewhat managerial or strategic, technical posts (architects, heads of ICT, etc.), or heads of technically-oriented projects. I also include consultants in this category, or people with a technical, broadly advisory and strategic position (e.g. e-Learning Advisor).

3.3. Technical Staff/Developers

People with specifically technical roles.

3.4. Non-Technical Managerial/Administrative

As above, people with a non-technical role, but whose work may touch on areas of strategy, law, intellectual property, etc.

3.5. Interested Parties

Other sorts of researchers, people involved in open source, etc.

4. Stakeholders random list

4.1. JISC

JISC funds OSS Watch and many development projects in HE and FE
JISC is not a legal entity, it is a number of committees (http://www.jisc.ac.uk/aboutus/committees/)
Funding is coordinated through a number of funding programmes (http://www.jisc.ac.uk/whatwedo/programmes.aspx)
Each programme is governed by a committee (http://www.jisc.ac.uk/aboutus/committees/)
Funding opportunities are pre-announced (http://www.jisc.ac.uk/fundingopportunities.aspx) and come in two forms, "calls" and "invitations to tender (ITT)".
All proposals for funding calls go through a bidding process (http://www.jisc.ac.uk/fundingopportunities/bidguide.aspx)
Each programme has one or more managers and a director.

4.2. Project staff

Each project has:

a principle investigator who is responsible for the project strategy and reporting
a project manager who is responsible for the day to day running of the project
developers (not necessarily software developers)
many projects have an advisory board

4.3. Regional Support Centres (RSC)

RSCs (http://www.jisc.ac.uk/whatwedo/services/as_rsc.aspx) provide regional focus for further education institutions

4.4. Accessibility-related

RSC Scotland North & East (http://www.rsc-ne-scotland.ac.uk) Creators of AccessApps FOSS accessibility apps collection and so primary stakeholder (other RSCs are also using it). Also maintainers of inclusive.ning.com community
TechDIS (http://www.techdis.ac.uk/) JISC information and advice service on accessibility and inclusion.
Open Source Schools Project (http://opensourceschools.org.uk/) Becta-funded compulsory sector but get a lot of info from us (Ross). Interested in NicheStick.
PortableApps (http://portableapps.com/) Collection of apps that run on USB sticks and the base technology for AccessApps. PortableApps.com itself and all the included projects (plus AccessApps projects)
AbilityNet (http://www.abilitynet.org.uk/) Accessibility info and advice service. Have 2 derivatives of AccessApps. We want to help them contribute back.
Schoolforge-UK (http://schoolforge.org.uk) A group of people interested in FOSS in education (compulsory + FE). Mostly a talking shop.
senit (http://lists.becta.org.uk/mailman/listinfo/senit) Becta mail list community for people using IT in SEN education

4.5. Strategic projects

These are a small number of projects that OSS Watch consider important for the future of OS development in UK HE and FE, and to which we plan to allocate a small amount of resources (no more than 0.2FTE) to build project community. By focusing our support on community building, project leadership is not bound in any way by our advice and, in turn, we are able to withdraw our support at any time if our strategies and those of the project diverge.

Some projects, like WebPA http://webpaproject.lboro.ac.uk/, have listened to our advice and are already carrying active work on community building in view of becoming sustainable.
Other projects, like Sakai http://sakaiproject.org/portal, are major players in their field, and by inviting OSS Watch to influence their development one hopes to see other projects following in their tracks.
Other projects, like OpenCast http://www.opencastproject.org, are too young to be leaders in their leagues yet, but they have the potential to become one in the future, and providing support at an early stage is likely to significantly affect their development.
Another category, which involve projects like FOSS Education, have been initiated by OSS Watch in collaboration with business and academic partners relevant for the UK academic sector.
Finally other projects, like Wookie and arts-humanities.net, are currently being monitored by OSS Watch as strategic project candidates.

4.6. Content-related

Professional journalists (people that we commission to write many different forms of content such as briefing notes, interviews, conference reports, case studies etc.)
Ad hoc event scribes (people commissioned to attend our events and act as scribe. These people always produce a short written report of the day for internal team use and may or may not also produce an external report for publication. They may also produce a live blog on the day)
Expert authors (people who are experts in their field and produce content that we solicit from them)
Graphic designer (responsible for designing and laying out monthly newsletter using content that we supply)
Volunteer contributors (unsolicited content that can come in at any time from any source)

4.7. IPR/licensing-related

Academic Software Authors (anyone who generates software as either a primary or secondary output of their research or teaching work)
Research Support Administration Staff (anyone involved in the administration of copyright/patents in software generated within HE or FE and/or involved contractual negotiations with external bodies that touch upon software under free and open source licences)
Knowledge Transfer Staff (staff charged with facilitating the free movement of knowledge - usually intellectual property - across the boundaries of an institution. This is usually achieved through the creation of spin-out bodies to pursue a business venture or the buying of time from a specific academic or department)
Institutional Legal Staff (in-house lawyers for HE and FE institutions)
Jobbing Software Development Staff (institutional employees who work to produce software. These might be assigned to a specific academic project and paid out of research funding or part of a institutional team or internal support service and paid out of institutional core funds)
Private Businesses (where any of the above stakeholders interact with private businesses we can help both sides achieve a better understanding of the other's needs (where they relate to intellectual property in software, free and open source software and associated communities)

4.8. Misc

HE/FE JISC/OMII developers, researchers, managers who are wanting to understand open development (via RT, conferences and strategic projects)
RSC teams, especially RSC Scotland N&W and RSC SW (AccessApps, workshops, conferences, shared events)
Accessibility Service provider managers (AbilityNet via AccessApps, conferences and workshops)
Compulsory sector IT managers, procurement staff and developers through Workshop and Open Source Schools Project
Maavis project team at Sheffield University and Barnsley NHS
Open Accessibility community and project developers (Mozilla, Gnome, Project:Possibility)
Anyone who has attended my presentations on Open Development or Open accessibility at RSC and OSSP events
Anyone who reads our tweets and blog posts

JISC's priority area funding 2010-12 cf JISC's draft strategy http://www.jisc.ac.uk/aboutus/strategy/strategyreview1012.aspx

$/!\$ Notes in this section have been moved to https://osswatch.mindmeister.com/maps/show/29703294