-
-
Notifications
You must be signed in to change notification settings - Fork 234
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
How to contribute #70
Comments
👍 Gonna start getting into Rust game dev. I've been working on a ton of networking in Rust recently.(Designing a gossip protocol) Not sure if multiplayer stuff is in the scope of piston or not. (I also missed the last ludum dare, so I wanna catch the next one and use Rust for it) |
Cool! I is nice to have people looking at Piston from that perspective, because this helps improve the design. Feel free to post issues about ideas around multiplayer, gossip etc. |
We will keep this issue updated even if it is closed. |
Is there a reason we don't have this information in a CONTRIBUTING.md so github points everyone to it when they try and file an issue/make a PR? |
@reem no, I didn't knew about that feature. Do you want to add it? |
Just made a PR adding it. |
Since I've been learning Rust for just two weeks (but I have coded in C++ for ~2 years), and so I'm still a rookie, I'd have some questions:
|
@UberLambda The "Easy" labels are used about stuff that require less thinking. It doesn't always apply to the amount of code. Feel free to look around. Also nice if you open issues about gaps in the documentation. We have no "roof" yet, because we use a very flat maintainer structure. If you got ideas, open up an issue. A scene graph would be very interesting. I picture the Piston project as a set of libraries designed to be used independently but also working nicely together. It is an open question whether the "game engine" lives in the individual parts or the sum as whole. |
@bvssvni I'll try to find something in the easy tasks for now, then 👍 |
Hey all, looking to contribute. Got a lot of time now and I'd like to do some meaningful work in rust. |
@mkcp Welcome to the team! |
Looking to contribute as well. Want to get my feet wet with some larger-scale rust. |
@maxsnew Welcome to the team! |
Hi, I'm was trying to get started with Piston yesterday with the getting-started tutorial (https://github.com/PistonDevelopers/Piston-Tutorials/tree/master/getting-started), but encountered a few bugs due to recent changes to EventIterator. I'd like to contribute and hopefully update the tutorial to work with a bit of help! |
@DarrenTsung Welcome to the team! I sent you an invitation. |
I'm looking to contribute as well. I enjoy bug fixing and am looking to contribute to a large project. |
@dgriffen Welcome to the team! I sent you an invitation. |
Is there a code of conduct for contributors? I was recently added, and had some questions on etiquette. These kind of things can vary from project to project, so just wanted to clarify some things for the Piston group. Some questions:
Looking forward to working with you all! |
@gchp I sometimes do analysis of "best practice" and then label with the "Information" tag. For example, self merging is encouraged under certain conditions #674 because it saves time. When problems appear we usually try to solve them isolated without adding another "rule" that everybody must follow, but we use the same labels everywhere so people recognize them. |
I'd like to contribute to your projects! I am hoping Rust really takes off and I think this is a good place to start. |
@mlschneid Welcome to the team! I sent you an invitation. |
Hi, I'd like to contribute to your project. I've really enjoyed learning Rust so far, and would very much like to contribute to projects I expect to popularise Rust (such as this one). |
@evenlis Welcome to the team! I sent you an invitation. |
I want to contribute to Piston. |
@davekong Welcome to the team! I sent you an invitation. |
@collin5 Welcome to the team! I sent you an invitation. |
I want to contribute to Piston |
@leftiness Welcome to the team! I sent you an invitation. |
I want to contribute to Piston |
@PinkFloyded Welcome to the team! I sent you an invitation. |
I want to contribute to Piston |
@dineshadepu Welcome to the team! I sent you an invitation. |
I want to contribute to Piston |
@robot0 Welcome to the team! I sent you an invitation. |
I want to contribute to Piston |
@quietlychris Welcome to the team! I sent you an invitation. |
I want to contribute to Piston |
@fintelia Welcome to the team! I sent you an invitation. |
I want to contribute to Piston |
@self-unaware Welcome to the team! I sent you an invitation. |
I want to contribute to piston |
@LazyPassion Welcome to the team! I sent you an invitation. |
Would like to contribute. I have several years of development with Atari GEM (helped with several GEM projects) and some experience with Qt/KDE. Would like to help simplify the library, and make things more efficient! |
@KenSuenobu Welcome to the team! I sent you an invitation. |
I think I wasn't officially invited, so commenting here just in case. I'm contributing to 3 repos: |
Since I haven't had any comments on this issue yet but have been in the organization for a while and have contributed, I'd like to retain my status. |
I want to contribute to Piston Specifically: I'd like to help out with Conrod maintenance and attending to issues. |
@shanehandley Welcome to the team! I sent you an invitation. |
@gratispress Can you open up a new issue to discuss this? This thread is for people who want to contribute to Piston and need write access. |
I want to contribute to Piston |
@bodagovsky Have you read https://github.com/PistonDevelopers/piston/blob/master/CONTRIBUTING.md#becoming-a-part-of-the-pistoncollaborator-team ? You don't need write access to contribute. |
I want to contribute to Piston |
@mario-s Have you read https://github.com/PistonDevelopers/piston/blob/master/CONTRIBUTING.md#becoming-a-part-of-the-pistoncollaborator-team ? You don't need write access to contribute. |
The guidelines are moved here
The text was updated successfully, but these errors were encountered: