How do we get the makers of FreeCAD to document their fucking software?
How do we get the makers of FreeCAD to document their fucking software?
22 comments
-
I mean, they may not have as much as you want, but they do appear to have documentation.
That has a manual in two ebook formats, PDF, and a French and Italian translation.
It has three help sections on the wiki, for each of users, power users, and developers.
And it apparently has some in-application help functionality.
And there's a help forum.
EDIT: It also looks like some people have written books about using FreeCAD.
-
Either donate or write the documentation yourself, complaining about unpaid FOSS devs and maintainers doesn't do anything
-
Once again, "I don't understand this, I guess it's up to me to explain how it works."
I didn't go to software engineering school. I went to flight school. Reading and understanding the source code of an application as large and complex as FreeCAD is outside my skillset.
I'm a flight instructor. I can and have taken people from never having flown a plane before to licensed pilot. You want me to teach flight school, you've got to give me the plane's POH. It is not my job to write the Pilot's Operating Handbook. It is my responsibility to teach students how to read it.
You get me good documentation for this software I'll create and publish a course on parametric furniture design. But I'm not going to sift through source code trying to figure out how to write a macro any more than I'm going to pull the panels off a Cessna and trace wires to figure out what the switches do. That is the responsibility of the people who made the damn thing.
-
-
I'm sorry you've had a poor experience with FOSS software, I'm sure the project will give you a full refund if you ask them.
-
You know what? That's okay, I'll just switch operating systems to Microsoft Windows or Apple MacOS and start using Autodesk Fusion360, paying hundreds if not thousands of dollars on a recurring basis to at least two American corporations that directly support the rise of fascism. I'll be directly financially supporting everything from AI slop to the abduction of academics in broad daylight but just think of the fives of minutes I'll save over the next decade drafting cabinets.
-
-
Do it as an end user? Be part of the solution?
Documentation is one of the many ways to contribute that don’t involve coding.
-
"I don't know how this works. I guess I'll have to be the one to explain it."
-
“I don’t know how this works. I guess I’ll have to be the one to explain it.”
Nope, it should read: "I don't understand how it works. It probably means I should (make the effort to) learn how to use it, and then I may want to share what I learned to make it easier to others." And then, yeah, you're right:
-
-
-
Unethical pro tip: write obviously wrong documentation, post it somewhere, and then wait for people to flame you while explaining the correct methods.
I'm ashamed to admit I've done that a couple of times when I was completly ignored for straight up asking how to do something.
-
Murphy’s Law: the best way to get the right answer on the internet is not to ask a question; it’s to post the wrong answer
-
This is the fastest and bestest way. And this is the reason Wikipedia works lol
-
-
The good thing about OSS is you don't have to be a programmer to contribute.
If the documentation is lacking you can write up a one pager and submit it to their wiki for integration.
https://wiki.freecad.org/User_hub-
How am I supposed to write the documentation for software that I have no method of learning how to use?
-
Read the wiki, experiment, and improve it.
But indeed, CAD is a very specific way of thinking, and if you haven't done any technical drawing course you won't find it by yourself
-
By watching YouTube tutorials or turning on the monkey part of our brains and poking around in the software until something happens.
-
-
-
Pay them?
-
How do we get the makers of FreeCAD to document their fucking software?
It's FLOSS. You may not like that but it's up to everyone of us to contribute to make things better. With our time, with our money, or with our expertise. And there is no fucking need to be fucking mad at anyone for not fucking doing it for you.
Or you can spend the money, time and expertise you don't have for FLOSS on shiny Apple or Microsoft proprietary apps so they can keep on not making good documentation and not giving a fuck about it. It's fucking up to you.
22 comments