still alive?

[hajika]

It looks like the developing of the app is paused at the moment, do you have plans to go forward with developing in the future?

[claudioc]

Hi,

thanks for asking :)

I have decided that the only way to go forward with Jingo would be to rewrite it and make it "modern" (the current codebase is really not super nice, for modern JavaScript standards – let's face it). Working on the current code base is not "fun", if you know what I mean, since I'd really love to refactor/change a lot of things that might break stuff that's working. I need then to start a new project and make the current one "deprecated" once the new would be released.

This obviously means that I need to schedule the time and goals for the Jingo 2.0 release and I'd rather do it once my workload in the company I work for at the moment (N26) gets a little bit more "relaxed" ;)

Jingo is by far my most successful project which means that I'd really love to keep working on it, maybe moving it (with a "plugin" system) to be a real CMS, git based.

What do you think?

[hajika]

the current codebase is really not super nice, for modern JavaScript standards – let's face it

to be honest, Iam not a nodejs developer and don't have a clue about that :) But iam surprised that you are still engaged, even in rewriting the code. I already expected that it will end with the same problem like other open source projects, that the original developer does not have the time to engage more energy in the project.

But it looks like you are still motivated, thats quite good :) And yes, a plugin system is always a very good idea! That would also make it possible to keep it simple and just add the necessary features.

[hajika]

you would not be interested to rewrite the app in ruby/rails code by any chance? I'am currently considering something like that.

[claudioc]

Mmmmh, no. One of the reasons Jingo is (moderately) successful is that it covers a niche for Nodejs and this is why I'd continue just to serve it like it is. The only other alternative there is (but it needs a database!) is Wiki.js

By the way, Jingo got inspired by a Ruby wiki (from Github itself): Gollum https://github.com/gollum/gollum

[mat-m]

@claudioc : This is all I wanted git-backed db-free markdown wiki in node.js, thanks for that.

Can we have a status on the rewrite ? Does it happen on a private repo ?

[claudioc]

@mat-m thank you :)

I took a moment to think about it and I decided to open what I currently have in Jingo 2, the rewrite.

It's hosted for now in Bitbucket (because it was created before Github started offering free private repos) and you can find it here https://bitbucket.org/claudioc/jingo-2/

As you can see, there are no new commits since the end of 2018 and I still don't know if I want to finish the project. One of the reasons is that (luckily!) now there is a lot more attention to security flaws, even directly from the npm organization itself and publishing a complete new version on npm means to have to consciously deal with some PRs to fix those flaws and I may not have time for that (without even thinking about new features and all the rest, obviously.

So, Jingo 2 is now open but I won't announce anything publicly, also because the project is somehow useful already (it has SO MANY more features) but not finished.

:)

[mat-m]

Thanks for this. I will have a look.