Re: Code Quality Improvements for docker-compose-executor

2016-06-13 Thread Joseph Wu
I'm not sure what the community adoption of the docker-compose-executor [1]
is, but from a Mesos perspective, the repo will eventually be superceded by
"pod" support in Mesos itself [2] [3].

Also, you should try to contact the developers of docker-compose-executor
itself, as they might not be subscribed to this mailing list.

[1] https://github.com/mesos/docker-compose-executor
[2] https://issues.apache.org/jira/browse/MESOS-2449
[3] https://issues.apache.org/jira/browse/MESOS-2634

On Sun, Jun 12, 2016 at 8:38 AM,  wrote:

> Hello,
>
> I'd like to send you some pull requests to improve the maintainability of
> docker-compose-executor.
>
> My company - DevFactory - is sponsoring me to identify and fix code
> quality issues and improve unit test coverage in open source projects.
> DevFactory is obsessed with code quality and is providing its commercially
> available code quality improvement service for free to qualified
> open-source projects.
>
> If you are interested, please let me know and we will add it to our
> pipeline. Our first step will be to utilize tools like PMD, FindBugs and
> Sonar to identify the most important issues to fix. Once we fix them, we'll
> follow up with some pull requests.
>
> Thanks,
> M.Ezzat
>
>


Code Quality Improvements for docker-compose-executor

2016-06-12 Thread mohamed . ezzat
Hello,

I'd like to send you some pull requests to improve the maintainability of 
docker-compose-executor.

My company - DevFactory - is sponsoring me to identify and fix code quality 
issues and improve unit test coverage in open source projects. DevFactory is 
obsessed with code quality and is providing its commercially available code 
quality improvement service for free to qualified open-source projects.

If you are interested, please let me know and we will add it to our pipeline. 
Our first step will be to utilize tools like PMD, FindBugs and Sonar to 
identify the most important issues to fix. Once we fix them, we'll follow up 
with some pull requests.

Thanks,
M.Ezzat