go for a blog like that this is visible to non geek too. Stef
On Jul 30, 2012, at 7:55 PM, Igor Stasenko wrote: > On 30 July 2012 17:59, Dale Henrichs <[email protected]> wrote: >> >> >> ----- Original Message ----- >> | From: "Igor Stasenko" <[email protected]> >> | Another thing, which i discussed locally , i thinking about creating >> | a >> | dedicated blog for VM developers, where we can share the news and >> | describe >> | details about changes and stuff.. >> | In a way, that it will serve as a source of information about VM , >> | jenkins , configurations, settings , building etc etc.. >> | Because all of the bits of knowledge , which we collected till now is >> | kind of floating in the air, and like any energy it tends to >> | dissipate >> | (things we remember and forget, the more things we should keep in >> | head, the faster it happens). >> | Also, blog is preferable to just simple CHANGELOG file (or similar), >> | because it is two-way communication , and people can comment and >> | discuss things. >> >> Igor, >> >> You might find GitHub as a very good place for this. GitHub has a number of >> collaboration features that play very well together: >> >> source code control with git >> issues where you can report bugs, but also host conversations >> wiki for documentation although I like markdown for documentation >> since the docs are then versioned with the code >> >> When you view code diffs you can make line by line comments/questions that >> are visible to other developers who can in turn comment on your comments ... >> talk about real two-way communication:) >> >> The real advantage is that all of these things are versioned together ... >> code/documentation/articles ... >> >> Anyway, it's worth considering:) >> > > Hi, Dale, do you have any links, nicely demonstrating the features you > described above? > For me, as an utterly lazy guy, who also doesn't loves writing much, > the simpler the better.. > that's why i thought about just setting up a blog and posting notes > there, which is just few minutes.. > Throwing git into the cycle would extend this time.. and as result, a > willingness to post about updates.. :) > >> Dale >> >> >> > > > > -- > Best regards, > Igor Stasenko. >
