Library Status?

[machineghost]

I'm looking for a JS-based wiki, and Jingo seems promising, but it hasn't had any commits made in ten months. Clearly it's not "done" yet (as it has 55 issues), so my question is: how come?

Has the maintainer lost interest in the project, or is there some other reason? And if they lost interest, was it because of core issues with the library, or because they found a better solution, or because the library is "good enough" for them, or ...?

It just would be helpful to understand why a seemingly great library with almost 1k stars has had no activity for such a long time.

[claudioc]

Hey @machineghost

thanks for the questions (I should consider adding the answers to the README at this point).

I am the only developer of Jingo and as you can see it is quite an old project. A lot of people have it installed (I don't have the numbers of course, but over the years I got a lot of feedback and almost 1k stars here in github) which means that I consider it definitely "done", at least as its version "1". The open issues are mostly "wontfix" or integrations that I cannot consider be part of the core system... I leave some of the issues open because sometimes people find a solution to a specific problem other users may have... it's kind of a "public forum" for Jingo...

I keep updating Jingo for bugs and security issues (I am about to release an update just now).

Features wise, I am not actively developing it because:

• I have now less time than I had before, when I started it
• a couple of years ago I started developing the second version of the wiki engine which means that all the development efforts are of course focused on that version, not this one
• to be honest, since Jingo is a pet project and should be fun to work with, the codebase is pretty old, which means that working with it is not fun; the new version is much better in this regard

The problem with Jingo 2 (source code available https://github.com/claudioc/jingo-2/ ) is that the list of (new) features is quite big and being a single person with a big project to handle is not easy, if you want to release something useful, secure, maintainable and well documented (all MUST HAVEs for Jingo 2).

That's the status of things right now :)

[machineghost]

Thanks!

…

On Fri, Nov 15, 2019 at 5:50 AM Claudio Cicali ***@***.***> wrote: Hey @machineghost <https://github.com/machineghost> thanks for the questions (I should consider adding the answers to the README at this point). I am the only developer of Jingo and as you can see it is quite an old project. A lot of people have it installed (I don't have the numbers of course, but over the years I got a lot of feedback and almost 1k stars here in github) which means that I consider it definitely "done", at least as its version "1". The open issues are mostly "wontfix" or integrations that I cannot consider be part of the core system... I leave some the issues open because sometimes people find a solution to a specific problem other users may have... it's kind of a "public forum" for Jingo... I keep updating Jingo for bugs and security issues (I am about to release an update just now). Features wise, I am not *actively* developing it because: - I have not less time than I had before, when I started it - a couple of years ago I started developing the second version of the wiki engine which means that all the development efforts are of course focused on that version, not this one - to be honest, since Jingo is a pet project and should be fun to work with, the codebase is pretty old, which means that working with it is not fun; the new version is much better in this regard The problem with Jingo 2 (source code available https://bitbucket.org/claudioc/jingo-2/ ) is that the list of (new) features is quite big and being a single person with a big project to handle is not easy, if you want to release something useful, secure, maintainable and well documented (all MUST HAVEs for Jingo 2). That's the status of things right now :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#264?email_source=notifications&email_token=AADNTDHTLHKIBU3QIJQWQYLQT2SKVA5CNFSM4JFSFXNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEFPEGQ#issuecomment-554365466>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADNTDFGWLXPIA5X4T4VWADQT2SKVANCNFSM4JFSFXNA> .

[tiger73]

Hello -

I just installed Jingo 1.9.4 and was going to make some queries when I stumbled across this post and am of course intrigued. Thank you very much for Jingo 1.x!!! I selected Jingo because this was exactly what I was looking for - LIGHT, online editing & preview, git mgmt (I have an internal git repo) as this will be a small wiki.

Is the current jingo-2 @ bitbucket stable enough for light use and these light requirements? Can I install jingo-2 and point it to the current jingo-repository?

Thank you very much for your consideration and continue investment in Jingo!

-t

[claudioc]

@tiger73 you can try! A couple of days ago I released some important changes in Jingo2 that should make it usable "enough". Please keep in mind that:

• that version is currently totally unsupported. If it works, good but if it doesn't… sorry :)
• it's in active development, which means that if I want to break something or change the look or some configuration keys or values I want to be able to do it without thinking of the installed base (like I do for Jingo 1, of course)
• it's not packaged, which means that you have to install it yourself

I wouldn't consider it ready for its prime time, unless you ALSO want to contribute to its development :)

[tiger73]

Howdy, Thank you very much for the rapid response and totally legit considerations / caveat. I'm not much of a developer, so I would just be holding you back. :-( Best of luck to both of us!

…

-t

On Thu, Nov 28, 2019 at 1:29 AM Claudio Cicali ***@***.***> wrote: @tiger73 <https://github.com/tiger73> you can try! A couple of days ago I released some important changes in Jingo2 that should make it usable "enough". Please keep in mind that: - that version is currently totally unsupported. If it works, good but if it doesn't… sorry :) - it's in active development, which means that if I want to break something or change the look or some configuration keys or values I want to be able to do it without thinking of the installed base (like I do for Jingo 1, of course) - it's not packaged, which means that you have to install it yourself I wouldn't consider it ready for its prime time, unless you ALSO want to contribute to its development :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#264?email_source=notifications&email_token=AFBMXCPLYSXVBLE4CFIXZADQV6FO7A5CNFSM4JFSFXNKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFL7WSI#issuecomment-559414089>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFBMXCOP7VJPX2GJ22LQXN3QV6FO7ANCNFSM4JFSFXNA> .

[leviwheatcroft]

@claudioc I'm really interested in helping out with jingo-2

I had a look at the repo you shared and managed to get it to run!

Absolutely not a criticism at all, but just to mention a few things I needed to do:

• install es6-promise and @types/passport
• create config.json from src/config/defaults.json (not necessary ?)
• copy templates from src/routes to dist/routes

You should absolutely make a github repo for jingo-2. It looks like you're not far off from a somewhat-working-alpha, I'd be happy to help you work towards that and build a docker container.

Once we achieved that you might get some love from other contributors. I do think there's a niche for a nodejs git backed wiki, and jingo is the best in that category for the moment.

[claudioc]

Hey @leviwheatcroft ,

Damn right, sorry... es6-promise is needed and I forgot to add it :/

Yes, the config must be created manually and you can use (as for Jingo-1), ./jingo -s

I am going to fix those things and move the repo to github today! (I will keep you updated).

Thanks!

[claudioc]

@lewiswalsh All done (https://github.com/claudioc/jingo-2

I don't get the issue you have with the templates though?