CoderGlue: Let’s Code Together 😉 This topic was inspired by FedeProxy project, and my interactions on their forum. There’s a wink in the title, because “CoderGlue” name and icon design is just a proposal I made, as alternative more descriptive project name. Nothing more than that. Culture and process I really like how the team is setting up the FedeProxy project organisation. A thorough approach, deep thought, and proper preparation. So too on diversity: @anon20068248: Diversity: F...

This SocialHub topic was inspired by Forgefriends (then called FedeProxy) and constitutes a wild brainstorm for envisioning what could be an entirely new paradigm to softwrare development: United Software Development.

Exploration of the idea involves looking from a non-technical perspective at all the possible ways in which Decentralization and fediverse standards (ActivityStreams, ActivityPub, Linked Data) can be leveraged to shape this paradigm.

Preliminary definition of United Sotware Development is “Free, libre software development, processes and culture united,. Sustainable, open and accessible to anyone.”, but I’m sure that can be further improved.

@dachary@lemmy.ml offers a very enticing look into what “Federated Development” might entail. I highly encourage people to read the SocialHub thread, and am very curious about your musings and thoughts.

  • @csdummi@lemmy.ml
    1•2 years ago

    My post is incomplete though: I’ve defined problem that the united software development paradigm should set out to solve, but I didn’t provide much information as to how that problem might be solved.

    For that I suggest a new definition of the free software development process:

    1. An idea is had and published.
    2. The idea is made concrete.
    3. A group of developers finds themselves to work on the idea.
    4. The group writes the code.
    5. The group makes a release.
    6. The group’s software gains adoption
    7. The community of users and the developer group grows.

    At no point during this new process does the success of the project depend on an individual. Indeed each step of this process could theoretically be done by a different person or persons. Thus requiring a whole new definition of what a maintainer is, how they become one and forge software has to change accordingly.

    And there should be software to support the first three steps of this process especially, software where you could publish ideas (1), make them concrete (2) and find developers to work on a project together (3). Federating this software and embedding it in Gitea or another federated forge would probably be the best approach.

    Since Big tech cannot use this process really, since it includes giving away your ideas and not just your code to the commons.