Quote:
Originally Posted by John Peterson
I want to bring attention to this message
> * there's no significant disadvantage or inconvenience with discussing a patch on GitHub compared to Launchpad
|
* there's no significant disadvantage or inconvenience with discussing a patch on Launchpad compared to GitHub.
Quote:
Originally Posted by John Peterson
> * there's no significant disadvantage or inconvenience in applying a patch from GitHub bcause the patch is retrieved from a .patch suffix to the commit URL and can be applied with `bzr git-apply` |
* there's no significant disadvantage or inconvenience in submitting a patch via Launchpad.
Quote:
Originally Posted by John Peterson
> * GitHub is popular and it's therefore within reasonable flexibility to allow discussion there
|
* Launchpad is popular and it's therefore within reasonable flexibility to use it.
Quote:
Originally Posted by John Peterson
> * Allowing code discussion on GitHub too encourage competition between the sites which is beneficial
|
* Allowing code discussion on Launchpad encourages collaboration on calibre which is beneficial. Competition between two hosting services isn't the goal of calibre and outside of calibre's scope.
Quote:
Originally Posted by John Peterson
* Allowing patch discussion on GitHub might bring more ideas and coding effort to the project because some users prefer to discuss patches there
|
Let's see you're willing to use Launchpad simply because you don't want to even though that's what calibre uses and what every calibre developer uses. This tells me two things. 1) You're not able to take any level of criticism because you won't make even the slightest attempt to work within calibre's development guidelines. 2) You're contributions no matter how brilliant are going to be more trouble then they're worth.