I added some basic material to the GitHub Camping Wiki (new pages): http://wiki.github.com/camping/camping ...because I''m starting with a vanilla OS X Leopard install (new MacBook) and - finally - Camping 1.9, and I thought it would be a good test run to go through the setup and tutorial process in the ''Camping book'': http://stuff.judofyr.net/camping-docs/book/02_getting_started.html to find any gotchas. Only one (in my setup) - on ''Wrapping it up'', in the Controllers: class Pages needs the explicit class Pages < R ''/'' to show the pages... anyone not have the same issue? Thinking about existing stuff, some time ago Magnus wrote:> As for the documentation ideas, I''ve already implemented the > templates in RDoc, so "rake docs" builds all the three parts (the > book is simply files in the book directory). I still need to make a > way to link book chapters from the reference, but at least it''s > working. A Camping app can be useful when you want to edit it, so > you don''t need to run the rake task all the time.The book dir on GitHub doesn''t have all the current content found at: http://stuff.judofyr.net/camping-docs/book/ or in the Camping install (unless I''m daft, which is possible) so where can the current book files be obtained?> I guess we could also implement it as a wiki, which might be > better. Then we can''t have it on camping.rubyforge.org (unless we > can change the DNS-settings) though since it only allows static > files. What do you think? I prefer having everything in files, and > I think those who really want to contribute to the book wouldn''t > mind a "git clone"...I don''t think there was a response at the time Magnus wrote this, so (given whywentcamping.com, which would be a separate exercise): ideas, opinions, anyone? Be really good to have camping.rubyforge.org updated, and I''m ready to pitch in, but how to start? Dave Everitt
Very silly me. Forgot about ''Index'': - class Pages < R ''/'' + class Index have corrected the Pastie: http://pastie.org/679826 Dave Everitt> Only one (in my setup) - on ''Wrapping it up'', in the Controllers: > class Pages > needs the explicit > class Pages < R ''/''
Thanks for bringing this up again! I''ve pushed out what I have so far, but not your latest suggestions (you had some more in an earlier mail, right?) If you have a Github account I can give you (and anyone else who wants to contribute) push-access. I''m a little busy at the moment, but I''ll try to fix it as soon as possible. //Magnus Holm On Mon, Nov 2, 2009 at 01:22, Dave Everitt <deveritt at innotts.co.uk> wrote:> I added some basic material to the GitHub Camping Wiki (new pages): > ?http://wiki.github.com/camping/camping > > ...because I''m starting with a vanilla OS X Leopard install (new MacBook) > and - finally - Camping 1.9, and I thought it would be a good test run to go > through the setup and tutorial process in the ''Camping book'': > ?http://stuff.judofyr.net/camping-docs/book/02_getting_started.html > to find any gotchas. > > Only one (in my setup) - on ''Wrapping it up'', in the Controllers: > ?class Pages > needs the explicit > ?class Pages < R ''/'' > to show the pages... anyone not have the same issue? > > Thinking about existing stuff, some time ago Magnus wrote: > >> As for the documentation ideas, I''ve already implemented the templates in >> RDoc, so "rake docs" builds all the three parts (the book is simply files in >> the book directory). I still need to make a way to link book chapters from >> the reference, but at least it''s working. A Camping app can be useful when >> you want to edit it, so you don''t need to run the rake task all the time. > > The book dir on GitHub doesn''t have all the current content found at: > ?http://stuff.judofyr.net/camping-docs/book/ > or in the Camping install (unless I''m daft, which is possible) so where can > the current book files be obtained? > >> I guess we could also implement it as a wiki, which might be better. Then >> we can''t have it on camping.rubyforge.org (unless we can change the >> DNS-settings) though since it only allows static files. What do you think? I >> prefer having everything in files, and I think those who really want to >> contribute to the book wouldn''t mind a "git clone"... > > > I don''t think there was a response at the time Magnus wrote this, so (given > whywentcamping.com, which would be a separate exercise): ideas, opinions, > anyone? Be really good to have camping.rubyforge.org updated, and I''m ready > to pitch in, but how to start? > > Dave Everitt > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >
Magnus - I did make some earlier suggestions/edits and would be happy to implement them. I''m a sad and rather newbie (still working through the O''Reilly Git book) GitHub lurker (with no repos yet: http:// github.com/DaveEveritt) so let me know when you''re ready and I''ll start work - Dave E.> Thanks for bringing this up again! I''ve pushed out what I have so > far, but not your latest suggestions (you had some more in an > earlier mail, right?) > > If you have a Github account I can give you (and anyone else who > wants to contribute) push-access. I''m a little busy at the moment, > but I''ll try to fix it as soon as possible. > > //Magnus Holm > > >> On Mon, Nov 2, 2009 at 01:22, Dave Everitt >> <deveritt at innotts.co.uk> wrote: >> I added some basic material to the GitHub Camping Wiki (new pages): >> http://wiki.github.com/camping/camping >> >> [SNIP] >> >> Thinking about existing stuff, some time ago Magnus wrote: >> >>> As for thedocumentation ideas, I''ve already implemented the >>> templates in RDoc, so "rake docs" builds all the three parts (the >>> book is simply files in the book directory). I still need to make >>> a way to link book chapters from the reference, but at least it''s >>> working. A Camping app can be useful when you want to edit it, so >>> you don''t need to run the rake task all the time. >> >> The book dir on GitHub doesn''t have all the current content found at: >> http://stuff.judofyr.net/camping-docs/book/ >> or in the Camping install (unless I''m daft, which is possible) so >> where can the current book files be obtained? >> >>> I guesswe could also implement it as a wiki, which might be >>> better. Then we can''t have it on camping.rubyforge.org (unless we >>> can change the DNS-settings) though since it only allows static >>> files. What do you think? I prefer having everything in files, >>> and I think those who really want to contribute to the book >>> wouldn''t mind a "git clone"... >> >> >> I don''t think there was a response at the time Magnus wrote this, >> so (given whywentcamping.com, which would be a separate exercise): >> ideas, opinions, anyone? Be really good to have >> camping.rubyforge.org updated, and I''m ready to pitch in, but how >> to start? >> >> Dave Everitt
Okay. After 3-4 intensive days I now know Git well enough to go. Today I cloned the camping repo and grepped for the issues I spotted before but it seems they''re fixed. So only corrected a minor typo in README :-) Will push (with anything else I notice) when access granted - Dave E.> Magnus - I did make some earlier suggestions/edits and would be > happy to implement them. I''m a sad and rather newbie (still working > through the O''Reilly Git book) GitHub lurker (with no repos yet: > http://github.com/DaveEveritt) so let me know when you''re ready and > I''ll start work - Dave E. > >> Thanks for bringing this up again! I''ve pushed out what I have so >> far, but not your latest suggestions (you had some more in an >> earlier mail, right?) >> >> If you have a Github account I can give you (and anyone else who >> wants to contribute) push-access. I''m a little busy at the moment, >> but I''ll try to fix it as soon as possible.
You''re now added as a contributor. Feel free to push/commit at will, but if it involves any larger refactorings/changes, I think it''s better if you fork off so we can discuss it a bit. If you''re not quite sure where to push though, just push it to camping/camping. We can always revert it later if needed :-) //Magnus Holm On Thu, Nov 5, 2009 at 17:50, Dave Everitt <deveritt at innotts.co.uk> wrote:> Okay. After 3-4 intensive days I now know Git well enough to go. Today I > cloned the camping repo and grepped for the issues I spotted before but it > seems they''re fixed. So only corrected a minor typo in README :-) Will push > (with anything else I notice) when access granted - Dave E. > >> Magnus - I did make some earlier suggestions/edits and would be happy to >> implement them. I''m a sad and rather newbie (still working through the >> O''Reilly Git book) GitHub lurker (with no repos yet: >> http://github.com/DaveEveritt) so let me know when you''re ready and I''ll >> start work - Dave E. >> >>> Thanks for bringing this up again! I''ve pushed out what I have so far, >>> but not your latest suggestions (you had some more in an earlier mail, >>> right?) >>> >>> If you have a Github account I can give you (and anyone else who wants to >>> contribute) push-access. I''m a little busy at the moment, but I''ll try to >>> fix it as soon as possible. > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >
Thanks Magnus - done. Will take care to confine changes to typos, bad links, ''getting started'' etc. and fork for anything more complex (like the blog example, which is where this whole thing started for me :-) - DaveE> You''re now added as a contributor. > > Feel free to push/commit at will, but if it involves any larger > refactorings/changes, I think it''s better if you fork off so we can > discuss it a bit. If you''re not quite sure where to push though, > just push it to camping/camping. We can always revert it later if > needed > :-) > > //Magnus Holm > > On Thu, Nov 5, 2009 at 17:50, Dave Everitt <deveritt at innotts.co.uk> > wrote: >> Okay. After 3-4 intensive days I now know Git well enough to go. >> Today I cloned the camping repo and grepped for the issues I >> spotted before but it seems they''re fixed. So only corrected a >> minor typo in README :-) Will push (with anything else I notice) >> when access granted - Dave E.