Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

 


Proposal 1: Native inbound and connector for IBM MQ 8.0

Description

Currently with WSO2 Enterprise Service Bus recommended way to connect to IBM MQ is using JMS transport. But this has limitations and sometimes gives issues when integrating. 

Iidentifying lmitations and provide a better solution is part of this project.

Deliverables 

  • Custom inbound endpoint as consumer.
  • Connector as producer.

Skills Needed

  • JMS Transport
  • Message brokers
  • Java

References

[1] JMS Inbound Protocol

[2] Configure with IBM WebSphere MQ

[3http://mrmalakasilva.blogspot.com/2013/10/connecting-mechanisms-other-than.html

[4] Creating a Third Party Connector and Publishing in WSO2 Connector Store

Possible Mentor/s

Malaka Silva, Kevin Ratnasekera


Proposal 2: Native inbound and connector for FTP/SFTP operations 

Description

Currently with WSO2 Enterprise Service Bus recommended way to connect to file systems is using VFS transport. This uses common-vfs library internally. But this has limitations and sometimes gives issues when integrating. 

Objective of this project should be to optimise and provide more options in addition to the current operations to support mainly FTP/SFTP.

Identifying limitations and provide a better solution is part of this project.

Deliverables

  • Custom inbound endpoint as listener.
  • Connector as sender/writer.

Skills Needed

  • VFS Transport
  • File Systems
  • Java/NIO

References

[1] File Inbound Protocol

[2] NIO based local file connector

[3] Creating a Third Party Connector and Publishing in WSO2 Connector Store

Possible Mentor/s

Malaka Silva, Kevin Ratnasekera


Proposal 3: Implementing AccountChooser support for WSO2 IS

Description

AccountChooser is a facility where users can store basic identifying information for accounts that they use for signing in to Web sites (Sites). Once stored, users are able to use the AccountChooser user interface to transmit simple account hint information such as email addresses or federated issuer identifiers to sites rather than typing that information manually into login or signup forms. The OpenID AccountChooser working group is currently developing two separate specifications:OpenID AccountChooser Basic API Profile 1.0 and OpenID AccountChooser Advanced Specification. The objective of this project is to integrate AccountChooser support for WSO2 Identity Server. This would give the user experience that a given user can login to multiple service providers with different accounts from WSO2 IS - in the same browser session.

Deliverables

  • AccountChooser implementation for WSO2 IS.

Skills Needed

  • Java
  • Basic understanding about Identity protocols like SAML, OpenID Connect

References

[1]  OpenID AccountChooser Advanced Specification

[2] OpenID AccountChooser Basic API Profile 1.0

[3] OpenID AccountChooser Working Group

[4] OpenID AccountChooser API

Possible Mentor/s

Prabath Siriwardena


Proposal 4: Siddhi Extension Doc Auto Generation

Description

From Siddhi 4.0, Siddhi[4] extension[1] classes are annotated with documentation information. We need an approach to auto-generate HTML documentation when building the Siddhi extensions, like something similar to Java Docs[3]. 

Deliverables 

  • Searching through all Siddhi classes and generating HTML documentation

  • Create a maven plugin[2] to generate HTML docs for a single extension module

  • Way to combine multiple doc files to a combined documentation.

Skills Needed 

  • HTML, JavaScript and CSS to generate the documentation HTML

  • Java 

  • Maven

References

[1] Siddhi Extension

[2] https://maven.apache.org/guides/plugin/guide-java-plugin-development.html

[3] https://docs.oracle.com/javase/8/docs/api/java/lang/Object.html

[4] https://github.com/wso2/siddhi

Possible Mentor/s

Suho, Nirmal


Proposal 5: Idea Plugin for Siddhi 

Description

Build a JetBrains IntelliJ IDEA Plugin[1] for Siddhi[2] with syntax highlighting, code completion, error reporting and if time permits support for running Siddhi and debugging support. 

Deliverables 

  • Idea plugin to with syntax highlighting, code completion and error reporting

  • Running Siddhi in Idea

  • Debugging Siddhi in Idea

Skills Needed 

  • JetBrains IntelliJ IDEA Plugin development

  • Java 

References

[1] http://www.jetbrains.org/intellij/sdk/docs/basics/getting_started.html

[2] https://github.com/wso2/siddhi

Possible Mentor/s

Suho, Tishan


Proposal 6: Eclipse Plugin for Siddhi 

Description

Build an Eclipse Plugin[1] for Siddhi[2] with syntax highlighting, code completion, error reporting and if time permits support for running Siddhi and debugging support. 

Deliverables 

  • Eclipse plugin to with syntax highlighting, code completion and error reporting

  • Running Siddhi in Idea

  • Debugging Siddhi in Idea

Skills Needed 

  • Eclipse Plugin development

  • Java 

References

[1] https://www.eclipse.org/articles/Article-Your%20First%20Plug-in/YourFirstPlugin.html

[2] https://github.com/wso2/siddhi

Possible Mentor/s

Suho, Nirmal


Proposal 7: Atom Plugin for Siddhi 

Description

Build an Atom Plugin[1] for Siddhi[2] with syntax highlighting, code completion, error reporting. 

Deliverables 

  • Atom plugin to with syntax highlighting, code completion and error reporting

Skills Needed 

  • Atom Plugin development

  • JavaScript 

References

[1] https://github.com/blog/2231-building-your-first-atom-plugin

[2] https://github.com/wso2/siddhi

Possible Mentor/s

Suho, Ramindu


Proposal 8: Environments Support for WSO2 API Manager

Description

Currently the WSO2 API Manager user interfaces don't have a mechanism of switching between different environments such as Dev/QA/Staging. This project is for building capability in the user interfaces of WSO2 API Manager version 3.0.0 (SNAPSHOT version as of now) to switch between different environments for performing user operations. The user interface, at a given time will connect to one environment and will have the capability to switch to any other while seamless transferring the user session.

Deliverables

  • The completed user interface for the API Store.
  • Documentation on how to setup the environments.

Skills Needed

  • HTML, CSS, Javascript
  • Handlebars.js
  • Fair knowledge on using REST services

References

[1] http://wso2.com/products/api-manager/

[2] https://github.com/wso2/carbon-apimgt/tree/C5

[3] https://github.com/wso2/product-apim/tree/C5

Possible Mentor/s

Nuwan Dias, Thilini Shanika, Kasun Tennakon


Proposal 9: CLI tool for WSO2 API Manager

Description

This project is about developing a CLI tool for the WSO2 API Manager which is capable of performing the following operations.

1. Exporting a given API from one environment and Importing to another
2. API Creation / Publishing
3. API Subscription
4. Key Generation

Deliverables

  • CLI tool

  • Documentation on how to run the CLI and it's functionality

Skills Needed

  • Go
  • Fair knowledge on using REST services

References

[1] https://golang.org/

[2] http://wso2.com/products/api-manager/

[3] https://github.com/wso2/carbon-apimgt/tree/C5

[4] https://github.com/wso2/product-apim/tree/C5

[5] Migrating the APIs to a Different Environment

Possible Mentor/s

Nuwan Dias, Pubudu Gunatilaka, Sajith Kariyawasam

 


 

Proposal 10: API Tooling: Support Deploying an API

 

Description

WSO2 API Manager version 3.0.0 (SNAPSHOT version) comes with an editor which enables users to design their APIs offline and later push to the server. This project is for having a capability on the editor user interface itself to be able to push an API to the server. When a particular user performs the "Deploy" action, the editor should prompt the user for his credentials, logon on behalf of the user to the server and then do the deployment operation.

Deliverables

  • The enhanced editor user interface

Skills Needed

  • HTML, CSS, Javascript
  • Handlebars.js
  • Fair knowledge on using REST services

References

[1] http://wso2.com/products/api-manager/

[2] https://github.com/wso2/carbon-apimgt/tree/C5

[3] https://github.com/wso2/product-apim/tree/C5

Possible Mentor/s

Nuwan Dias, Thilini Shanika, Kasun Tennakon, Harsha Kumara

 

 


 


 

Proposal 11: Video Scene Detection with WSO2 CEP

 

Description

This project proposes implementation of video scene detection system based on WSO2 Complex Event Processor (CEP). It will consist of a tracking module as well as scene identification module. The project will be carried out in an iterative manner where an initial prototype will be developed in 4 weeks and the prototype will be refined in the latter half of the project.

 

Deliverables

  • Video scene detection system
  • Documentation on the system architecture, algorithms, performance tuning, etc.
  • User guide

 

Skills Needed

  • Familiarity with Image/Video processing
  • Programming with Java and C
  • Knowledge on WSO2 CEP

 

References

[1] http://wso2.com/products/complex-event-processor/
 

 

Possible Mentor/s

Anusha Jayasundara, Miyuru Dayarathna

 


 

Proposal 12: Grouping APIs into Packages

 

Description

 

The WSO2 API Manager allows an API Developer to create and publish an API. This API can be consumed by Application Developers. This project is about introducing a capability for API publishers to group APIs into API packages so that Application developers can subscribe to all APIs in the package in one go.

 

Deliverables

 

  • The relevant product API that allow grouping APIs into a package.
  • The relevant product API that allows subscribing to the API package.
  • The product user interfaces for packaging and subscribing.

 

Skills Needed

 

  • Java8
  • Maven
  • Fair knowledge on using REST services
  • HTML, CSS, Javascript
  • Handlebars.js

 

References

 

[1] http://wso2.com/products/api-manager/

 

[2] https://github.com/wso2/carbon-apimgt/tree/C5

 

[3] https://github.com/wso2/product-apim/tree/C5

 

Possible Mentors

 

Nuwan Dias, Sanjeewa Malalgoda

 


 

Proposal 13: User Managed Access based Device Sharing

 

Description

 WSO2 IoT Server currently provides support for device grouping and sharing. However, the implementation does not support UMA. UMA is quickly gaining popularity as a lightweight access control protocol that is built around OAuth2.0. A draft of UMA has been implemented in WSO2 Identity Server.

 

Deliverables

  • Share statistics and control of devices managed by IOT Server using UMA.
  • Apply same functionality for device groups

 

Skills Needed

  • Java 8
  • Maven
  • Familiarity with OAuth2 and Access Control Protocols
  • HTML, CSS, Javascript and Handlebars

 

References

[1] https://docs.kantarainitiative.org/uma/rec-uma-core-v1_0.html

[2] https://github.com/wso2/carbon-device-mgt

[3] https://github.com/wso2/carbon-device-mgt-plugins

[4] https://github.com/wso2/product-iots

 

Possible Mentor/s

 Sumedha Rubasinghe, Ruwan Yatawara, Geeth Munasinghe



  

Proposal X: <Enter title here>

 

Description

 

<text>

 

Deliverables

 

  • <text>
  • <text>

 

Skills Needed

 

  • <text>
  • <text>

 

References

 

[1] <link>

 

Possible Mentor/s

 

<text>


Save

  • No labels