[Development] issue tracker rights

Joseph Crowell joseph.w.crowell at gmail.com
Thu Feb 7 02:06:00 CET 2013


On 02/07/2013 02:11 AM, Charley Bay wrote:
> Mitch sayeth:
>
>     I think a lot of people are hesitant to contribute fixes because
>     of all of the
>     setup required to contribute, also (yeah, it's easy once you are
>     familiar with
>     it). <snip>,
>
>
> +1
>
> It would be nice to make this, "turn-key".
>
> For example, on platforms like Windows, it "would-be-nice" to have an 
> "installer" that you could download, which installs a 
> "QtContributor.exe", which is a simple GUI to pull Qt modules or 
> otherwise make "easy" the local-codebase management and 
> compiling/linking/install of a module configuration.
>
> I don't want to make "more-work" for anyone, but I think a 
> "contributor-IDE" with contributor-utility-help would be useful 
> (enter/search-for/reproduce bugs, pull module updates so bugs could be 
> reproduced/fixed/verified, etc.)

How about an optional Qt Creator plugin shipped with Creator but 
disabled by default? I know disable by default would be fairly simple 
because the TODO plugin was done that way for a while.

>
> If we want "casual-users" to find/reproduce/look-at bugs, a 
> one-click-setup would be great, IMHO.  Yes, once it's "in-place", it's 
> easy.  But it's not easy getting it "in-place".
>
> Also, many of us must maintain "clean-reference" development 
> environments where we maintain "last-released" development in addition 
> to (wanting-to) closely follow new Qt module development.  An easy 
> "module-configurator" tool would be nice for this.  I'm thinking of 
> something like a simple GUI on top of Thiago's 
> Qt-module-selector/configurator-scripts.
>
> --charley
>
>
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130207/2bd45411/attachment.html>


More information about the Development mailing list