Hi all, On Tuesday, January 21, 2014, Senaka Fernando <[email protected]> wrote:
> Hi all, > > +1 for Sagara's proposal. These projects have a life outside the Carbon > Platform. But, we need to find a place to host them. If everything ends up > on GitHub should these be in their too? If so, are they a WSO2 repository? > Or is it a separate TLP? > Here Sagara, Senaka came up with a good point. We don't need each and every one to have a git repo in wso2 space but we can still use svn for managing these codes where not much of the developers of carbon worry about. WDYT? Thanks Eranda > Thanks, > Senaka. > > > On Tue, Jan 21, 2014 at 9:11 PM, Sagara Gunathunga <[email protected]>wrote: > > > > > On Tue, Jan 21, 2014 at 3:34 PM, Sriskandarajah Suhothayan > <[email protected]>wrote: > > How about WSO2 Commons projects, E.g Siddhi ? > > Currently its in commons and under dependencies/commons > > Where should we have this? > > I believe projects like Siddhi also need to be top level repos may be > "commons-siddhi" and it don't need be in dependencies/commons anymore. > > WDYT? > > > Ideally these projects should be treated as external dependencies to > Carbon code base just like Apache XMLSchema or Axiom only difference here > is those project are managed by WSO2. We should create separate repos for > each of them and Carbon should only take them as Maven dependencies only. > For naming I guess "Siddhi" is a good name because "commons" part does not > make any meaning here. > > in my POV these should be the project we need to move out of Carbon code > base. > > > Jaggery ( we just need to get rid of SVN externals as code base it already > on GitHub) > Caramel > Charon > Balana > Siddhi > > Thanks ! > > > > > > Suho > > > On Tue, Jan 21, 2014 at 3:13 PM, Eranda Sooriyabandara <[email protected]>wrote: > > Hi All > Please find the updated governance component in [1]. > > thanks > Eranda > > [1]. https://github.com/wso2/carbon-governance > > > On Tue, Jan 21, 2014 at 2:56 PM, Shariq Muhammed <[email protected]> wrote: > > On Tue, Jan 21, 2014 at 2:42 PM, Eranda Sooriyabandara <[email protected]>wrote: > > Hi Shariq, > Yeah, we may not needed those to be build again and again. So let's add > related stubs to service-stubs directory in each repo. > > > Yea lets structure it that way. > > > > thanks > Eranda > > > On Tue, Jan 21, 2014 at 12:51 PM, Shariq Muhammed <[email protected]> wrote: > > On Tue, Jan 21, 2014 at 12:38 PM, Kishanthan Thangarajah > > > > *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* > Senior Technical Lead; WSO2 Inc.; http://wso2.com > > > > * Member; Apache Software Foundation; http://apache.org > <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 > 408 754 7388; ext: 51736*; > > > *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando > <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware > -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
