Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
make art - a week dedicated to the world of Free Software and digital art organised by goto10 ... This year make art focusses on distributed and open practices in FLOSS art. What the fork?! is about decentralization. Forking is the new black. Work from one source, copy, patch, improve, experiment, change direction, inspire! Forking is not about quick hacks, but about creating room to experiment, letting go of the one working copy and creating a multiplicity of ideas. i kind of find this irritating, it seem to be suggesting people fork projects just for the hell of it - let's do all those things the original developers never wanted their projects to be - and remember, most open source projects start out because the developer(s) had like-minded goals as the above goals state. i think forking of an open source project is generally not taken lightly and is seen as a last resort when disputes/disagreements between developers of the project cannot be resolved in any other way. i'd be interested to know what kind of projects are intended to be forked, or more precisely what complexity/size? there's no point in forking a big project to just add a handful of experimental or idiosyncratic features. however, while i'm a little critical of what the fork! the project i forked (gfract to create gkII*) a few years ago was because i patched, improved (arguable), experimented (definitely), and changed direction. in my case, i was never a developer of the project i forked. when I forked gfract and formed gkII, my contact with the author of gfract resulted in the update of his code (ie from GTK, to GTK2), and he also developed what in his opinion was a better implementation of part of the user interface i had developed in my experiments. There were also features he simply disliked, and he then implemented in ways I disliked. But in this case it was all quite friendly and we simply wanted to do things differently, and he also had more important things to work on. james. * http://www.jwm-art.net/gkII currently does not compile unless you remove -DGTK_DISABLE_DEPRECATED from the Makefile. ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
Being familiar with the MakeArt festival and people involved, I would say that their suggestion that people fork for the hell of it is much more artistic than utilitarian. I don't think you can equate forking a project to turn it into art with forking a project because it's not quite the utility that you think it could or should be. Pall james morris wrote: make art - a week dedicated to the world of Free Software and digital art organised by goto10 ... This year make art focusses on distributed and open practices in FLOSS art. What the fork?! is about decentralization. Forking is the new black. Work from one source, copy, patch, improve, experiment, change direction, inspire! Forking is not about quick hacks, but about creating room to experiment, letting go of the one working copy and creating a multiplicity of ideas. i kind of find this irritating, it seem to be suggesting people fork projects just for the hell of it - let's do all those things the original developers never wanted their projects to be - and remember, most open source projects start out because the developer(s) had like-minded goals as the above goals state. i think forking of an open source project is generally not taken lightly and is seen as a last resort when disputes/disagreements between developers of the project cannot be resolved in any other way. i'd be interested to know what kind of projects are intended to be forked, or more precisely what complexity/size? there's no point in forking a big project to just add a handful of experimental or idiosyncratic features. however, while i'm a little critical of what the fork! the project i forked (gfract to create gkII*) a few years ago was because i patched, improved (arguable), experimented (definitely), and changed direction. in my case, i was never a developer of the project i forked. when I forked gfract and formed gkII, my contact with the author of gfract resulted in the update of his code (ie from GTK, to GTK2), and he also developed what in his opinion was a better implementation of part of the user interface i had developed in my experiments. There were also features he simply disliked, and he then implemented in ways I disliked. But in this case it was all quite friendly and we simply wanted to do things differently, and he also had more important things to work on. james. * http://www.jwm-art.net/gkII currently does not compile unless you remove -DGTK_DISABLE_DEPRECATED from the Makefile. ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
aside : can you imagine my joy naming an exhibition, 'the garden of forking paths' ps: and thanks ruth for agreeing :) On 27/11/2009, at 1:49 AM, james morris wrote: make art - a week dedicated to the world of Free Software and digital art organised by goto10 ... This year make art focusses on distributed and open practices in FLOSS art. What the fork?! is about decentralization. Forking is the new black. Work from one source, copy, patch, improve, experiment, change direction, inspire! Forking is not about quick hacks, but about creating room to experiment, letting go of the one working copy and creating a multiplicity of ideas. i kind of find this irritating, it seem to be suggesting people fork projects just for the hell of it - let's do all those things the original developers never wanted their projects to be - and remember, most open source projects start out because the developer(s) had like-minded goals as the above goals state. i think forking of an open source project is generally not taken lightly and is seen as a last resort when disputes/disagreements between developers of the project cannot be resolved in any other way. i'd be interested to know what kind of projects are intended to be forked, or more precisely what complexity/size? there's no point in forking a big project to just add a handful of experimental or idiosyncratic features. however, while i'm a little critical of what the fork! the project i forked (gfract to create gkII*) a few years ago was because i patched, improved (arguable), experimented (definitely), and changed direction. in my case, i was never a developer of the project i forked. when I forked gfract and formed gkII, my contact with the author of gfract resulted in the update of his code (ie from GTK, to GTK2), and he also developed what in his opinion was a better implementation of part of the user interface i had developed in my experiments. There were also features he simply disliked, and he then implemented in ways I disliked. But in this case it was all quite friendly and we simply wanted to do things differently, and he also had more important things to work on. james. * http://www.jwm-art.net/gkII currently does not compile unless you remove -DGTK_DISABLE_DEPRECATED from the Makefile. ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
I thought forking was intrinsic to open source mentality, the possibility of taking what's out there and driving it somewhere else. Keeping one singular path instead of forking I guess requires a top-down strategy, doesn't it? However I see there a tension that I never quite understood how is solved in practical code development. If everybody took different directions we would be left with infinite parallel options and would be missing the point of working together on one particular project to make it stronger. I guess open source culture is about reaching a balance between the two. Still don't know exactly how it works in practice. How does ubuntu evolves out of so many people working for example? How is it all put together? Who decides what's to be included and what not? -- Olga P Massanet -- www.ungravitational.net virtualfirefly.wordpress.com www.vimeo.com/ungravitational ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
I guess you have read: El jardin de senderos que se bifurcan Jorge L. Borges 1941 Andreas Jacobs e: aj...@xs4all.nl m: 31 6 16 732 018 w: http://www.nictoglobe.com w: http://burgerwaanzin.nl On 26 Nov 2009, at 16:07, Neil Jenkins n...@netpraxis.net wrote: aside : can you imagine my joy naming an exhibition, 'the garden of forking paths' ps: and thanks ruth for agreeing :) On 27/11/2009, at 1:49 AM, james morris wrote: make art - a week dedicated to the world of Free Software and digital art organised by goto10 ... This year make art focusses on distributed and open practices in FLOSS art. What the fork?! is about decentralization. Forking is the new black. Work from one source, copy, patch, improve, experiment, change direction, inspire! Forking is not about quick hacks, but about creating room to experiment, letting go of the one working copy and creating a multiplicity of ideas. i kind of find this irritating, it seem to be suggesting people fork projects just for the hell of it - let's do all those things the original developers never wanted their projects to be - and remember, most open source projects start out because the developer(s) had like-minded goals as the above goals state. i think forking of an open source project is generally not taken lightly and is seen as a last resort when disputes/disagreements between developers of the project cannot be resolved in any other way. i'd be interested to know what kind of projects are intended to be forked, or more precisely what complexity/size? there's no point in forking a big project to just add a handful of experimental or idiosyncratic features. however, while i'm a little critical of what the fork! the project i forked (gfract to create gkII*) a few years ago was because i patched, improved (arguable), experimented (definitely), and changed direction. in my case, i was never a developer of the project i forked. when I forked gfract and formed gkII, my contact with the author of gfract resulted in the update of his code (ie from GTK, to GTK2), and he also developed what in his opinion was a better implementation of part of the user interface i had developed in my experiments. There were also features he simply disliked, and he then implemented in ways I disliked. But in this case it was all quite friendly and we simply wanted to do things differently, and he also had more important things to work on. james. * http://www.jwm-art.net/gkII currently does not compile unless you remove -DGTK_DISABLE_DEPRECATED from the Makefile. ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
Yes, I see what Olga means, for me it seams something magical. I am also interested in collaboration structures within communities working together on one code. On Thu, Nov 26, 2009 at 4:55 PM, Olga olga.pana...@gmail.com wrote: I thought forking was intrinsic to open source mentality, the possibility of taking what's out there and driving it somewhere else. Keeping one singular path instead of forking I guess requires a top-down strategy, doesn't it? However I see there a tension that I never quite understood how is solved in practical code development. If everybody took different directions we would be left with infinite parallel options and would be missing the point of working together on one particular project to make it stronger. I guess open source culture is about reaching a balance between the two. Still don't know exactly how it works in practice. How does ubuntu evolves out of so many people working for example? How is it all put together? Who decides what's to be included and what not? -- Olga P Massanet -- www.ungravitational.net virtualfirefly.wordpress.com www.vimeo.com/ungravitational ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour -- Double Blind (Love) performance Annie Abrahams Curt Cloninger 29 - 11 - 2009 Information : http://livingroomart.wordpress.com/performance/double-blind-love/ Video Squad fragment 3 min Riam06 http://aabrahams.wordpress.com/2009/10/06/squad/ http://vimeo.com/6926113 ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
Try googling for Sourceforge and probably most of your blanks will be filled in. Andreas Jacobs e: aj...@xs4all.nl m: 31 6 16 732 018 w: http://www.nictoglobe.com w: http://burgerwaanzin.nl On 26 Nov 2009, at 17:09, anniea a...@bram.org wrote: Yes, I see what Olga means, for me it seams something magical. I am also interested in collaboration structures within communities working together on one code. On Thu, Nov 26, 2009 at 4:55 PM, Olga olga.pana...@gmail.com wrote: I thought forking was intrinsic to open source mentality, the possibility of taking what's out there and driving it somewhere else. Keeping one singular path instead of forking I guess requires a top-down strategy, doesn't it? However I see there a tension that I never quite understood how is solved in practical code development. If everybody took different directions we would be left with infinite parallel options and would be missing the point of working together on one particular project to make it stronger. I guess open source culture is about reaching a balance between the two. Still don't know exactly how it works in practice. How does ubuntu evolves out of so many people working for example? How is it all put together? Who decides what's to be included and what not? -- Olga P Massanet -- www.ungravitational.net virtualfirefly.wordpress.com www.vimeo.com/ungravitational ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour -- Double Blind (Love) performance Annie Abrahams Curt Cloninger 29 - 11 - 2009 Information : http://livingroomart.wordpress.com/performance/double-blind-love/ Video Squad fragment 3 min Riam06 http://aabrahams.wordpress.com/2009/10/06/squad/ http://vimeo.com/6926113 ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
Re: [NetBehaviour] make art - a week dedicated to the world of FreeSoftware and digital art
I see.. Thanks for the link.. -- Olga P Massanet -- www.ungravitational.net virtualfirefly.wordpress.com www.vimeo.com/ungravitational ___ NetBehaviour mailing list NetBehaviour@netbehaviour.org http://www.netbehaviour.org/mailman/listinfo/netbehaviour
