Timeline for When joining open source project, how to get out of the code review swamp?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20, 2022 at 9:27 | answer | added | x64 | timeline score: 0 | |
| May 4, 2022 at 11:13 | answer | added | mngeek206 | timeline score: 2 | |
| Apr 18, 2022 at 19:20 | answer | added | Andy Lester | timeline score: 3 | |
| Apr 14, 2022 at 6:55 | comment | added | x64 | I try to adhere to the published standards, the hell begins with standards that are not published so can only be learned the way "do wrong once, fix and then remember". | |
| Apr 13, 2022 at 19:30 | comment | added | doneal24 | Many projects have coding standards that should be adhered to. For example, the Linux kernel guide here has advisory standards. Check with the project that you're working with to see if they publish standards for changes. | |
| Apr 13, 2022 at 14:53 | vote | accept | x64 | ||
| Apr 13, 2022 at 13:47 | answer | added | Philipp | timeline score: 12 | |
| Apr 13, 2022 at 0:25 | comment | added | curiousdannii | If all the feedback in reviews is non-constructive, then that might just be indicative of the people in that project's development team. It hasn't been my experience. Keep trying contributing to other projects! | |
| Apr 12, 2022 at 11:23 | history | asked | x64 | CC BY-SA 4.0 |