{"action":"created","issue":{"url":"https://api.github.com/repos/mloskot/qt-creator-plugin-boostbuild/issues/13","labels_url":"https://api.github.com/repos/mloskot/qt-creator-plugin-boostbuild/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/mloskot/qt-creator-plugin-boostbuild/issues/13/comments","events_url":"https://api.github.com/repos/mloskot/qt-creator-plugin-boostbuild/issues/13/events","html_url":"https://github.com/mloskot/qt-creator-plugin-boostbuild/issues/13","id":58137661,"number":13,"title":"Preparing contribution of plug-in to Qt Creator","user":{"login":"mloskot","id":80741,"avatar_url":"https://avatars.githubusercontent.com/u/80741?v=3","gravatar_id":"","url":"https://api.github.com/users/mloskot","html_url":"https://github.com/mloskot","followers_url":"https://api.github.com/users/mloskot/followers","following_url":"https://api.github.com/users/mloskot/following{/other_user}","gists_url":"https://api.github.com/users/mloskot/gists{/gist_id}","starred_url":"https://api.github.com/users/mloskot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mloskot/subscriptions","organizations_url":"https://api.github.com/users/mloskot/orgs","repos_url":"https://api.github.com/users/mloskot/repos","events_url":"https://api.github.com/users/mloskot/events{/privacy}","received_events_url":"https://api.github.com/users/mloskot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":22,"created_at":"2015-02-18T22:16:43Z","updated_at":"2015-05-06T10:23:20Z","closed_at":null,"body":"As it is explained in the README/FAQ, originally I wasn't going to contribute the plug-in to Qt Creator, but @jhunold suggested (#8 and #12) it would be beneficial for the plug-in if it is maintained as part of Qt Creator.\r\n\r\nLet's discuss what it takes, tasks and steps needed, to submit the plug-in to Qt Creator.\r\nI have also announced this issue on Qt Creator ML: [Preparing to contribute Boost.Build Plugin to Qt Creator](http://lists.qt-project.org/pipermail/qt-creator/2015-February/004436.html)\r\n\r\nAFAIU, according to the guidelines I've found, here is the procedure and related issues:\r\n0. Basically, follow [Qt Contribution Guidelines](http://qt-project.org/wiki/Qt-Contribution-Guidelines)\r\n1. [Build Qt Creator](http://doc-snapshot.qt-project.org/qtcreator-extending/getting-and-building.html) using the repository from Gerrit, then build the plug-in against such build.\r\n2. [Setting up Gerrit](http://qt-project.org/wiki/Setting-up-Gerrit)\r\n3. Follow the [Qt Creator Plug-in Contribution Guide](https://wiki.qt.io/Qt_Creator_Plug-in_Contribution_Guide), where I see a few issues:\r\n * ~~What does *merge request on gitorious.org* mean?~~ Andre Poenitz from Qt clarified that this is completely outdated nonsense. He'll try to correct it. All Qt and Qt Creator code submissions need go through gerrit (codereview.qt-project.org) for quite some time.\r\n * Presumably, *coding standard conformance* is deal breaker, becasue I did neither follow Qt Coding [Qt Creator Coding Rules](http://doc.qt.digia.com/qtcreator-extending/coding-style.html). If I'm asked to restructure and reformat the plug-in codebase, it's going to be a time issue.\r\n * There is *tangible commitment by the submitter to help maintain the code*, as the [Qt Creator Plug-in Contribution Guide](https://qt-project.org/wiki/Qt_Creator_Plug-in_Contribution_Guide) suggests, but I can't make hard promises. @jhunold would you be willing to join me?\r\n\r\nThe points 2 and 3 are not a mystery, so I will proceed, but it is not clear to me how to perform the actual code submission to Qt Creator for review. Would you be available to help and clarify, @jhunold?"},"comment":{"url":"https://api.github.com/repos/mloskot/qt-creator-plugin-boostbuild/issues/comments/99409104","html_url":"https://github.com/mloskot/qt-creator-plugin-boostbuild/issues/13#issuecomment-99409104","issue_url":"https://api.github.com/repos/mloskot/qt-creator-plugin-boostbuild/issues/13","id":99409104,"user":{"login":"jhunold","id":3115501,"avatar_url":"https://avatars.githubusercontent.com/u/3115501?v=3","gravatar_id":"","url":"https://api.github.com/users/jhunold","html_url":"https://github.com/jhunold","followers_url":"https://api.github.com/users/jhunold/followers","following_url":"https://api.github.com/users/jhunold/following{/other_user}","gists_url":"https://api.github.com/users/jhunold/gists{/gist_id}","starred_url":"https://api.github.com/users/jhunold/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhunold/subscriptions","organizations_url":"https://api.github.com/users/jhunold/orgs","repos_url":"https://api.github.com/users/jhunold/repos","events_url":"https://api.github.com/users/jhunold/events{/privacy}","received_events_url":"https://api.github.com/users/jhunold/received_events","type":"User","site_admin":false},"created_at":"2015-05-06T10:23:20Z","updated_at":"2015-05-06T10:23:20Z","body":"Glad to hear that you have solved your problems. I'm still swamped with work but will get the latest changes from gerrit today. Backup on GitHub is a good idea.\r\nI think that you/we should simply request/gpush a merge from master to our wip-branch. This is what all other repositories do all day. "}}