I just do not know the rules either!!
I have been all over github and i see old and outdated posts. people crying to be assigned etc...
Ad another thing is When im looking to edit files or to just look at the files. I can ever get to find your conventional old .html and .css and or .js files.
I wanna provide solutions but i find myself getting lost in the myriad .md or someother form of jsx etc ocean of type of files. this is not at all like the tutorials.
It's easier to contribute to a project you actively use, than coming into a new project without having experienced it a lot as a user.
Think of the parts you do already use - perhaps your first contributions can be via the forums, answering questions you know the answer to, or testing the scenarios in people's questions and raising well-described bugs if you find any - or even checking for known bugs to link to forum questions.
Then, some projects just aren't very well documented (how to build this? what are the requirements? how to test this?), and have no clear starting point. They would clearly benefit from a contribution documenting the basics - maybe you can provide this :-)
The more you go through this, the more you get to see of the project, and the files start to make sense .
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
yes awesome post .Me too!!!
I just do not know the rules either!!
I have been all over github and i see old and outdated posts. people crying to be assigned etc...
Ad another thing is When im looking to edit files or to just look at the files. I can ever get to find your conventional old .html and .css and or .js files.
I wanna provide solutions but i find myself getting lost in the myriad .md or someother form of jsx etc ocean of type of files. this is not at all like the tutorials.
What is the big deal.
Please help us.
It's easier to contribute to a project you actively use, than coming into a new project without having experienced it a lot as a user.
Think of the parts you do already use - perhaps your first contributions can be via the forums, answering questions you know the answer to, or testing the scenarios in people's questions and raising well-described bugs if you find any - or even checking for known bugs to link to forum questions.
Then, some projects just aren't very well documented (how to build this? what are the requirements? how to test this?), and have no clear starting point. They would clearly benefit from a contribution documenting the basics - maybe you can provide this :-)
The more you go through this, the more you get to see of the project, and the files start to make sense .