On Thu, Mar 19, 2020 at 8:40 AM Rich Bowen <rbo...@rcbowen.com> wrote: > > My experience with Whimsy matches every project I've ever tried to > contribute to. > > When I looked at the code with a vague "I want to get involved" mindset, > it was inscrutable nonsense. Not because it *was*, but because I had no > goal. > > When I had a specific thing that I wanted to fix - an itch to scratch - > the code was pretty clear, and it was fairly clear where I needed to > scratch. Also, the people on the Slack channel gave me the direction I > needed when I got lost, so there was the community building aspect of > "bad code, good community" that Stefano advocates.
Thanks. And as long as there are people interested in contributing, I'm interested in helping them get started. > So, sure, change to a different language if you think it'll help, but > without people trying to scratch specific itches (which is, really, the > heart of the Whimsy project, even more than most!) I don't think it's > the right solution. It won't *hurt*, of course, but I don't think it'll > help much. > > If anything is lacking, it's clear working docs about getting a local > copy working for testing purposes. (Yes, there are instructions. No, I > was not able to get it working. Yes, I'm still trying.) Are these instructions unclear: https://github.com/rubys/whimsy-board-agenda-nodejs ? If not, where did you get stuck? > All just MHO, based on possibly a dozen hours working on the project. > Take that for whatever it's worth. > > -- > Rich Bowen - rbo...@rcbowen.com > http://rcbowen.com/ > @rbowen - Sam Ruby
