Skip to content
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

open it up? #1

Closed
jbenet opened this issue Jun 22, 2015 · 2 comments
Closed

open it up? #1

jbenet opened this issue Jun 22, 2015 · 2 comments

Comments

@jbenet
Copy link

jbenet commented Jun 22, 2015

hey @whyrusleeping we should open this up, i wanna start using it and playing with it. feel free to open it up under protocol/ or under whyrusleeping/ or whatever you want.

once you open it up, i'll start using it + compiling feedback and post it in the repo. I'll have it as criteria:

  • MUST handle go-specific packaging/distribution concerns well
  • SHOULD handle go-specific module system concerns well[0]
  • MAY handle packaging/distribution concerns well
  • MAY handle module system concerns well

[0] go get's failure as a module system stems from not realizing a "module system" is different from a "package distribution tool". And this distinction is where npm shines (node packaged modules).

@whyrusleeping
Copy link
Owner

alright, i'll open it up under my name for now

@travisperson
Copy link
Collaborator

You should add install directions, as well as make sure it actually works. I'll give it a try again. Might just have to try a shell script unless someone knows some make magic.

@jbenet jbenet closed this as completed Aug 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants