-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collaboration via github #5
Comments
I'd like to add my voice to this. I am using piwik and I'd like to be able to follow the project here (or bitbucket, really) and particularly use the features here to subscribe to issue notifications. |
+1 for github, I am so confused by the SVN process and patching (yes I know it's my fault) |
I submitted 4 commits for 4 tickets in trac. Hopefully this can bring some life into contribution via github. They are a 'mirror' of the submitted patches via trac. |
@chmielot Thanks for posting the patches on Trac. I've closed the PRs here because the team is still using Trac+svn. There's nothing in place to automatically dcommit back to svn, and then update the authors when pushing back to the mirror. The project has moved most of its infrastructure to a new hosting provider. There's still some work to be done (e.g., Jenkins and Trac integration) but moving to git (Github) appears to be the direction. I'll leave this issue open until then... |
This is an old thread, but next week, we will migrate to Github issues! so all of Piwik development will happen on Github http://dev.piwik.org/trac/ticket/5273 |
) * [Coding Style] Enable rules PSR2.Methods.FunctionCallSignature.* * Apply coding style around FunctionCallSignature #1 (#21927) * Apply coding style around FunctionCallSignature #2 (#21928) * Apply coding style around FunctionCallSignature #3 (#21929) * Apply coding style around FunctionCallSignature #4 (#21930) * Apply coding style around FunctionCallSignature #5 (#21931) * Apply coding style around FunctionCallSignature #6 (#21932) * Apply coding style around FunctionCallSignature #7 (#21933) * Apply coding style around FunctionCallSignature #8 (#21934) * Apply coding style around FunctionCallSignature #9 (#21935)
I found a ticket dealing with migration to git. This seems just to be a mirror. Is it possible to submit pull requests via github to fix bugs, too? Or is participation limited to svn patches?
It would be absolutely GREAT to help via github!
The text was updated successfully, but these errors were encountered: