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

jpeg-js is now an Open Open Source Project #27

Open
eugeneware opened this issue Jun 27, 2017 · 5 comments
Open

jpeg-js is now an Open Open Source Project #27

eugeneware opened this issue Jun 27, 2017 · 5 comments
Labels

Comments

@eugeneware
Copy link
Collaborator

eugeneware commented Jun 27, 2017

Hi everyone,
@mrkelly @strandedcity @patrickhulce @XadillaX @petli @wmossman @benwiley4000

I've just released jpeg-js as an Open Open Source Project

This means that:

Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.

See the CONTRIBUTING.md file for more details.

This has been done in order to scale the maintenance of small but popular node.js modules like jpeg-js and also to put the governance and control of the project into the hands of it's user and greatest stakeholders.

As a result, all past contributors (ie. you've landed a commit into jpeg-js) have been given contributor (ie. commit access) to this repo.

You should have been sent an invite which you need to accept to get contributor access.

The includes the following fine people, which are also listed on the README under the contributor list.

jpeg-js is only possible due to the excellent work of the following contributors:

AdobeGitHub/adobe
Yury DelendikGitHub/notmasteryet
Eugene WareGitHub/eugeneware
Michael KellyGitHub/mrkelly
Peter LiljenbergGitHub/petli
XadillaXGitHub/XadillaX
strandedcityGitHub/strandedcity
wmossmanGitHub/wmossman
Patrick HulceGitHub/patrickhulce
Ben WileyGitHub/benwiley4000

I've been personally struggling to stay across the open issues for this project, so as contributors, please feel free to help to triage, review, resolve issues as you see fit :-)

And once again, a huge thanks for all your support and contributions of this project!

Currently I've added anyone that I could guess their npm usernames to also have npm publish rights as well. If you haven't been added correctly let me or any of the other owners know and we'll sort that out.

Cheers,

Eugene

@patrickhulce
Copy link
Collaborator

Awesome news thanks for sharing the project @eugeneware! It'd be great to get a list of others interested in reviewing changes as well :)

@benwiley4000
Copy link
Collaborator

Cool, thanks for trusting us to help out @eugeneware!

P.S. I think I still have "contributor" rather than "collaborator" status, which hasn't offended me yet, though I'm not sure it's what you intended. 😉

@eugeneware
Copy link
Collaborator Author

@benwiley4000 I must have messed up. You should have an invite now:

image

@XadillaX
Copy link
Collaborator

I think my name in the table can be just XadillaX

@benwiley4000
Copy link
Collaborator

@XadillaX you should be able to edit it yourself 😛

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants