Thanks for guidance so far ! I looked at all responsibilities of PHP tribe leader, sorry, I am unable to commit to all the community management tasks at this time. I updated the other two tasks assigned to me, created some bug reports on first pass-through, and thinking how to revisit PHP specs again. I created https://issues.apache.org/jira/browse/NETBEANS-1367 proposing a bunch of them being taken out (both from netbeans and test specification list). I do not think it is worth spending limited time we have verifying UI that even though might work as part of these tests, will not work in a real project today. The way I see it, these NetCAT tests will be false positive passes. And while the JIRA issue is created only for frameworks (for the sake of organization), I am tempted to stretch this proposal to the entire list, as the test specification (Eg. Doctrine 2) is still targeting PEAR workflow which is gone for 6 years now. Those frameworks can be put back once verified against composer workflow.
Next week when I will get to do real testing, I will test how well the dialogue detects composer libraries for PhpUnit and some others, which do not have config fields with bias of global install the way larger frameworks do. If you agree, I will clone the spec, and delete the risky entries, and the PHP plugin can be updated accordingly. ср, 3 окт. 2018 г. в 18:10, Jiří Kovalský <[email protected]>: > Hi Alex, > > Dne 3.10.2018 v 21:51 Alexander Romanenko napsal(a): > > > 1) In the list of tribes, UnitTesting is described as "JUnit and TestNG > > frameworks". Since PHP is one of goals, I am wondering, will PhpUnit not > be > > part of the verification or that is just a description error. > > PHPUnit will not be part of the verification unless someone writes at > least simple test specification for that. Will you be so kind enough to > write one for that Alex? > > > 2) Some frameworks listed, or the usecases are no longer relevant. > > Eg. Zend Framework 2 has long been superseded by 3, and now Zend > Expressive > > is next big thing, so that should not even be listed, I think. > > "Doctrine project" type no longer makes sense either, because everything > is > > exclusively done through "Composer Support". There are no longer global > > pear installations to detect. > > PHP tribe is missing its leader. We would love to see you take over this > role if you are interested. As a tribe leader you can update the list of > valid test specifications and remove those which are obsolete or add > missing ones. Let me please know if you would like to become PHP tribe > leader. > > > Is the process of removing them as simple as cloning the Synergy > > specification and deleting them? (no permission to do that so far) > > You are now member of the PHP tribe so please give it a try now. > > > 3) Are new PHP projects still should say "Create new PHP *5* project"? > > If PHP plugin still supports version 5+, why not? If you miss the + > character, create a bug for that, fix it, create a pull request and we > will cherry-pick it into the 10.0 release branch. > > Thanks a lot for your activity! > > -Jirka > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
