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

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 ...

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.

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

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.

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

If we can't find someone I'll use this ML!!! 

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.

cu

Fabian
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

Fabian Franz wrote:
> 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 ...
>
> 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.
>
> Perhaps even adding documentation as use-cases to the
Wiki while doing so.
>
> 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.
>
> Btw. they will be i18n()'able as well ... 
>
> If we can't find someone I'll use this ML!!! 
>
> 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.
>
> cu
>
> Fabian
>
____________________________________________________________
____
>      Were you helped on this list with your FreeNX
problem?
>     Then please write up the solution in the FreeNX
Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com
/kb/ 
>
>
____________________________________________________________
____
>        FreeNX-kNX mailing list --- FreeNX-kNXkde.org
>       http
s://mail.kde.org/mailman/listinfo/freenx-knx
>
____________________________________________________________
____
>   
I'm not native English speaker, but I could help with
documentation if 
it does not take all my free time and there is nobody else
to do it.
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

I'm a native UK English speaker and happy to help.

On Wednesday 04 July 2007 17:28, Fabian Franz wrote:
> 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 ...
>
> 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.
>
> Perhaps even adding documentation as use-cases to the
Wiki while doing so.
>
> 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.
>
> Btw. they will be i18n()'able as well ... 
>
> If we can't find someone I'll use this ML!!! 
>
> 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.
>
> cu
>
> Fabian
>
____________________________________________________________
____
>      Were you helped on this list with your FreeNX
problem?
>     Then please write up the solution in the FreeNX
Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com
/kb/
>
>
____________________________________________________________
____
>        FreeNX-kNX mailing list --- FreeNX-kNXkde.org
>       http
s://mail.kde.org/mailman/listinfo/freenx-knx
>
____________________________________________________________
____

____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> 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
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

This sounds very great, Fabian. 

I'll be happy to help out in any way I can. I'm one of those
who's
been longing for some good documentation for FreeNX. I don't
have the
required insight to write any documentation myself, but I
can proof
read, translate and I'm also very good at being a stupid
user, so I
might be useful in testing the documentation as well.

> - FreeNX 0.7.0 will be rewritten / re-designed from
scratch as else I cannot support the new features of NX
3.0.

Does this mean you'll be able to implement features such as
shadowing,
sharing of local display _and_ guest accounts, LDAP
integration, etc?

/Jo-Erlend
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> This sounds very great, Fabian. 
> 
> I'll be happy to help out in any way I can. I'm one of
those who's
> been longing for some good documentation for FreeNX. I
don't have the
> required insight to write any documentation myself, but
I can proof
> read, translate and I'm also very good at being a
stupid user, so I
> might be useful in testing the documentation as well.

Nice.

So lets form a team.

> > - FreeNX 0.7.0 will be rewritten / re-designed
from scratch as else I
> cannot support the new features of NX 3.0.
> 
> Does this mean you'll be able to implement features
such as shadowing,
> sharing of local display _and_ guest accounts, LDAP
integration, etc?

Have to think of guest accounts (thx for the reminder), but
all others: YES.

cu

Fabian
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> I'm a native UK English speaker and happy to help.

Okay, I'll send the first materials now.

As we now have several people I'll see if we can start just
by using this list and if traffic gets too high then split
it up.

The advantage is that other users can read this threads and
comment on them as well and also know what to expect in the
next versions so we have more users that know things about
it.

The first component to be reviewed is nxserver-login and we
have to discuss how to describe it in the config file and
the options that are usable.

I'll write a separate mail for that now ...

cu

Fabian
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> > Have to think of guest accounts (thx for the
reminder), but all others:
> YES.
> 
> Do you stick with bash or do you switch to some
scripting language like
> python, perl, ruby, whatever ?

I'll stick with whatever is appropriate for the task.

As I know bash best, I'll stick with it for most parts, but
there will be also some parts written in C.

And the version will be so modular, that the language really
does not matter anymore.

Btw. I have mostly heard:

Oh, wow its bash, it was easy to fix for me. And not: I
don't know that language unfortunately.

So it is a good choice? I dunno.

I'll now try to keep all components really, really simple,
so that they are not using any advanced things no one
understands on first sight, but easily changeable and
customizable.

The problems that freenx nxnode was not as stable and error
free as !M nxnode were two:

- I first hacked it together and it has grown out of a 1
night hack
- I did not look at the actually source components how
things are done, but just looked at client / server
protocol. So I did write code without really understanding
it.
- There had been some bad design issues, which had proven
really hard to fix and which had lead to hard to trace race
conditions after race condition.
- I did not actually design or think about it, but just
looked at what !M did and tried to do the same as best as I
could.

That is why I am now doing a re-design and I disagree that
this is the fourth attempt. I had changed some major things
in nxnode and nxserver before, but it was all still only
code-change not code-rewrite.

The goals of the new design are:

- flexible and customizable, so that new developers can join
easily.
- stable and not feature creep, so that features are not
affecting the core functionality

While the features are incorporated into the design, they
have the lowest priority in implementation.

And again this got off-topic and will be re-send in the
Release + QA: future mail.

cu

Fabian
____________________________________________________________
____
     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX
Wiki/FAQ:
  http://openfacts.berlios.de/index-en.phtml?title=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____