<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class="">On 02/21/2016 08:35 PM, Fred Jan Kraan wrote:<br class=""><blockquote type="cite" class="">This mail is the last I will write about cyclone in the foreseeable<br class="">future.<br class=""></blockquote><br class="">this is about the worst possible outcome of the entire discussion.</blockquote><div class=""><br class=""></div><div class="">Exactly.</div><div class=""><br class=""></div><div class="">Discussions are great and all but discussions also involve listening to both sides. At some point, things seemed to go one sided. Developer burnout is a *huge* problem in open source so Fred’s concern about maintainability vs. extensibility is valid. Maybe that concern wasn’t quite coming through over email. I can personally say, OS developers tend to start getting into a situation were they work on things not because they are interested anymore but because they feel like they *have* to support the needs of others … for free. That’s where things get toxic and it’s sometimes hard to find a balance between the two.</div><div class=""><br class=""></div><div class="">I’m not trying to figure blame, etc, I’m trying to see what we can all learn from this unfortunate outcome.</div><div class=""><br class=""></div><div class="">Instead of consistently asking for Fred to integrate and increase his workload, the better course of action might have been to make a companion library that utilizes cyclone and begins adding functionality. Maybe start with abstractions and go from there? Putting up code and workable ideas always influences things more than "here’s a huge bug/feature list for one person to implement.” Oftentimes, if the work is good and the developer can see things are coming together nicely, talk begins about a possible integration with the base code base and direct collaboration. This has been the case in the OpenFramework community where a few addon libraries have been vetted and proven outside of the core code, then integrated later on.</div><div class=""><br class=""></div><div class="">That being said, the huge compatibility list a *great* resource and basis for organizing work for a number of people. Sometimes, QA is great help in defining what makes sense beyond the developer perspective. Throw that up on a wiki with checkboxes and bring your students in on a “make an external/abstraction party”. :)</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="">On Feb 21, 2016, at 10:14 PM, <a href="mailto:pd-list-request@lists.iem.at" class="">pd-list-request@lists.iem.at</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><span class="" style="font-size: 13px; float: none; display: inline !important;">The repo is a fork from the last update in previous maintenance (cyclone version 0.2beta1), which was on its own a fork from cyclone's repo for version 0.1-Alpha56 (available in Pd Extended).</span></div></blockquote><br class=""></div><div class="">Fred did a large amount of work in bring cyclone forward, build-wise and bug wise. Why wouldn’t you start with his work? Seems like a step backwards after all of this...</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">--------<br class="">Dan Wilcox<br class=""><a href="https://twitter.com/danomatika" class="">@danomatika</a><br class=""><a href="http://danomatika.com" class="">danomatika.com</a><br class=""><div class=""><a href="http://robotcowboy.com" class="">robotcowboy.com</a></div></div>
</div>
<div><br class=""></div><br class=""></div></body></html>