Tag: openculture

Shifting the #mainstreaming to the #openweb

To make the #mainstreaming agenda more functional in an #openweb reboot, we need to address issues of inclusion, governance, and sustainable development while ensuring that the openweb embodies participatory paths. How do we do this?

Strengthen community governance decentralized and transparent decision-making by createing frameworks for governance that involve more voices from the grassroots, like the #OGB project. Tools based on federated models (like those used in the #Fediverse) empower people to participation in decision-making processes. Collaborative standards, working groups that draw from a mix of tech experts, community members, and non-expert voices to create paths that reflect collective needs rather than top-down dictates.

Develop a supportive ecosystem for builders with funding beyond the #fashernistas. Shift funding mechanisms toward projects that align with the values of the (open data, open standards, open source, and open process). This means supporting those who build with the public good in mind, not just flashy, trendy ideas, and tech fashions. Empower developers with a community focus by highlighting developing projects that prioritize #UX and community needs rather than tech novelty. Encourage #FOSS governance practices that are transparent and inclusive. Foster this inclusivity by bridging silos with cross-community dialogues, this can facilitate discussions that bring together different sectors of alt-tech, civic tech, and grassroots movements to cross-pollinate ideas and useful paths to take.

Ensure that platforms being built do not only cater to niche tech communities but are accessible and usable by the public, to focus on practical relevance. This helps to empower people to understand the importance of decentralized tech and how it benefits them directly. Thus helping to break down the barriers posed by the #geekproblem and demystifies participation in the openweb paths. A strong part of this is organizing hands-on workshops that engage people in contributing to and shaping the projects.

Accept that failures are part of the process. Instead of discarding what doesn’t work, use these experiences as compost—breaking down what failed and learning from it to build stronger initiatives.
This plays a role in shifting cultural narratives to challenge and change the stores around the #openweb and wider #openculture to include cooperative problem-solving and mutual respect. Shifting the focus from tech utopianism to realistic, impactful change.

Build tech paths that are adaptable and capable of evolving with peoples needs and global conditions, including #climatechaos and socio-political shifts that are accelerating. A part of this is support for meany small tech paths that link and flow information and communities.

To reboot the #openweb to become a part of a shifting mainstream, we need to promote messy participatory governance, redirect funding to genuine, community-oriented projects, and champion inclusive, sustainable paths. The composting analogy emphasizes learning from past mistakes and continuously building resilient, inclusive solutions #KISS

What can we do with our fashernistas?
How can we mediate the #NGO blocking?

The act of linking goes far beyond a simple convenience; it forms the backbone of an interconnected, accessible, and transparent internet. Yet, many people overlook its importance or misunderstand its role, especially when transitioning from #dotcons (corporate-controlled platforms) to #openweb environments. To sustain the promise of an open, people-driven internet, we need to recognize and actively engage with the practice of sharing non-mainstream links #KISS

Don’t feed the trolls, keeps coming to mind, when looking at the influx, this is like waves washing on the shore, be the shore not the wave.

Building #FOSS bridges

There is a divide in #FOSS between #openculture and #opensource that is becoming more visible and a significant tension today, with each movement originating from different perspectives on sharing and collaboration, even though they overlap in the broad mission of making knowledge and technology more accessible. You can see this in the AI debates and in grassroots “governance” in the #Fediverse and the issues this brings up as current examples. The differences are in focus and motivation:

  • Value path: Open Source focuses on the technical, structured development of software, with licences that ensure people can access, modify, and redistribute code. It tends to be practical, driven by the necessity to create robust, community-driven technology.
  • Open Culture, however, extends beyond software to include media, art, and knowledge. It centres around the idea that cultural paths—art, literature, music, and other media—should be freely accessible and adaptable by all. It values knowledge sharing in all forms, encompassing the ethical path that information and culture should be democratized.
  • Legal frameworks and licenses: Open Source relies on licenses like GPL, Apache, and MIT licenses that set clear boundaries on how code can be used and ensure that software modifications remain open. This fosters collaboration but also keeps contributions within a strong structured framework.
  • Open Culture, leans on Creative Commons (CC) licenses, which are more flexible in terms of content usage and address a broader range of creative and educational materials. These licenses vary widely, allowing authors to shape how much or how little freedom people have to use their contributions, which can lead to different interpretations of “openness.”
  • Open Source communities are more driven by practical needs and more standardized approach to governance, which function at times as gatekeeping and can be seen as restrictive by Open Culture advocates. There’s often an emphasis on the meritocratic and structured contributions, rather than the more mess cultural paths.
  • Open Culture communities are more fluid, valuing inclusivity, encouraging contributions from broader groups. This can create tension with Open Source projects that prioritize hard structured paths.

Today, we see this division in action with increasing calls from the Open Culture side for a more inclusive, less restrictive approach. Open Culture argue that #FOSS and Open Source can be rigid, excluding many types of cultural contributions and voices that don’t fit neatly into software development paths. Conversely, Open Source proponents view Open Culture as lacking in the clear boundaries that have shaped Open Source to work in structured technological development.

Bridging the gap: For #openweb projects, addressing this divide requires a path that respects both technical standards and the inclusiveness Open Culture calls for. Projects like #OMN and navigate this divide, building on community-driven networks where technical governance is balanced with cultural openness. Building tools that emphasize accessibility and collaboration—while being technically robust and community-driven—bridge the gap, aligning Open Source rigour with Open Culture’s inclusiveness.

To move forward, both communities benefit from dialogues focused on shared values, finding where their paths complement each other, but with clear strengthens and weakness to both paths. This issue is important as we confront the composting of #techshit and #dotcons and in the wider world the onrushing #climatechaos that all require technological, cultural, and social innovation.

Then there is this issue to think about https://lovergine.com/foss-governance-and-sustainability-in-the-third-millennium.html