#103

Here is an issue over on github. As I mention over there, totally happy to be told that we should move in a different direction, just happy to contribute to the discussion :grin:

3 Likes
#105

I commented on your proposal @robbbiecloset. Cool ideas there!

I wanted to bring up in here, that as I use norns more I am now feeling like treating the state of dust as a 1:1 mapping of the library stored on norns that something like my naive idea that is basically a button to do git fetch && git reset would not really map to how I want to use norns.

I want to follow along (and explore) when people like @dan_derks @martinmestres work through super cool scripts in gists and the review thread. I want to grab stuff like the experiments @jflee is doing on remixing scripts to work with different engines. (and Iā€™m pinging yā€™all to see what ways yā€™all would like to (or to not) share these things for others to download before they are ā€œdust-readyā€)

EDIT: also, once you do it once, the SFTP path and manually adding stuff to the file system really is not that terrible of a way to grab scripts.

1 Like
#106

script project management is high on our list for the next update, so weā€™ll be discussing it here more in the near future.

on that note, if anyone could spare a few minutes and make a norns-SFTP howto (in markdown with a screenshot or two) itā€™d be great to add this to the docs. (iā€™ll get there after the next study otherwise!)

6 Likes
#107

How does everyone feel about starting a community sample library? Iā€™ve got some samples that I think work well with scripts that Iā€™d be happy to share, and maybe others feel the same. They could live within the audio/common directory or perhaps in itā€™s own directory. Of course filling up disk space is a concern, so the samples would have to be well curated.

8 Likes
#108

Apologies if this has been covered already, but whatā€™s the protocol for adding features to existing scripts? Should we contact the original author to make sure they approve of the change before opening a PR?

Also, I noticed only a couple scripts list ā€œenhancementsā€ under ā€œissuesā€ in the repo. Maybe it would encourage more collaboration if people got in the habit of listing desired features for individual scripts there?

I just received my Norns last week and I thought a nice way to learn it would be to update some of the existing scripts, but I donā€™t want to step on anyones toes if theyā€™re working on that same script concurrently, and also wouldnā€™t want to add something to a script if the original author doesnā€™t like the change.

2 Likes
#109

Iā€™ve largely asked people on here - in threads or in private. People are pretty cool - certainly Iā€™ve interacted with a lot of the people with scripts on the Norns right now and everyone has been lovely. I suspect given the nature of lines it will stay that way.

None of my stuff is on there yet (but soon - Kria port is well underway as part of Islands and Iā€™m hoping to have the standalone midi version in PR next week - and maybe even Islands released too) and certainly Iā€™ll be more than open to changes - probably prefer to talk first just because like you say - donā€™t want to be doing duplicate/conflicting work

1 Like
#110

Personally speaking, I think making changes to an existing script should probably happen in the form of a github PR. I wouldnā€™t mind seeing a random PR notification, but it would also be nice to know itā€™s coming, that way I could potentially share some guidance to my script.

If your changes are substantial enough to warrent it being called something different, thatā€™s fine too. I see it in lotā€™s of open-source environment (and itā€™s sort of the whole point that we build off of each other). Itā€™s probably best practice to credit the original in your documentation. Even if an author doesnā€™t like the fact that youā€™re using/editing their code (unlikely), they donā€™t really have reasonable means for complaint as it exists in an open-source environment.

I definitely agree with this.

1 Like
#111

Has anybody taken a look at a sort of icon/glyph system or library for norns? I wouldnā€™t want to make the platform homogenous in any way but it could be a handy resource (and something I would enjoy contributing to)

5 Likes