-
Notifications
You must be signed in to change notification settings - Fork 47
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
@osdi scope on NPM #329
Comments
We're not really node experts, so we don't understand what this means. It sounds like it would be useful for the node community. Would you be able to attend a future call to educate us on what this is and how it would be used? |
Of course, I totally understand that. I'd be happy to attend a call and discuss it! |
Nate, can you email me at info@opensupporter.org ? we have a meeting tomorrow. |
@natemoo-re can you email me at info@opensupporter.org ? we have a meeting tomorrow. |
@natemoo-re If there's no further activity on this, the issue will be closed. |
Thanks @joshco – unfortunately I don't have the bandwidth to move forward on this right now. Should that change, I will get in touch. |
People have reported the concurrence of homophobic bullying behaviors like behind the back gossip where their target's voice has been silenced, as well as being threatened with retaliation if they don't participate in a homophobic boycott. If you've have been or come to be exposed to this behavior, and believe the rights of all minorities should be respected on an equal footing, that their voices should be heard, and you wish to be fully informed of the LGBT rights side of this conflict, feel free contact me. |
Related to #328. In the process of finding some way to publish my TypeScript type definitions for OSDI, I discovered that the
@osdi
scope on NPM was still available.I created an organization at http://npmjs.com/org/osdi and would be happy to invite anyone to the organization, or even turn it over to the committee.
It could be a great place to publish official opensupporter resources for the JavaScript/TypeScript communities. For example,
npm install @osdi/types
could provide developers with the types for every data structure in the spec and down the line the jQuery plugin could be replaced with something like@osdi/client
(which is another project I’d love to tackle!)The text was updated successfully, but these errors were encountered: