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

[RFC] Move non-core related repositories to a friends of org #380

Closed
WyriHaximus opened this issue Aug 3, 2017 · 7 comments
Closed

[RFC] Move non-core related repositories to a friends of org #380

WyriHaximus opened this issue Aug 3, 2017 · 7 comments

Comments

@WyriHaximus
Copy link
Member

Several PR's have been to improve non-core related repositories like espresso, stomp, and partial that would be a shame to waste.

I would like to propose moving them over to an friends of org as a home for projects like that and other projects related to reactphp but that don't fit into the core. That way we can keep the focus of the reactphp org on low level infrastructure packages.

Ping @cboden @jsor @clue @msfidelis @the-eater @shadowhand

@msfidelis
Copy link

I agree with that.

@shadowhand
Copy link

Good idea.

@the-eater
Copy link

Sounds good to me :)

@clue
Copy link
Member

clue commented Aug 23, 2017

Makes perfect sense to me! These repos are clearly distinct from what others see as the "core" and I agree that this would help making this more obvious. Also, the "core" usually tries to stay neutral on framework choices and alike to foster a diverse ecosystem, while the "friends of org" could certainly use a more opinionated approach 👍

@redunta
Copy link

redunta commented Aug 24, 2017

What jargon do you speak gentlemen... friends of org. huh.

@jsor
Copy link
Member

jsor commented Aug 24, 2017

@redunta The Friends of [Project] projects are often github organisations which provide libraries related to that project. A popular example is Friends of Symfony. @WyriHaximus created a similar Friends of ReactPHP organistaion.

@WyriHaximus
Copy link
Member Author

Closing the issue in favour of follow up issue at #382

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

No branches or pull requests

7 participants