This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 97
Pick a less confusing name for ipfs-labs github org #467
Comments
Yeeah I can see how that might be confusing. I don't have the one great idea, but something like:
|
|
IPFS Launch Pad
… On Jun 26, 2017, at 9:22 AM, ᴠɪᴄᴛᴏʀ ʙᴊᴇʟᴋʜᴏʟᴍ ***@***.***> wrote:
ipfs-community
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#467 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABvqNBgWZXkMhkbnEhfLZTckVBuqsDWbks5sH9rTgaJpZM4OFhsj>.
|
What about dropping the
|
I almost went with ipfs-incubator then I realized we can call it ipfs-shipyard, riffing on @JayCarpenter's launch pad suggestion. We're starting to release stuff from that org, like https://github.com/ipfs-labs/shared-editing-demo, so need to settle on a name. I propose ipfs-shipyard Let's allow 24 hours for people to 👍 or 👎 this comment. If it gets any -1 votes we'll check in. Otherwise I will update the organization name to ipfs-shipyard |
Decision on ipfs-shipyard! https://github.com/ipfs-shipyard |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
background: #448
https://github.com/ipfs-labs/
This name is great, and descriptive, but it confuses things because the main company steering IPFS is called Protocol Labs. What's another name we can use for the org that still implies open experiments that are less tightly controlled/maintained?
The text was updated successfully, but these errors were encountered: