So I had to temporarily remove all his permissions. If Doubaokun can cooperate with us friendly, I can add new permissions for him at any time. Regarding the security issue, the initial warning was on last Saturday, the second warning was on this Tuesday. But the issue is only resolved after the Open Swoole fork. Regarding the 'extremely bad words' were just concern about only matyhtf has the account to do the release and silently push through the package with issues.
At this stage, all the member's releases have to use matyhtf's PECL account which is ridiculous for a project contributed by a group of people. I was trying to stop the security issues to be published on PECL. The purpose is cleared said in the commit log: Added release permission , I didn't listed myself as dev in PECL for 4 years to receive credits and I don't care neither.
Also the fact is that my commits are in the logs, everyone can see it. I didn't try or think to add myself for such a long time and did't expect these things can happen. It is scary to see these things happening and to be removed the Owner role of the organization after you have spend tons of resources on a project for 4 years, then randomly and emotionally removed by another Owner. Then trying to define some new rules make the removing looks like 'legitimate'.
Maintaining something for 4 years doesn't make you a leader. Expecting to become the leader of a sub- project after investing work over years is no good behavior to demonstrate your leadership skills. If you would be ready for a project lead, the entire issue here would have been solved differently and with less drama from your side. Plus I have the Owner role of this whole organization 'previously'. Does not change anything. Your decisions lead to a conflict which you were unable to handle appropriate.
I recommend to fix the root cause of the issue without creating another realm where the root cause still persists. Learn from it, find a solution that does not require to fork or alter directions of a project. And this time, no public drama please.
Maybe you should just share the conversation instead of making vague accusations at each other. From the outside, I wouldn't trust either Swoole or Openswoole at this point. There doesn't appear to be dispute about what happened as far as I can tell both parties agree on what happened and just think they were both justified in their actions.
If multiple people need to be able to make releases, they all need to have their own PECL account, and be lead in the package. If it's not well understood why people are complaining about the addition of code download on the fly:. Adding hot code download in the background inside some random file of the swoole project it's considered shady at best.
Obviously, the correct approach is to create a separate project which contains said dashboard. No one ever could possibly believe that a group of people which have a high degree of coding skills would do this "by accident". And I'm inclined to believe this is why Bruce reacted the way he did. Overall, it is good that this has happened now than in the future when even more projects would depend on Swoole.
If anything Swoole project will become one step better and more resilient to such issues, I believe. If we all leave any personal reasons here aside a bit, doubaokun has pointed one major issue. Swoole project needs to operate more openly and with a bigger development team in mind.
This is not a personal project anymore where Git commits with messages Add something and gazillion new features can land in a patch version. What is needed in Swoole is a semantic versioning a bit and a better communication when something major is introduced in the code. Many projects depend on this extension. And Swoole needs to make sure that those projects will live on with this extension. Also, all team members need to start respecting each others work here.
No matter who started the project and who manages the community announcements on Twitter etc. Discussions and difficulties about changes are normal.
I hope and wish Swoole and OpenSwoole all the best on their way and may both sides resolve the issues as soon as possible. It is very pleasant to see that matyhtf is open to collaboration with doubaokun who contributes on Twitter really a lot. Notice: the documentation is suitable for PHP extension swoole until v4. Latest vesrion: pecl install openswoole Important: Please make sure you have followed the prerequisites guide before trying to install Swoole, this ensures you have an up-to-date system and all the required third-party packages and libraries.
Either compile PHP directly or use your Unix like package installation system, for example on Ubuntu:. Open Swoole is released as a PECL package and can be installed using the command line from the binaries. This is the easiest and quickest way to get working with Swoole. When installing Swoole via PECL, during the installation it will ask you if you would like to enable certain features, this can be provided before running the installation, this helps with automating the installation of Swoole or for when you don't want the installation to stop and wait for input.
Some options require third party libraries to be installed, see prerequisites. Make sure to read the prerequisites first before compiling Swoole. To compile and install the Swoole extension for PHP, we can clone the repository from GitHub where Swoole is developed, checkout the version you want to compile and manually install it. Download the source package from GitHub Releases or clone from the git repository.
The script above will clone Swoole from GitHub, checkout v4. We then use. You can choose which configuration options you need, see the configuration parameters for more information. After installing the Swoole extension to the PHP extensions directory, you will need to enable Swoole so that PHP can load the extension when executing code.
Phone Number. Job Title. Company Size Company Size: 1 - 25 26 - 99 - - 1, - 4, 5, - 9, 10, - 19, 20, or More. Get notifications on updates for this project. Get the SourceForge newsletter. JavaScript is required for this form. No, thanks. Linux Mac. Summary Files Reviews. Project Samples. Project Activity. Categories Networking , Libraries.
License Apache License V2. Follow Swoole Swoole Web Site.
0コメント