<div dir="ltr"><div><div><div><div>I am sorry for keeping you wait,but in the last 5 days I can not replay for any email.I hope that you accept my apologies.<br></div>And about the issue which ask me about until now I still thinking how I can solve it.<br></div>If you have any suggestion, I will be grateful for you.<br><br><br></div>regards:<br></div>watfa<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 2, 2015 at 4:00 PM, <span dir="ltr"><<a href="mailto:scribus-dev-request@lists.scribus.net" target="_blank">scribus-dev-request@lists.scribus.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send scribus-dev mailing list submissions to<br>
<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.scribus.net/mailman/listinfo/scribus-dev" rel="noreferrer" target="_blank">http://lists.scribus.net/mailman/listinfo/scribus-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:scribus-dev-request@lists.scribus.net">scribus-dev-request@lists.scribus.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:scribus-dev-owner@lists.scribus.net">scribus-dev-owner@lists.scribus.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of scribus-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: What does ?acknowledged? issue status mean? (JLuc)<br>
2. Re: Dear Oman team (JLuc)<br>
3. Re: What does ?acknowledged? issue status mean? (Gregory Pittman)<br>
4. Re: What does ?acknowledged? issue status mean? (William Bader)<br>
5. Re: What does ?acknowledged? issue status mean? (JLuc)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 1 Nov 2015 14:02:29 +0100<br>
From: JLuc <<a href="mailto:jluc@no-log.org">jluc@no-log.org</a>><br>
To: <a href="mailto:scribus-dev@lists.scribus.info">scribus-dev@lists.scribus.info</a><br>
Subject: Re: [scribus-dev] What does ?acknowledged? issue status mean?<br>
Message-ID: <n152h5$t97$<a href="mailto:1@ger.gmane.org">1@ger.gmane.org</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Le 01/11/2015 11:05, Khaled Hosny a ?crit :<br>
> The immediate issue that triggered my question is #6230, but I?m also<br>
> interested in a general answer as understanding how the bug triaging<br>
> works in Scribus is crucial to outside contributors in general.<br>
<br>
for indepth details on how and why a bug is acknowledged,<br>
look at the bottom of the report and see who did what.<br>
<br>
JL<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 1 Nov 2015 15:11:39 +0100<br>
From: JLuc <<a href="mailto:jluc@no-log.org">jluc@no-log.org</a>><br>
To: <a href="mailto:scribus-dev@lists.scribus.info">scribus-dev@lists.scribus.info</a><br>
Subject: Re: [scribus-dev] Dear Oman team<br>
Message-ID: <n156is$qma$<a href="mailto:1@ger.gmane.org">1@ger.gmane.org</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Le 01/11/2015 06:22, Khaled Hosny a ?crit :<br>
> Do you have examples of untested patches being sent? AFAIK, all patches<br>
> are tested or otherwise how the contributor knows it fixed the issue. Or<br>
> may be I misunderstood the kind of testing needed?<br>
<br>
Well i've recently compiled and tested 2 patches that revealed wrong<br>
and the patche's issues were triggered in simple situations.<br>
<br>
<a href="http://bugs.scribus.net/view.php?id=12195" rel="noreferrer" target="_blank">http://bugs.scribus.net/view.php?id=12195</a><br>
The patch leads to erratic zoom changes for low values of zoom.<br>
<br>
<a href="http://bugs.scribus.net/view.php?id=11365" rel="noreferrer" target="_blank">http://bugs.scribus.net/view.php?id=11365</a><br>
The patch improves the issue and also improves the UX,<br>
but some issue remain when deleting 2 guides.<br>
<br>
These issues are originaly why i wished to remember the students<br>
to this universal cooperating principle : test before submitting.<br>
<br>
Sometimes, a good test requires to first<br>
get the head "out of the code can"<br>
so as to get wider and more user-natural approach.<br>
<br>
Asking a colleague to test is a good alternative,<br>
because an independent tester might find errors<br>
that the developer never thought about.<br>
<br>
Sincerly...<br>
and keep up the good work !<br>
<br>
JLuc<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 1 Nov 2015 14:52:03 -0500<br>
From: Gregory Pittman <<a href="mailto:gpittman@iglou.com">gpittman@iglou.com</a>><br>
To: Scribus Development Mailing List <<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a>><br>
Subject: Re: [scribus-dev] What does ?acknowledged? issue status mean?<br>
Message-ID: <<a href="mailto:56366D63.7040702@iglou.com">56366D63.7040702@iglou.com</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
On 11/01/2015 05:14 AM, Khaled Hosny wrote:<br>
> On Sun, Nov 01, 2015 at 08:35:14AM +0100, JLuc wrote:<br>
>> ale has answered well but here are a few more precisions :<br>
>> in the scribus community only few people are C++ developpers and have commit rights :<br>
>> franz, MrB=Craig and jghali (and also avox when he is there).<br>
>><br>
>> In a bug report their voice should be more important for you to know<br>
>> what features or code will possibly be merged.<br>
><br>
> But asking for core contributors opinion before working on any issue is<br>
> counter productive and decreases the usefulness of the bug tracker<br>
> greatly. On the other hand working on some issue to found that the<br>
> feature is deemed unacceptable is demotivating, such issues should not<br>
> have been kept open in the first place.<br>
><br>
<br>
Like any ad hoc system, it's hard to be always sensible and fair. One<br>
reason for letting some feature request hang out there is to see if<br>
others see the feature as useful. In general, it's not a good idea to<br>
just start implemented requested features unless you know that there is<br>
some consensus that it would be good to have. Sometimes a collection of<br>
minor feature requests can be combined in some new collective feature.<br>
<br>
Generally speaking fixing bugs is a good thing, provided they're<br>
reproducible and produce something drastic like a crash.<br>
<br>
Greg<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sun, 1 Nov 2015 17:12:28 -0500<br>
From: William Bader <<a href="mailto:williambader@hotmail.com">williambader@hotmail.com</a>><br>
To: Scribus Development Mailing List <<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a>><br>
Subject: Re: [scribus-dev] What does ?acknowledged? issue status mean?<br>
Message-ID: <BLU179-W549F372ACEBC38AFDE5ACEC42D0@phx.gbl><br>
Content-Type: text/plain; charset="windows-1252"<br>
<br>
<br>
<br>
> To: <a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
> From: <a href="mailto:gpittman@iglou.com">gpittman@iglou.com</a><br>
> Date: Sun, 1 Nov 2015 14:52:03 -0500<br>
> Subject: Re: [scribus-dev] What does ?acknowledged? issue status mean?<br>
><br>
> On 11/01/2015 05:14 AM, Khaled Hosny wrote:<br>
> > On Sun, Nov 01, 2015 at 08:35:14AM +0100, JLuc wrote:<br>
> >> ale has answered well but here are a few more precisions :<br>
> >> in the scribus community only few people are C++ developpers and have commit rights :<br>
> >> franz, MrB=Craig and jghali (and also avox when he is there).<br>
> >><br>
> >> In a bug report their voice should be more important for you to know<br>
> >> what features or code will possibly be merged.<br>
> ><br>
> > But asking for core contributors opinion before working on any issue is<br>
> > counter productive and decreases the usefulness of the bug tracker<br>
> > greatly. On the other hand working on some issue to found that the<br>
> > feature is deemed unacceptable is demotivating, such issues should not<br>
> > have been kept open in the first place.<br>
> ><br>
><br>
> Like any ad hoc system, it's hard to be always sensible and fair. One<br>
> reason for letting some feature request hang out there is to see if<br>
> others see the feature as useful. In general, it's not a good idea to<br>
> just start implemented requested features unless you know that there is<br>
> some consensus that it would be good to have. Sometimes a collection of<br>
> minor feature requests can be combined in some new collective feature.<br>
><br>
> Generally speaking fixing bugs is a good thing, provided they're<br>
> reproducible and produce something drastic like a crash.<br>
><br>
> Greg<br>
<br>
<br>
Mozilla periodically has "paper cuts" projects where they focus on fixing "the stuff that gets in the way or annoys you about Firefox on a daily basis", see <a href="http://limi.net/articles/papercuts/" rel="noreferrer" target="_blank">http://limi.net/articles/papercuts/</a> and <a href="https://blog.mozilla.org/ux/2013/03/papercuts2/" rel="noreferrer" target="_blank">https://blog.mozilla.org/ux/2013/03/papercuts2/</a> . Regards, William<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.scribus.net/pipermail/scribus-dev/attachments/20151101/38fc1707/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.scribus.net/pipermail/scribus-dev/attachments/20151101/38fc1707/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 2 Nov 2015 08:52:31 +0100<br>
From: JLuc <<a href="mailto:jluc@no-log.org">jluc@no-log.org</a>><br>
To: <a href="mailto:scribus-dev@lists.scribus.info">scribus-dev@lists.scribus.info</a><br>
Subject: Re: [scribus-dev] What does ?acknowledged? issue status mean?<br>
Message-ID: <n174o0$5bf$<a href="mailto:1@ger.gmane.org">1@ger.gmane.org</a>><br>
Content-Type: text/plain; charset=windows-1252; format=flowed<br>
<br>
Le 01/11/2015 23:12, William Bader a ?crit :<br>
> > Generally speaking fixing bugs is a good thing, provided they're<br>
> > reproducible and produce something drastic like a crash.<br>
<br>
> Mozilla periodically has "paper cuts" projects where they focus on fixing "the stuff that gets in the way or annoys you<br>
> about Firefox on a daily basis", see <a href="http://limi.net/articles/papercuts/" rel="noreferrer" target="_blank">http://limi.net/articles/papercuts/</a> and<br>
> <a href="https://blog.mozilla.org/ux/2013/03/papercuts2/" rel="noreferrer" target="_blank">https://blog.mozilla.org/ux/2013/03/papercuts2/</a> . Regards, William<br>
<br>
Scribus has a set of "Most Annoying Bugs".<br>
These require simple conditionss to trigger and "get in the way on a (quite) daily basis"<br>
<a href="http://wiki.scribus.net/canvas/Most_Annoying_Bugs" rel="noreferrer" target="_blank">http://wiki.scribus.net/canvas/Most_Annoying_Bugs</a><br>
<br>
One seems easy to fix : #1752<br>
<br>
One is about undo : #12276 and could be not so difficult to fix<br>
all the more since one student has allready achieved results about undo.<br>
<br>
#11420 and #11814 are related and could be fixed at once.<br>
<br>
Some of them are about layout and probably difficult to fix...<br>
but are a good introduction toward complex scripts layout.<br>
<br>
JL<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
scribus-dev mailing list<br>
<a href="mailto:scribus-dev@lists.scribus.net">scribus-dev@lists.scribus.net</a><br>
<a href="http://lists.scribus.net/mailman/listinfo/scribus-dev" rel="noreferrer" target="_blank">http://lists.scribus.net/mailman/listinfo/scribus-dev</a><br>
<br>
<br>
------------------------------<br>
<br>
End of scribus-dev Digest, Vol 91, Issue 4<br>
******************************************<br>
</blockquote></div><br></div>