advices #1707
Replies: 1 comment
-
welcome! @davidp88 :)
there are priority lists ("Projects"). This is yet to be used. (This can still be done better with a single project (with priority as a 'label, 'milestone or 'status)
Many contributors (volunteers), assumably work on their own system. Sometimes working for themselves and the public only as a bonus. Happy to "only, help for example for 15% of users soon, while being understandably bored to increase width rather than height and just hope for other to pick it up for other systems etc. - Our project must be on the verge to be self-sustain, since we can try to invite several % of users to github, discord, etc. Most of your advice above seems to fit for most repos(?), besides " |
Beta Was this translation helpful? Give feedback.
-
1.Think completely and work and that thinking should be done at once ,do like this when writing also as little thinking causes mistakes.
2.think of each bit of how it can be improved but don't add useless features
3.Increase patience
4.Do important work first
5.If u can't reproduce a bug normally then test thoroughly and try to reproduce for 2,3 times
6.As far as possible try to reproduce bugs in win10 64bit as most of the users in the world use win10.
Make this read by your developers or else mistakes will happen.If they completely think and work then bugs will be properly fixed
Beta Was this translation helpful? Give feedback.
All reactions