sooo you want a conda cep i think :D
@sils1297

from @underyx

Create coala community code of conduct

• create [email protected] email (done. Thanks @sils)
• create coala.io/conduct that redirects to the code of conduct cEP

I have the content in https://github.com/coala/coala/wiki/Code-of-Conduct but will create a formal cEP for this.

No longer will the local bears be dependent on global bears to finish, local and global are interchanged

difficulty/newcomer

Opened via gitter by @jayvdb

Instead of referring to user or team leader as he, use they 😃
https://en.wikipedia.org/wiki/Singular_they

Example:
cEP 5:
... allowing the user to specify what aspects of his code should be analyzed

cEP 3:
His job is not to do the ...
A Team Member agrees to focus his work ...

The part of cEP (click the link):

Every org member that started following the newcomer guide is declared a newcomer by invitation into the GitHub organisation. Newcomers can work on issues with an assignment.

Actual: GitHub 404 Page (behaves as relative link)
Expected: coala newcomer guide

I think we should:

• rename coala to coala-core
• make a coala package that bundles cib and coala and coala-quickstart etc.

Useful dates:
Date it was first authored,
Effective date,
Last update

Thoughts?

See discussion. Mockup:

[python]
language = python
analyze = complexity, syntax, smells.feature_envy

Opened via gitter by @sils

Opened via gitter by @sims1253

CC @plaindocs , was his idea

We can add a paragraph to every leaf of aspects with placholders for e.g. the settings and then we can generate a full written guide on how to write beautiful code from all selected aspects!

Opened via gitter by @sils

Opened via gitter by @sils

The community may at all times abandon the project and create a fork if the BLD acts stupidishly or is uncovered a fraud.

This can be interpreted as "the community MAY NOT abandon the project and create a fork UNLESS the bld acts stupidly or is uncovered a fraud"

Even though (or especially because) I don't expect this statement to be meant that way this should probably be changed...

and also "stupidishly" should probably be "stupidly"

In the heading titled The aspests there is a spelling error change it to The aspects.
I think this will be a good newcomer or gci issue.

Subsection: Problem
Paragraph: 2
Last sentence
analyses-->analysis

In line 195 replace max_identifier_length with min_identifier_length

Difficulty/newcomer

Many cEP titles have mentioned 'Coala' instead of 'coala'

https://github.com/coala/cEPs/blob/master/README.md

In LIne 84 please correct the format of Markdown link.

difficulty/newcomer

Opened via gitter by @sils

right now the only shortURL that works
is this one ---> coala.io/cep5

all the othere; i.e. coala.io/cep#

where # is 0 to 4 or 6 are re-directed to cEP-0000
difficulty/low

This is useless as without a leader the team does not exist :D

I feel as the main channel is to crowded as a landing channel.
Maybe try to set up channels from the ground up again and remove the "grown" ones.

The policy, and the technical framework which supports it, need to be documented and accepted, before 1.0.

They are closely linked and should really be a unified cEP, as the policy imposes requirements on the implementation.

The most critical task is defining where we are now, at 0.8/9. Are we currently trying to provide a dependable API, or is it still in flux until 1.0?

However, the most important step is demarcating what is public vs private. If that is not clear, there may be parts of the code base that need to be declared non-public, which means the API is still in flux.

A common policy that most people agree with is that _ prefix means that the object is explicitly not covered by a deprecation policy. A client that invokes a _ prefixed object has no contract to rely on.

Is everything else a part of the public API? If not, do we have a clear definition of what is in the public API?

Maybe give time for others to apply before voting

Add a file named ISSUE_TEMPLATE.md which includes general information and guidelines for issue reporter, you can see ISSUE_TEMPLATE.md of coala repository for reference.
label: initiatives/gci
Opened by @Monal5031 at gitter//Monal5031

IMO:

• making members as we do know (jsut write it down)
• dememberize any member that hasn't done a contribution within the last three months. This should be evaluated for all members every three months.A "Contribution" is rather loosely defined on purpose. There should be a committee taking care of this and deciding what counts and what doesn't. If members disagree they can of course make a B (or C) level decision.

Any opinions? @sims1253 ?

Maybe we can even have a bear and enforce a bit of API docs incrementally?

Opened via gitter by @sils

It would be great if we have a cEP index in the readme with headings | brief description of cEPs.

coala will use aspects instead of bear names in the future, but some bears have extern dependencies.
E.g. a user want to use a brackets linter for CSS but doesn't how what extern dependencies are needed

Opened via gitter by @sils

the zeros are useless and python does it as well

Add a file named PULL_REQUEST_TEMPLATE.md which includes general information and guidelines for the author of Pull Request, you can see PULL_REQUEST_TEMPLATE.md of coala repository for reference.
label: initiatives/gci
Opened by @Monal5031 at gitter//Monal5031

The correct spelling for doxing is doxxing

A formal definition of our release procedures, frequency, and tools

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/2

It further affects coala/documentation#223

@sils Please! :D

@coala/aspects-developers @EverWinter23

#aspectsYEAH

Member is not well defined I feel. We vote to invite people to the maintainer channel and member could just be a member of the github org eg.

Make cEP for the teams introduced here:
https://github.com/coala-analyzer/coala/wiki/Governing-coala

• report mechanism eg. every few months an activity report is published

Would be nice to make it impossible to merge cEPs with only one ack

Any concerns with a public vote? If we use a google formular the answers can be seen.

It would be good to have a cEP defining the specification of the config files we use.