sparkfun / phant

the data logging engine behind data.sparkfun.com

700 stars 99 forks source link

Update project status in README #223

Closed thcipriani closed 7 years ago

thcipriani commented 7 years ago

The ambiguity of the status of this project has been touched upon in many recent issues. This update removes ambiguity about this service and this software. The outcome here is that phant will officially be de-prioritized; however, this signals to the community surrounding phant that new maintainership would be welcome.

An alternative to this pull request may be to open up commit access to members of the dev community. @stoto and @adewinter have done some stuff recently...

Fixes: #222, #221, #219, #208, #188, #187, #179

thcipriani commented 7 years ago

To be clear, while I previously had write access to this repo, I do not now. I have no affiliation with SparkFun and the views of this pull request are entirely the perspective of an outsider who is still, because of laziness, getting notifications about this repo. This is not, necessarily, what SparkFun thinks the best course of action is in this case, and, who knows, there may be Big Plans™ in the works.

jschertz commented 7 years ago

Thanks @thcipriani — I'm going to attempt to offer up a status here, I'm the software dev manager at Sparkfun, been with Sparkfun for about 11 months. Greetings.

Status:

[x] Make a lot of people upset
[x] Throw more AWS resources at the problem in the meantime (This is a war we'll lose eventually)
[ ] Establish a team at Sparkfun to pick this project back up
[ ] Have a lot of conversations both internally and with the phant community
[ ] Build a v2 (likely a python lib) while maintaining the legacy project and api

I can offer no timeline, but I can tell you that yes we're ready to move on Phant, it's a great project, the community has built a lot of cool stuff with it. We don't want to let that go. I'm going to bring myself up to speed on the project in the meantime and serve as a direct line of communication to Sparkfun. Yes, we hear you.

thcipriani commented 7 years ago

@jschertz howdy!

Happy to have an update about this repo and to hear that it's a priority for SparkFun. I'll close out my pull request for the time being since it is evidently not the way forward (an update with the New Plan on the README would be awesome). There are also a number of issues that could be closed-out, and some good pull requests to merge.

Glad to see SparkFun demonstrate its commitment to open source. I look forward to future updates :)