Wow, Leif. This is great. Thanks so much for doing this. For #1 - Proposing a label for issues appropriate to newcomers seems like something very doable to get this kickstarted. I propose "bite-sized," to keep in line with what OpenHatch <https://openhatch.org/wiki/Bug_trackers>does. Does anyone have other suggestions?
#3 I saw as an issue, also. The tag could be meaningless if there is huge variance. Maybe publish some sort of definition? Working on this is on my active Todo list, but other things have taken precedence (called ClojureBridge :). I should have some more time in a couple of weeks. Anyone available to team up? I think Marcus' suggestion to put up a web page/wiki to start the ball rolling would be great. Bridget On Monday, April 14, 2014 9:51:36 AM UTC-4, Leif wrote: > > Below is a list of the top 1,000 clojure projects (by star count) from > github with issues with labels that sound somewhat appropriate for > newcomers. Don't worry, the final list is way less than 1,000. > > Considering the list, we see that: > > 1. The community may want to attempt to standardize these labels. > 2. Most of the 1,000 projects had no such labels (or no issues at > all). I pessimistically take that to mean that there are lots of issues > yet to be found, and a newbie should just find a project in an area they > know a lot about, or are interested in, and stress test it. > 3. Some tags may need to be taken with a grain of salt. E.g. an Om > issue tagged as "trivial" may or may not be so to, say, a newbie to > clojure > who is not a professional UI developer. > 4. Everyone wants docs. This may interest you less than programming, > but trust me, you'll have to do some programming with a library before you > can write sensible docs for it. Also, you may in the process be able to > influence the API / usability of a library. > > (["https://github.com/LightTable/LightTable"; #{"starter"}] > ["https://github.com/technomancy/leiningen"; #{"usability" "docs" > "Newbie"}] > ["https://github.com/weavejester/compojure"; #{"easy" "trivial"}] > ["https://github.com/swannodette/om"; #{"trivial" "example" "minor"}] > ["https://github.com/overtone/overtone"; #{"newbie"}] > ["https://github.com/nathanmarz/cascalog"; #{"newbies"}] > ["https://github.com/marick/Midje"; #{"cleanup" > "ripe-for-new-contributor" "better-error-msgs" "documentation"}] > ["https://github.com/cemerick/friend"; #{"doc"}] > ["https://github.com/pallet/pallet"; #{"Documentation" "Newbie"}] > ["https://github.com/brentonashworth/one"; #{"sample application"}] > ["https://github.com/clojure-liberator/liberator"; #{"documentation"}] > ["https://github.com/emezeske/lein-cljsbuild"; #{"Documentation"}] > ["https://github.com/relevance/labrepl"; #{"documentation"}] > ["https://github.com/gdeer81/marginalia"; #{"cleanup" "docs"}] > ["https://github.com/semperos/clj-webdriver"; #{"documentation"}] > ["https://github.com/michaelklishin/monger"; #{"documentation"}] > ["https://github.com/xsc/lein-ancient"; #{"better error message"}] > ["https://github.com/neotyk/http.async.client"; #{"Docs"}] > ["https://github.com/ato/clojars-web"; #{"cleanup"}] > ["https://github.com/clojurewerkz/elastisch"; #{"low-hanging fruit" > "usability" "documentation"}] > ["https://github.com/michaelklishin/langohr"; #{"documentation"}] > ["https://github.com/michaelklishin/validateur"; #{"documentation"}] > ["https://github.com/cemerick/clojurescript.test"; #{"documentation"}] > ["https://github.com/sonian/carica"; #{"documentation"}] > ["https://github.com/michaelklishin/neocons"; #{"usability" > "documentation"}] > ["https://github.com/michaelklishin/quartzite"; #{"documentation"}] > ["https://github.com/cfpb/qu"; #{"docs"}] > ["https://github.com/michaelklishin/welle"; #{"documentation"}] > ["https://github.com/abedra/accession"; #{"Documentation"}] > ["https://github.com/Raynes/irclj"; #{"documentation"}] > ["https://github.com/aaronfeng/trixx"; #{"bitesize"}] > ["https://github.com/gameclosure/hermes"; #{"documentation"}] > ["https://github.com/wri/forma-clj"; #{"cleanup"}] > ["https://github.com/cgmartin/clj-wamp"; #{"docs"}]) > > --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.
