FreeCAD
FreeCADWeb.Org ➞ FreeCAD.Org
Goal
This issue tracks the progress on updating internal
& external resources to use the new FreeCAD address.
Note
Even if all of the PRs listed below have been merged,
that doesn't mean all instances have been updated.
Also this issue should be moved to the
meta repository once it's been created.
Scope
This endeavor concerns all non-fork
repositories and Crowdin projects.
Tracker
Internal
- https://github.com/FreeCAD/homebrew-freecad/pull/685
- https://github.com/FreeCAD/FreeCAD_Conda/pull/46
- https://github.com/FreeCAD/FreeCAD-LibPack/pull/51
- https://github.com/FreeCAD/freecad.ship/pull/73
- https://github.com/FreeCAD/FreeCAD-documentation/pull/7
- https://github.com/FreeCAD/Examples/pull/12
- https://github.com/FreeCAD/FreeCAD-Homepage/pull/265
- https://github.com/FreeCAD/FreeCAD-render/pull/481
External
- https://github.com/Schievel1/dactyl_manuform_r_track/pull/14
- https://github.com/yzaguirre/alexandria/pull/1
- https://github.com/marmni/FreeCAD-PCB/pull/82
- https://github.com/ickby/FreeCAD_constraint/pull/1
- https://github.com/geobruce/FabLab/pull/7
- https://github.com/seamplex/feenox/pull/33
- https://github.com/JeromeL63/Wood-Frame/pull/23
- https://github.com/yorikvanhavre/FreeCAD-manual/pull/18
- https://github.com/qingfengxia/FreeCAD_Mod_Dev_Guide/pull/24
- https://github.com/pycollada/pycollada/pull/158
- https://github.com/sfepy/sfepy/pull/1220
- https://github.com/makespacemadrid/goliat-py-fcad/pull/2
- https://github.com/jdohm/ZP_Muelleimer/pull/5
- https://github.com/TheRaytracers/freecad-povray-render/pull/8
- https://github.com/helm-compiler/carpentry-compiler/pull/1
- https://github.com/Reqrefusion/FreeCAD-Documentation-Project/pull/9
- https://github.com/Reqrefusion/FreeCAD-Documentation-Project/pull/8
- https://github.com/realthunder/FreeCAD_assembly3/pull/1344
- https://github.com/LibreScanner/ciclop/pull/42
- https://github.com/Reqrefusion/FreeCAD-Documentation-Project/pull/7
- https://github.com/hkroeger/insightcae/pull/40
- https://github.com/opensimcraft/opensimcraft.github.io/pull/3
- https://github.com/james481/cat-trainer/pull/2
- https://github.com/sy2002/TeleBall/pull/2
- https://github.com/lowdrant/mySatComm/pull/1
- https://github.com/system76/launch/pull/97
FYI : The discussion in the comments below has
already been resolved in a developer discussion.
https://github.com/search?q=repo%3AFreeCAD%2FFreeCAD-Homepage%20FreeCADWeb&type=code
wHile IT Is gOod ThaT THE thiNGs StArt To use tHe CORRECt UrL, ChanGing THe CasiNg Of ThE dOMAIn mAkeS it STanD out aND BEcOMeS QUiTE unREAdabLe.
@hyarion What are you on about?
Yes if one were to misuse casing like you did in your comment sure.
The fact is the actual correct case
was used: https://FreeCAD.Org,
this is just bike shedding ..
Also, thank you for spamming your comment
under every linked issue, forcing me to respond
likewise instead of just discussing the issue here.
Also to respond to your comments here as well:
- Just because the internet commonly does something is not indicative of it being the better or the best way.
- The changes commited in the various repositories cause NO technical issues anywhere, as they follow the spec.
- The casing improves the editing experience while not affecting any usage ( Browsers might normalize the casing to lowercase but don't even redirect for that ) ( There is a reason why ads often uses casing when they show website addresses )
- I deliberately left of the
wwwsubdomain as that inverse should happen - FreeCAD ( if possible ) should drop & redirect the subdomain in favor of .. nothing .. just like any other modern website. Not prefixing it makes it shorter, more readable and slightly more future proof.
- chrome, firefox and safari all shows it as lower case
- the webserver uses lowercase in redirects:
curl -I https://FreeCAD.Org
HTTP/2 301
server: nginx
date: Thu, 03 Jul 2025 06:57:58 GMT
content-type: text/html
content-length: 162
location: http://www.freecad.org/
- you make suggestions a lot of places which doesn't follow the two points above
If you've changed the homepage to be an outlier on the internet, then suggested everyone to follow then it would have been fine, now you forced me to respond to all your PRs on various projects as there was no central discussion
I'll write a comment that the discussion is continuing here to avoid work for both of us :)
- And?
- And?
- A yes, I was supposed to follow whatever you
have to say before you had even said anything.
Oh I forced you to answer on all of these PRs, that's news to me.
To me it seems more like you blew something that is equivalent to
the importance of whether someone uses 2 or 4 spaces for their tab
key out of proportion and responded as if this were an emergency.
YOU had the choice of addressing your decorative concern here, making
me pause with my changes or even having me convert the yet-to-be-merged
issues into draft status.
Instead you spammed your comment on every single PR I linked here for
reference, which will now force every party involved to come here and
read through everything to get context and potentially give their opinion.
If I didn't know any better, I'd think this is a wayland protocol discussion. Guess I'll have to pack some years worth of time for the bike shedding.
It wasn't my intension to be a pita, in retrospect I could have commented with a link to this issue instead in the PRs. There was just no good way of responding to them all as they are all handled by different parties, so I wanted to keep it local to the repo owners.
You clearly prefer another way than what is traditionally used. The argument that marketing sometimes uses the same style as the registered trademark holds true when looking at it on an image. This way they draw your attention to the trademark used, but from what I remember people in those cases leave out www and .com/.org in lowercase because that's just how people are used to read and write it and if you make that uppercase, then you will visually add significance to those parts.
If we go against almost everyone else we implicitly add meaning to the difference. In this case some people will start to think it matters which casing you use.
I think this answer to a question on when to use upper case is quite relevant: https://english.stackexchange.com/a/41791
FYI: Regardless of any personal preferences elsewhere, we cannot make this change to any addons' namespace URI, which has to remain all lowercase.
FYI, when you for example link a PR in an issue - like I
did here - they are automatically linked in the PR history.
Example
@chennes Right, wasn't planning on doing that,
if you notice any such errors, let me know~
https://github.com/FreeCAD/FreeCAD-render/commit/9f35d303a4bd12ef8b8bef17b63ab6978d90047b (fixed in https://github.com/FreeCAD/FreeCAD-render/commit/acdb8ccd0961c0e0ecc70ee3369f4fe75073cc5e).
Regarding the case change: this is clearly not yet an "identified and agree upon issue" (per https://github.com/FreeCAD/FreeCAD/blob/main/CONTRIBUTING.md). So no action should be taken on it until we've reached consensus. @PhoneDroid I suggest switching the currently-open PRs to draft status in the meantime.
In the developer discussion held
on Discord it was decided that:
- The url should drop the
wwwprefix - Use all lowercase for the domain part