If you are looking for people's opinions, then mine would be, "this is fine". I already use GitHub for my own business projects, and it's the defacto standard. Many other free and open source projects also rely on GitHub for managing their repos. The network effects are undeniable, and it will likely increase visibility of the project.
If the move is coupled with a blog post somewhere, that could be shared to social media such as Hacker News and garner more attention as well, potentially.
GitHub also has a lot of resources and features that may prove useful. You can take advantage of GitHub Actions (not sure how many come with the free plan) to automate some processes. Not sure if that's where you want to go, but it's an option. I use it for automating my tests before allowing merges with the master branch of some projects, for example.
I am not saying you *should* move the project to GitHub, I am just saying I support your decision and your reasons for doing so, if that makes sense.
Long time PDT user
On Mon, May 4, 2020 at 2:45 pm, Dawid Pakuła <zulus@xxxxxxxxx> wrote:
As I mentioned in past, we have to push project forward. Since we lost support from Zend we have to find more contributors (commiters, testers, etc..).
In long term, I and Thierry can’t be only developers.
I believe that most of PHP developers currently have account in GitHub:
1. Symfony Framework / Symfony Libraries
2. Zend Framework / Laminess
7. Most composer libs
So I want move our project to GitHub also:
1. We can use travis for path-builds
2. Github branch/pull-request rather than Gerrit path set
3. One-commit - one-feature can be achieved via force push on feature_branch
I hope this will allow us to reach new people.
Any thoughts/objections. If not I’d like to start migrations process after two weeks.