zbizu
Legendary OT User
Since it quite doesn't fit issue format, I'm posting it here.
We had a rough week discussing the client and how fixes should be shared, now what about the server? I think that we need a solid to do list that won't be just 2 positions unchanged for years or just a link to issues.
Now you may think that pushing tfs forward is not worth it when otx/that global project is ahead, but remember which repo is their server based on.
Another thing regarding otx: I want to remind you that both projects are open source so it's not a shame to copy a fix from another open project that is based on ours if that leads to improving both. We're a community after all and authors can be credited in commit description. Don't worry, we aren't leechers - our improvements that don't come from them get added to their project eventually so the progress can be mutual.
I feel that we're lacking a direction and at least some user to job list (eg. users a, b and c will code, d and e will do tests, f will control code quality, something like that).
Please take this one seriously. While I understand that we're an open community and everyone can contribute any part, I think that a bit of formal approach could move our project forward.
It's much easier to get work done when we say "you, go do it" instead of "somebody should do it". Of course ideal solution would be "I will do it", but it leads to one person doing a lot and burning out very fast due to lack of any help or recognition, therefore I'm inviting everyone, especially people who have write access to TFS repo to write their thoughts here.
I would also like some short list of
We had a rough week discussing the client and how fixes should be shared, now what about the server? I think that we need a solid to do list that won't be just 2 positions unchanged for years or just a link to issues.
Now you may think that pushing tfs forward is not worth it when otx/that global project is ahead, but remember which repo is their server based on.
Another thing regarding otx: I want to remind you that both projects are open source so it's not a shame to copy a fix from another open project that is based on ours if that leads to improving both. We're a community after all and authors can be credited in commit description. Don't worry, we aren't leechers - our improvements that don't come from them get added to their project eventually so the progress can be mutual.
I feel that we're lacking a direction and at least some user to job list (eg. users a, b and c will code, d and e will do tests, f will control code quality, something like that).
Please take this one seriously. While I understand that we're an open community and everyone can contribute any part, I think that a bit of formal approach could move our project forward.
It's much easier to get work done when we say "you, go do it" instead of "somebody should do it". Of course ideal solution would be "I will do it", but it leads to one person doing a lot and burning out very fast due to lack of any help or recognition, therefore I'm inviting everyone, especially people who have write access to TFS repo to write their thoughts here.
I would also like some short list of
- which things should be done (absolute high priority)
- which "jobs" are needed in tfs repo (so we can create a list of people who would be willing to help). Personally I think that we need more reviewers.
- what is holding us back from moving to client version 12 support? Is that otclient?
Last edited: