Hello Everyone, This is an update on the current status of the work as of 20/11/2013;
*The meeting minutes of the progress update meeting has been sent out as a separate mail : [Architecture] APIM Store migration to ES Store progress update meeting minutes* *Completed* - Implemented the Throttling tab - Implemented the API Console tab - Added the thumbnails and document files - Implemented the Overview tab *Pending Tasks* - Identify main tasks and create Redmine issues. - Setup nightly builds of the changes - Decide on the approach taken to implement commenting. - Document migration steps for moving the images and files to Store storage mechanism *Immediate Goals* - Implement the My Applications page - Implement the My Subscriptions page - Implement the commenting component of the Overview tab Thank You, Sameera On Thu, Dec 19, 2013 at 3:14 PM, Sameera Medagammaddegedara < [email protected]> wrote: > Hello Everyone, > > When would be a good time to schedule a meeting in order to perform ; > > 1. A UX Review > 2. To get input on the requirements mentioned by Senaka > > @Nuwan: > > - I am currently working on a 1.5.0 pack after setting up a soft link > to the store and manually copying relevant modules > - I will be shifting to a scratch space after the release of APIM, at > which point I will be able to start creating builds for milestones > - However, I can host the current working pack. > > Thank You, > Sameera > > > On Thu, Dec 19, 2013 at 6:25 AM, Nuwan Bandara <[email protected]> wrote: > >> Hi Sameera, >> >> Can we get some milestone builds from this work, so we can download and >> try the new packs. >> >> Regards, >> /Nuwan >> >> >> On Wed, Dec 18, 2013 at 7:56 AM, Sameera Medagammaddegedara < >> [email protected]> wrote: >> >>> Hello Everyone, >>> >>> This is a small update on the current status of the task as of 18/12/2013 >>> >>> *Completed* >>> >>> - Implemented the Documentation Tab in the API Details page >>> >>> >>> *Problems faced* >>> >>> - *None* >>> >>> >>> *Pending Tasks* >>> >>> - Identify main tasks and create redmine issues . >>> - The working repository for the APIM Store integration needs to be >>> moved to wso2scratch repo.In addition, any changes that are implemented >>> to >>> the ES Store must be pushed to the wso2/enterprise-store repo. >>> - Decide on the approach taken to implement commenting >>> - Decide on how images and documents will be stored *[Working on >>> this]* >>> >>> *Immediate Goals* >>> >>> - Implement the Overview Tab in the API details page >>> - Implement the Throttling Tab in the API details page *[Working on >>> this]* >>> - Implement the API Console Tab in the API details page* [Working on >>> this]* >>> >>> *Reference* >>> >>> [1] Git repo, url: https://github.com/splinter/apim >>> Thank You, >>> Sameera >>> >>> >>> On Tue, Dec 17, 2013 at 6:59 PM, Sameera Medagammaddegedara < >>> [email protected]> wrote: >>> >>>> Hello Everyone, >>>> >>>> This is a small update on the current status of the task as of >>>> 17/12/2013 >>>> >>>> *Completed* >>>> >>>> - Tagging feature has been integrated to the APIM Store >>>> - The "More APIs from provider" widget has been implemented >>>> - This feature has been implemented at the Store level. >>>> - It requires a bit of re factoring in order for it to be >>>> enabled/diabled from a configuration file (By default this widget >>>> will not >>>> be enabled for the Generic store) *[Working on this]* >>>> >>>> >>>> *Problems faced* >>>> >>>> - The module structure of the APIM Store differs from that of the >>>> Generic Store. >>>> - There are two possible ways of integrating the APIM Store >>>> modules; >>>> 1. Copying the modules to the /extensions/assets/api/modules >>>> folder and changing the module path of the Jagg object >>>> 2. Re factoring the modules to the structure of the Generic >>>> Store >>>> - I have opted for the 1st option due to; >>>> 1. Time constraint >>>> 2. The risk of possibly breaking one of the modules during >>>> the re factoring >>>> - However, it must be noted that these modules will need to >>>> be switched to the structure of the Generic Store at some point in >>>> the near >>>> future. >>>> >>>> >>>> *Pending Tasks* >>>> >>>> - Identify main tasks and create redmine issues .*Please note that >>>> the gdoc documenting the task breakdown has been updated *[1]. >>>> - The working repository for the APIM Store integration needs to be >>>> moved to wso2scratch repo.In addition, any changes that are implemented >>>> to >>>> the ES Store must be pushed to the wso2/enterprise-store repo. >>>> - Decide on the approach taken to implement commenting >>>> - Decide on how images and documents will be stored >>>> >>>> *Immediate Goals* >>>> >>>> - Implement the Overview Tab in the API details page >>>> - Implement the Document Tab in the API details page *[Working on >>>> this]* >>>> >>>> Thank You, >>>> Sameera >>>> >>>> >>>> On Thu, Dec 12, 2013 at 12:05 AM, Sameera Medagammaddegedara < >>>> [email protected]> wrote: >>>> >>>>> +1 to a UI similar to the Store >>>>> >>>>> >>>>> On Wed, Dec 11, 2013 at 11:48 PM, Nuwan Bandara <[email protected]>wrote: >>>>> >>>>>> Hi Sameera, >>>>>> >>>>>> Good progress, can you attach the screenshot again. Also @APIM team >>>>>> are we doing a new UI or going stick to the same UI ? am +1 to a new UI, >>>>>> which aligns little bit to the ES look and feel WDYT ? >>>>>> >>>>>> Regards, >>>>>> /Nuwan >>>>>> >>>>>> >>>>>> On Wed, Dec 11, 2013 at 6:43 AM, Sameera Medagammaddegedara < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hello Everyone, >>>>>>> >>>>>>> This is an update on current status of the task as of 11/12/2013 >>>>>>> >>>>>>> *Completed* >>>>>>> >>>>>>> - The API listing page has been integrated >>>>>>> - The basic API detail page has been integrated. >>>>>>> - The customization of this page in order to mirror the APIM >>>>>>> Store has been started. >>>>>>> - All UI customizations will occur by overriding the default >>>>>>> Store theme in the api extensions folder of the Store >>>>>>> (store/extensions/api/theme/store). >>>>>>> >>>>>>> >>>>>>> *Problems faced* >>>>>>> >>>>>>> - The API listing and detail page both perform a life-cycle >>>>>>> state check with a visibleIn parameter defined in the store.json >>>>>>> file. >>>>>>> However, since the API rxt uses the status property instead of the >>>>>>> registry >>>>>>> Life Cycle (LC) , this check fails.In order to integrate these two >>>>>>> pages >>>>>>> the LC check has been disabled (till APIM moves to the Registry LC >>>>>>> model) . >>>>>>> - The tagging feature of the ES does not currently work with the >>>>>>> tags attached using the APIM Publisher. [Working on this] >>>>>>> - The comments section of the APIM details page[2] does not have >>>>>>> an immediate counterpart in the ES Store.The Social app in ES does >>>>>>> not >>>>>>> allow commenting.However, it does provide a User Review feature that >>>>>>> can be >>>>>>> used instead of the commenting.It has been suggested to integrate >>>>>>> the ES >>>>>>> Social app. >>>>>>> >>>>>>> >>>>>>> *Pending Tasks* >>>>>>> >>>>>>> - Identify main tasks and create redmine issues .*Please note >>>>>>> that the gdoc documenting the task breakdown has been updated *[1]. >>>>>>> >>>>>>> - The working repository for the APIM Store integration needs to >>>>>>> be moved to wso2scratch repo.In addition, any changes that are >>>>>>> implemented >>>>>>> to the ES Store must be pushed to the wso2/enterprise-store repo. >>>>>>> >>>>>>> *Immediate Goals* >>>>>>> >>>>>>> - Integrate tagging support >>>>>>> - Implement the Overview Tab in the API details page >>>>>>> - Integrating the Social app to provide commenting features >>>>>>> - Implement the Document Tab in the API details page >>>>>>> >>>>>>> >>>>>>> *References* >>>>>>> [1] ES-> APIM Store Task breakdown, url >>>>>>> https://docs.google.com/a/wso2.com/document/d/1w8kjQ5GLgENC_GVKDiHXU4mT-8MmSCgkqMAeJiVo6O0/edit?usp=sharing >>>>>>> [2] >>>>>>> >>>>>>> Thank You, >>>>>>> Sameera >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Dec 10, 2013 at 7:09 PM, Sameera Medagammaddegedara < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hello Everyone, >>>>>>>> >>>>>>>> This is a small update on the current progress of the task as of >>>>>>>> 10/11/2013: >>>>>>>> >>>>>>>> - The earlier approach of moving the ES Store code to the APIM >>>>>>>> Store has been changed. The new approach involves gradually moving >>>>>>>> the APIM >>>>>>>> Store to the ES Store. This was deemed better as; >>>>>>>> - It would allow changes to the ES to be more easily >>>>>>>> propagated to the APIM Store and Publisher >>>>>>>> - The working git repository has been changed to: >>>>>>>> https://github.com/splinter/apim .The new repo is a copy of the >>>>>>>> Enterprise Store master branch as opposed to the earlier repo which >>>>>>>> merely >>>>>>>> contained the APIM Store and Publisher code.This change is inline >>>>>>>> with the >>>>>>>> previous point. >>>>>>>> - The new Jaggery test framework has been integrated >>>>>>>> - The first task which is been tackled is getting the API >>>>>>>> listing page implemented using the ES Store. [In Progress] >>>>>>>> >>>>>>>> *Problems* >>>>>>>> >>>>>>>> - There is a discrepancy between the storage paths used by the >>>>>>>> ES asset types and those used by the APIM RXTs (api, document and >>>>>>>> provider). The differences are; >>>>>>>> - ES path: >>>>>>>> >>>>>>>> /_system/governance/{ASSET_TYPE}/@{overview_provider}/@{overview_name}/@{overview_version} >>>>>>>> - APIM >>>>>>>> - API path: >>>>>>>> >>>>>>>> /_system/governance/apimgt/applicationdata/provider/@{overview_provider}/@{overview_name}/@{overview_version}/api >>>>>>>> - Document path: >>>>>>>> >>>>>>>> /_system/governance/apimgt/applicationdata/provider/@{overview_apiBasePath}/documentation/@{overview_name} >>>>>>>> - Provider path: >>>>>>>> >>>>>>>> /_system/governance//providers/@{overview_version}/@{overview_name} >>>>>>>> - In order to accommodate APIM paths the ArtifactManager >>>>>>>> (modules/carbon/scripts/artifact.js:line104) will need to be >>>>>>>> changed. >>>>>>>> >>>>>>>> *Notes:* >>>>>>>> >>>>>>>> - Identify main tasks and create redmine issues .A link [1] to >>>>>>>> a gdoc containing a high level breakdown of the tasks is given in >>>>>>>> the >>>>>>>> references section. >>>>>>>> >>>>>>>> *References* >>>>>>>> >>>>>>>> [1] ES-> APIM Store Task breakdown, url >>>>>>>> https://docs.google.com/a/wso2.com/document/d/1w8kjQ5GLgENC_GVKDiHXU4mT-8MmSCgkqMAeJiVo6O0/edit?usp=sharing >>>>>>>> >>>>>>>> Thank You, >>>>>>>> >>>>>>>> Sameera >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Dec 9, 2013 at 6:42 PM, Sameera Medagammaddegedara < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> This is a small update on the current status of the task; >>>>>>>>> >>>>>>>>> - All ES modules have been placed in the ref.modules/ folder >>>>>>>>> in order to provide a cleaner separation between the existing >>>>>>>>> APIM-Store >>>>>>>>> modules and the ES modules. In order to do this I have added a >>>>>>>>> script to >>>>>>>>> resolve paths to modules and scripts (refer: >>>>>>>>> modules/orchestrator/orchestrator.js) .Once we finish moving >>>>>>>>> APIM-Store to >>>>>>>>> ES we can move the ES modules to the modules root. >>>>>>>>> - Added app.js script which contains the initialization code >>>>>>>>> for the store (This involved some re factoring). >>>>>>>>> - Added Caramel and the Store theme from ES. >>>>>>>>> >>>>>>>>> *Note:* >>>>>>>>> >>>>>>>>> - I am planning to add the new Jaggery test framework to the >>>>>>>>> APIM Store app. >>>>>>>>> >>>>>>>>> >>>>>>>>> The working branch in git for task is given below; >>>>>>>>> >>>>>>>>> https://github.com/splinter/apim-apps/tree/add-caramel-configs >>>>>>>>> >>>>>>>>> >>>>>>>>> Thank You, >>>>>>>>> Sameera >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sameera Medagammaddegedara >>>>>>>>> Software Engineer >>>>>>>>> >>>>>>>>> Contact: >>>>>>>>> Email: [email protected] >>>>>>>>> Mobile: + 94 077 255 3005 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Sameera Medagammaddegedara >>>>>>>> Software Engineer >>>>>>>> >>>>>>>> Contact: >>>>>>>> Email: [email protected] >>>>>>>> Mobile: + 94 077 255 3005 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sameera Medagammaddegedara >>>>>>> Software Engineer >>>>>>> >>>>>>> Contact: >>>>>>> Email: [email protected] >>>>>>> Mobile: + 94 077 255 3005 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> >>>>>> >>>>>> *Thanks & Regards,Nuwan Bandara Technical Lead; **WSO2 Inc. * >>>>>> *lean . enterprise . middleware | http://wso2.com <http://wso2.com> * >>>>>> >>>>>> *blog : http://nuwanbando.com <http://nuwanbando.com>; email: >>>>>> [email protected] <[email protected]>; phone: +1 812 606 7390 >>>>>> <%2B1%20812%20606%207390> * >>>>>> <http://www.nuwanbando.com/> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Sameera Medagammaddegedara >>>>> Software Engineer >>>>> >>>>> Contact: >>>>> Email: [email protected] >>>>> Mobile: + 94 077 255 3005 >>>>> >>>> >>>> >>>> >>>> -- >>>> Sameera Medagammaddegedara >>>> Software Engineer >>>> >>>> Contact: >>>> Email: [email protected] >>>> Mobile: + 94 077 255 3005 >>>> >>> >>> >>> >>> -- >>> Sameera Medagammaddegedara >>> Software Engineer >>> >>> Contact: >>> Email: [email protected] >>> Mobile: + 94 077 255 3005 >>> >> >> >> >> -- >> >> >> >> *Thanks & Regards,Nuwan BandaraTechnical Lead; **WSO2 Inc. * >> *lean . enterprise . middleware | http://wso2.com <http://wso2.com> * >> >> *blog : http://nuwanbando.com <http://nuwanbando.com>; email: >> [email protected] <[email protected]>; phone: +1 812 606 7390 >> <%2B1%20812%20606%207390> * >> <http://www.nuwanbando.com/> >> > > > > -- > Sameera Medagammaddegedara > Software Engineer > > Contact: > Email: [email protected] > Mobile: + 94 077 255 3005 > -- Sameera Medagammaddegedara Software Engineer Contact: Email: [email protected] Mobile: + 94 077 255 3005
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
