Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch language of documentation, development, communication to english #2

Closed
andygrunwald opened this issue Apr 20, 2017 · 5 comments

Comments

@andygrunwald
Copy link
Collaborator

Most of the communication of the LANSuite system is / was done in German.
E.g. in the demo page, documentation or bug tracker at http://lansuite.orgapage.de/

The system LANSuite is mostly spreaded in the DACH area.

Suggestion

My suggestion is to switch the official language to english for everything like

  • Documentation
  • Source code comments
  • Bug tracking issues / discussions
  • and all other topics that affects this project

Why should we do this?

There are a few reasons why this can be beneficial:

  • This might attract more endusers who using this system
  • This might attract more contributor to apply pull requests to the system
  • This is kind of the common standard for open source projects world wide

What about the language barrier?

Yes, there might be a language barrier for non native speakers.
In the OSS world this is common and accepted.
I never met a person who said negative points about not to use a proper time or grammar.
So people will overlook those errors and even might be able to help you to eliminate this language barrier over time to fix typos or grammar issues.

How do we come to a conclusion to solve this ticket?

In my opinion this has to be a decision of the main contributors. I would encourage them to post their +1 for english or a -1 for stay with german here.

@andygrunwald
Copy link
Collaborator Author

Update: @M4LuZ is fine with this as well. He agreed to this in a private email conversation.

@M4LuZ
Copy link
Collaborator

M4LuZ commented Apr 25, 2017

I rather have no strong feelings either way. We should be fine with English as documentation and development language, but it may be beneficial to keep German as valid language for any communication towards/with the end users as they are the current target audience

@andygrunwald
Copy link
Collaborator Author

That is fine for me :)
In my opinion this ticket is clarified and can be closed.
I don't think that we need to document it in the readme, because this is more or less the standard here on github.

@byte666
Copy link
Collaborator

byte666 commented Apr 25, 2017

Also eine englische Doku ist ok... hab ich auch eine Zeitlang versucht aber irgendwann wars für mich Sinnfrei weil in den 14 Jahren wo ich schon mitmische genau 2 Leute aus dem erweiterten EP-Raum in EN nachgefragt haben. Allgemeine Kommunikation muss ich aber sagen hab ich keinen Bock das komplizierte Zeug aus der Lansuite auch noch auf EN durchzukauen. Die Lansuite wird kein Kaliber Wordpress mehr, den Zug haben wir verpasst.

@andygrunwald
Copy link
Collaborator Author

@byte666 Wie @M4LuZ ja schon geschrieben hat. Deutsch kann als Sprache zur Kommunikation auch genutzt werden. Doku dann auch englisch.

mbraun81 added a commit to mbraun81/lansuite that referenced this issue Mar 10, 2018
add check to $teams if instance of mysqli_result to fix #0 db->num_rows() called at [/var/www/lansuite/modules/tournament2/plugins/home.php:51] lansuite#1 include(/var/www/lansuite/modules/tournament2/plugins/home.php) called at [/var/www/lansuite/modules/home/show.php:33] lansuite#2 include_once(/var/www/lansuite/modules/home/show.php) called at [/var/www/lansuite/index_module.inc.php:98] lansuite#3 include_once(/var/www/lansuite/index_module.inc.php) called at [/var/www/lansuite/index.php:415]
@Pimmal Pimmal mentioned this issue Jun 7, 2018
@M4LuZ M4LuZ added this to the LanSuite 5.0 RC milestone Sep 12, 2018
andygrunwald added a commit that referenced this issue Nov 14, 2023
… Argument #2 ($array) must be of type array, null given in /modules/picgallery/show.php on line 372
andygrunwald added a commit that referenced this issue Feb 28, 2024
…rgument #2 ($array) must be of type array, bool given in /code/modules/seating/Classes/Seat2.php on line 376"
M4LuZ added a commit that referenced this issue Feb 28, 2024
[Seating] Fix "Fatal error: Uncaught TypeError: array_key_exists(): Argument #2 ($array) must be of type array, bool given in /modules/seating/Classes/Seat2.php on line 376"
andygrunwald added a commit that referenced this issue Mar 24, 2024
…ment #2 ($options) must be of type array, string
andygrunwald added a commit that referenced this issue Mar 24, 2024
* [Foodcenter] Fix Fatal error: Uncaught TypeError: unserialize(): Argument #2 ($options) must be of type array, string

* [Foodcenter] Fix PHP Warnings and Fatal errors

* [Foodcenter] Use prepared statements to query user barcode

Co-authored-by: M4LuZ <MaLuZ@gmx.net>

---------

Co-authored-by: M4LuZ <MaLuZ@gmx.net>
M4LuZ pushed a commit that referenced this issue Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants