Hi Den man. 10. dec. 2018 kl. 17.35 skrev Peter Kokot <peterko...@gmail.com>: > Composer has been under discussion over a year now, so it's a pretty > logical choice I think. I'm not sure if there's anything else besides > Composer today out there that can install dependencies in such a > breeze... > https://github.com/php/web-bugs/pull/27
But there still have not been any discussion on the webmaster list, which is where we discuss such things at all, that is what baffles me the most that such a move has not even been mentioned here, which is where the development of the website systems takes place. > PEAR dependencies themselves have been made obsolete also in some commits > here: > http://git.php.net/?p=web/bugs.git;a=commit;h=23298a123688443276f60143c1261f85a85873fe > > and mostly also by the fact that none of these dependencies produce > warning-free outputs anymore. There is currently only one dependency > used in bugs.php.net and that is Text_Diff which doesn't work ok on > today's PHP versions. It's even deprecated and horde's Diff should be > used. > > Now, installing any dependency for production actually is not yet > possible because the deployment step needs an additional composer > install step somewhere here: > https://github.com/php/systems That is fine and all that PEAR itself is getting obsolete, but if we break down the dependencies then its all native PHP besides the Text_Diff component you mentioned. I don't really think anyone uses this as a standalone bug tracker anyway as its so baked into the PHP.net systems and not customizable so I kinda fail to see the point when its only running on one machine. I'm sorry for the blantness but it seems a bit pointless to me. I mean sure if you are installing and developing locally but its such a minority. > About the additional EditorConfig file and its configurations, those > were picked by current majority of open source code style in the > community out there. We can reinvent the PSR-2 code style again but I > would really like to avoid doing that. Running the php-cs-fixer tool > is very simple and works out of the box without any additional > configuration file. Basically, the sensible defaults are pretty > standard for the PHP code so it's nothing so drastic. Currently, > bugs.php.net code uses somewhere around 3 coding styles together with > a free-style which is definitely not going anywhere in any organized > direction as I see it. Something like that. As for CS, we have always refered to the PEAR Coding standards[1] (with a minor exception to the examples in the PHP documentation as noted in the tutorial[2]), and I don't see any discussion about changing this anywhere on the discussions nor making it for web/bugs only so far. I don't want this to come out as too negative, whilst I do appreciate the care being taken to update the system, I just prefer we do it with discussions where we all can chime in, I do miss most of them as I'm only subbed to the php-src on github (webmaster ML is the official). [1] http://pear.php.net/manual/en/standards.php [2] http://doc.php.net/tutorial/style.php -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
