|
|
# ExaHyPE Wiki
|
|
|
|
|
|
## Resources and technical infrastructure
|
|
|
The different systems we operate can be found at the [infrastructure](infrastructure) page. The wiki page [git branches](git branches) explains how we use git.
|
|
|
|
|
|
## Work in progress and ToDos
|
|
|
- The issues give us a good overview, who is working on what at the moment. Every developer of the ExaHyPE team should track his progress [in the issues](https://gitlab.lrz.de/gi26det/ExaHyPE/issues?label_name[]=workInProgress).
|
|
|
This is the wiki associated with the [ExaHyPE gitlab project at LRZ](https://gitlab.lrz.de/gi26det/ExaHyPE). It consists of pages written in the [Gitlab flavoured Markdown format](https://github.com/gitlabhq/gitlabhq/blob/master/doc/user/markdown.md) and can be offline [accessed and edited as a git repository](https://gitlab.lrz.de/gi26det/ExaHyPE/wikis/git_access). See the [page index](https://gitlab.lrz.de/gi26det/ExaHyPE/wikis/pages) for a list of all available pages.
|
|
|
|
|
|
- The open ToDos can be found [at the issue list](https://gitlab.lrz.de/gi26det/ExaHyPE/issues)
|
|
|
## Resources and technical infrastructure
|
|
|
- The different systems we operate can be found at the [infrastructure](infrastructure) page.
|
|
|
- The wiki page [git branches](git branches) explains how we use git.
|
|
|
- There is an extensive tutorial how to do the [Eclipse import](Eclipse import) in order to use the powerful IDE.
|
|
|
- There is a guide how to get (supermuc internet access)[supermuc internet access] e.g. in order to clone the ExaHyPE code repository at [SuperMUC](https://www.lrz.de/services/compute/supermuc/)
|
|
|
|
|
|
## Coding days / Communication
|
|
|
Information can be found at wiki page [Codingdays](Codingdays).
|
|
|
## Communication
|
|
|
- There are annual or biannual long meetings where all developers come together at one place, called **coding days**. Documentation about these meetings is at the wiki page [Codingdays](Codingdays).
|
|
|
- We do a weekly developer meeting using [Google hangouts](http://askubuntu.com/questions/261369/desktop-client-for-google-and-hangout), called **Jour Fixe**. All jour fixes are documented in the wiki by Vasco with both a prepraratory agenda as well as minutes after the meeting.
|
|
|
- Don't forget to subscribe the [mailing list](https://lists.lrz.de/mailman/listinfo/exahype). The [list archives](https://lists.lrz.de/mailman/private/exahype/) are a comprehensive documentation of problems and their solutions.
|
|
|
|
|
|
The next [jourfixe](jourfixe) takes place at **Wednesday, 10:00 CEST** (== 9:00 @DUR) at **August 31**.
|
|
|
|
|
|
## Jour fixe
|
|
|
The next [jourfixe](jourfixe) takes place at **Wednesday, 10:00** (== 9:00 @DUR) at **August 24**.
|
|
|
## Further reference for the Gitlab
|
|
|
The following links contain further references in the gitlab which are beyond the code:
|
|
|
|
|
|
## Wiki documentation
|
|
|
The documentation for using the markdown format of this wiki can be found at http://doc.gitlab.com/ce/markdown/markdown.html |
|
|
- The issues give us a good overview, who is working on what at the moment. Every developer of the ExaHyPE team should track his progress [in the issues](https://gitlab.lrz.de/gi26det/ExaHyPE/issues?label_name[]=workInProgress).
|
|
|
- The open ToDos can be found [at the issue list](https://gitlab.lrz.de/gi26det/ExaHyPE/issues) |
|
|
\ No newline at end of file |