Author | Comment | Last activity | Moderation | ||
---|---|---|---|---|---|
sarasage | "We are very close to being able to use our bucket kits in the field and want to thank everyone who made a reliable kit based on the CBE buckets. Th..." | Read more » | over 3 years ago | |||
stoft | "Jeff - hands-on experiences are usually helpful even if incomplete. You could tinker with the paper-n-tape process even if there are not enough hou..." | Read more » | about 8 years ago | |||
warren | "Hi, Dave - we're doing some work on this now -- I don't think we have enough spec kits to do the paper-n-tape version here, but we are trying to cr..." | Read more » | about 8 years ago | |||
stoft | "@warren, I posted some draft note on testing to: https://publiclab.org/questions/stoft/09-15-2016/what-mechanical-specs-can-and-should-plab-spectro..." | Read more » | about 8 years ago | |||
rjstatic | "While not MVP, newt compile price <int> will be so cool in the future when there is adoption of this sort of thing. " | Read more » | almost 10 years ago | |||
warren | "I had some ideas (talking with @rjstatic) about how a more Bower- or NPM-style utility could parse such files... these are just roughly sketched ou..." | Read more » | almost 10 years ago | |||
btbonval | "@amysoyka bitbucket can use git or mercurial, which are both options I noted in a previous comment. GitHub is not the same as git. I actually have ..." | Read more » | almost 10 years ago | |||
amysoyka | "@warren What you are talking about reminds me of what Mozilla Science were talking about at the Open Knowledge meetup which Public Labs was also i..." | Read more » | almost 10 years ago | |||
btbonval | "Oh here's a crazy idea. You could point at other contributor.json files by reference using a universal identifier, aka UUID. https://en.wikipedia.o..." | Read more » | almost 10 years ago | |||
btbonval | "Timestamping would probably be better than versioning because version numbers don't always get used in proper ways. Think of forking a feature bran..." | Read more » | almost 10 years ago | |||
btbonval | "That covers the first problem but not the second. So I think you'd need to do one of two things to really preserve the historical contributors: ..." | Read more » | almost 10 years ago | |||
warren | "ah, to look to bower and npm again on that point of the linked-to-projects changing, we could link to a specific version of the contributors.json f..." | Read more » | almost 10 years ago | |||
btbonval | "I think linking to other files would be alright. In that sense, you are emulating a graph by issuing pointers as opposed to trying to copy-by-value..." | Read more » | almost 10 years ago | |||
warren | "I was a bit inspired by bower's bower.json or npm's package.json formats -- and actually, one thought was that the builds_upon would link to more c..." | Read more » | almost 10 years ago | |||
btbonval | "I like that its JSON and that there isn't a hard coded standard. It seems more like a guideline or a best practice, but of course deviation is acce..." | Read more » | almost 10 years ago |