[Bf-committers] New blog: code.blender.org (proposal)
ton at blender.org
Fri Nov 12 12:51:17 CET 2010
Good idea to allow (and communicate) edited blog posts.
Communicating a comment policy is fine, but I wouldn't demand anyone
to work on removing the noise. Our coder blog probably attracts a
different audience anyway. In case the commenting becomes annoying we
can review ideas for how to fix that though.
Ton Roosendaal Blender Foundation ton at blender.org www.blender.org
Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands
On 11 Nov, 2010, at 14:39, Thomas Dinges wrote:
> +1 for this comment policy!
> Am 11.11.2010 10:43, schrieb mindrones:
>> 2) Comments policy
>> There are so many things to read that in the end you simply don't
>> anything anymore...
>> Example: Durian posts --> if I see 175 comments I can expect 95%
>> like "cool!" comments, and "5%" interesting informations...
>> There's the same risk here IMO, so I would like to propose that
>> such a
>> blog has a well stated COMMENTS POLICY (I took this idea from a cool
>> - people freely comment and make questions
>> - the blog author replies and when appropriate he enhances or fix the
>> post above
>> - the author deletes all noisy comments, so that the page is always
>> and complete, and we don't have to read noisy comments or things that
>> have already been fixed in the post
>> - to say "post has been cleaned up" the author just leaves a comment
>> like "edited" or so, so we know, otherwise he just cleans noisy
>> and don't leave a "edited" comment.
>> - if he cleans many times, more of his "edited" stamps also let us
>> if/when it's worth re-reading the post
>> IMO this would result in a beautiful workflow to do documentation:
>> - wiki people can then use that material as a base for user docs
>> - devs can use that as a base for dev documents too.
>> Bf-committers mailing list
>> Bf-committers at blender.org
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers