Hi, We also had a product review with Paul on the 27th and the points that were discussed are listed below. Dimuthu has already added these to the road map.
*Improvements:* 1. Jenkins should not have security holes - i.e when building an application there should be mechanisms to make sure whether there are no malicious scripts running 2. Usage of OAuth instead of mutual SSL for accessing the admin services 3. Application roles in AF 1.0 enables good use cases for private installations - hence a similar role based concept should be available in aPaaS. (Using tenant roles instead as mentioned in the mail above would be a solution to this) *Features:* 1. Each tenant should be able to link to their own preferred issue tracker 2. There needs to be a graphical way to govern life cycles and bpels 3. There should be a way where user who is trying out aPaaS to be able to sign up easily - possibly without having to create a tenant. (Having a default tenant in the preview which is for all OT account holders as mentioned in the email above would be a solution to this) Thank you, Shiro On Thu, Aug 29, 2013 at 10:22 AM, Shiroshica Kulatilake <sh...@wso2.com>wrote: > Hi, > > We had our 4th mid milestone review yesterday. The review was conducted in > 2 stages. The first being a demonstration of the AF 1.0 version to James > and the second a quick review of work ongoing in milestone 4. Below are the > discussion points that came up during the meeting. > > *AF 1.0 review:* > Features: > 1. Currently the 3rd party systems that we connect to have their own look > and feel - a question was raised whether the same Look and feel (of AF) is > required for the 3rd party eco system products > 2. Linking of the bug tracker to the SCM system - this is a feature which > makes the life of a developer using AF comfortable. A user should be able > to click on the bug and be directed to the relevant file/module in SCM. > 3. When code is checked in to the SCM this should ideally be checked as to > whether the build is not broken and only then should the commit go through. > 4. Debugging facilities within AF > 5. Social features within AF > > Improvements: > 1. AF needs to connect through SSO to all other systems i.e. SCM, Build > system, Issue tracker etc. > 2. In the governance page currently the the promote/demote buttons do not > indicate that once they are clicked an option list would pop-up - check > list of items that need to be done in order to go through with a promote or > a demote should be visible on the page itself. > 3. Branch/Version naming should be anything > > *Mid milestone 4 review:* > 1. There should be a default tenant created for all OT users - this will > allow people who already have an OT account to simply try out aPaaS without > having to create a new tenant. > 2. Though application specific roles have been removed, tenant roles > indicating devs, QA etc should be in place with the necessary permissions. > > > @AF team, please add any missing details if any. > > Thank you, > Shiro > > -- > Shiroshica Kulatilake > > Architect, > WSO2, Inc. http://wso2.com/ > Phone: +94 776523867 > -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
