-
Notifications
You must be signed in to change notification settings - Fork 594
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
Moving image libraries to separate open source organization #881
Comments
Which organization do you have in mind? |
Create a new one? |
I'd propose we create |
@bvssvni what exact packages do you have in mind? Format decoders/encoders or filters too? |
I feel like this is the right step, thought about creating |
|
Nah, we don't depend on image crate. Did you consider rustgd org?
… On Mar 15, 2019, at 06:58, Eduard-Mihai Burtescu ***@***.***> wrote:
gfx-rs seems already related to this area (although it's pretty clear their use of "graphics" refers to GPUs), but I'm not sure they want to take all of these crates in.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Since I'm not planning to take much responsibility in the future, I want people who are interested in this to decide the direction to go. I think that decoders/encoders should be moved with the image crate. |
What about some group related to servo (or the servo project itself)? They host many other crates only related to pure rendering as well, including but not limited to 2D graphics library Skia. We surely need to ask, but first should try to evaluate if contributors to these projects would feel okay with that change and clear up potential licensing concerns. It would surely take responsibility from you @bvssvni 😄 . |
I don't think Servo relies on the image crate for its function either, so they wouldn't be interested. |
My main concern for moving these libraries is security, so it would be preferable to use an organization with higher security than PistonDevelopers. |
|
@nox who seems to be contributing to both |
I suggest that we go with @fintelia idea of creating Created https://github.com/image-rs |
Here is the plan:
The idea is that we first focus on moving a single project, to figure out what issues and concerns people have. Once these are figured out, we can move the other projects quicker as people feel comfortable with the new organization. |
The |
@eddyb Sure! |
I'll give the few people that I invited ownership permission to the new organization, in case anything unexpected happens during the transition period. This does not mean that one has to agree to leading the organization by accepting the invitation. We'll deal with these issues later. |
OK, we have now 2 people besides myself with ownership permissions, making the transition safe in case anything unexpected happens. I'll wait 24 hours to see if there are any last objections with the plan before we proceed to step 2. (see #881 (comment)) In 24 hours (or more), I will transfer the |
The I've created 3 teams:
|
The Publish team has now access to publish on crates.io. Github teams can not add or remove owners, so we need at least one extra owner. I suggest adding two people in case anything unexpected happens. @HeroicKatora , @theotherphil are you willing to be added as owners on crates.io to the |
@bvssvni Could you also add me to the image-rs organization? |
That would be fine for me. |
@fintelia I've sent you an invitation! |
@fintelia are you willing to be added as owner on crates.io to the |
Sure |
I've now added @HeroicKatora and @fintelia to the Publish team, in case something unexpected goes wrong on Github. I've removed myself from the Publish team. Two steps remaining before the security is improved to the minimum I wanted:
I'm waiting for @fintelia to accept the invitation as owner on crates.io for |
I'm starting to discuss two issues on gitter to get things going: https://gitter.im/image-rs/community
|
After the other repositories are moved as well, I plan to restrict my access on Github to the Merge team. Before I do that, I would like to have the inviting policy to Merge and Publish resolved (whether to copy the Piston project or figure out something else). This can be done in parallel. Otherwise I can't think of anything that might prevent the new organization from running smoothly. I would trust to the current three owners on Github to lead the organization in the immediate period after the transition (in alphabetic order): @fintelia , @HeroicKatora , @theotherphil . I'm open to other suggestions, and have no strong opinions of how the tasks should be shared, or what leadership in the long run. What I recommend is building an Admin team so owners only have to appoint new administrators. And, of course, adding new owners in case there is shortage on people with necessary permissions to run things smoothly. I might contribute from time to time, but I won't try to influence policy making if the people running this want to go in another direction. My main focus will be on the Piston project. |
Btw, happy 0th birthday image-rs! |
I think the most critical problems to solve/communicate:
Also, it might be cool to have a blog in which every member can contribute to their own separate space. Both to get a feeling of involvement and an outlet for ideas and progression. And we should do regular progression posts (once every one/two months maybe? every six weeks?) on the overall project there and actively invite collaboration on these from new contributors and older ones alike. |
Yes |
The inviting policy is now resolved. @fintelia @theotherphil I'm waiting for you to accept the invitation as owner of |
@bvssvni I've already accepted, is it not showing up? |
@fintelia Look here: https://crates.io/crates/image |
Oh, oops. Done |
Also oops. Also now accepted. |
Can I be added too, please? |
Information regarding the invites: A short guide on the new structure regarding contributing. Remember to follow the Code of Conduct
|
I've now removed the Publish team under the Piston project as owners on crates.io for The transition of |
Will the |
@pizzaiter These issues should probably be raised in the repository of the crate they concern. I'm going to close the transition as finished. |
@PistonDevelopers/pistoncollaborator @PistonDevelopers/admins
I think it's time to consider moving image libraries to a separate open source organization.
Once the transition is made, I plan to reduce my own access.
The text was updated successfully, but these errors were encountered: