Ok, I got stuck here: I cloned the repo: git clone https://github.com/rubys/whimsy-board-agenda-nodejs.git Cloning into 'whimsy-board-agenda-nodejs'...
I was told I could not fork it. Not sure if what I'm doing is all throwaway but I'm willing to try. [MacBook-Pro-10:~/apache/git] clr% cd whimsy-board-agenda-nodejs/ [MacBook-Pro-10:~/apache/git/whimsy-board-agenda-nodejs] clr% yarn start yarn: Command not found. [MacBook-Pro-10:~/apache/git/whimsy-board-agenda-nodejs] clr% which yarn yarn: Command not found. So I googled yarn and found https://engineering.fb.com/web/yarn-a-new-package-manager-for-javascript/ [MacBook-Pro-10:~/apache/git/whimsy-board-agenda-nodejs] clr% npm install -g yarn /usr/local/lib └── yarn@1.22.4 npm ERR! Darwin 18.7.0 npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "yarn" npm ERR! node v6.9.1 npm ERR! npm v3.10.8 npm ERR! path /usr/local/lib/node_modules npm ERR! code EACCES npm ERR! errno -13 npm ERR! syscall access npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules' npm ERR! at Error (native) npm ERR! { Error: EACCES: permission denied, access '/usr/local/lib/node_modules' npm ERR! at Error (native) npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'access', npm ERR! path: '/usr/local/lib/node_modules' } npm ERR! npm ERR! Please try running this command again as root/Administrator. So, I usually suspect requests to run stuff as root. Should I do sudo npm install -g yarn, or chmod to give user clr access to /usr/local/lib/node_modules? > On Mar 19, 2020, at 6:32 AM, Sam Ruby <ru...@intertwingly.net> wrote: > > On Thu, Mar 19, 2020 at 8:40 AM Rich Bowen <rbo...@rcbowen.com > <mailto: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 > <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 <mailto:rbo...@rcbowen.com> >> http://rcbowen.com/ <http://rcbowen.com/> >> @rbowen > > - Sam Ruby Craig L Russell c...@apache.org
