[Bf-webcontent] blender site

[Luigi Monaco]

> What's the policy on these anyway? Do we even link to personal sites? I 
> can't imagine it being a good idea to link to geocities pages. These are 
> notoriously unreliable and my guess is a geocities account couldn't 
> handle the site traffic generated anyway.

I am uncertain if to even answer this request. I visited the site and am far of
feeling the urge to link to it from the blender site. 

This though not being the first uncertainity in if or not putting a site into a
section I would suggest to do s.th. like a democratic election tool. 

Requests should be redirected to a site listing the new locations, with two
buttons for each entry. Button one - Yes it's okay for me, Button 2 - Nope I
think not. Both Buttons have a comment field, entries can be done while
electing pro or against. Decision is automatically triggered after - let's say
20 days. The requester can see the actual comments, bf-webcontent members can
decide. 

What do you think? 

> 
> Matt Cross wrote:
> >*NAME*	Matt Cross 
> >*REALNAME*	1 
> >*USERNAME*	Casalist 
> >*USERNAME*	1 
> >*EMAIL*	casalist at hotmail.com 
> >*WEBSITE_TITLE*	TTS Pix 
> >*ADDRESS*	www.geocities.com/ttspix 
> >*LANGUAGE*	English 
> >*IS_YOUR_SITE_HOSTED_BY_A_FREE_*	Yes 
> >*WEBSITE_FOCUS*	Personal 
> >*GALLERY*	1 
> >*DESCRIPTION*	This site is image gallery of all my images still being 
> >updated all the time though. 
> >*UPLOAD*	now 
> >*ALLOW_SHARING_OF_INFO*	1 
> >
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >Bf-webcontent mailing list
> >Bf-webcontent at projects.blender.org
> >http://projects.blender.org/mailman/listinfo/bf-webcontent
> _______________________________________________
> Bf-webcontent mailing list
> Bf-webcontent at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-webcontent

-- 
tel: +49(0)60214590690 | mobil: +49(0)1713113868 
skype: luigi.monaco    | public.key at ocanom.com

BOFH excuse #260:

We're upgrading /dev/null