Project/repo maintenance status?

pataquets commented 7 years ago

While checking for news on open issues, I've found no significant activity on the project since quite a long time. I wondered if the project is dead/abandoned, but browsing https://github.com/ustream/openduty/network/members I've found a openduty/openduty repo with more recent activity. Has this project moved? Is the above fork maintained/monitored by the authors? Is it related in any way? Clarifying this would prevent people posting issues & PR in the wrong one if moved, or at least, having reasonable expectations on them to be addressed. TIA.

(In case this repo notifications are off, tentatively pinging possible relevant parties @deathowl @jkapusi @DazWorrall, sorry for the spam)

kjetilmjos commented 7 years ago

Good post! Have been trying to find out myself recently as we plan to use openduty in production. Love the idea of openduty, but we should try and find one master project from all the forks and get a community up and running again. I'm certain a lot of people have a need for a opensource and free alternative pagerduty and the others.

kjetilmjos commented 7 years ago

New issues and pull requests should be posted here: https://github.com/openduty/openduty-old A new version of openduty written in nodejs has been started on, and anybody interested can find the project here: https://github.com/openduty/openduty

antgel commented 7 years ago

Shame nobody from the ustream team has responded yet. My question is whether there will be a migration path from the Python to node.js versions...

sysrex commented 6 years ago

@antgel , sorry for being late at the party, we worked hard in the past few months to bring a new updated version for Openduty under nodejs, and also creating a mobile application, we expect in the next couple of months to have a beta release.

pataquets commented 6 years ago

A few thoughts:

I share @kjetilmjos first comment, a FLOSS alternative to PD is definitely needed. However, I don't agree with the steps taken later.
Having an OpenDuty user is OK. Perhaps a org would be better, but not a problem, anyway.
I appreciate the effort on rewritting a new PD clone, but I think it should not be named OpenDuty. It would confuse new users, and even confuse more current ones. It could be named OpenDutyJS or something different, even a new name not related to OpenDuty. What if some person/org wants to take over the project in its current language later? How will people distinguish versions (adding 'old' or 'new' sounds cheap and will end being confusing).
Also, if the OpenDuty project as is now has to be abandoned, so let it be. I think it's beter to make it obvious than to fake that it's still alive and spread the possible issues and PRs (unless there is some commitment to maintain it). Someone might eventually pick it up.
Linked to the above, the openduty-old repo naming is also unfortunate. It should have the openduty original. Think in the fork graph and SEO.
Also agree with @antgel: a shame nobody responded yet. In the ustream user page it can be read 'an IBM company'. Anybody knows how to contact them. I think this situation is just being unnoticed, otherwise IBM's policy on FLOSS would be questionable. Perhaps they should be contacted, not sure about IBM's policy. (cc @deathowl @jkapusi @DazWorrall)
Ideally, no matter who is taking over the project, should make clearly visible who is behind it, if a group of individuals, some company and (desirable) what commitment can have. Using the correct username and/or organiztion on Github would help make it visible and event let people jump in later.

Thoughts? Comments?

krutaw commented 6 years ago

@deathowl, Any chance expanding the folks who can merge/whatnot so that we can breathe a bit of life back into this project?

syntaxerror13 commented 6 years ago

Hi all, sorry for the so long silence, this got a bit under the radar on our end. The Ustream team which is now part of IBM are no longer maintaining this project. We will also review our Github account to see if there are other such projects. Feel free to fork it and maintain it somewhere else, we will leave it accessible here but no new merges or commits will be made.

syntaxerror13 commented 6 years ago

Also please note that the NodeJS version was not created by us (it was started by @deathowl after he left)

sysrex commented 6 years ago

@pataquets - https://github.com/openduty/openduty the project has been reinstated, openduty is an org and anyone who whishes can be part of it. @kjetilmjos please let me know if you want to submit PR's . I got caught in some work lately and haven't had time to pursue the JS version (which has been name as you guys suggested, btw thanks) I will however submit some front-end improvements in order to update the bootstrap version.

kjetilmjos commented 6 years ago

Hi, I dont have any pull requests at the moment, decided to use the linkedin Iris project https://github.com/linkedin/iris due to the lack of activity on this one, but I might go back to openduty again now if it's going to be more activity again :)

kjetilmjos commented 6 years ago

Are the pull requests from this repo added into the new reinstated project @pataquets ?

sysrex commented 6 years ago

https://github.com/openduty/openduty

ustream / openduty

Project/repo maintenance status? #92