Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Longer supported? #302

Closed
fayimora opened this issue Dec 21, 2016 · 7 comments

Comments

Projects
None yet
6 participants
@fayimora
Copy link

commented Dec 21, 2016

Please note that this package is no longer supported.

I just spotted this in the README but I see @gandm still pushing commits. Clarification on that statement will appreciated 馃槂

@FlorianWendelborn

This comment has been minimized.

Copy link

commented Dec 21, 2016

@fayimora @gandm probably doesn't want to fully commit to this project anymore. I think it's more like a disclaimer that it's not a high priority project.

@gandm

This comment has been minimized.

Copy link
Owner

commented Dec 22, 2016

I will attempt to fix issues and add grammar support for new features (such as private class fields) if at all possible. However, I can't guarantee that these will be done in a timely manner, hence the support notice. If a new grammar should appear that is better supported I may choose to deprecate this package.

@gandm gandm closed this Dec 22, 2016

@timneutkens

This comment has been minimized.

Copy link

commented Dec 29, 2016

@gandm maybe a notice saying PR's are welcome is a good thing in this case, since right now it looks like it's deprecated and that's a waste of all time that has been put into it 馃槃 I will add it if you agree 馃憤

@FlorianWendelborn

This comment has been minimized.

Copy link

commented Dec 29, 2016

@timneutkens PR's what? The suspense is killing me!

@jayands

This comment has been minimized.

Copy link

commented Dec 31, 2016

@dodekeract That's actually proper, if somewhat "dated" grammar that has its basis in handwriting. in order to ensure clarity when pluralising acronyms and initialisms, people would often put periods between the all-capital sequence $(Boolean OR) use an apostrophe after said sequence. It's kind of fallen out of use since the proliferation of type as the primary interpersonal communication medium, but it's still not wrong, per se.

For example, you might see in a handwritten letter the phrases C.D.s, DVD's, and V.H.S.'s, assuming the letter was about someone's collection of "vintage" technology.

@timneutkens

This comment has been minimized.

Copy link

commented Jan 1, 2017

@jayands haha great sample on English grammar 馃槃 I'm Dutch... sometimes I tend to forget that it's PRs in english... 馃憤 In dutch we have words like pictures => foto's it's basically multiplying.

@michalczaplinski

This comment has been minimized.

Copy link

commented Jan 11, 2017

I would also strongly support changing the wording in the notice, because it makes it seem like the package is abandoned completely. I initially did not install it until a colleague pointed out to me that it is not the case and I believe many people will stop reading and move on after seeing the notice :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can鈥檛 perform that action at this time.