Good ideas IMHO. 1. I wouldn't separate Javadoc vs. non-Javadoc. Everyone should care about Javadoc (or generally, code-level) documentation. Javadoc is part of the code. 2. Need to ensure that IDEA configs don't have any absolute paths in it.
We would also need a separate doc for Java and Scala coding guidelines. Not everything can be (or should be) enforced by IDEA. Thanks, -- Nikita Ivanov On Sat, May 23, 2020 at 8:53 AM Sergey Kamov <[email protected]> wrote: > Hi Furkan! > > Yes, prepare and share IDEA configuration properties for all team members. > > > Regards, > > Sergey > > 23.05.2020 17:18, Furkan KAMACI пишет: > > Hi Sergey, > > > > Do you mean something like this: > > https://github.com/apache/druid/tree/master/.idea > > > > Kind Regards, > > Furkan KAMACI > > > > On Sat, May 23, 2020 at 1:46 PM Sergey Kamov <[email protected]> > wrote: > > > >> I guess we need to have some common configuration for our IDEs to have > >> same project files' warnings for all team members. > >> Can we add these configuration files under git? > >> > >> One additional point - maybe better to have 2 different configs? The > >> reason is javadoc warnings are optional. > >> > >> - Some team members (which work on javadoc) need these warnings > >> - Other team members don't need such warnings because they can > >> distract them (they will ignore such warnings and can skip as result > >> some other) > >> > >> > >> Regards, > >> > >> Sergey > >> > >> >
