DevApp Content Life-cycle [was: Re: Wiki ideas]

[Nick Loeve]

Sean Wheller wrote:
> On Friday 01 April 2005 11:11, Mark Shuttleworth wrote:
> 
>>Let's see what we can get done at UDU, but in parallel, let's see what
>>you guys come up with. 
> 
> 
> Hello Mark, Corey,

<snip><snip>

Hi Sean and All,

I have not had much time to really sit down and think about this whole 
thing, but Sean's analysis of the problem looks very good, and goes a 
bit deeper into whats has to happen than most of the discussion about 
the wiki/docbook idea.

I agree with Sean on the following points:

  - We need to look at what products are out there that can help

  - It makes no sense to not be able to use those products because of 
the
    technology they are implemented with (especially if that is the start
     and end of the argument there)

  - Surely security can be achieved with other technologies - i have had 

    a lot of experience with PHP and would be willing to help share my
    experience with PHP and security issues

  - I do not think that a web based solution is the way to go for
    everything. I know that for a large document (or even for something
    as big as the quickguide) it is more manageable if editing is
    offline)

I can appreciate that Python and related technologies are the primary 
development tools used throughout Ubuntu, because it is a common 
'language' for all using it (not just the semantics of the language 
itself but terms and meanings surrounding it), there are experienced 
people who can help out when things go wrong, it may help when auditing 
software (i do not know how that works exactly, but am sure that having 
a focus on one primary technology helps to make that process not so 
tedious, expensive or difficult).

The problem that i can see is that when a team like the docteam wants to 
do something, like the wiki/docbook idea, then immediately we are told 
or get the impression, that we will have to use python and related 
technologies. That in itself is not a problem, but as Sean said, not 
everyone is a coder here.

So:

  - Those that want to contribute have to learn Python
  - At the present time it does not sound like there are any Ubuntu
    developers who are wanting to work on this process
  - There is no sort 'point-of-contact', other than Enrico, for
    issues/idea/problems in regards to technology/deployment
    options/availability of software for the doc team to use.

And after all that, to get back to another of Sean's point, those 
working on this project will not be creating documentation. Maybe what 
we need is a seperate subteam 'Ubuntu Documentation Technology Team' or 
something. That way energy is not being sapped from the documenation 
effort, but those that want to contribute to both seperate ideas 
(creating docs, creating a system for creating docs) are free to do so.

At present the doc team is pretty small, so i do not know if there is 
enough man power to create another seperate team, but over time the 
'Ubuntu Documentation Technology Team' could attract existing or new 
Ubutnu developers, and build closer ties with those that are in the know 
in regards to building software for Ubuntu, deploying software for 
Ubutnu and maintaining software Ubutnu.

So that my 2 cents, i hadn't really thought out all i had said, feel 
free to ignore it, i mainly just wanted to show that i have been 
listening to what eveyone has been saying :)

Cheers
trickie (Nick Loeve)