| 1 | | There are currently five tickets open. If you managed to solve the right compiler, this might close two tickets. Another two tickets (#36904/#40333) are again the same issue that is in my opinion just a matter of discussion, making some decision and following that decision in all `wxPython-2.8` dependencies. Then you are left with a single remaining issue (#36594) that should eventually be solved upstream and would probably be avoided if wxWidgets 2.8 was used (the other two tickets). Becomming the maintainer would also be a great chance to get some additional experience. Being a maintainer doesn't mean that you need to be able to solve every single problem on your own. |
| | 1 | There are currently six tickets open. If you managed to solve the right compiler (#32797), this might close two tickets (including this one). |
| | 2 | |
| | 3 | Another two tickets (#36904/#40333) are again the same issue that is in my opinion just a matter of discussion, making some decision and following that decision in all `wxPython-2.8` dependencies. |
| | 4 | |
| | 5 | Then you are only left with: |
| | 6 | * #36594 that should eventually be solved upstream and would probably be avoided if wxWidgets 2.8 was used (the other two tickets); your only task could be complaining about the problem upstream |
| | 7 | * #40315 which could be partially avoided if wxWidgets was made non-optional (complete solution could also involve requesting an upstream fix) |
| | 8 | |
| | 9 | Becoming the maintainer would also be a great chance to get some additional experience. Being a maintainer doesn't mean that you need to be able to solve every single problem on your own. |
