I can think of another benefit of standardizing components: one can aggregate all the opened issues in a given component. However, often the reporter doesn't know where the issue is, and some tasks go beyond a single component.
Regards, Arnab.. On Sat, May 22, 2021 at 12:50 AM Mark Dokter <mdok...@know-center.at> wrote: > On 5/20/21 2:00 PM, Janardhan wrote: > > Hi all, > > > > Hi! > > > We do have some components with just one or two issues and some > > duplicates (like, Tutorial, Optimization, NeuralNetworks). > > > > We already identified the commit tags and types of commits[1]. > > > > Shall we identify the core components and derivative components? > > > > The list has probably grown historically and revisiting how to organize > it might be a good thing. Splitting it up too much would add an > administrative burden though imho. > > > Ideally, we need > > 1. a small description (if need be.) > > 2. Core component / Derivative component. > > For example, Algorithms, Compression are core components > > 3. Which components to drop. > > > > Components List:[2] > > > > > [...] long list [...] > > There are also organizational "components" like "Website". So it'd be > core/derivative/organizational? A description would definitely help. > > Regards, > Mark > > > -- > > [1] https://github.com/apache/systemds/blob/master/CONTRIBUTING.md#tags > > [2] > > > https://issues.apache.org/jira/projects/SYSTEMDS?selectedItem=com.atlassian.jira.jira-projects-plugin:components-page > > > > >
