Skip to content
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.

Getting involved in the project #31

Open
jchristi opened this issue Apr 9, 2019 · 4 comments
Open

Getting involved in the project #31

jchristi opened this issue Apr 9, 2019 · 4 comments

Comments

@jchristi
Copy link

jchristi commented Apr 9, 2019

Hi, my co-workers and I are going to be creating a proof-of-concept deployment of openduty to assess if it could be a useful tool for teams in our org. We are doing this for a three-day hack-a-thon next week starting Monday. Aside from the README file, is there anything else we should know about the project? Is the current state of the code in a working state? Is development still active? Are there new features planned or a roadmap? Thanks!

@sysrex
Copy link
Contributor

sysrex commented Apr 9, 2019

Hi there, the current code state might not be the best scenario for you right now, you might want to use the docker image. We are currently upgrading it to django 2 and python 3, with a nicer interface and hopefully some more features and integrations, if you need any help let me know.

Regards,

@jchristi
Copy link
Author

jchristi commented Apr 9, 2019

Is that in a different branch than master or is the new code not open source yet? If not, would you mind pushing it to a new branch so we can inspect? I will use the docker image for the PoC, thanks for the tip.

@sysrex
Copy link
Contributor

sysrex commented Apr 9, 2019

you mean the docker container? - https://hub.docker.com/u/openduty/

@sysrex
Copy link
Contributor

sysrex commented Apr 9, 2019

the code is in master, you will see we swotched to python 3.6 and django 2.1.4, we have at least another 2 - 3 weeks until general release

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants