<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Dear Dune,<div><br></div><div>I think Steffen’s argument is perfectly valid. Therefore, I have created an account on github,</div><div>forded dune-grid and dune-geometry and assigned the respective upstream links.</div><div>We will now start to work into these repo’s from the next week on.</div><div><br></div><div>We very much look forward to this endeavour!</div><div><br></div><div>Greetings and thanks for the support, Benedikt</div><div><br></div><div><br></div><div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">--------------------------------------------------------------------------------------------------------------------------------------------------------------<br>Dr. sc. techn. Benedikt Oswald - first engineer - LSPR AG - phone - +41 43 366 90 74<br>Technoparkstrasse 1, CH-8005 Zürich, <a href="mailto:benedikt.oswald@lspr.ch">benedikt.oswald@lspr.ch</a> - 'Ambition is a dream with a V8 engine', The KING<br>--------------------------------------------------------------------------------------------------------------------------------------------------------------</div></div></div>
</div>
<br><div><div>On 23 Jan 2014, at 19:57, Steffen Müthing <<a href="mailto:steffen.muething@iwr.uni-heidelberg.de">steffen.muething@iwr.uni-heidelberg.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Sorry for the empty post, my mail client is confused…<br><br>If the idea is to create an integrated solution, I think the idea Markus<br>brought up is probably the easiest solution: Just fork dune-{geometry,grid}<br>on GitHub and use those as a publicly visible repositories. Then you can<br>periodically merge in the upstream changes from our repositories and once<br>the new implementation works, we can just merge it back like any feature<br>branch. That way, if you are stuck and need help by a developer, we can just<br>check out those repositories and take a look (or simply browse them on the<br>GitHub site). That’s much easier than keeping the stuff on your local machines<br>and then having to send patches and stuff….<br><br>Pulling in the upstream changes is almost no work, I do it regularly for the<br>EXADUNE repositories. Last time Git forced me to resolve conflicts in less than<br>ten files for all core modules + PDELab, and the changes in those repositories<br>are much more intrusive than extending GeometryGrid and adding a new<br>Geometry implementation.<br><br>Just my 2c<br><br>Steffen<br><br>Am 23.01.2014 um 12:29 schrieb Christian Engwer <<a href="mailto:christian.engwer@uni-muenster.de">christian.engwer@uni-muenster.de</a>>:<br><br><blockquote type="cite">On Thu, Jan 23, 2014 at 10:08:00AM +0000, Andreas Dedner wrote:<br><blockquote type="cite">So you are suggestion a branch of dune-grid?<br></blockquote><br>Not necessarily, actually I think a fork of GeometryGrid is better, as<br>it allows to keep the current dune-grid. But I don't think that we<br>want to (on the long run) to maintain two seperate grids which share<br>most of their code, but we should try to merge them again.<br><br>Christian<br><br><blockquote type="cite"><br><br>Dear all, while forking for the development is surely a good thing, why<br>would we want to rename this thing again. Basically the two<br>implementations will (hopefully) only differ in the choice of the<br>geometry implementation. I think we should try to share as much cde as<br>possible and thus try to merge the functionality into GeometryGrid,<br>,,all'' that needs to be done is to provide a more general way of<br>specifying the transformation and storing its data. my 5 cents Christian<br><br></blockquote><br>-- <br>Prof. Dr. Christian Engwer <br>Institut für Numerische und Angewandte Mathematik<br>Fachbereich Mathematik und Informatik der Universität Münster<br>Einsteinstrasse 62<br>48149 Münster<br><br>E-Mail<span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:christian.engwer@uni-muenster.de">christian.engwer@uni-muenster.de</a><br>Telefon<span class="Apple-tab-span" style="white-space:pre"> </span>+49 251 83-35067<br>FAX<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span>+49 251 83-32729<br><br>_______________________________________________<br>Dune mailing list<br>Dune@dune-project.org<br>http://lists.dune-project.org/mailman/listinfo/dune<br><br></blockquote><br>_______________________________________________<br>Dune mailing list<br><a href="mailto:Dune@dune-project.org">Dune@dune-project.org</a><br>http://lists.dune-project.org/mailman/listinfo/dune<br></blockquote></div><br></div></body></html>