-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename to sparks? #3
Comments
Much better name <3 |
I'm not good at physics but don't sparks come before bolts?
or something better. (Advancement|Application|Applied) |
My line of thinking with sparks is that it's a tiny start of a lightning bolt, which is what we describe here: much smaller things than bolts, that could potentially evolve later into a bolt (it remains to be seen if that "upgrade" path makes sense and is ever used). I don't like blast, which sounds "bigger" than bolts, which would give the wrong idea about what we're doing here IMHO. |
I feel like the "are bLIPs a pre-BOLT, or something different (ie just a vendor standard)" question is the question here, and I'm not a fan of renaming to imply one or the other yet. |
Not necessarily, I quite like spark mostly because it's smaller than bolts, a small addition to the ecosystem (and dislike blast because it's bigger), regardless of whether it may or may not become a bolt afterwards? |
Hmm, I can be wrong but from what I understand bLIPs are about 2 things: Unless I misunderstood and this is strictly for potential BOLT-candidates which certainly would be a more focused approach, however there's already bLIP 10 which is mostly on the app-side. Btw, the only real plus of |
Fair enough. I dunno that I care too much about names, or, really, at all. Y'all do what you want :)
I think it depends a lot on who you ask. Based on text in bLIP 1 today, bLIPs are exclusively about (ii) with maybe an exception for things that weren't intended to become BOLTs but which found their way into everything and maybe then could be BOLTs, not things seeking to eventually become BOLTs. |
I see, yeap, I initially got (i) from Ryan's bLIPs intro/proposal on lightning-dev ML, although I didn't translate it precisely. Anyhow, I don't mind about the name, as much as having a fully capitalized word... that lowercase |
yes |
Now that the spec is called
lightning/bolts
, I'd find it really cool if this repo waslightning/sparks
.It could stand for "SPecifications for Additional Really Kool Stuff/Software".
Please vote on this issue with a 👍 (to rename to sparks) or 👎 (to keep blips)
The text was updated successfully, but these errors were encountered: