GitHub repo name #3815
Replies: 12 comments 1 reply
-
|
Personally, I like the idea of renaming the repo to stacks-core. I also think the name stacks could work, Some examples of main repositories with minimal names: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @stjepangolemac. Yeah, the stacks-network/stacks repo can contain documentation and high-level details etc. This is similar to how other projects like IPFS have https://github.com/ipfs/ipfs for docs and then the reference implementations (they have multiple implementations). I'd love to hear input from other people as well -- thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I like the idea @muneeb-ali , but you do raise some concerns, namely around redirects using the old repo name. I'm also curious what would happen to forks/stars (as well as specific repo settings around permissions) if we were to rename it, but i think we can run a small test scenario to see what happens. As long we don't hit any major issues with those, this seems like a proposal that makes a lot of sense, with the added bonus of typing less characters. |
Beta Was this translation helpful? Give feedback.
-
Yep, agreed!
The stars and people watching the repo will remain the same. We've done some such renaming before (even on this repo) and that aspect was fine. I think forks also auto redirect but should confirm if that is still the case. I only tested this type of thing a few years back and something might've changed.
Ha, yes! I think with a name like stacks-core it also immediately makes it obvious to new devs that this is like "bitcoin-core" and a reference implementation of a protocol. So far I'm seeing support here e.g., @friedger's thumbs up above. Would love to hear from other folks 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
I like "stacks-core" too, especially as it is in line with "bitcoin-core". Additionally stacks-core is more distinct then just "stacks" which could help findability. |
Beta Was this translation helpful? Give feedback.
-
|
I also like 'stacks-core'. |
Beta Was this translation helpful? Give feedback.
-
|
should we move this to a discussion @muneeb-ali ? |
Beta Was this translation helpful? Give feedback.
-
|
@wileyj yep please to a discussion. I wasn't sure what tag to use to mark as discussion :-) |
Beta Was this translation helpful? Give feedback.
-
|
Catching up here -- was there a decision or some next steps identified? |
Beta Was this translation helpful? Give feedback.
-
|
+1 to @diwakergupta. Can we resolve this? I think most people are supportive. @wileyj what's the best way for next steps? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Done |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
This discussion has been automatically locked since there has not been any recent activity after it was closed. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone!
It's great to see increased open-source contributions lately (I assume Bitcoin Summer hackathon/sprint can be one reason!). I've been meaning to start a discussion topic here RE the name of this Github repo. I think it is safe to say that this is the most imp Github repo and as the decentralized ecosystem continues to grow we expect more devs and users to discover and interact with it.
I think the name stacks-blockchain doesn't accurately represent what users should/would expect from this repo, especially after Nakamoto release. The comms WG is moving to a Bitcoin L2 terminology which will appear at various places in the ecosystem in the coming months. See this for more details on Stacks as L2 or not. Here are some points to note:
If most users and devs get introduced to the project as a Bitcoin L2 then seeing the term "blockchain" in the repo might be confusing. Stacks L2 will still obviously have chain state and a ledger but the term "blockchain" typically refers to L1 chains.
This repo might start including code for sBTC signers and even validating blocks (see latest proposal from Aaron for better blocks). With this expanded functionality the term "blockchain" might not be appropriate e.g., if I'm running a signer or a validator, using stacks-blockchain repo for that might not be intuitive.
Given the above reasons, I want to proposal that we rename stacks-blockchain repo to stacks-core. This name will better fit the convention where the reference implementation of Bitcoin is called bitcoin-core. I understand that this renaming might break some links (although Github has been very good about redirecting things) and might cause some other headaches for devs and automated testing tools. So we should definitely discuss it further and see if the potential benefits are worth it and the potential downsides can be mitigated.
This is a good time to have this discussion given the rest of the Github repos and README files are also getting cleaned up and updated to bette reflect what the repos are used for now (vs some earlier state). Thanks!
Beta Was this translation helpful? Give feedback.
All reactions