Also push changes to the original gist?

[ziadoz]

Also push changes to the original gist?

[h4cc]

This could be done using Travis-CI.
But i would suggest keeping it as is to keep this repo the single point of truth :)

[Potherca]

You wouldn't even need Travis, just adding another remote to the local git repo should work (after some initial fiddling to get the histories to match).

As there is no nice webpage for this repo, one of the advantages would be that the list could be accessed from gist-blog services like bl.ocks/gist.io/roughdraft:

http://gist.io/1677679
http://ziadoz.roughdraft.io/1677679
http://bl.ocks.org/ziadoz/1677679

(Ofcourse, a gh-pages branch that loads the data from the list could also work for this 😄)

As everything would still link to the github repo I don't think it will be diluted as "the true source", there would just be another high-profile way in (Google still ranks it rather high when looking for "awesome php list" ).

I could be wrong, it might not be worth the effort. Who knows?

[ziadoz]

The main reason I moved over to a repository was to make it easier for people to submit suggestions and pull requests. @h4cc is right, though — this repository should remain the canonical source. Ideally Github would have a gist redirect option, then I could just redirect people here.

I know people would like a website, too, but I don't have any finalised plans just yet.