Article about Documaster in todays DN.

[Thomas Sødring]

I have to office365 webclient so reply to is a bit weird ... just in case you were wondering why it's looking like it is.



From: nikita-noark-bounces at nuug.no <nikita-noark-bounces at nuug.no> on behalf of Petter Reinholdtsen <pere at hungry.com>
Sent: Tuesday, May 23, 2017 14:47
To: nikita-noark at nuug.no
Subject: Re: Article about Documaster in todays DN.

[Thomas Sødring]
> I doubt they are.

Heh, so we are probably alone covering the web API segment of the
market? :)

I think so. From the way I understand how things work in this segment,
I think the vendors will only invest time into updating Noark if the
customer really cry out. I think they will argue that upgrading costs
the customers more. Look at how many years it took Software Innovation
to go from temporary approval to final gives me this impression.

> I don't think that is possible. The project has been forked. The
> license clearly says AGPL. Even if I were to shut down my version, I
> can't stop anybody else from continuing with theirs. Also I have no
> commercial interest, so that helps.

So there are no copyright issues blocking further development.  But
there are others, if you were to leave, so it is a real risk that should
be taken into account. :)

I will leave eventually but so will you :) I have said I want to put this project
behind me and move on with "normal" R&D. But my intention is to stay
around until we get approval. We also are using this for teaching so I'm
not going anywhere soon. I could be hit by a bus, but there's little we can
do about that. My goal has always been to make the project bigger than me.
It worked with dots and I think it will work here to.

>> Dimitar donated a copy dots to me and this can be found here:
>>
>> https://github.com/tsodring/dots-noark5-core

>
> What is the code license for this copy?
>
> It says it there on the page I believe. But it's licensed under
> LGPL. I have an email from Dimitar somewhere where he's OK that it can
> be under APL.

Right.  So there are no copyright issues blocking futher development
there either.  That code is far as I can tell, the code from 2013 before
the program was commercialized.  I had a look at a later version from
NXC, but did not get far before it was pulled.  I learned back then that
people on github can remove other peoples git repositories if they want
to.  My github repository disappeared without my concent.  Learned not
to trust github to grant me control over my own git repositories when it
happend. :)

Anyway, I never managed to get the code to build, neither the one you
pointed to or the NXC code, so I do not really know how well it work.

I guess what you saw was what I built edu-dots on. edu-dots is not built
on 2013 dots, but an upgraded version that NXC gave me.

If you can delete other peoples repository, I suggest that people regularly
download a copy of nikita where the license clearly states that it is free. Do
not trust that the repo won't disappear. I always assumed you couldn't touch a fork!
My boss is also a proponent of openness so I cannot see us ever pulling the repo.

Perhaps NUUG/ you could host a copy on gitlab. That way I cannot touch it!

> No, not really. It's based on ZK. The only thing that's reuseable is
> the Java mail client integration and you have a much better approach
> to handling that.

Perhaps some GUI design features we could learn from, if you have used
it already in teaching?

Yes, I need to get the case-handling GUI finished for the 6th june. So I will
base it on the edu-dots gui. Or at least the parts of it that work well!

Btw, regarding GUI, can you push the latest web changes to
<URL: http://nikita.hioa.no:3000/ >?

done ..

Did not find  you on IRC, so I
poke here instead. :)

I've stayed away from IRC as I need to concentrate on correspondencepart
and it's variants. It has proved far more difficult than what I imagined it would
be to finish it. I'll hopefully push it today, but I doubt. So I'll push something
that works and fix the finer details. I don't believe it's clear from the
standard how it should be implemented so the mangelmelding I wrote covers
the approach I chose. We can discuss it once it's implemented, but it's hard to
implement a moving target :)

  - Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.nuug.no/pipermail/nikita-noark/attachments/20170523/32d12a78/attachment-0001.htm