Menu
▾
▴
Re: [Tiki-devel] December TRM - Tiki Roundtable Meeting today!
|
From: Guillaume L. <gu...@sl...> - 2019-12-21 16:42:52
|
luci asked me to share my thoughts to the dev list on a point we've discussed during the last RTM that is: * How can we get more people attracted to/interested in Tiki? so here we go. first let me mention that there are different definitions of what "attracted to/interested in" mean. that could be trying, using, spreading the word, marketing, editing the docs, etc... i focus here on development (and design): * tiki is currently using its own PHP coding standard. that makes it hard for newcomers to join (my belief + talking from experience). if tiki has enough contributors, then it could enforce its own standard, but if we're looking for contributors, let's use the most common one. the PHP-FIG is built by big heads from the PHP world that discuss together to enhance projects/frameworks interpretability. the common coding standard for PHP followed by most project ~~is~~ was PSR-2 (it's getting extended now by PSR-12). most big projects/frameworks are using it. even when they have their "own" standards, it's actually an extension of PSR-2 (where they had a few of their own rules on top of it). i'd suggest switching to it. there's no point fighting those standards, if we're looking for more contributors. if we're not then it's fine, we can just do anything we like, as long as the whole community uses it. * the passage to git will help greatly, i believe. again, less entrance barrier to join the project * for javascript it's not as straightforward as for PHP. there's several big coding standards out there (google, airbnb, etc...). personally i like to use semistandard JS. it's just standard JS, that is a set of rules that you can't modify: no config file, no tweaking, nothing. it just works. semistandard JS is standard JS but while adding the semicolon ';'. the semicolon is not necessary in javascript, but if you're not expert in it (i'm not, i focus on PHP), you might end up with weird bugs as the js engine is mixing several statements into one. * (possibility to run a full test suite easily would be a great bonus, as probably standard composer directory structures/usage, but that's another story.) those are the thoughts. let's see what the community thinks? if we decide to make a change, i can work on that. tiki currently already uses PHP CodeSniffer ( https://github.com/squizlabs/PHP_CodeSniffer ) to highlight the coding standard errors. this handles of course PSR-2 and could be switched very quickly. there's another tool from the symfony guys calle PHP CS Fixer ( https://github.com/FriendsOfPHP/PHP-CS-Fixer ) that can also fix/format the code automatically (when save, or with keyboard combo), according to rules defined in a config file. there's also editorconfig files ( https://editorconfig.org/ ) that set up IDEs according to file types an rules set up for a project. all those config files work for all editors (PHPStorm, Sublime Text, VS Code, etc...) by default or with plugins. all those things wouldn't be hard to do, but would allow everyone to be on the same page + open contributors to easily dig in the project as the standards would be similar to what's happening in most projects. also i want to add that this wouldn't require to update the whole source at once. we can format files only when are working on them for something else, and therefore update the source little by little. what matters is not that the whole source is changed to a new standard, what matters is that newcomers know directly which standard to use, and that it is a common one, not one that is specific to tiki, which would put off people who don't want to make such a huge jump into tiki's world. let us know what you think! if we decide to move, i can start working on it. if not, then we keep as it is now :)) enjoy the holidays! —— Guillaume Leclerc sleeplessmind.com.mo ( https://sleeplessmind.com.mo ) +853 6239 0630 On Fri, Dec 20th, 2019 at 1:57 PM, Bsfez Tiki <bs...@ti...> wrote: > > Thank you all for your wishes for my recovery. > > > Live long and proper > Bernard > > >> >> > > On 20 Dec 2019, at 14:15 , luciash < lu...@ti... > wrote: > > > > Oh! Get well and recover soon Bernard! > > > > Merry Christmas and Happy Hanukkah to you and your family too! > > > > luci > > > > PS: here is the recording ;-) https://recordings.rna1.blindsidenetworks.com/citadelrock/d559965849921585c1849af03b7a51638700d979-1576763971053/presentation/ > > > > > > > > Dne 19.12.2019 v 16:01 Bsfez Tiki napsal(a): > > >> Enjoy the meeting ! >> >> I had an encounter with a serious virus a few weeks ago and I’m still >> recovering. :( >> (I still can’t hear a dam thing) >> >> >> Hopefully Santa will bring more steroids and I’ll be fine for 2020. >> >> >> Happy Hanukkah, Merry Christmas, happy New Year and happy Underdog Day >> (wth ?) >> >> >> Bernard >> >> >> >> >> >> >> >>> On 19 Dec 2019, at 13:19 , Roberto Kirschbaum < rob...@gm... > >>> wrote: >>> >>> Thanks Luci! >>> >>> >>> See you all soon. >>> >>> >>> br >>> Roberto >>> >>> On Thu, Dec 19, 2019 at 10:35 AM luciash < lu...@ti... > wrote: >>> >>> >>>> Hi devs, >>>> >>>> this is a gentle reminder we have a TRM today 14:00 UTC! >>>> >>>> https://tiki.org/Roundtable-Meeting-2019-12 >>>> >>>> Add your last minute topics! >>>> >>>> luci >>>> >>>> _______________________________________________ >>>> TikiWiki-devel mailing list >>>> Tik...@li... >>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >>>> >>> >>> >>> _______________________________________________ >>> TikiWiki-devel mailing list >>> Tik...@li... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >>> >>> >> >> >> >> >> >> _______________________________________________ TikiWiki-devel mailing >> list Tik...@li... https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel >> > > > _______________________________________________ > TikiWiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > > > |