Open userzimmermann opened 7 years ago
sure go for it ;)
Sincerely,
Lasse Schuirmann
lasse@schuirmann.net http://coala.io/ - http://viperdev.io/ - http://gitmate.com/
On 28 March 2017 at 21:17, Stefan Zimmermann notifications@github.com wrote:
Just like coala itself, the terms aspect and aspects are just too fundamental to be ever written capitalized :)
Also all new API elements in coalib containing the term aspect are stricly lowercase. So always keeping it lowercase would give a much more consistent feeling and make the future of coala even brighter :)
This requires an additional rule in cEP-0005 and some changes to existing cEP-0005 text, doc strings in coalib.bearlib.aspects, and #67 https://github.com/coala/cEPs/pull/67.
@sils https://github.com/sils Please! :D
@coala/aspects-developers https://github.com/orgs/coala/teams/aspects-developers @EverWinter23 https://github.com/EverWinter23
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/coala/cEPs/issues/69, or mute the thread https://github.com/notifications/unsubscribe-auth/AFc6KG4uI96pI-WnCt74XFT9AcZMkA2tks5rqVzTgaJpZM4MsEsr .
Started with correcting https://github.com/coala/teams/issues/11 and https://github.com/orgs/coala/projects/2 :)
It is bad enough that we have this rule for coala; but as that is not a real word, grammar rules about it are invalid anyway.
However people use the word aspects all the time, especially in programming, without any intention that it refers to this part of coala.
There are lots of other important sub-units within coala. If named according to pep 8, they would all be lower class in the source code. That isn't reason to create special grammar rules, and more inhouse-only bears.
@jayvdb You got the intention correctly. It's just like the lowercase coala and only intended for in-house use. Or better: only to be applied to coala's only repositories and documentation :)
So we are not allow to use the word aspects except to talk about aspects and then we must write it the way you want?
@jayvdb The whole thing is only about coala's new aspects framework and the spelling rules shall only apply when related to that framework. And the @coala/aspects-developers and @sils are fine with it. As you correctly pointed out in https://github.com/coala/cEPs/issues/69#issuecomment-293244845 , an aspect is a general term used for many things. It's not our intention to extend our little dogma ;) to any use beyond coala's aspects framework :)
FWIW I'm not for this I'm fine with you having your fun as long as there is no negative impact on the rest of the community. This seems to be controversial and thus @userzimmermann it might be good to just not do it: use aspects in your spelling in your docs but leave the cEP and don't make a builtin bear? @userzimmermann please wait until we have a decision on this ok?
FWIW I'm not for this I'm fine with you having your fun as long as there is no negative impact on the rest of the community. This seems to be controversial and thus @userzimmermann it might be good to just not do it: use aspects in your spelling in your docs but leave the cEP and don't make a builtin bear? @userzimmermann please wait until we have a decision on this ok?
@sils @jayvdb It's more about motivation than fun. Or let's say motivation through fun. It's about team bonding and identity that arises from such ideas and that kind of uniqueness. It's an important reason for the small aspects team working so well and efficiently together. We should not destroy that
I also can't really see that negative impact on the community or any real controversy. But you are right! We need a definite decision of the whole core community about this. So let's keep the cEP untouched regarding this for now. And the aspects team will just keep those spelling rules inside coalib.bearlib.aspects
as an unwritten law :)
We can of course delay the aspectsYEAHBear
development or just put it inside of coalib.bearlib.aspects
for now and use it just for linting coalib.bearlib.aspects
. That would again be much simpler in an own coala-aspects project
@coala/aspects-developers
This issue seems stale!
@userzimmermann please reassign yourself if you're still working on this.
(Powered by GitMate.io)
Just like coala itself, the terms aspect and aspects are just too fundamental to be ever written capitalized :)
Also all new API elements in
coalib
containing the term aspect are stricly lowercase. So always keeping it lowercase would give a much more consistent feeling and make the future of coala even brighter :)This requires an additional rule in cEP-0005 and some changes to existing cEP-0005 text, doc strings in
coalib.bearlib.aspects
, #67, and https://github.com/orgs/coala/projects/2It further affects https://github.com/coala/documentation/issues/223
@sils Please! :D
@coala/aspects-developers @EverWinter23
#aspectsYEAH