Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Marten #161

oskardudycz opened this issue Jan 25, 2020 · 1 comment

Marten #161

oskardudycz opened this issue Jan 25, 2020 · 1 comment


Copy link

@oskardudycz oskardudycz commented Jan 25, 2020

1. General Information

Project Name:


Contributor (Company, Organization or individual name(s)):
Jeremy D. Miller, Babu Annamalai, Oskar Dudycz, Joona-Pekka Kokko

Existing OSS Project? (Yes/No):

Source Code URL:

Project Homepage URL (if different):

Project Transfer Signatories:
Full legal name and email address required of the individual(s) with the authority to transfer or contribute the project to the .NET Foundation. Note that if you'd prefer not to include this in the public application, it can be submitted via e-mail to (referencing this issue number).

Jeremy D. Miller
Babu Annamalai
Oskar Dudycz
Joona-Pekka Kokko

2. Description

Please provide a brief statement about your project in terms that are understandable to the target consumer of the library or project, i.e. an elevator pitch for the project:

Marten gives developers a multi-paradigm framework for modelling, storing and querying data on PostgreSQL. Making use of the battle hardened database engine, Marten transparently exposes the JSON(B) capabilities of PostgreSQL for managing objects and events alike, requiring no ceremony to enable friction-less development. Marten is your object (document) and event store, with bells and whistles attached, be it CRUD, Event Sourcing or anything between.

Please provide a 1 sentence (<140 character) summary of your to help users when searching the .NET Foundation projects
Polyglot Persistence providing object (document) and event store Powered by .NET and PostgreSQL

3. Project Governance

Please complete this section about who will be maintaining the open source project and how it will run.
Project Lead:
(Who is the primary contact point for the community and the .NET Foundation when discussing governance of the project.)

Name: Jeremy D. Miller
GitHub Profile URL:


Which individuals have commit / write access to the repository, what is their GitHub ID and who is their employer (if contributions are on behalf of an employer)

Jeremy D. Miller

Babu Annamalai

Oskar Dudycz

Joona-Pekka Kokko

Governance Model:

Please describe how new code changes are proposed to the project, how those changes are reviewed and how a decision is made to accept proposed changes. Also describe the process for identifying and appointing new committers.

Changes are proposed via GH issues. All issues are reviewed and labelled with the proper type and scope. Issues that have the estimated timeline are assigned to a proper milestone. Milestones reflect the package version based on the semantic versioning.
Plans for the new releases are discussed publicly in the issues (see eg. JasperFx/marten#1307 or JasperFx/marten#1391).
Quick surveys, questions, clarifications and in general contact with community is done in dedicated Gitter channel
Normally 2 approves from maintainers are needed to merge the Pull Request.
New committers were appointed once by Jeremy based on the number and quality of commits, activity and helping the community. See more:


If already an OSS project, was a Contribution License Agreement in place for contributions accepted? How does the project check who has signed one?


CLA Notification Alias
Provide an email address that will receive CLA related notifications from the .NET Foundation CLA automation

Project Transfer Type

Projects may join the .NET Foundation in one of two ways and you should chat with your .NET Foundation contact to discuss the best mechanism for your project. You can either a) assign the copyright of the project's source code to the .NET Foundation or b) contribute the project source code to the .NET Foundation under an open source license. Assignment is the preferred approach, but licensing a project to the Foundation may be more appropriate for longer running open source projects that have not previously had a contribution license agreement and have accepted contributions from many different sources.
a) Assignment
b) Contribution


4. Repository Layout

_The .NET Foundation host guidance for new projects and details on recommended structure here:

Note that the open source repository should be the master where changes are made by the core development team using the same PR process that is used for non-committer contributions.

Please define below any changes you would want to make to your repositories as part of the process of joining the .NET Foundation_

I don’t think any repository changes are required as part of this process.

5. PR Plan

Please summarize the public relations plan for the announcement when joining the foundation (and releasing as open source if appropriate). What is the main story we wish to promote, through what channels, what issues should we be aware of? For significant news events then please also work with your .NET Foundation contact to ensure a full PR plan is developed.

Currently we'll promote that through blog post, twitter announcement using twitter handle @marten_lib & updated website We also want to provide the newsletter and maybe more video tutorials. Contributors also speak about the Event Sourcing with .NET Core and Marten on the local meetups. We also plan to get some sponsorship plan (not clear as yet - JasperFx/marten#1393).

6. Infrastructure Requirements

Please describe any infrastructure requirements for the project. For example, how will build servers be operated? Any web hosting or service hosting requirements? Do we need to set up SSL certificates or provide Authenticode Code Signing arrangement for releases?

Currently, we're using the Azure Pipelines and AppVeyor OSS plans and we're happy with that process. We are building our documentation using Storyteller ( hosted on GitHub pages and Netlify so we also don't need to change it as for now. We might need in the future SSL certificates or Authentication Code Signing.

7. Additional Notes

Please provide any additional information required or use this area for notes during the on boarding process. If this open source project has similarities with any other projects in this space then please detail them and why this project is different. If there are any potential issues that you feel the project might need help with early on then also state them here and discuss with your .NET Foundation Contact.

Marten is sometimes compared to Entity Framework. But Marten is not an ORM, it should be treated as the .NET Document and Event Store that's just backed with PostgreSQL. Our approach to using the PostgreSQL and its sophisticated JSON(B) features is unique in .NET space. It should be more compared to RavenDB rather than Entity Framework.
We're working on the sustainability of our model (so getting sponsorship) to be able to work on the dedicated time and get more reliability in bigger Enterprise companies. Such help would be more than welcome from .NET Foundation.


This comment has been minimized.

Copy link

@oskardudycz oskardudycz commented Jan 25, 2020

Wrong repository... 🤦‍♂ dotnet-foundation/projects#47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.