Edited
Good evening!
I've been having this issue on my mind since at least January, and it's high time to raise it. we have a problem.
For some time now, on polish community we have had separate forums for errors, suggestions and archives, appropriate tags and categorization. And it works very well. Or at least partially, because there are some problems:
1. We don't know which version of the fix is affected,
2. Nor in which specific beta etc. the issue is realized,
but most importantly:
3. It closes us to Poland, Poland and maybe even... well... Poland.
So there are some ideas. I'm not hiding that I'm most tempted to go with the whole Issue Tracking to GitHub. It's a portal that enables programmers to collaborate on software development, very popular and has its own API.
We could use it and even program it nicely from the client level. The advantage of GitHub is the possibility of marking a specific point of proposal realization, combining proposals with changes in the code and so on. Also dividing project development into milestones, opening specific subprojects and goals.
Generally, for me it is a great convenience.
But it does not have to be GitHub. We can even essentially write our own Issue Tracker. However, the problem concerns this internationalization.
I make no secret of the fact that I think very seriously about the requirement to submit all proposals and errors in English. I do not see any other way to communicate efficiently.
Before you answer too fast, I will summarize the matter in two points:
1. Currently the most popular community is the Polish one and many of us do not speak English,
2. On the other hand, also the lack of influence on the project by other communities inhibits them.
I invite you to a serious, thoughtful discussion here, because the topic is not at all simple and obvious. Giving up the Polish discussion about the project may have a huge positive impact on it by facilitating decision making by non-Polish speakers, but it may also have a negative impact by cutting off the widest river of ideas.
With respect,
David Pieper
I've been having this issue on my mind since at least January, and it's high time to raise it. we have a problem.
For some time now, on polish community we have had separate forums for errors, suggestions and archives, appropriate tags and categorization. And it works very well. Or at least partially, because there are some problems:
1. We don't know which version of the fix is affected,
2. Nor in which specific beta etc. the issue is realized,
but most importantly:
3. It closes us to Poland, Poland and maybe even... well... Poland.
So there are some ideas. I'm not hiding that I'm most tempted to go with the whole Issue Tracking to GitHub. It's a portal that enables programmers to collaborate on software development, very popular and has its own API.
We could use it and even program it nicely from the client level. The advantage of GitHub is the possibility of marking a specific point of proposal realization, combining proposals with changes in the code and so on. Also dividing project development into milestones, opening specific subprojects and goals.
Generally, for me it is a great convenience.
But it does not have to be GitHub. We can even essentially write our own Issue Tracker. However, the problem concerns this internationalization.
I make no secret of the fact that I think very seriously about the requirement to submit all proposals and errors in English. I do not see any other way to communicate efficiently.
Before you answer too fast, I will summarize the matter in two points:
1. Currently the most popular community is the Polish one and many of us do not speak English,
2. On the other hand, also the lack of influence on the project by other communities inhibits them.
I invite you to a serious, thoughtful discussion here, because the topic is not at all simple and obvious. Giving up the Polish discussion about the project may have a huge positive impact on it by facilitating decision making by non-Polish speakers, but it may also have a negative impact by cutting off the widest river of ideas.
With respect,
David Pieper