better bring section on dissemination in line with shift from a socials product to a library facilitating portability
This commit is contained in:
parent
4d2d6a1205
commit
60ef86a8cb
1 changed files with 4 additions and 19 deletions
|
@ -189,18 +189,15 @@ Some of them are:
|
|||
|
||||
<!-- Make knowledge and results publicly available free-of-charge -->
|
||||
|
||||
We've identified multiple dissemination measures we can apply to our project in our plan:
|
||||
We've identified multiple dissemination measures we can apply to our project in our plan to engage the open-source community to further expand on work in this direction:
|
||||
|
||||
1. Offering automated dev-ops workflows.
|
||||
1. Ensuring external developers empowered to contribute:
|
||||
We want for external developers to feel empowered similar to core developers, which we aim to achieve using accessible documentation, reproducible project infrastructure, tests doubling as live documentation of our components, a module upstreamed to nixpkgs, as well as by offering a familiar interface by making our core abstraction a NixOS configuration.
|
||||
1. Developing key messages:
|
||||
We'll develop clear, concise, and compelling messaging that highlight the benefits and unique features of our project, such as the focus on **user control**, **privacy**, and **data & service portability**.
|
||||
1. Using multiple channels:
|
||||
We will be utilising a variety of channels to reach our target audiences outlined above, among which through online communities, social media, webinars, blog posts, tech conferences and press releases.
|
||||
1. Building partnerships:
|
||||
We have identified a number of partners already to help us reach out to our target audiences.
|
||||
These organisations share our **values and mission**.
|
||||
1. Monitoring and evaluation:
|
||||
We will monitor the success of our dissemination activities and evaluate their effectiveness in reaching and engaging our target audiences.
|
||||
We will then use this information to adjust and improve our strategies over time.
|
||||
|
||||
Concrete examples of dissemination activities for our project will include:
|
||||
|
||||
|
@ -227,18 +224,6 @@ There are several communication strategies and measures that we will utilise dur
|
|||
We will reach out to Fediverse channels (e.g. Mastodon, Pixelfed, Peertube and Owncast) as well as commercial social media platforms such as BlueSky, Threads, and LinkedIn to reach a wider audience and share project-related news and updates.
|
||||
Social media are used to engage with stakeholders and respond to their queries and feedback.
|
||||
While our values may be closer aligned with the open-source social media, we will also still have use for the commercial ones to spread our message initially.
|
||||
1. Organising workshops and events:
|
||||
Workshops and events will be used to engage with stakeholders and share project-related information.
|
||||
Workshops will be used to share technical knowledge, while events will be used to showcase the project's outputs and outcomes.
|
||||
1. Publishing project-related articles:
|
||||
Publishing project-related articles in mainstream media publications and through the channels of our partners will help to promote the project and its outcomes.
|
||||
It will also help to raise awareness among stakeholders and potential users of the project.
|
||||
1. Developing communication materials:
|
||||
Developing communication materials such as videos, podcasts and infographics will help to make it easy to communicate about the project and its outcomes.
|
||||
We'll make sure our communication materials will be designed to be visually appealing and easy to understand.
|
||||
1. Engaging with the media:
|
||||
Engaging with the traditional media will help to promote the project and its outcomes.
|
||||
Partners like [SDEPS](https://www.sdeps.eu/) consist of mainstream media actors across Europe who are aligned with our mission and are themselves potential users and ambassadors of the tools we build.
|
||||
|
||||
### Exploitation
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue