5 ms·

I completely understand your concerns, especially given the issues that NPM had lately. We are an open-source focused company and our success is tightly tied to

I completely understand your concerns, especially given the issues that NPM had lately. We are an open-source focused company and our success is tightly tied to the success of our open-source solutions. Here are some of the things that we are doing in order to resolve (or minimize) the concerns: * Completely open API to retrieve the registry data (it's a work in progress, but our GraphQL API is open to everyone to use: https://registry.wapm.io/graphql https://registry.wapm.io/graphql ) * De-centralized hosting of the packages (news to come soon!)

yuvipanda 8y ago
Thanks! This is a good start. Do you have ideas on how you will make the governance of the registry open? Who will make important decisions around policies, and how will they be made? I personally find this to be the core reason I find it hard to use startup-run package registries.
- deleted 8y ago
  [deleted]
- syrusakbary 8y ago
  We are starting to research on governance, but to date nothing is defined (since we have just launched). However, I would love to follow up with you personally to make sure we make the right choices from the start. Can you write me an email to syrus@wasmer.io so we continue the conversation there?
badsectoracula 8y ago
> our success is tightly tied to the success of our open-source solutions It is not obvious from your website, so if your success is tied to your open source solutions - as you say - how do you actually make money?
jake_the_third 8y ago
> De-centralized hosting of the packages (news to come soon!) Is the index also going to be changeable? Will I be able to completely avoid your servers if I wanted to?
hobofan 8y ago
> * De-centralized hosting of the packages (news to come soon!) Given that "integration in package managers" is a big point in the IPFS 2019 Roadmap[0], I'm going to guess those two are related. [0]: https://blog.ipfs.io/78-ipfs-2019-roadmap/ https://blog.ipfs.io/78-ipfs-2019-roadmap/
intertextuality 8y ago
How are you going to make money? How are you going to fund offices in CA + developers + the operating costs of the registry? I really don’t think a private entity should be running a registry. Ruby is just about the only example of a registry handled correctly - via the community and non-profits.
- fnord123 8y ago
  Ruby is an example of it done so wrongly that other languages are chopping their hands off to avoid making the same mistakes. Apparently there is a namespacing in the Ruby repository and Github started automatically pushing every fork to the repo as a gem. So fnord123/cool-project would also have intertextuality/cool-project just because you forked it. And it was a nightmare to figure out which one was the right one. Now the Rust team avoids namespaces like the devil citing the Ruby issue even though there are people begging to have something like Java's scheme since it works. So really, Java is just about the only example of a registry handled correctly - distributed and namespaced and signed.
  - intertextuality 8y ago
    Sigh. There is a difference between architectural design (namespacing), and funding income. I am -not- discussing the software architecture of rubygems here, please don't start a bikeshed with that. Rubygems is a shining example of how non-profits and the ruby community fund rubygems, not yet-another-californian-company-without-clear-income-plans. Also, there's no need for highly embellished language ("languages are chopping their hands off").
    - fnord123 8y ago
      Fair enough. I jumped the gun because I agree with your actual point and then I moved onto the sliver where it's possible to disagree.

yuvipanda 8y ago

Thanks! This is a good start. Do you have ideas on how you will make the governance of the registry open? Who will make important decisions around policies, and how will they be made? I personally find this to be the core reason I find it hard to use startup-run package registries.

deleted 8y ago
[deleted]
syrusakbary 8y ago
We are starting to research on governance, but to date nothing is defined (since we have just launched). However, I would love to follow up with you personally to make sure we make the right choices from the start. Can you write me an email to syrus@wasmer.io so we continue the conversation there?

badsectoracula 8y ago

> our success is tightly tied to the success of our open-source solutions It is not obvious from your website, so if your success is tied to your open source solutions - as you say - how do you actually make money?

jake_the_third 8y ago

> De-centralized hosting of the packages (news to come soon!) Is the index also going to be changeable? Will I be able to completely avoid your servers if I wanted to?

hobofan 8y ago

> * De-centralized hosting of the packages (news to come soon!) Given that "integration in package managers" is a big point in the IPFS 2019 Roadmap[0], I'm going to guess those two are related. [0]: https://blog.ipfs.io/78-ipfs-2019-roadmap/ https://blog.ipfs.io/78-ipfs-2019-roadmap/

intertextuality 8y ago

How are you going to make money? How are you going to fund offices in CA + developers + the operating costs of the registry? I really don’t think a private entity should be running a registry. Ruby is just about the only example of a registry handled correctly - via the community and non-profits.

fnord123 8y ago
Ruby is an example of it done so wrongly that other languages are chopping their hands off to avoid making the same mistakes. Apparently there is a namespacing in the Ruby repository and Github started automatically pushing every fork to the repo as a gem. So fnord123/cool-project would also have intertextuality/cool-project just because you forked it. And it was a nightmare to figure out which one was the right one. Now the Rust team avoids namespaces like the devil citing the Ruby issue even though there are people begging to have something like Java's scheme since it works. So really, Java is just about the only example of a registry handled correctly - distributed and namespaced and signed.
- intertextuality 8y ago
  Sigh. There is a difference between architectural design (namespacing), and funding income. I am -not- discussing the software architecture of rubygems here, please don't start a bikeshed with that. Rubygems is a shining example of how non-profits and the ruby community fund rubygems, not yet-another-californian-company-without-clear-income-plans. Also, there's no need for highly embellished language ("languages are chopping their hands off").
  - fnord123 8y ago
    Fair enough. I jumped the gun because I agree with your actual point and then I moved onto the sliver where it's possible to disagree.