[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Preparation of Blends tasks



Hi, Andreas:

On Tuesday 17 August 2010 08:42:15 Andreas Tille wrote:
> Hi,
>
> as I proposed in my last mail[1] I created a Wiki page which can be used
> to prepare some Blends tasks.  Please take it a first shot of an
> uneducated person and perhaps non of the few suggestions makes any sense
> but at least it is a start.  I have linked to the page from the general
> Debian Enterprise wiki page which I would like to promote here as well:
>
>    http://wiki.debian.org/Teams/DebianEnterpriseTeam

I've been having a look at the Debian Pure Blends general documentation.

I found that there was an initial effort for Debian Enterprise back in 2003 
that lost air (humm... that's more or less by the same dates when Bruce 
Perens was pushing his UserLinux project.  Are/were those two somehow 
related?).  If this new push takes moment somebody will need to remember to 
update the pages listing blends*1,2.

Within Debian Enterprise goals *1 I miss trying to offer a common 
framework/best practices so all the other blends can take advantage of it 
when deployed in a corporate/professional environment.  After all, they all 
need, say, authentication/authorization, disaster recovery, file/print 
services, etc. so why not sharing components?

Regarding sharing components, the documentation*3 states that "...People who 
are interested in working on common issues like building metapackages, 
technical issues of menu systems or how to create CDs for Blends could 
subscribe to this list or read the list archive." but this list is marked 
as "dead list"*4: docs should be updated either with the new list, if it 
exists or stating its dead status (alternatively, the list can be came back 
into live if it regains interest).

Cheers,

*1 http://blends.alioth.debian.org/blends/ch-existing.en.html
*2 http://blends.alioth.debian.org/
*3 http://blends.alioth.debian.org/blends/ch-todo.en.html
*4 http://lists.debian.org/debian-custom/


Reply to: