Contributions to #FOSS constitute unexpected and precious gifts.
#SocialCoding commons is a movement of people interested in exploring the more #social sides of decentralized #SocialNetworking environments and focuses on building solutions that serve people’s needs: social experiences. For this we explore a methodology called Social experience design ( #SX ) tailored to cocreating Sustainable open social systems ( #SOSS ) in order to deliver services for the #SocialWeb. A fediverse that goes “beyond the app” towards a #peopleverse that serves our daily lives.
@theron29 @simon_brooke @hosford42
@gse @hosford42
Yes! Among others. Delightful developments are underway. Not just in #Gitlab and #Forgejo but more code #forge softwares to follow.
As you likely know and with great help of @NGIZero - and @nlnet - the protocol extension of #ActivityPub called @forgefed is maturing and evolving.
The curated #fediverse experience list taxonomy has a #SocialCoding section with #FOSS projects that are adopting #ForgeFed specs. See:
https://delightful.coding.social/delightful-fediverse-experience/#social-coding
Hey, that's cool, #Radicle Desktop landed today! From the @radicle team:
> Since Radicle reached version 1.0 in September last year, we’ve been focused on improving the overall user experience. We believe the Radicle network becomes more valuable the more people participate - and Radicle Desktop is a step toward making that participation more accessible, without making any compromises.
Follow-up to chat with @mapache and @dajb on #SocialVerifiableCredentials and #BadgeFed's #ActivityPub realization.
Some more draft text of the - thanks to @nlnet support - soon revamped delightful-fediverse-experience curated list, demonstrating how I deliberately step away from strict #TechnicalLanguage.
After all the cold hard #tech is just a click away. Tons of #CodeForges awaiting our #SocialCoding
Not sure if you like the language. Yet feel its good if fluffy and spiky are in balance.
@Linux this is very nice useful info. Thank you!
This could be a candidate service, and possibly a delightful commons-based curated list (hosted by #SocialCoding commons). Have a script update the markdown on a regular basis, using #codeberg CI and a cronjob.
Delightful project, which I initiated, is evolving atm and being repositioned. The new name is Delightful #commons and still all about "delightful gems of freedom" i.e. gathering great #FOSS, #OpenData, and #OpenScience related resources.
Totally. I started #SocialCoding movement at https://coding.social and https://discuss.coding.social
Coding is social and if working on social networking solutions "social coders social code the social code"
Exploring some fascinating subjects, like Social experience design #SX, Sustainable open social software / systems / services #SOSS, Free software development lifecycle #FSDL and hedonic peer production (a method that the movement 'self-services' i.e. dogfoods, among others.
Social Coding: Code better, together
Coding isn’t just a solo mission- great projects thrive on teamwork!
In our #SocialCoding session, you’ll learn how to contribute and collaborate effectively, as well as what you need to know about licensing.
Join us: https://coderefinery.github.io/2025-03-25-workshop/
@frankstrater @dansup @peertube @Gargron
I am not advocating to throw tech at things and see what sticks to the wall. That I call what others dogmatically pursue and think is what people want: #DigitalTransformation
We live in a #technosphere and a big chasm of missing #sociosphere must be bridged.
I'm hobbying along here in #fedi advocacy for years hoping to share dreams of #peopleverse. This I now continue at #SocialCoding movement under the flag of #SocialExperienceDesign (or simply #SX)
#coding --> #socialcoding
#community --> #movement
#users --> #fedizens
and
#technosphere --> #sociosphere
#fediverse --> #peopleverse
#foss --> #soss
and
#socialmedia --> #socialnetworking
#socialgraph --> #socialfabric
#techstack --> #socialstack
#app --> #solution #service
#product --> #socialexperience
and
#dx #ux #ui --> #sx
#project --> #fsdl
#projects --> #ecosystem
#development --> #cocreation
#forge --> #forging
#contributor --> #peer
#contributing --> #peerproduction
Code forges could significantly reduce the emotional labour of project maintainers by adding a separate tracker for "Bugs", next to the one for "Issues". Maintainers could then turn off notifications for Issues, without missing notifications about bugs. If people started making features requests or starting general discussions in the bug tracker, all the maintainer would need to do is move them to Issues and ignore them.
@Migueldeicaza Or file an issue (and then maybe submit a PR).
Rather than considering even just once the needs & massive benefits for creators and maintainers, current open source software infrastructure, support tools, but also developer culture itself is completely biased and optimized purely for the benefit of consumers/users. Choosing a non-standard project structure (in my case a mature Google-style monorepo with almost 200 largely independent, but related projects/libraries/tools) is increasingly actively punishing my work and efforts in a variety of ways, e.g.
- non-supportive UIs for improved browsing/overviews of monorepos
- harmed discovery via search & metadata limitations
- wrong, misleading and downgraded project ranking calculations (npm)
- misleading/broken automated project analysis (GitHub)
- lack of support by documentation tooling (TypeDoc)
- lack of support by package managers (Zig) and/or hosting platforms
All of these (and more) factors are actively hurting, disqualifying & even completely nullifying much of my time & energy spent on these projects, making my dream goal of working on open source fulltime increasingly intangible (because the above factors all have an actively downgrading effect which makes these project seem lower quality/relevance). To some extent this is purely because this work is stored in a project structure which is optimized for maintenance & automation. Technically, we're speaking about _one_ additional level of nesting. An extra subdirectory! Otherwise, not any different than a "normal" repo. Still — BOOM — confusion, inflexibility & punishment ensues!
So many external aspects and people do not give a damn that a monorepo setup like this and the custom tooling created to automate the maintainance and cross-linking of all these ~360 packages (incl. example projects) are _the only sane way_ for me as a single person to efficiently manage & release a codebase of this magnitude.
I was aware of some misunderstandings about monorepos on purely social/human level, but never saw it coming that the more I was expanding and deepening this work, the more this structure and scope would hurt the project & my goals, because 3rd party infrastructure is just as weirded out by such a "blasphemy" as some people are...
I'd genuinely like to hear ideas what I could/should do to escape the vicious circle created by the above factors, which is a real motivation killer... I really do wonder how other maintainers (esp. would like to hear from indie devs)
handle projects & codebases of this scale without running into these issues...
Thank you for any insights!
Ps. I really seem to have a feeble for "think different" and going against the grain with these things (or maybe being too early?). The first set of 20+ https://thi.ng libraries for Clojure/ClojureScript were mostly written in a #LiterateProgramming format, often combining source code with diagrams & tables — this too led to many complaints and was partially to blame for not gaining much traction, even though these projects were singular offerings to that language community at the time (and funnily only became more popular _after_ 6-7 years, once I'd already left Clojure behind... go figure!)
https://discuss.coding.social/t/unionize-free-software-found-software-guilds/59 the recent #XZ disaster has prompted me to reread my own article from two years ago next month on "Free Software Unions". While I'd put some of the details in there differently today, I think the core point still stands: that free software maintainers are vulnerable to exploitation, both from Big Tech and, as is now evident, malicious attackers. And that the only way to protect them is to join into mutual support, solidarity groups.
So I just learned about #socialcoding (https://coding.social/) which is absolutely awesome!
For decades I'm learning to code on and off as a hobby. I feel like helping out in #foss would be a gamechanger for me but I cant identify where to help (I know some python and c# but nothing great).
My github account is meh at best and when TIL about git forges joining the #fediverse I was thunderstruck. Is anyone else eager to de-corpo git once we have it running? Forgejo seems to be pioneering atm.
As part of the Drupal Global Contribution Weekend 2024, we are excited to host the London chapter's Code Contribution Day!
Come and be part of something bigger!
More details & RSVP at https://www.meetup.com/london-drupal-user-group/events/298435308/
@smallcircles @trwnh
@fedidevs@a.gup.pe
@fedidevs@venera.social
That's great news!
And the discussions continue at:
https://socialhub.activitypub.rocks/
Thanks for your tirelessly consistent commitment to advancing #Fediverse adoption and #ActivityPub development for the past several years too - your efforts continue to be an inspiration for all concerned #Fedizens!
#tallship #FEP #SocialHub #SocialCoding #swicg #FOSS #fediverse-city:matrix.org
.