Michael T. Pope
2016-12-24 01:36:47 UTC
Subject Subscribing to the developer list
From Frode Pedersen
Date 2016-06-09 23:36
Welcome, and hopefully you are not discouraged by the mail stuff up.From Frode Pedersen
Date 2016-06-09 23:36
Getting started as a FreeCol contributor is summarized at
http://www.freecol.org/how-to-contribute.html. Most of the project
infrastructure lives at the sourceforge site
https://sourceforge.net/projects/freecol/. Once you have checked
out the source there is more developer documentation in the doc/
directory.
We usually encourage new contributors to start small, working on some
fairly self-contained bug or feature. If you wish to work on a
particular open bug or feature, please leave a comment on the report
saying so. Patches can be sent to the freecol-developers mailing list,
or now you can use a sourceforge pull request. Full write access to
the git repo is typically offered after <small-number> of useful patches.
I have used java 8 rather extensively, as it is the main language used
at my university (I am particularly having fun with the features java 8
brought with it).The most recent project I have been a part of was a
distributed text editor, where we had to communicate within a network,
solving concurrency issues while securing consistency among peers.
Agreed that Java 8 was a step up. FreeCol switched to requiring Java 8at my university (I am particularly having fun with the features java 8
brought with it).The most recent project I have been a part of was a
distributed text editor, where we had to communicate within a network,
solving concurrency issues while securing consistency among peers.
fairly recently so there are probably quite a few places where the codebase
could be simplified with Java 8 features. Note though, simplification is
the aim --- I like lambdas, but there are a few places where I can see I
could use a lambda, but did not do so because it did not significantly
improve things.
FreeCol should be in pretty good shape with respect to consistency. It is
strictly client-server, with clients waiting for the server to respond.
However it is by no means perfect, and I am trying to migrate the c-s
comms away from using DOM, which is likely to be introducing bugs in the
new code.
I will also be applying a TDD approach to what I implement, as I love
the idea of automated testing.
We have a test suite, but as you might expect, coverage is spotty. Morethe idea of automated testing.
help there would be most welcome.
Cheers,
Mike Pope