-
Notifications
You must be signed in to change notification settings - Fork 3
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-source collaboration #3
Comments
If smizell won't take over JavaScript part I might do it as well or find some other suitable person. Also let's add the MIT license in the charter repo? |
@zdne I have reached out to Stephen and will hopefully have a hangout tomorrow to see his interest. Will let you know how it goes. |
Also, per MIT license, in the charter repo, shall we add ourselves as the initial members as the copyright holders. In the future, if we pull in some of our exiting libraries, we will probably have to defer to any existing MIT licenses there. E.g. I am going to be talking with my old company about pulling stuff into the project to boot strap the ruby work. We have tons done there already. |
Yes, I'm very interested in the Javascript side of this and would be willing to fork Halpert into this organization. Python is also my strong suit, so I'm interested in that as well, as I've already started experimenting with it. I'd love any help in either of these and would be happy to provide another set of eyes on other languages. |
Hi, Are you still looking for a C# contributor? I'd be interested in picking this up. thanks |
I would like to propose that we agree on organization members who are stakeholders for the various languages we write libraries for. These stakeholders will be a limited set of members who can manage their various projects and accept PRs from the open-source community.
I feel we as organization members should be the ones who chart direction and anyone in the open-source community is welcomed to participate in the implementation.
That being said we would probably want to keep that to a short list (maybe 2 or three individuals per language over time). We don't need multiple initially, but lets just let each other know.
E.g. (presumed examples only)
etc.
Add a comment to this issue about which language you would like to be a stakeholder for so we can keep track of this.
The text was updated successfully, but these errors were encountered: