I second Zhaoxing's comments. A project should have a well defined, limited scope, for the reasons cited above as well as many others having to do with the overall health of the community. A DMaap project makes sense to me, AAA project, a Common Frameworks project does not.
Ed On Thu, Jun 1, 2017 at 11:32 PM, <meng.zhaoxi...@zte.com.cn> wrote: > Hi Liron, > > > I don't see significant benefits by putting a new project on top of other > projects after going through the "Common Frameworks" proposal. Instead, > there are some potential issues. > > If some codes/modules are put together into one project, ideally, they > should be interrelated. But these projects which are claimed to be put into > this proposal are created in different problem domains and no overlap. This > will create some management problems, such as > > - > > How to correctly define the committer for this project? Committers are > supposed to have written the seed codes and have the right skills to > contribute to the project, and they have access to modify and commit the > codes of the project which they are in. Given that the needed skillset and > background knowledge are totally different for the individual projects > inside this proposal, it's hard to assign access control to committers > properly. > - > > This project will become too huge to manage, for example, the mailist, > gerrit, jira, meeting, etc. will be full of a lot of unrelated discussion > and clues, similar to the current TSC maillist, which are flooded by > messages coming from different concerns. > > > Thanks, > > Zhaoxing > > > > > > 原始邮件 > *发件人：* ＜liron.shtraich...@amdocs.com＞; > *收件人：* ＜onap-tsc@lists.onap.org＞; > *日 期 ：*2017年06月01日 18:00 > *主 题 ：**[onap-tsc] Common Frameworks - Project Proposal* > > > Hello Committee Members, > > > > I would like to submit the following project proposal: > https://wiki.onap.org/display/DW/Common+Frameworks?src= > contextnavpagetreemode > > This project is a *consolidation of several other common projects* that > were already introduced to this committee > > > > > > Thanx, > > > > Liron > > > > > > > > > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, > you may review at https://www.amdocs.com/about/email-disclaimer > > > > > _______________________________________________ > ONAP-TSC mailing list > ONAP-TSC@lists.onap.org > https://lists.onap.org/mailman/listinfo/onap-tsc > >
_______________________________________________ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-tsc
