I saw the fuss about the “Don’t link to our website” people yesterday, and didn’t comment much until this morning, because I hadn’t realized just how crap-laden their page was (my ad-blocker did its job). My initial reaction was that they kept talking about “the mastodon devs should fix this” but isn’t part of the deal with open source (which mastodon is, right?) that if you see a problem, you can go fix it yourself which they didn’t seem to have any interest in. Open source much, guys?
I thought about this because of the question “what do you wish you knew about #OSS?” and thought that a fine answer was “you can fix other people’s code. But they don’t have to take your fixes.” But that’s a thing I’ve seen a lot during the decades of my career. People want to write shiny new code (and are rewarded for it in most places), but almost nobody wants to fix the old stuff. And removing code is a place where newbies can make extremely outsized contributions. / @mahryekuh
Open source contributors, what did you wish you knew when you started contributing? Or is there something that kept you from contributing for too long?
I am asking for a presentation, which I will give in two weeks.
The goal of tic is to enhance and simplify working with continuous integration (CI) systems
🙏 Maintained by Patrick Schratz
📝 https://docs.ropensci.org/tic/
I'd like to become more involved in Open Source. Any suggestions for an interesting Open Source #PHP project that needs some help?
(And sorry, no, I don't want to write docs :-) #oss
Hey #journalists if you're going to use an open source project as an example of a hack, can you at least let them know in advance you're about to do something reckless so they can prepare?
When opening a bug in an #OSS (dev-oriented) project, don't simply say "please do X". Tell them what the problem you're trying to solve is, what methods you've tried, and why that isn't working. You can include history of the paths you've gone down and even suggest a possible answer, but without knowing what problem you're actually trying to solve, project maintainers don't even know what problem your solution is for, and when you even have it.
My latest pet #project: Replace the "free" #location sharing services with simple solution where one has full control of (a) data collection (b) data storage (c) data sharing/visualisation.
If you want to give this #GoogleLatitude like alternative a go, I'd be happy for any and all comments:
folks, @whit537 is at it again and just dropped a barn burner about the #CRA, #OSS Stewards, Borland Turbo Pascal, and uh, green onions. (just read it, I promise it all comes together)
#OpenSource with #SLU gives students practical software development experience and helps researchers with their custom software needs.
“We are trying to, first, give students real-world software development experience. Second, build software that supports research. Third, promote a center of gravity for open source software development and broader conversations about open scholarship on campus.”
Daniel Shown,
Open Source with SLU
@martinsteiger Es gibt etliche Gründe, wieso einige Projekte Audacity vor ein paar Jahren geforkt haben. U.a. die Erosion sowohl von Privatsphäre als auch GPL.
Ein bisschen davon sieht man hier zusammengefasst. Und dass sich Leute engagieren.