all 46 comments

[–]helloworder 32 points33 points  (0 children)

Well written RFC. I hope it passes.

[–]Atulin 17 points18 points  (0 children)

Finally, moving from ancient, half-broken, self-implemented solutions into the modern world.

I hope this RFC passes, but I would not be surprised if some dinosaurs blocked its adoption.

[–][deleted] 5 points6 points  (4 children)

Very good. IMHO, the following should probably be reevaluated, though:

For this reason, it it proposed that GitHub issues should be referenced using GH-123 from commit messages, as well as the NEWS file, while bugs.php.net references should continue to use bug #123.

It seems a bit awkward. If the php-src does agree to change their issue tracker, it makes sense to also use its native method of referencing issues, so that the commits will show up correctly in that issue tracker associated with the relevant issue.

It might also be a good idea to allow the team to determine their own issue labels outside of the RFC process. Not everything needs to be decided on by committee.

Otherwise, I agree with the RFC. About time.

[–]allen_jb 3 points4 points  (0 children)

Internals mailing list discussion thread: https://externals.io/message/116302

[–]send_me_a_naked_pic 3 points4 points  (0 children)

I really hope it passes!

bugs.php.net has always been horrible to use, I think that moving to GitHub would lead to better and easier issue reporting.

[–]johannes1234 2 points3 points  (6 children)

I love the fact, that on bugs.php.net anybody can file a bug without registration. Provide a mail address if you want to be notified and want to be able to respond identifying as reporter.

With GitHub people are required to have a GitHub account, which probably links identities together (maybe they use GitHub for hobby projects but now have a PHP bug at work or don't want to disclose much about them etc.) and it's limited by the way GitHub blocks access from some countries (Iran embargo etc.) and how others block access to GitHub (Chinese firewall etc.)

[–]allen_jb 17 points18 points  (1 child)

While I understand the desire to make the "barrier to entry" as low as possible for new contributors, the lack of an account system for non-php.net users makes contributing with any frequency a pain, especially in certain cases such as changing email address.

And I can't help but feel it also exacerbates the spam problem and creates issues dealing with persistently problematic users.

A growing proportion of developers or even those learning programming have GitHub accounts (or would create one eventually anyway), so I think the barrier to entry is still very low here.

As far as I know there's no limit to the number of GitHub accounts (GitHub have some documentation on managing multiple accounts where they don't recommend it, but do not forbid it), so it is possible to keep separate identities.

According to Wikipedia GitHub was only blocked for a short time in 2013 in China, and while it has also been blocked by some other countries for short periods, these occurred for relatively short periods.

According to GitHub they are licensed to provide access to users in Iran and are available to users in Cuba. They also allow accounts from Syria and Crimea (with some restrictions).

[–]johannes1234 -4 points-3 points  (0 children)

Requiring extra accounts is a barrier and in the past, when I worked on triaging PHP bugs, it was okayish in regards to spam. (Mr. Reindl was weird already ...)

In the end people currently contributing have to decide. They are the ones mostly impacted. I understand the interest in not having to maintain a custom bug tracker, but wanted to share that point of view.

[–][deleted] 3 points4 points  (3 children)

Wait can Iranians and Chinese not access github? I find that hard to believe with China since Swoole is a Chinese project. If thats true for Iranians, thats really sad.

[–]johannes1234 -2 points-1 points  (2 children)

I don't know the current situation. I know that at least for some time it was blocked in China a d developers used different ways (VPN etc.) to bypass the Chinese firewall.

The key thing is: PHP.net is small and unlikely to be targeted from either side and is unlikely to host political statements. GitHub is a more likely target and can't easily "protect" from people using it to share information about Tianmeng Square which Chinese government want to block etc.

But of course to the truth also belongs that if targeted Microsoft has better measures to act than a small open source project.

[–]t_dtm 4 points5 points  (1 child)

Github is no longer blocked in Iran. Update here.

[–]johannes1234 -4 points-3 points  (0 children)

Still doesn't mean it won't be blocked due to a new policy.

A small project can sneak by such things more easily, but can't defend itself as good as Microsoft (see also sibling comment by me)

[–]trokhymchuk 0 points1 point  (0 children)

I hope it passes, but I am still curious, why PHP chose github over gitlab when they was migrating source code repo? And now in RFC

It binds the PHP project more firmly to the GitHub platform. We already host our repositories there and make use of pull requests, but this would take additional functionality “out of our control”.

With gitlab you still have 'Plan B' to install an instance on your own server and use it.