<_whitenotifier-f>
[solvespace] phkahler commented on pull request #626: Fix issue #295 keep circles to 16 edges minimum. - https://git.io/JfXNH
f8l has quit [Ping timeout: 260 seconds]
_whitelogger has joined #solvespace
ohsix has quit [Ping timeout: 260 seconds]
ohsix has joined #solvespace
f8l has joined #solvespace
ohsix has quit [Ping timeout: 256 seconds]
ohsix has joined #solvespace
ohsix has quit [Ping timeout: 246 seconds]
mauz555 has joined #solvespace
<mePy2[m]>
whitequark: I think you are taking it too heavy. Mine would be just an easy way to get into the code. I will not write any code if I do not deeply understand the actual code. To be honest you should already have something about the code. An overview of the entire project. I know it is the fault of no one. And I know many projects do not have such a thing. But if you really would like to make things well you should have
<mePy2[m]>
it, for yourself above all. Also, it took you a year to understand the codebase. It makes little sense to me that each new person who wants to contribute should spend a year or more to understand the codebase because no one provided a simpler way to do it. I mean, I am not saying it will not require time to understand the codebase, but with a support, I am sure it will take half of the time.
<whitequark>
mePy2[m]: to put it another way, the workload I have for SolveSpace is already more than what I can manage. I'm not going to add to it unless it has a direct and immediate benefit to the project
<whitequark>
is that unfair? yeah, it is. life is generally unfair
<whitequark>
there's an enormous backlog of patches on the tracker that i should review and merge before i even get around to any *new* contributions. some of those have been sitting there since 2017
<whitequark>
once we get that sorted out it makes sense to look at sweeping new changes
<whitequark>
of course i'm not the only developer (anymore), but insofar as i will spend any time on this project it will go to address that backlog first and foremost
<whitequark>
that's one part of the problem
<whitequark>
the other part of the problem is that most of what i learned in that year? unnecessary. it's simply a consequence of idiosyncratic design that requires keeping so much info in your head
<whitequark>
rather than painstakingly describing it (and in the process making it more permanent), i'd much rather make the codebase more approachable
<whitequark>
i've been doing that for quite some time too; it's better than before, though there's still much to do
<mePy2[m]>
Ok... again, I want to precise that I do not want to make any contribution to the code, atm. What can I do atm, in order for a day in the future to contribute to the code, is to analyse the code and write my understanding. Yeah, maybe it is a work I do for myself mostly. But _maybe_ someone else could take advantage from it. Just that.
<mePy2[m]>
And since I am lazy, I do not want to learn by myself the code, knowing that other people too before me, knows how it works. Just that!! 😄
<mePy2[m]>
If someone else, would like to help me, just write me :P Someone who already knows the codebase is preferred but anyone who wants to contribute is welcome ;)
<mePy2[m]>
* If someone else would like to help me, just write me :P Someone who already knows the codebase is preferred but anyone who wants to contribute is welcome ;)
<mePy2[m]>
* Ok... again, I want to precise that I do not want to make any contribution to the code, atm. What can I do atm, in order for a day in the future to contribute to the code, is to analyse the code and write my understandings. Yeah, maybe it is a work I do for myself mostly. But _maybe_ someone else could take advantage from it. Just that.
<mePy2[m]>
And since I am lazy, I do not want to learn by myself the code, knowing that other people too before me, knows how it works. Just that!! 😄
mauz555 has quit [Read error: Connection reset by peer]