Community Organization: What do we want to be? #13

Open
opened 6 months ago by CSDUMMI · 7 comments
CSDUMMI commented 6 months ago
Owner

It's always best to have something concrete in mind when developing software. Otherwise you end up seeking a problem for a solution you developed.

In the case of SocialCoding the concrete case is very easy to find - SocialCoding is both a paradigm shift in free software development and a software development community.

The first example for a SocialCoding Community must be the Community developing the socialcoding Software.

Answering these questions in a manner that fulfills the CODE principles is a first step to achieve this goal:

  • How do we want to organize ourselves?
  • How do we want to govern ourselves?
  • And how do we want to resolve conflicts in our Community?
It's always best to have something concrete in mind when developing software. Otherwise you end up seeking a problem for a solution you developed. In the case of SocialCoding the concrete case is very easy to find - SocialCoding is both a paradigm shift in free software development and a software development community. The first example for a SocialCoding Community must be the Community developing the socialcoding Software. Answering these questions in a manner that fulfills the CODE principles is a first step to achieve this goal: - How do we want to organize ourselves? - How do we want to govern ourselves? - And how do we want to resolve conflicts in our Community?
CSDUMMI added the
principle:community-first
principle:openness
principle:democratic
principle:educate-learn
labels 6 months ago
CSDUMMI added the
organization
label 6 months ago

As you said the thing to start with is to consider our own project as the reference implementation of Social Coding. In other words we directly 'dogfood' what we are creating. We can apply that everywhere, and it fits really well with README-driven development (but in our website), and ensures we keep focus on having up-to-date documentation.

Guideline: Our initiative is a reference implementation of Social Coding.

As you said the thing to start with is to consider our own project as the reference implementation of Social Coding. In other words we directly 'dogfood' what we are creating. We can apply that everywhere, and it fits really well with [README-driven development](https://tom.preston-werner.com/2010/08/23/readme-driven-development.html) (but in our website), and ensures we keep focus on having up-to-date documentation. > **Guideline**: Our initiative is a reference implementation of Social Coding.

The first example for a SocialCoding Community must be the Community developing the socialcoding Software.

There is a need for evidence that demonstrates the problem that what you call "socialcoding Software" tries to solve. You have an intuition and I think I share it. Nevertheless, this is not enough. User Research must be conducted to collect those evidences.

Do you agree with this or not?

> The first example for a SocialCoding Community must be the Community developing the socialcoding Software. There is a need for evidence that demonstrates the problem that what you call "socialcoding Software" tries to solve. You have an intuition and I think I share it. Nevertheless, this is not enough. User Research must be conducted to collect those evidences. Do you agree with this or not?

Yes, we share your notion on the importance of User Research and created #11 for that.

Yes, we share your notion on the importance of User Research and created #11 for that.

On the landing page I have formulated what we wanna be as follows:

  1. Community: Passionate free software lovers that work together.
  2. Practitioners: Refine a methodology and collect best-practices.
  3. Supporters: Build a fediverse platform with helpful tools.

Community

We want to gather a movement of fine people who think, act and feel to be Social Coders and want to propagate the field.

Practitioners

We want to stimulate the methodology of Social Coding to evolve and be actively used in free software development by technologists and their audience (stakeholders).

Supporters

We want to provide the supportive technology and tools to make social coding a fun and useful exercise for any technologist to adopt, as well as for the audience that is served by their work.

On the landing page I have formulated what we wanna be as follows: 1. **Community**: Passionate free software lovers that work together. 2. **Practitioners**: Refine a methodology and collect best-practices. 3. **Supporters**: Build a fediverse platform with helpful tools. ### Community We want to gather a movement of fine people who think, act and feel to be Social Coders and want to propagate the field. ### Practitioners We want to stimulate the methodology of Social Coding to evolve and be actively used in free software development by technologists and their audience (stakeholders). ### Supporters We want to provide the supportive technology and tools to make social coding a fun and useful exercise for any technologist to adopt, as well as for the audience that is served by their work.
Poster
Owner

Maybe make clear that this is what we are (or want to be).

Maybe make clear that this is what we are (or want to be).

It is published to the site already :)

I'm just filling in initial content and refinement can be done later.

It is published to the site already :) - [Home](https://coding.social/) mentions 3 tracks, and links through to [Join our movement](https://coding.social/community/about-us.html) with more details. I'm just filling in initial content and refinement can be done later.
Poster
Owner

Maybe say "We are" instead of "Our activities are divided in three tracks:".

Maybe say "We are" instead of "Our activities are divided in three tracks:".
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.