Kim,
For posterity, please include the main developer mailing list in all
non-sensitive discussions.
Generally speaking new contributors are required to fork the FreeCol
repository and submit a pull request or even a patch via the SourceForge UI.
The developer guide LaTeX file is available at https://sourceforge.net/p/
freecol/git/ci/master/tree/doc/developer.tex though I don't know if there a
PDF available of the most current version. You may need to create the PDF.
Once established, users are often given read/write access by a project
administrator, most likely Mike Pope. I would assume that all of your
students are going to sign up for an SF account so that `git blame` works
properly.
Hopefully Mike will chime in if he has a better way to manage a new group
of contributors. My opinion is that the more help, the better. The more
sets of eyes, the more potential fixes can be added to the code base.
Thanks,
- Caleb
On Nov 23, 2016 7:10 PM, "Dong Kim" wrote:
> Hi Caleb,
>
> Yes I received it, thanks a lot! Also I have another question- how do we
> push changes or make pull requests?
>
> On Wed, Nov 23, 2016 at 3:57 PM, Caleb Williams wrote:
>
>> Kim,
>>
>> Did you see that we responded via the mailing list to your question?
>>
>> Caleb Williams, on behalf of FreeCol
>>
>> On Nov 22, 2016 3:17 PM, "Dong Kim" wrote:
>>
>>> Hello FreeCol developers,
>>>
>>> My team and I are working on contributing to an open source project as
>>> part of our class, and we wanted to claim tickets #43 and #199 for
>>> Improvement Requests:
>>>
>>> #199 Hotkey for move all goods: https://sourceforge.net/p/free
>>> col/improvement-requests/199/
>>> #43 Display selling price when trading:
>>> https://sourceforge.net/p/freecol/improvement-requests/43/
>>>
>>> In addition, we had a few questions regarding ticket #43- which are
>>> the relevant GUI elements that need EU pricing details on goods displayed?
>>> We've encountered just the trade windows with the natives so far, and were
>>> wondering how many other panels/dialogues we'd be working with, and if
>>> there are any specific classes we should be looking at.
>>>
>>> Please let us know at your earliest convenience. Thank you!
>>>
>>
--
___
Freecol-developers mailing list
Freecol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freecol-developers
