Re: [Development] (no subject)
Additionally, if you’re reading and replying on your iPhone (as the signatures suggest) there is the option to unsubscribe in the header of every email in the mail app. Sent from my iPhone > On 31. Jan 2020, at 15:23, Florian Bruhin wrote: > > Emily, Jenifer, > > Every post to this list has a link to the list information page in the footer: > >> On Fri, Jan 31, 2020 at 12:02:25PM +, Emily Kaizer wrote: >> Development mailing list >> Development@qt-project.org >> https://lists.qt-project.org/listinfo/development > > You can unsubscribe at the bottom of that page. > > Florian > > -- > m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org > https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ > GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc > I love long mails! | https://email.is-not-s.ms/ > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] (no subject)
Emily, Jenifer, Every post to this list has a link to the list information page in the footer: On Fri, Jan 31, 2020 at 12:02:25PM +, Emily Kaizer wrote: > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development You can unsubscribe at the bottom of that page. Florian -- m...@the-compiler.org (Mail/XMPP) | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] (no subject)
Hi Emily and Jenifer, If you wish be removed from the mailing list, you can unsubscribe via: https://lists.qt-project.org Do not send requests asking to be removed from the list, just unsubscribe following the instructions online. Yours, Tuukka On 31.1.2020, 15.29, "Development on behalf of Jenifer Lambert" wrote: Take me off this list Sent from my iPhone > On Jan 31, 2020, at 5:02 AM, Emily Kaizer wrote: > > Take me off this list > > Sent from my iPhone > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] (no subject)
Take me off this list Sent from my iPhone > On Jan 31, 2020, at 5:02 AM, Emily Kaizer wrote: > > Take me off this list > > Sent from my iPhone > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] (no subject)
Take me off this list Sent from my iPhone ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] (no subject)
http://lists.qt-project.org/pipermail/interest/2015-April/016264.html. I got the same error while starting wayland client with wayland-brcm platform plugin on raspberry pi . Can anyone help me to fix this error ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] (no subject)
___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] (no subject)
I have several patches to Qt4 that I have posted on the bug tracker. Now that the new contribution model is in place, I wanted to submit those as patches. I'm not very familiar with git (we use SVN), and am having trouble at the following step on the Qt Contributions Guidelines page: Qt 4: Add a git remote called gerrit in your cloned repository, which points to the Qt 4 project on codereview.qt-project.org. Note there is currently no Qt 4 reviews on codereview.qt-project.org so proposals should still go to Gitorious. I have absolutely no idea what that means. I looked through the git manual and think I see how to create a remote, but I am not sure what to put as the target. I do not see any Qt4 project on the codereview site, only Qt5. Could someone please explain what the above statement means and perhaps just include the git command I need to run to fulfill the requirement? Thanks! Dave ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] (no subject)
Hi Dave, Welcome! Enjoy your stay. :) On Tue, Dec 20, 2011 at 2:59 PM, Dave Mateer davemateerw...@gmail.com wrote: I have absolutely no idea what that means. I looked through the git manual and think I see how to create a remote, but I am not sure what to put as the target. I do not see any Qt4 project on the codereview site, only Qt5. As the comment implies - for the moment, Qt 4 isn't in gerrit, only Qt 5. There are hopes to change this in the near future, as is being discussed on the list at the moment (http://lists.qt-project.org/pipermail/development/2011-December/000908.html). I'd personally recommend waiting a few days and seeing what the outcome of that discussion is, if you still want to target Qt 4. Could someone please explain what the above statement means and perhaps just include the git command I need to run to fulfill the requirement? To add remotes, you want something like: git remote add nameofremote gitrepourl for instance, git remote add github_backup g...@github.com:rburchell/foo.git git push github_backup master would add a new remote to my current repository, and sync the 'master' branch up to it ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] (no subject)
Could someone please explain what the above statement means and perhaps just include the git command I need to run to fulfill the requirement? To add remotes, you want something like: git remote add nameofremote gitrepourl for instance, git remote add github_backup g...@github.com:rburchell/foo.git git push github_backup master would add a new remote to my current repository, and sync the 'master' branch up to it You might also want to read through the git community book[1] at times. It's quite useful in getting you going on git. [1]http://book.git-scm.com/index.html ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] (no subject)
Posting patches to the JIRA bugreporting system is contrary to the terms of use for that system. https://bugreports.qt.nokia.com/secure/TermsAndConditions.html Don't do this. -Original Message- From: development-bounces+mark.keir=nokia@qt-project.org [mailto:development-bounces+mark.keir=nokia@qt-project.org] On Behalf Of ext Dave Mateer Sent: Tuesday, December 20, 2011 11:59 PM To: development@qt-project.org Subject: [Development] (no subject) I have several patches to Qt4 that I have posted on the bug tracker. Now that the new contribution model is in place, I wanted to submit those as patches. I'm not very familiar with git (we use SVN), and am having trouble at the following step on the Qt Contributions Guidelines page: Qt 4: Add a git remote called gerrit in your cloned repository, which points to the Qt 4 project on codereview.qt-project.org. Note there is currently no Qt 4 reviews on codereview.qt-project.org so proposals should still go to Gitorious. I have absolutely no idea what that means. I looked through the git manual and think I see how to create a remote, but I am not sure what to put as the target. I do not see any Qt4 project on the codereview site, only Qt5. Could someone please explain what the above statement means and perhaps just include the git command I need to run to fulfill the requirement? Thanks! Dave ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] (no subject)
On 21/12/2011, at 12:19 PM, mark.k...@nokia.com mark.k...@nokia.com wrote: Posting patches to the JIRA bugreporting system is contrary to the terms of use for that system. https://bugreports.qt.nokia.com/secure/TermsAndConditions.html Don't do this. I know I'll probably be shot down immediately, but. This is one of the more annoying things about the changes that have been going on with Qt. Previously, it was enough to understand how to build Qt from source, then find the bugs that are affecting you and contribute a fix via posting it to JIRA. Granted, someone else would have to merge in that code into Qt and make sure it went through all the CI systems, etc., but for the average developer, this arrangement was not a significant barrier to helping fix things that were broken. With the new system, we are asking such people to learn a whole lot more just to get their patch submitted for someone to even look at. Previously, you could download a source tarball and that was about as hard as it got. With the new system, you need to be conversant with git and gerrit, plus understand the repository structure. These are barriers that probably mean higher quality contributions, but they also filter out the efforts of those who do not have the time or are not willing to learn the new things. I think the all-or-nothing nature of this shift is unfortunate and I'd really encourage some thought on how we might be able to accept patches from people who are willing to do the work to find and fix bugs (that's the real value here, remember), but not necessarily to also put in the time to work out how to use the new infrastructure. I'm sure plenty of people (most?) on this list are happy with the new system, but I for one am concerned at just how much more complicated it is now to get a relatively simple patch incorporated if you are an average developer. I'm sure processes and documentation will likely be streamlined as we all move forward, but let's also be aware that we are losing some useful contributors as well. -Original Message- From: development-bounces+mark.keir=nokia@qt-project.org [mailto:development-bounces+mark.keir=nokia@qt-project.org] On Behalf Of ext Dave Mateer Sent: Tuesday, December 20, 2011 11:59 PM To: development@qt-project.org Subject: [Development] (no subject) I have several patches to Qt4 that I have posted on the bug tracker. Now that the new contribution model is in place, I wanted to submit those as patches. I'm not very familiar with git (we use SVN), and am having trouble at the following step on the Qt Contributions Guidelines page: Qt 4: Add a git remote called gerrit in your cloned repository, which points to the Qt 4 project on codereview.qt-project.org. Note there is currently no Qt 4 reviews on codereview.qt-project.org so proposals should still go to Gitorious. I have absolutely no idea what that means. I looked through the git manual and think I see how to create a remote, but I am not sure what to put as the target. I do not see any Qt4 project on the codereview site, only Qt5. Could someone please explain what the above statement means and perhaps just include the git command I need to run to fulfill the requirement? Thanks! Dave ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development -- Dr Craig Scott Computational Software Engineering Team Leader, CSIRO (CMIS) Melbourne, Australia ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] (no subject)
On 21/12/2011, at 5:14 PM, Robin Burchell wrote: On Wed, Dec 21, 2011 at 2:57 AM, craig.sc...@csiro.au wrote: On 21/12/2011, at 12:19 PM, mark.k...@nokia.com mark.k...@nokia.com wrote: Posting patches to the JIRA bugreporting system is contrary to the terms of use for that system. https://bugreports.qt.nokia.com/secure/TermsAndConditions.html Don't do this. I know I'll probably be shot down immediately, but. This is one of the more annoying things about the changes that have been going on with Qt. This isn't new. Ever since I've been wanting to submit patches, pretty much, JIRA - at least officially - hasn't been an option for legal reasons, because it bypasses the CLA. The CLA is the primary reason why patches can't be accepted from other sources, as far as I understand it. I've hit that wall too with patches I submitted. Even if you've accepted the CLA though, your patches still are not accepted via JIRA, which is annoying since it's really just a book keeping problem at that point. All the legal stuff is settled (you've accepted the CLA) but how does JIRA know that when you try to upload a patch? How does an issue assignee know that the patch you've provided is legally safe for them to incorporate into Qt? It would be great if someone knew of a way to mark users as having accepted the CLA or not and only allowing them to upload patches if they had accepted it. Maybe even go so far as having to accept the CLA for uploading any attachment to a bug, but that might be annoying for people who just want to report a bug with a screenshot but not also contribute a fix (and I'd expect there would be a non-trivial number of people wanting to do that). Any JIRA ninjas on the list who have ideas for how this could be done? [ that having been said, I agree that it's really annoying, but I can't really see a nice method to solve this, other than possibly directing them to accept the CLA on gerrit the first time they upload a patch to JIRA, but that's going to require customisations.. and in the end, it's probably better to focus on streamlining the contribution review process we have first ] I'd actually suggest the reverse. I would hope that it would be a relatively non-disruptive change to make JIRA aware of who has accepted the CLA and who hasn't. It should be possible to do this without any developers having to know about it. If that is done, then there are no more steps required to allow anyone who wants to submit a patch to do so. In contrast, getting the contribution process in place for gerrit looks like more work and targets a smaller number of users (everyone could submit a patch, but only those willing to learn the process would submit via gerrit). Don't get me wrong, the contribution and review process is a great idea. What I'd really like to see though is the ability for the average developer to submit a patch to JIRA and for the maintainer to be able to then merge in the patch if they are happy with it. The alternative is that the patch is not submitted at all and the maintainer has to come up with the patch themselves. If you are worried that the maintainer would get overloaded with patches, well they can always ignore them until they are ready to deal with them - this is no different to the patches not having been submitted in the first place, which is what the current situation will result in anyway. -- Dr Craig Scott Computational Software Engineering Team Leader, CSIRO (CMIS) Melbourne, Australia ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
