Talk:Genealogy / Archeology of the Prusa i3 X Motor End
Great work! I'm thrilled to see people starting to develop incrementally. --Traumflug (talk) 16:08, 17 December 2014 (PST)
- Hi, thanks! Well I guess what you call "incremental development" is what I think the GNU / Open Source philosophy is all about i.e. the source code is there for all to see and fix / improve and keep "alive". Imho removing the proper attributions in Open Source code also removes much of the motivation for developers to release their code under a GPL or similar license, and closing the source or only releasing binaries makes it impossible for future developers to work on a piece of code (or 3D design as in this case). I think the Prusa i3 and its numerous variants is a classic case of Open Source development at work in the 3D / mechanical design domain and I was sorry to see it straying off the path, so I wrote this page to see if we can reverse this and put things on course again. --AndrewBCN (talk) 21:11, 17 December 2014 (PST)
- Removing attributions isn't OK, of course. For the future I could think about a RepRap-owned repository collecting all these improvements. Then we could control these attributions and also make clear which development the most recent one is. For example, currently it's a bit unclear for less involved people wether i3 Rework or i3 Hephestos (or yet another design) is the more recent one. I thought about an official Github account, but honestly, Github is a usability nightmare. The other side of the coin is, opening a custom repository is quite some work. Good thing is, we do have the server resources. --Traumflug (talk) 03:54, 19 December 2014 (PST)
- I fully agree about GitHub being a usability nightmare, specially when it comes to hosting documentation - the wiki concept is much more adapted to this use. What I am really trying to do with this page is to educate developers by showing the negative long-term consequences of breaking the GPL development chain. Of course I am not blaming anybody in this case, it seems almost to have happened as a consequence of an accidental series of small - but imho wrong - decisions. --AndrewBCN (talk) 21:08, 19 December 2014 (PST)
- Removing attributions isn't OK, of course. For the future I could think about a RepRap-owned repository collecting all these improvements. Then we could control these attributions and also make clear which development the most recent one is. For example, currently it's a bit unclear for less involved people wether i3 Rework or i3 Hephestos (or yet another design) is the more recent one. I thought about an official Github account, but honestly, Github is a usability nightmare. The other side of the coin is, opening a custom repository is quite some work. Good thing is, we do have the server resources. --Traumflug (talk) 03:54, 19 December 2014 (PST)
Nice page! BTW, J.Rodrigo and Mecan0 (Manuel Palacios) are not the same person. You can see the origin of the SCAD files for PowerCode (from the original ones in Catia) in this thread [1] --Xoan Sampaiño (talk) 02:52, 18 December 2014 (PST)
- Thank you very much Xoan, I have corrected the page! Also somewhere I think I should mention your significant contributions to the design of various improved Prusa i3 parts (and I know - from reading your source code - that you are respectful of the GPL)! --AndrewBCN (talk) 17:53, 18 December 2014 (PST)
Well, today the bq/Prusa-Hephestos GitHub repository was fixed and proper attribution was given for the .stl files (I had opened an issue in GitHub almost exactly one month ago about this), so I am removing my previous remark in the page about this mishap.
