How best to contribute?

[yalnte]

Hi,

I would like to contribute to this project but don't know how best to get involved. Is there any consensus on what is needed / where to start?

Specific items I think are needed:
FAQs: simple instructions on how to compile; stable version identification; summary of key features; summary of 'missing' features; discussion of how documentation relates to current version; good pre/post processors.

Long term issues: discussion of any licence issues; test problem library; plans for new features...

Are there mechanisms for doing this via Githib without forking to add documentation?

Thanks in advance!

[ldallolio]

Hi, I do not have all the answers but I can provide some of them: - I think that you should fork the project, this is the right way to do this. Forked projects can exchange code, a "main" fork can be identified but actually I do not think that any one has such role at the moment - the original NASA project is, in my opinion, mostly a "commit and forget" contribution - About compiling, You might know that there is an official Debian package, you can find references at the bottom of this page (links are on images) : https://www.aego.ai/community The debian package means that you can easily reproduce the compilation under any debian compatible distribution and probably under any Linux distribution using gfortran. I can provide instructions if you are interested in this kind of environment About other questions (license issue, perspectives etc) I am more than willing to exchange: you can write me personally at luca.dallolio@aego.ai if you wish to do so. Best regards, Luca 2017-12-10 16:08 GMT+01:00 yalnte <notifications@github.com>:

…

Hi, I would like to contribute to this project but don't know how best to get involved. Is there any consensus on what is needed / where to start? Specific items I think are needed: FAQs: simple instructions on how to compile; stable version identification; summary of key features; summary of 'missing' features; discussion of how documentation relates to current version; good pre/post processors. Long term issues: discussion of any licence issues; test problem library; plans for new features... Are there mechanisms for doing this via Githib without forking to add documentation? Thanks in advance! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB4KDTh-4fQhAe2m9oJAKez8Fyy-emTwks5s-_PvgaJpZM4Q8hiL> .

-- If you want things you've never had, you have to do things you've never done.

[yalnte]

Hi Luca,

Thanks - I'll look into these and join in where possible.

Tom