Is this project still maintained?

[hrbonz]

Seeing a lot of opened issues and PR and last commit 11 months ago, I'm wondering if this project is still maintained.
This was a very promising service when it was published but the lack of follow up makes it a dangerous choice IMHO.

So what is the status here?

[istathar]

Ordinarily one would take this as a troll, but I think given the security critical nature of what stud does it's probably a timely question. As @hrbonz points out, there have been a lot of contributions but no activity from the original authors. I know full well the bumptech people are busy with things like nitro, but the fact that angel was also recently abandoned does make one wonder. Hopefully it's just a case of "hasn't been a priority" but if that's the case, perhaps a deliberate handover to a new maintainer would be something to consider, if someone is willing to step up.

AfC

[afterfate]

I opted to use the insom(https://github.com/insom/stud) fork as my point of reference when I worked on stud and it's going to be my source for updates going forward unless the activity here picks up. My assumption is that the authors have stud where they want it to be and are busy with other work.

[hrbonz]

Not every controversy is troll, even on internet ::)
I'm genuinely concerned, given the critical nature of the product and
planning to use it myself on a vomit project. Just trying to get objective
status.

Thanks for your answers, will probably help future users figure it out as
well.

Stefan, from my mobile

http://www.bonz.org/
/(bb|[^b]{2}/
On 8 Aug 2013 20:36, "Andrew Cowie" [email protected] wrote:

Ordinarily one would take this as a troll, but I think given the security
critical nature of what stud does it's probably a timely question. As
@hrbonz https://github.com/hrbonz points out, there have been a lot of
contributions but no activity from the original authors. I know full well
the bumptech people are busy with things like nitro, but the fact that *
angel* was also recently abandoned does make one wonder.

AfC

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/137#issuecomment-22320305
.

[AlekSi]

I guess now we know the answer (663d9c3).