[
https://issues.apache.org/jira/browse/JAMES-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907790#comment-15907790
]
Pramod Dilshan commented on JAMES-1931:
---------------------------------------
Hi [~BTellier]
Thank You for the answer. And Please suggest me what I have to do next? Is it
good if try to fix some issues that mentioned here
(https://issues.apache.org/jira/browse/JAMES-1537?jql=project%20%3D%20JAMES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC)
to familiar with code base before starting GSOC? Or are there any other
helpful things that I can do After configuring James Server and before GSOC
2017 Student application period opens.
Thanks
Pramod Dilshan
> Implement a web ui for James administration
> -------------------------------------------
>
> Key: JAMES-1931
> URL: https://issues.apache.org/jira/browse/JAMES-1931
> Project: James Server
> Issue Type: Task
> Reporter: Matthieu Baechler
> Labels: backend, frontend, gsoc2017, java, js, json, rest, sse
>
> James today provides a command line tool to do administration tasks like
> creating a domain, listing users, setting quota, etc.
> It requires access to JMX port and even if lot of admins are confortable with
> such tools, to make our user base broader, we probably should expose the same
> commands in Rest and provide a fancy default web ui.
> The task would need some basic skills on frontend tools to design an
> administration board, knowledge on what REST mean and enough Java
> understanding to add commands to existing Rest backend.
> In the team, we have a strong focus on test (who want a mail server that is
> not tested enough ?) so we will explain and/or teach the student how to have
> the right test coverage of the features using modern tools like Cucumber,
> Selenium, rest-assured, etc.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
