[scribus-dev] scribus-dev Digest, Vol 91, Issue 4

Tue Nov 10 05:43:18 UTC 2015

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.
And about the issue which ask me about until now I still thinking how I can
solve it.
If you have any suggestion, I will be grateful for you.

regards:
watfa

On Mon, Nov 2, 2015 at 4:00 PM, <scribus-dev-request at lists.scribus.net>
wrote:

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