Month: July 2019

I’m going to write a small guide to building open source communities….so, will use this blog as a scratch pad.

First some links of previous stuff:

• In a Plane, Pondering Community

• Design for Community

• Community Building and FLOSS Manuals

• Death of the Benevolent Dictator

• Cultural Method

• Open Innovation

• 

  What a Collaborative Community Looks Like

  Those organisations building platforms on top of PubSweet gather together every 3-4 months for our PubSweet Community Meeting. It started off as Coko, Hindawi and eLife but now we are also joined by the wonderful folks from the European Bioinformatics Institute. The events usually go for 2 da

  Collaborative Knowledge Foundation

• Things I think Open Source Needs to Address

• Designing for All

• Coko and Open Source

• Collaboration on UX

• Release now…

• Getting Design and User Experience Right in Open Source

• Going where your people are

• Brief chat with Tony in the car

• Another Interesting Article on Moving Beyond the Developer-centric Approach

• Diversity and Open Source Solution Models

• I love it when a clan comes together

• Cabbage Tree Adoption

• Leadership, diversity and sector change in open source

• Open Source is not about technology, or people, it’s about change

• Facilitators not Editors, Collaborators not Writers

• 

  Open source software has to sell user experience

  Open source software that is to succeed in this new world is going to have to be better than anything else. You can’t sell just openness anymore.

  Opensource.com
• 

  How the ‘itch-to-scratch model’ can solve our UX woes

  If we want open source UX to improve, we have to change the way we’re approaching the problem. Learn how the itch-to-scratch model works if we’re consistent in how we apply it.

  Opensource.com
• 

  7 ways to make better user-facing software

  Open source has been amazingly good at solving two sets of issues: 1) infrastructure and 2) developer tools. This is because those developers and users are basically the same people—the developer is an “insider” to the problem, understands it well, and is motivated to solve it.

  Opensource.com

Oh my gawd….didn’t think there would be so much of my own stuff to re-read first! eeek!