in projects hosted on GitHub, often only a select few people are allowed to make changes to the online version of the repository, which serves as the “one true” version of the repository. When others have made changes to the project that they would like to contribute to the whole project, they open a “pull request,” requesting that the repository owner “pull in” the changes that they have made.
Pull up resistor
entirely unrelated to software version control, a “pull-up” or “pull-down” resistor sets the “resting state” of an electrical line by providing a weak (high-impedance) connection to a positive voltage (pull-up) or ground (pull-down.) this is typically needed when multiple circuits are “reading” and “setting” the same line by means of transistors or switches (components which physically connect or disconnect the line from ground or +V.) without the pullup/pulldown resistors, the line would be left in a “floating” and indeterminate state whenever no “clients” are actively setting it.
most relevant to modular synthesizer usage, pullup resistors are required in systems which use an i2c bus. (which is active-low.) the amount of pullup resistance required can depend on the number and characteristics of components attached to the bus - the pullup resistance must be large enough to be “defeated” when a switch is closed, but small enough that it still “reads” as a connection to +V when all switches are open. This Sparkfun article explains more about pull-ups from an electronics perspective.
acronym for “read evaluate print loop.” This is a sort of “command line interface” that allows users to try short commands and gain quick feedback about their effect. Maiden’s REPL (at the bottom of the screen) is perhaps the most commonly referenced one here.
short for “repository.” In git, a repository is a folder containing everything to do with a project. Git tracks the contents of these folders to allow for version control and collaboration over the web.
There are some hopefully useful ideas in the below linked thread… I have to go get into Boston commuter hell now so I will let this speak for me until I can get back for more later… thanks again for the support on this!!!
I’m not sure why the distinction is being made of having " on llllllll.co: " in front of the lines posts but if people seem to like that I tried to clean it up a little so it was more readable
I made a couple changes
added SOS secrets
“fixed”? (maybe just to me haha) “on lines:” formatting. if this wasn’t there I don’t think the bolding would be necessary
tried to unify the posting method
if it is on lines then it says so, also that seems to come first in each heading
bolding the important links
formatting on the github heading in tools and environment
added shbobo to language specific
added making music heading
added resources & inspiration (under making music) subheading
added pocket operations
executing the modular album
learning music ableton
modular ahha moments
@GoneCaving I see what you are saying about linking to specific posts I think I’d like a blend of the two potentially (see the shbobo shnth link for how I’d handle it)
EDIT: I thought it would indent nicer than that hmmm maybe that isn’t the solution I’ll leave it up for now and think some more because I do like having the link back to the original start of the thread while also having specific posts mentioned
should live-coding stuff be a separate category in the programming section? planning to add some ORCA IDE & SonicPi stuff later.
@wednesdayayay thanks for the formatting/edits. i think they help a lot. and i’m with you re: a mix of threads & individual posts. some of the threads are focused & content-rich enough to merit full inclusion.
also, i’ll be better able to add to the wiki when i’m not just accessing via phone. i’ll set aside some time with my laptop this weekend & dig in.
I imagine some threads that get posted could have a lot of individual posts linked that would be nice to access quickly in this way
however it sticks out like a sore thumb in the flow of things
it also doesn’t need to always be open which is why this drop down menu is nice
but it can’t be indented at all (at least I can’t figure it out)
I originally conceived that there could be separate pages (or a continuation further below) with further details so that the top-level topical lists wouldn’t get jammed up with a lot of details…
Kind of a table of contents at the top…
Regarding posts and threads, it’s great to have specific links, but in a perfect world it would be great to have teams distilling the gems into more accessible chunks… that would be most user friendly, while also recognizing the value of actually reading threads…