Is the project alive?

Question

Is the project alive?

Trapulo opened this issue 8 years ago · 13 comments

I see that also the main website has been closed... :(

Answer 1 · 2017-02-13T12:23:58.000Z

seems that it is not anymore alive... so sad, it was great.. 😞

Answer 2 · 2017-02-16T07:21:16.000Z

Bugnet project is officially discontinued but software is still available and fully working. It will just no longer be improved.

Answer 3 · 2017-02-16T07:24:58.000Z

so is dead :(

Answer 4 · 2017-02-23T01:40:22.000Z

I am not actively developing the project anymore but the source code and previous releases are all available. Sadly no one has shown interest in contributing code to the project.

Answer 5 · 2017-02-23T04:44:50.000Z

I started participating in this project initially but then I came to know that the repo I am working on was not the current one. I reported a few issues about missing stored procedures but they were not resolved anyways. So I had no option than to stop working. I am still very much interested. Let me know if we can resume.

Answer 6 · 2017-02-23T05:44:50.000Z

We're doing improvements that we needed in BugNet locally, and then send PR's when we're done. Currently we've only pushed so that project titles are shown in the roadmap pages. If people with interest would fork and fix issues, everyone would be glad I think. :)

Answer 7 · 2017-02-23T08:38:11.000Z

In the past we translated BugNET in italian, so if you are planning to continue development we offer our collaboration localizating future versions (at least in italian).

Answer 8 · 2017-02-24T08:36:26.000Z

A great goal can be integrate Bugnet with Bonobo (https://github.com/jakubgarfield/Bonobo-Git-Server), also ASP.NET: it will be a great OSS solutions that can compete with many SAAS services. Bonobo is MVC and can be the starting platform where to move Bugnet features, leaving the old Webform GUI.

Answer 9 · 2017-02-25T01:00:31.000Z

@Trapulo That sounds neat. Please feel free to implement this.

Answer 10 · 2017-02-25T01:02:23.000Z

In regards to all the missing stored procs in #233 and #218. This was mostly because I didn't have a branch when making destructive changes and now some features are half complete. I don't mind spending an hour or two just getting it back to where it can be installed and running again.

Answer 11 · 2017-03-10T23:10:12.000Z

Occasionally came to check what's new, and read:

Sadly no one has shown interest in contributing code to the project.

I guess the reason is that the project is already good as it is. I implemented BugNET a little less than a year ago, and without taking into account the minor flaws that I corrected, I am very pleased. So far, I'm satisfied with almost everything. There are some ideas for improving the product, and if I'll have time (o-oh), I'll definitely realize them. But ... I think that it's incorrect to say that the project is dead.
I want to express my deep gratitude to the Author for his Work.

Answer 12 · 2017-03-20T07:45:55.000Z

I'm starting to migrate BugNet on Asp.NET MVC and Entity Framework, upgrading Bootstrp versione and introducing Kanban dashboard and other issues.
It would be great do this on the Pro version... Could you provide source code?

Answer 13 · 2017-05-10T05:29:36.000Z

I've just deployed BugNET on Azure App Service. So far so good. I used this Azure Marketplace Template.
Version: Powered by BugNET 1.6.339.0. Hoping this one comes without missing stored procedures. I'm really looking forward to it.