Well it was only a minor irritation and I'm not familiar with the festival or the people involved and my example of how I forked a project was supposed to show how my opinion on this is not straightforward or totally defined.
Can you give some examples of artistically forked projects?? Taking this further toward the utilitarian side of things... I've witnessed discussion about a forked project (Improvisor) on LAD, which caused a lot of ongoing arguments and noise on the list: http://lists.linuxaudio.org/pipermail/linux-audio-dev/2009-July/thread.html#23753 >From reading discussions about implementations and specifications (also on the same list), from seeing how much thought and work goes into making these things. Even stuff which you might think as fairly straight forward can bring up lots of complex considerations - especially when trying to future proofed extensibility. Particularly thinking about LV2 and JACK. There's people who want tighter integration of JACK into the desktop, so for new and inexperienced users "it just works" out of the box (ie it works fully without the user having to go through a complex configuration process). But then there are other developers who are against forcing desktop dependencies because they don't run JACK on a desktop system and they don't want to be forced to install software for a desktop system. James. On 26/11/2009, "Pall Thayer" <[email protected]> wrote: >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 >> [email protected] >> http://www.netbehaviour.org/mailman/listinfo/netbehaviour >_______________________________________________ >NetBehaviour mailing list >[email protected] >http://www.netbehaviour.org/mailman/listinfo/netbehaviour > _______________________________________________ NetBehaviour mailing list [email protected] http://www.netbehaviour.org/mailman/listinfo/netbehaviour
