[FreeNX-kNX] Need help for FreeNX 0.7.0 / NX 3.0 - Technical writers needed

[Terje Andersen]

> Hi,
>
> after long pondering I will proceed as follows:
>
> - Current SVN will be released as 0.6.1 called "Jornade SPL Edition".
>
> (See www.jornadespl.org)
>
> - FreeNX 0.7.0 will be rewritten / re-designed from scratch as else   
> I cannot support the new features of NX 3.0.
>
> This was long due and I think it will greatly help reduce bugs and   
> problems that keep popping up again and again and again ...
>

This is great news! Thank you, Fabian!

> But as one of the biggest complaints about FreeNX in the past was   
> the wrong / missing documentation in node.conf and I am really not a  
>  technical writer and not even a native speaker, I need help with  
> that.
>
> I would like to have one or more persons that are preferable native   
> speakers that I can send my texts to and which make them into nice   
> understandable English.
>

I did an early attempt at this that I never got to release and I am  
more than willing to help with writing documentation. If needed and  
wanted, I could send you the file (think you already have an early  
version of it, Fabian) which could be updated to be a reference up to  
version 0.6.1. We just need to sort out the little issue that was a  
stopped me from releasing it when it was finished.

> Perhaps even adding documentation as use-cases to the Wiki while doing so.
>

Excellent idea.

> This is not a one-time task, but a continuing ongoing work, while I   
> develop the new configuration keys and document them and also write   
> the new strings.
>

Then, if more people are willing, maybe we should organize a team that  
you could send them to, so that the team could delegate what the  
individuals should work on?

> Btw. they will be i18n()'able as well ... :-)
>

Agree.

> If we can't find someone I'll use this ML!!! ;-)
>

I'm willing & able.

> Also FreeNX will move to a much more modular concept and use more   
> "drop-in" scripts / hooks on its way, so its more easily   
> customizable replacing some built-in functionality on the way.
>

Yes! I can't wait? :-)

/Terje