On Fri, Jun 7, 2013 at 2:32 AM, Tommaso Cucinotta wrote:
> On a related note, following LyX through time, I noticed that if something
> is really easy to fix, or if anyone thinks so, then it mostly happens that
> the person will provide a fix and drop it onto the list. On the other hand,
> when it
On 27/05/13 21:08, Scott Kostyshak wrote:
> However, I will never be sure unless I actually solve the bug myself.
+1 :D!
Just a remark on the easyfix thread: how easy it is to fix, might greatly
depend on the experience and knowledge the developer has about the specific
part of the code that is a
On Mon, May 27, 2013 at 3:57 PM, Vincent van Ravesteijn wrote:
> But please be sure that you know when something is easy to fix or not ;)..
> (see bug #8664).
Thanks for correcting that, Vincent. OK I will be more careful.
However, I will never be sure unless I actually solve the bug myself.
Op 27-5-2013 22:04, Scott Kostyshak schreef:
On Mon, May 27, 2013 at 3:40 PM, Vincent van Ravesteijn wrote:
On the other hand, I'm not sure whether marking bugs as 'easyfix' will
really help.
I'm fine with this. I just wanted to see if others thought it would
*hurt* anything.
Scott
No, it do
On Mon, May 27, 2013 at 3:40 PM, Vincent van Ravesteijn wrote:
> On the other hand, I'm not sure whether marking bugs as 'easyfix' will
> really help.
I'm fine with this. I just wanted to see if others thought it would
*hurt* anything.
Scott
Op 27-5-2013 21:40, Vincent van Ravesteijn schreef:
Op 27-5-2013 21:13, Uwe Stöhr schreef:
Am 27.05.2013 20:10, schrieb Scott Kostyshak:
Scott, please don't mark bugs as easyfix if they are apparently
not that
easy to fix. If this bug would be easy to fix, somebody would
have done
this
Op 27-5-2013 21:13, Uwe Stöhr schreef:
Am 27.05.2013 20:10, schrieb Scott Kostyshak:
Scott, please don't mark bugs as easyfix if they are apparently
not that
easy to fix. If this bug would be easy to fix, somebody would have
done
this in the last 2 years, but nothing happened.
I do no
Am 27.05.2013 20:10, schrieb Scott Kostyshak:
Scott, please don't mark bugs as easyfix if they are apparently not that
easy to fix. If this bug would be easy to fix, somebody would have done
this in the last 2 years, but nothing happened.
I do not agree with the logic of "easy bug" -> "q
>From Uwe posted on #7723
> Comment:
>
> Scott, please don't mark bugs as easyfix if they are apparently not that
> easy to fix. If this bug would be easy to fix, somebody would have done
> this in the last 2 years, but nothing happened.
I do not agree with the logic of "easy bug" -> "quick fix
Richard Heck wrote:
> We do sometimes get people asking about this kind of thing on the list. True,
> they usually disappear, but perhaps that is because we aren't seen as very
> responsive.
Well, that was the idea behind howto contribute FAQ on web. I felt that many
people appear and disappear be
On 05/25/2013 01:58 AM, Pavel Sanda wrote:
Given the fact that I can't remember single case that some newcomer
started by 'easyfix' bugs during last x years (heh, how many of
easyfixes have been targeted by the students applying for GSOC?) I
think that this whole discussion is purely academic a
Scott Kostyshak wrote:
> I propose the following description (and perhaps a new keyword name?):
>
> easyfix: fixing this bug is achievable for a newcommer to LyX
> development and would be a good learning experience.
Feel free to change it.
> Two questions I have are:
>
> How confident should I
During GSoC applications and even after, there was demand for small
bugs to work on that was not met. I would like to start marking
tickets as 'easyfix' tags to indicate that such tickets would be a
good learning process for someone that is not very familiar with LyX's
code.
I'm interested in know
13 matches
Mail list logo