Hello, On Wed, 22 May 2019 at 22:52, Peter Kokot <[email protected]> wrote: > > Hello webmasters, > > I was requested to write email here (apologies for missing that sooner > but my last email didn't get responses because the constant > discussions are probably too time consuming for everyone in their busy > lives so no problem basically, I understand). > > There are few adjustments taking place on the PHP bugs tracker - > application level at the moment. > > Two main things are currently being worked on: > 1.) Bugs categories (a.k.a. packages) > https://bugs.php.net/bug.php?id=78036 > (how good that can be done depends on many things but plan is to move > the categories to static configuration-alike layer instead of the > database directly). So, yes we will finally be able to add some new > bug category, or update current ones. > > 2.) Splitting front controllers to the templates: > We have already discussed this thoroughly and integrated a template > engine in the bugs.php.net and now it's time to split all the www/* > front controllers gradually to the template layer and the "controller" > alike code in the files. > > I've also already integrated a data fixtures importer functionality. > So that on localhost installation we have some demo data to work with > and test how the app behaves. Anyone working today with web apps need > to have also some data already in the app so the local installation > behaves as much similar to the production as possible. Kalle alerted > me, that I've missed the discussion about it here, so now that's > already done and others don't need to invest that more... If it turns > out that we don't need to have demo data on localhost for development, > we'll refactor this more later on. > > For this reason I also use Docker extensively - if someone will want > to use it and install it locally: > https://github.com/petk/bugs.php.net > > Next steps depend here on multiple things. > > My suggestion here is very basic actually for now: > - make code more OOP-alike (mainly the functions usage migrated to classes) > - add more tests > - and finally getting to fix the current opened bugs (there are quite > many and some are not very trivial without some changes in the code - > like moving things around, renaming some files etc). > > In case you're interested in the project progress and plan to also > code on it directly, please start following GitHub and pull requests > (anyone's suggestion and contribution is as always welcome): > https://github.com/php/web-bugs > > To not disorient the progress too much as far as the first two points > are concerned, I'll get forward with those two. > > Thanks and have a nice day forward. > > -- > Peter Kokot
Also a quick response here: I'm leaving these web/* PHP projects. Some have been fixed a bit, most have failed because next steps involve too many things such as accesses and similar which I think PHP internals are not ready for it yet nor actually willing to do. I really appreciate all the effort from some people's side here, you were all doing the best you can, but I think that I'm in a way a bit here with some of the suggestions according to the response(s) I've received here. Well, maybe someone will make it. Doing a change over a discussions that take place over a period of months to half a year is not acceptable for me. Or discussing the PSR-4 autoloading, or Composer, or something from PEAR's museum arsenal... My evaluation of this bugs.php.net project is that it's time for the internals people to sit down, close the mailing list commits (one of the most problematic thing is that people who don't code on this app or have done a semicolon fix give opinions on how the app should be coded) and fix it. Because this is not a usable tracker of bugs for php and belonging extensions. Neither is an open source project as it should be. Not yet... To not make our experiences any worse, the initial plan is now reset and left to the next person working on it or who ever picks this up - Pieter I assume. -- Peter Kokot -- PHP Webmaster List Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
