Discuss : Best Practices

[gabru-md]

This issue is for discussion only.
Please write down the best practices that you consider must be contained into this organisation.
Let us all write what we consider to be a good practice, since this is a for-community org, we must work together.
So let us start by writing a simple yet beautiful Best-Practices Guide together.

Thank You Everyone.
Please start commenting down below.

[Manas-kashyap]

One, should be given a good time to solve the issue, as this community is not serving a company, its a community where one will learn things by taking time and do so , no one should make him or her feel like they are inferior in knowledge, in this community , everyone is good and everyone has a scope to be the best .
So giving the right amount of time to solve issues, it would be great, plus, we should guide them ,

[xeon-zolt]

how should time be decided (maybe the user can give an estimate of how much time he requires once he takes up the issue ) or it can be decided on the level of difficulty but it may vary person to person.

[Ananthavijay]

I think choosing time is a wrong thing..

When a user is assigned to a issue, PR's from others should not be considered.
If the assignee has some doubts he can ask in gitter to telegram.

[xeon-zolt]

@Ananthavijay what if the assigned user have not sent a PR ! and other are not sending PR cause its assigned to someone else

[Ananthavijay]

If the assigned user is not active, lets say for 1 week. Lets unassign him by saying this "Unassigned due to inactivity" or lets ask him on gitter or telegram. What u say @xeon-zolt

[gabru-md]

A good practice shall be
Creating a Pull request from a separate branch rather than the main branch of the repository. It means if the repo is maintained on development, then the PR must not come from the development branch of any fork