[Dune-devel] Draft for GSoC application

Christian Engwer christian.engwer at uni-muenster.de
Sun Feb 20 17:55:55 CET 2022


Hi Christoph,

thanks for pushing this!

Is there anything you would need from us?

Ciao
Christian

Am Sat, Feb 19, 2022 at 12:18:46AM +0100 schrieb Christoph Grüninger:
> Hi,
> I am still not fully convinced that we have enough mentors and ideas to make
> a good GSoC application. But as I promised, I prepared everything for an
> application. Unfortunately, we have only two days left to apple (deadline
> February 21).
> What do you think?
> 
> Please find attached my answers. If you have any improvements, please share
> them or send me a private mail. I am also locking for a second org admin.
> Who wants to do so?
> 
> Bye
> Christoph
> 
> == Organization Profile ==
> 
> If your organization is accepted into Google Summer of Code all of the
> Profile information on this page will be publicly visible on the program
> site.
> 
> Website URL for Organization
> "https://dune-project.org"
> 
> Logo Preview: dune-logo6.png
> 
> 
> Tagline
> Describe the organization's mission. This is often the only thing a
> participant will read about your org, be sure to make it clear and concise.
> 50 characters maximum.
> "C++ lib for solving PDEs with grid-based methods"
> 
> Primary Open Source License
> "GNU General Public License version 2 (GPL-2.0)"
> 
> What year was your project started?
> "2002"
> 
> Link to your source code location
> https://gitlab.dune-project.org/
> 
> Organization Categories
> Select which categories fit your organization best. You may select up to 2
> categories. This helps GSoC contributors filter the large list of
> organizations by their interests.
> 
> [ ] Data (databases, analytics, visualization, AI/ML, etc)
> [ ] Development tools (version control systems, CICD tools, text editors,
> issue managers, q/a tools, etc)
> [ ] End user applications
> [ ] Infrastructure and cloud (hardware, software defined infrastructure,
> cloud native tooling, orchestration and automation, etc)
> [ ] Media (graphics, video, audio, VR, streaming, gaming, content
> management, etc)
> [ ] Operating systems
> [ ] Programming languages (libraries, package managers, testing tools, etc)
> [x] Science and medicine (healthcare, biotech, life sciences, academic
> research, etc)
> [ ] Security (tools and frameworks)
> [ ] Social and communications (Blog, chat, forums, wikis, etc)
> [ ] Web (tools and frameworks)
> [ ] Other
> 
> Organization Technologies
> Enter up to 5 keywords for the primary specific technologies your
> organization uses. Examples: Python, Javascript, MySQL, Hadoop, OpenGL,
> Arduino
> 
> [c++]
> [templates]
> [python]
> [cmake]
> 
> Organization Topics
> Enter keywords for general topics that describe your organization. Examples:
> Robotics, Cloud, Graphics, Web, etc. Select up to 5.
> 
> [Numerics]
> [scientific computing]
> [hpc]
> [Grid manager]
> [FEM]
> 
> Organization Description
> Describe what it is your organization does. This information will also be
> included in the archive once the program has ended.
> 
> "DUNE, the Distributed and Unified Numerics Environment is a modular toolbox
> for solving partial differential equations (PDEs) with grid-based methods.
> It supports the easy implementation of methods like Finite Elements (FE),
> Finite Volumes (FV), and also Finite Differences (FD).
> 
> The underlying idea of DUNE is to create slim interfaces allowing an
> efficient use of legacy and/or new libraries. Modern C++ programming
> techniques enable very different implementations of the same concept using a
> common interface at a very low overhead. Thus DUNE ensures efficiency in
> scientific computations and supports high-performance computing
> applications."
> 
> Contributor Guidance
> Provide your potential contributors with a page containing tips on how to
> write a successful proposal for your organization. Let them know what you
> want included, how you want it structured, and how to best get in touch.
> Examples.
> 
> Link for contributor guidance (Wiki, blog, et cetera)
> "https://dune-project.org/dev/gsoc/"
> 
> 
> Communication Methods
> How do you want potential contributors to interact with your organization?
> Select methods that your community uses daily as you will receive many
> inquiries if your org is selected.
> 
> 
> "Mailing List / Forum": "dune-devel at lists.dune-project.org"
> "Mailing List / Forum": "https://gitlab.dune-project.org/"
> 
> 
> == Organization Questionnaire ==
> 
> Please be thorough in your answers. All fields are required, unless noted
> otherwise.
> 
> = Why does your organization want to participate in Google Summer of Code?=
> "
> * Teach people that are skilled and willing how to contribute to open
> source. We public share our code and work as a community for almost 20
> years. Introducing more people into this world is marvelous.
> 
> * Being caught in everyday live, it becomes difficult to start new features,
> try new ideas, or break with old habits. Having a GSoC project leads to a
> joint effort around the student working on the topic. Our 2016 GSoC project
> was the nucleus to our Python bindings as we have them today.
> 
> * Being part of GSoC increases our visibility within the programming
> community, might interest new users, and might attract bright students to
> graduate with our software."
> 
> 
> = What would your organization consider to be a successful GSoC program?=
> "
> * Be selected as one of the GSoC 2022 organizations.
> 
> * During bonding phase, to have a handful of interested students which show
> some effort to learn about our code base.
> 
> * Have at least one promising application from a student we believe in.
> 
> * The cherry on the cake would be a successful GSoC, with a happy student,
> happy mentors, and a future feature we can include. But having the first
> three points would be enough to consider it a successful GSoC program."
> 
> =How will you keep mentors engaged with their GSoC contributors?=
> "
> * Having regular meeting.
> 
> * Answering their email that should be sent at least in a to be defined
> frequency.
> 
> * Have regular video calls to bound and build up trust.
> 
> * As many of our project members work as faculty in universities, we are
> used to keep engaged with our mentees."
> 
> =How will you keep your GSoC contributors on schedule to complete their
> projects?=
> "
> If we see they
> * take the wrong routes,
> * that their original has a flaw, o
> * that they are just behind schedule,
> we have to ask them
> * whether they need more or more specific help,
> * to adjust their approach,
> * to discuss with us,
> * or simply to improve their effort (if we feel that lack of effort is a
> reason)."
> 
> =How will you get your GSoC contributors involved in your community during
> GSoC?=
> "
> * Encourage them to take part in discussions related and unrelated to their
> project.
> * Not only mentors will provide feedback and answer questions on the mailing
> list or GitLab discussions.
> * If possible, merge parts of the project as early as possible.
> * Invite GSoC contributors to project activities like developer or user
> meetings, if they happen during the GSoC time.
> * Some project might lead to a scientific publication, and the GSoC
> contribution would become one of the authors."
> 
> =Anything else we should know? (Optional)=
> ""
> 
> =Is your organization part of any government?=
> [ ] Yes
> [x] No
> 
> _______________________________________________
> Dune-devel mailing list
> Dune-devel at lists.dune-project.org
> https://lists.dune-project.org/mailman/listinfo/dune-devel

-- 
Prof. Dr. Christian Engwer 
Institut für Numerische und Angewandte Mathematik
Fachbereich Mathematik und Informatik der Universität Münster
Einsteinstrasse 62
48149 Münster

E-Mail  christian.engwer at uni-muenster.de
Telefon +49 251 83-35067
FAX     +49 251 83-32729



More information about the Dune-devel mailing list