I have a quick question. What is the process if I want to contribute some changes to the cfMesh source-code?
Basically, I would like to make some changes which would allow the use of regular expressions for patch names during the specification of local refinement regions, patch renaming, etc.
Looking into the sources, I think I have a couple of ideas how to implement this while still remaining within the foam-extend framework.
Wishing you a great remaining evening.
Philippose
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your interest in cfMesh. As we only recently started this project, we are still defining how the contribution process will work. We will get back to you on this. In the meantime, you may consider contacting the author of cfMesh directly at franjo.juretic@c-fields.com
Sincerely,
Tomislav Lugarić
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Tomislav,
Thanks a lot for your reply. I have one more question... There is a version of cfMesh within the foam-extend-3.1 git repository. Which version is expected to be kept more up to date? The code base in the cfMesh Sourceforge project, or the code base in the foam-extend-3.1 repository?
I shall contact Franjo directly regarding the code changes.
Regards,
Philippose
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe both of them will mostly be in sync, so you can use either one. The difference is only in the people behind them. The cfMesh SourceForge project is maintained by the Creative Fields team and therefore directly by the author. The version in the foam-extend repo is maintained by the foam-extend team with our input, and is based on the version on SourceForge. Therefore, some updates may get pushed to cfMesh SourceForge a little earlier than to foam-extend. We are working with the foam-extend team to make cfMesh an integral part of future foam-extend releases.
I guess you can view the version in cfMesh project as a bleeding-edge version, and the one in foam-extend repo as one considered stable by the foam-extend team. There won't be many differences regarding key functionalities, as they will be present in both repos.
Just a side note - Franjo is currently out of office, and will be back by next week, so you may have to wait for his response.
Regards
Tomislav
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the delay in answering.
I have added you into our Contributors group. You can now contribute code to our sourceForge repository.
We use the git-flow branching model as described in this article http://nvie.com/posts/a-successful-git-branching-model/. Please follow these guidelines when making commits.
Create your own branch from our development branch, name give it a logical name (e.g. philippose-contribution) and make your additons there. Once you are satisfied with them and have tested it all, you can merge it back into devleopment. Please use --no-ff flag when merging. You do not need to push your individual branches to our repo if you do not wish to do so.
Feel free to contact us for any further questions!
Tomislav
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
A Very good Evening.
I have a quick question. What is the process if I want to contribute some changes to the cfMesh source-code?
Basically, I would like to make some changes which would allow the use of regular expressions for patch names during the specification of local refinement regions, patch renaming, etc.
Looking into the sources, I think I have a couple of ideas how to implement this while still remaining within the foam-extend framework.
Wishing you a great remaining evening.
Philippose
Hello!
Thank you for your interest in cfMesh. As we only recently started this project, we are still defining how the contribution process will work. We will get back to you on this. In the meantime, you may consider contacting the author of cfMesh directly at franjo.juretic@c-fields.com
Sincerely,
Tomislav Lugarić
Hello Tomislav,
Thanks a lot for your reply. I have one more question... There is a version of cfMesh within the foam-extend-3.1 git repository. Which version is expected to be kept more up to date? The code base in the cfMesh Sourceforge project, or the code base in the foam-extend-3.1 repository?
I shall contact Franjo directly regarding the code changes.
Regards,
Philippose
Hello!
I believe both of them will mostly be in sync, so you can use either one. The difference is only in the people behind them. The cfMesh SourceForge project is maintained by the Creative Fields team and therefore directly by the author. The version in the foam-extend repo is maintained by the foam-extend team with our input, and is based on the version on SourceForge. Therefore, some updates may get pushed to cfMesh SourceForge a little earlier than to foam-extend. We are working with the foam-extend team to make cfMesh an integral part of future foam-extend releases.
I guess you can view the version in cfMesh project as a bleeding-edge version, and the one in foam-extend repo as one considered stable by the foam-extend team. There won't be many differences regarding key functionalities, as they will be present in both repos.
Just a side note - Franjo is currently out of office, and will be back by next week, so you may have to wait for his response.
Regards
Tomislav
Hello again!
Sorry for the delay in answering.
I have added you into our Contributors group. You can now contribute code to our sourceForge repository.
We use the git-flow branching model as described in this article http://nvie.com/posts/a-successful-git-branching-model/. Please follow these guidelines when making commits.
Create your own branch from our development branch, name give it a logical name (e.g. philippose-contribution) and make your additons there. Once you are satisfied with them and have tested it all, you can merge it back into devleopment. Please use --no-ff flag when merging. You do not need to push your individual branches to our repo if you do not wish to do so.
Feel free to contact us for any further questions!
Tomislav