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 be that criterion (a) is satisfied? I would > only be 100% sure that a ticket is easy to fix if I actually fix it. I > plan to be a little risky in assigning this tag and hope that other > developers will remove it if I do so mistakenly or that a newcommer > will still learn if they try to tackle a bug that is actually too > complicated. > > Should current developers be discouraged from working on 'easyfix' > tickets? In my opinion, no. Otherwise, one has to think very carefully > before assigning the tag. If developers wants to work on a ticket for > any reason, they should be unconstrained. I don't think current developers care much about this keyword, it was meant for newbies. Again, feel free to add keywords for the bugs which would be straightforward for you. > Any thoughts? 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 and not worth of nitpicking. Pavel
