That's interesting. I think such a database of common errors would be an extremely useful resource, not only for learning but also for development of linting tools (I think this is more or less what Dynalint does right now) and other tools. For example, I'd love to be able to flag these types of errors and provide suggestions to the user within Cursive about what might be the problem and how they might approach it - currently incomprehensible error messages is one of Clojure's huge weak points IMO.
On 16 April 2014 13:23, Leif <leif.poor...@gmail.com> wrote: > Re: tagging issues, we should probably just ask clojure library authors to > add their projects to OpenHatch's issue indexers. They have them for > Github issues and JIRA, which covers clojure/core (JIRA) and *most* current > open source libs (Github). That way, each individual project maintainer > could choose the tags they want to signify "newcomer" (if I'm reading > OpenHatch's docs correctly). > > Re: CodeAcademy-type sites, I think this might take a little work: > CodeAcademy translates exceptions *or incorrect answers* into > beginner-readable suggestions. Considering they do this even for non-"code > blows up" errors, they must make a list of common mistakes and the output > generated by those mistakes (which to do correctly would require lots of > user testing). > > > --Leif > > On Saturday, January 25, 2014 1:54:10 PM UTC-5, Bridget wrote: > >> OpenHatch has this great >> initiative<https://openhatch.org/wiki/Bug_trackers>for encouraging newcomers >> to get involved with open source projects. You >> tag some issues in your bug tracker as "newcomer" or "easy". This provides >> a gentle path into contributing. There is some work involved with this. You >> have to do the tagging, and there needs to be some capacity in your project >> for some mentoring. >> >> Leiningen is doing this <http://leiningen.org/> already with "newbie" >> tagged issues, which is awesome. >> >> Are there any other Clojure projects that are doing this? Would you like >> to do this with your project? If so, I can try to help. I have been >> spending a lot of time thinking about the Clojure newcomer perspective >> lately, and I'd like to work on some things that help smooth that path. >> >> Bridget >> > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
