I like the idea of taking care of copyright properly, thanks Sean for the links to those pages. I think the black and white split, docs = confluence, code = github, is not so good. I think John's point about the *.md files being a very good place for documentation. I think the right way to do the documentation is like this:
1 - github with *.md. 2 - take care of copyright like you are now. 3 - have a trusted person be the owner of the repo...Phil/Sean or someone else like that. 4 - let folks clone, edit and then send pull requests back to the site owner. my personal approach would be to give commit access to whoever seemed reasonable, though I know that freaks some people out. I'm not going to give up the wonderful prettiness that github does with a line like: ```clojure (defn myfunc [x] (+ 2 x)) ``` which i can't do with confluence. This group is about a programming language, nice colorizing is really great for documentation. I think having directed tutorials one for each of mac/linux/windows. Then these tutorials should go start to finish with the canonical implementation for that platform. Yes emacs is very weird for newbies, but most clojurians use it. There are reasons why they use it, and as long as we can have good docs around these things, then its okay. It's like standardization. I can sympathize with the concept of only teaching one thing at a time. I totally agree with that. But I also am not a big fan of teaching people something that they'd then throw away. If anyone wants commit permissions to my repo, just send me your github name, and I'll add u. I'd prefer that the clojure community took up some documentation inside of github with *.md files and that repo used instead, obviously tho. Cheers. On Thursday, June 14, 2012 10:31:44 AM UTC-7, Phil Hagelberg wrote: > > On Wed, Jun 13, 2012 at 8:01 PM, David Della Costa > <ddellaco...@gmail.com> wrote: > > I also think that, at present, while coming in through Leiningen is > > definitely the most painless way to do things (I'm really loving it > > actually, as a Ruby dev it kind of seems like rvm + bundler + rake all > > wrapped up in one handy package), trying to navigate whether to use > > 1.x or 2.x preview is a bit confusing--and the variety of docs > > available for setting things up is confusing. > > Yeah, as of the last release we're pretty much advising everyone to go > with 2.x, but the docs still need to be updated to reflect that. What > are some of the confusing docs you mention? Most people have said the > install process is pretty simple. > > > Similarly, it's easy to > > get lost (as a beginner) between namespace issues with packages and > > how to set things up properly with Leiningen. It'd be good to have > > some documentation on that. > > Maybe if the Leiningen tutorial linked to > > http://blog.8thlight.com/colin-jones/2010/12/05/clojure-libs-and-namespaces-require-use-import-and-ns.html? > > > > > All of that said, maybe I'll take a look at the docs and see if I can > > add anything constructive, since I've set it up now a few times on > > Macs. > > That would be great; thanks. We could also use some help improving > http://leiningen.org; it's pretty messy right now. > > -Phil > -- 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
