> > So if someone wants to setup the best environment for developing > clojure, like serious Java developers who want to make clojure their > new home, the community doesn't think having a single page for those > people to use to setup their environment, as a good idea? > > There should be several one stop shops. A single page where someone > can go to, to setup their whole system. I'm already maintaining this > for emacs/clojure-mode/leiningen, etc... > > I don't think having this all over the zoo is a great idea, it's a > good idea, but should be supplemented by the above. > > Phil, objects, because he see's the duplication...totally fair > comment, but there are different needs, that aren't met by just having > lein/clojure-more/marmelade, etc... all in their respective homes. > > Initially, I asked if posting links to the docs I was writing was > socially acceptable, and now I think it is, and will continue to do > what I am doing, I think it has a lot of value. Sure it has problems, > duplicate data, etc..., but it also has a lot of value too I think. > > Shall I clone clojure-mode, and update that doc you referenced to have > stuff about Leiningen? ...and all the other things...I'm happy to do > that. However, I suspect, this argument around: single source of > truth, and having fragmented getting started scenario, is a little > intractable. I think you have to live with the fact that you'll have > somewhere that pulls together single sources of truth to package them > in a way that is targetted at certain users. > > This is a typical problem that constantly crops up all over the > place. The best way would be for each section to be function that you > referenced and it got included inline, then people could mix and match > each section they needed to create documents that were nothing but > references back to the single source of truth. > > However, until we get to a place like that, people are going to opt > for copying information (that will go stale). Heck often the single > source of truth is out of date! > > What I'd suggest is that a git repo gets openned for this purpose. > Make contributing easy. > > Until someone in the community does that, I'll tool away at creating > docs that I need and I think can benefit others. Should I not post > them into the clojure group, because maybe they can confuse people > from the official docs? No, I don't think so, but I should reference > back to the official docs in my docs. I think that is a reasonable > alternative. > > I know someone suggested I try to keep up the docs that are already in > place, but I'm not super comfortable with that. 1 - they are just > fragments that I try to understand, and I'm not really the best person > to understand and document those things I think. I do better by just > putting what little I have succeeded (relatively speaking) down and > then having pros like Phil or whoever tell me where I'm doing things > wrong/stupidly, like he already did. Thats about all the value I can > add at this point. >
-- 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
