Haha, maybe Andres, Maybe. Trust me, there was one time that I spend a whole 
day trying to fix an issue, and still couldn't figure it out what's wrong with 
it … I then had to drop it. (I'm not proficient on working with Active Record 
stuff, tbh.)

But, I mean, if that easy tag really going to encourage new people to come in, 
I don't mind doing it. However, I feel like if the issue is easy to fix enough, 
people will tends to just send in a pull request with their fix instead of just 
reporting a bug, since it's so easy nowadays with GitHub and all the tools we 
have.

Oh boy, I don't want to take this one off topic, so I'll stop here for now. 
Happy contributing people! :)

- Prem  


On Tuesday, September 11, 2012 at 2:42 PM, Andreas Arnold wrote:

> Maybe I just chose the wrong issues then... :)
>  
> I'm just mentioning it since, for example, Poltergeist marked a few issues as 
> "easy" and has managed to get a few new people to contribute to it.
>  
> On Tue, Sep 11, 2012 at 8:38 PM, Prem Sichanugrist <sikand...@gmail.com 
> (mailto:sikand...@gmail.com)> wrote:
> > … right, if you look hard enough, you'll find one that it's simple. :P
> >  
> > BTW, while I like the idea here, I don't think we really need a easy bake 
> > oven for our issues. I remembered myself wanting to write a patch to Rails, 
> > so I dove down Active Record source code, head first, trying to fix 
> > something, and boy that was really fun. If they take issue as a challenge, 
> > regardless if the issue is hard or easy, it's still fun. :)  
> >  
> > - Prem
> >  
> > On Tuesday, September 11, 2012 at 2:34 PM, Steve Klabnik wrote:
> >  
> > > At this point, it seems to me that there isn't a whole lot of 'simple'
> > > bits to be fixed; most issues in a massive, years-old codebase are not
> > > trivial.
> > >  
> > > That doesn't mean they don't exist...
> > >  
> > > --  
> > > You received this message because you are subscribed to the Google Groups 
> > > "Ruby on Rails: Core" group.
> > > To post to this group, send email to rubyonrails-core@googlegroups.com 
> > > (mailto:rubyonrails-core@googlegroups.com).
> > > To unsubscribe from this group, send email to 
> > > rubyonrails-core+unsubscr...@googlegroups.com 
> > > (mailto:rubyonrails-core+unsubscr...@googlegroups.com).
> > > For more options, visit this group at 
> > > http://groups.google.com/group/rubyonrails-core?hl=en.
> > >  
> > >  
> > >  
> >  
> >  
> > --  
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby on Rails: Core" group.
> > To post to this group, send email to rubyonrails-core@googlegroups.com 
> > (mailto:rubyonrails-core@googlegroups.com).
> > To unsubscribe from this group, send email to 
> > rubyonrails-core+unsubscr...@googlegroups.com 
> > (mailto:rubyonrails-core%2bunsubscr...@googlegroups.com).
> > For more options, visit this group at 
> > http://groups.google.com/group/rubyonrails-core?hl=en.
>  
> --  
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Core" group.
> To post to this group, send email to rubyonrails-core@googlegroups.com 
> (mailto:rubyonrails-core@googlegroups.com).
> To unsubscribe from this group, send email to 
> rubyonrails-core+unsubscr...@googlegroups.com 
> (mailto:rubyonrails-core+unsubscr...@googlegroups.com).
> For more options, visit this group at 
> http://groups.google.com/group/rubyonrails-core?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com.
To unsubscribe from this group, send email to 
rubyonrails-core+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en.

Reply via email to