Hi Folks, Listing from git annotate are not informative because there are many contributors change same place of code.
Code author information can help us to solve 2 issues for new community members: - easy find reviewer and (Patch available queue), - find test author / mainteiner (MTCGA). So I strongly like Anton K. proposal. It's pity that author tag is banned by Apache. Let's think how we can solve these 2 issues without author tag. One more point: IMHO we should remove selection of 2+ mainterners or underline one (default) contact point for area. Necessity to choise may confuse newcomer. One main (default) mainteiner will redirect review. Sincererely, Dmitriy Pavlov ср, 14 февр. 2018 г. в 13:10, Anton Vinogradov <[email protected]>: > Anton, > > All listed info can be gained from git history. > > On Wed, Feb 14, 2018 at 1:01 PM, Дмитрий Рябов <[email protected]> > wrote: > > > For the first profit you should see maintainer table [1]. > > > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/How+ > > to+Contribute#HowtoContribute-ReviewProcessandMaintainers > > > > 2018-02-14 11:42 GMT+03:00 Vyacheslav Daradur <[email protected]>: > > > > > Hi Anton, > > > > > > Apache Ignite is licensed under the Apache License Version 2.0, which > > > does not allow to use author tag in java code [1]. > > > > > > [1] http://directory.apache.org/fortress/coding-standards. > > > html#classinterface-headers > > > > > > On Wed, Feb 14, 2018 at 11:23 AM, Антон Калашников <[email protected]> > > > wrote: > > > > Hello Ignite Community! > > > > > > > > My name is Anton. I joined to community some time ago and I want to > > > contribute to Apache Ignite. > > > > > > > > I would be want to make my first proposal. I noticed that Ignite > don't > > > have author description in header of classes unlike many other apache > > > projects. > > > > I propose to use javadoc tag @author in header of class when you > > created > > > it and also add extra tag @author when you do many changes in this > > class. > > > > > > > > Profits of this aproach, in my opinion: > > > > 1) You always know who has knowledge of this class unlike git > annotate > > > which are sensetive in refactoring, moving, etc. > > > > 2) It will highed responsibilty for code quality because nobody want > to > > > sign under bad code) > > > > > > > > Example: > > > > /** > > > > * @author Anton Kalashnikov > > > > * @author Other Author > > > > */ > > > > > > > > -- > > > > Best Regards, > > > > Anton Kalashnikov > > > > > > > > > > > > > > > > -- > > > Best Regards, Vyacheslav D. > > > > > >
