-
Notifications
You must be signed in to change notification settings - Fork 290
Announcement on Temporary Support Reduction #250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm sorry to renew the "support lack period" to other 1-2 weeks (from now 13 Oct 2015); I'm quite sure (certainity 85%) this is the last time. Sorry again, guys, I hope main contrib can help you... (If they have time). The nature itself of the project will already helps you, it's OSS; hack it -> use private hacked version for a while and when I'll be back available we can even disucuss to merge your work w/ a PR if of public utility. So at maximum extent first days of november this issue will be digitally killed and reduced to an useless junk sequence of 0 and 1, when I'll hit "Close and comment" buttton! (...and in GitHub DB system -- I don't know details -- this issue will be flagged as CLOSED). 😄 Giacomo 😸 |
Support restored! Please be patient while I try to catch up with backward issues. |
I'm sorry to announce that for period of time that can lasts/varies from 1 to 2 weeks (as maximum) from now (02 Oct 2015), I'll not be able to supply support to this (and other open source projects).
Cause: I'm overwhelmed from duties caming from ordinary (not OSS) job orders.
I'll try not to completely blackout (if possible) my presence here, but please be patient if I reply late to issues or emails (I can even not reply at all during this period, sorry).
I'm here also to ask help in giving support to developers/users to project's main contributors (in no particular order): @nemec, @mizipzor, @Thilas, @gimmemoore.
Regards and thanks for understanding!
Yours,
Giacomo
P.S.: End of such period will be emphasized/confirmed from the closure of this issue.
The text was updated successfully, but these errors were encountered: