I think Nick Ager has a great tool for this purpose. He showed us that in PharoConf. Nick, they are all years ;)
On Wed, Aug 1, 2012 at 4:40 PM, Dale Henrichs <[email protected]> wrote: > If you're not going to be intimately collaborating on code, then a general > blog will work just fine ... > > Dale > > ----- Original Message ----- > | From: "Igor Stasenko" <[email protected]> > | To: [email protected] > | Sent: Wednesday, August 1, 2012 2:10:47 AM > | Subject: Re: [Pharo-project] Going meta (VM development) > | > | Ah, I see, the docs in markdown. I like it. > | I tried to use markdown for NativeBoost documentation, and it quite > | nice.. > | But as Stef says, we need something non-geeky and easily accessible. > | > | I agree that documentation , which is well written and with good > | coverage is better to keep & organize together with sources and use > | of > | SCM is completely reasonable for it. > | But what i want to have is more like news posts, which not necessary > | need to have too much details > | and just serving to keep every developer(s) (and interested users) to > | stay updated and informed about changes. > | Because usually we post things into mailing list, and in a couple of > | days, the information is buried under tons of other mails. > | For documenting things we can use Cog project wiki, or files with > | markdown .. and of course the useful information can be distilled > | from > | blog posts, if needed. > | > | That's my impression. > | > | -- > | Best regards, > | Igor Stasenko. > | > | > > -- Mariano http://marianopeck.wordpress.com
