Melville.Pdf

[DrJohnMelville]

1.   General Information

Project Name: Melville.PDF

License: MIT

Contributor (Company, Organization or individual name(s)): John Melville, MS, MD

Existing OSS Project? (Yes/No): NO

Source Code URL: https://github.com/DrJohnMelville/Pdf

Project Homepage URL (if different): https://github.com/DrJohnMelville/Pdf

Project Transfer Signatories: John Donald Melville -- JohnMelville@gmail.com 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 contact@dotnetfoundation.org (referencing this issue number).

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:

Melville.PDF is a .NET PDF render. The project renders PDF documents to WPF or SkiaSharp using minimal external dependencies, a;; of which have liberal open source licenses.

Please provide a 1 sentence (<140 character) summary of your project to help users when searching the .NET Foundation projects .NET PDF rendering library

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: John Melville Email: JohnMelville@gmail.com GitHub Profile URL: https://github.com/DrJohnMelville

Committers:

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) John Melville -- Github ID DrJohnMelville

Governance Model: Right now I am the only contributor so right now I just do what I want. I presume that in the early days of this project simple consensus among a small number of comitters is a reasonable governance model. I do not currently have ambitions to outgrow the need for simple governance.

CLA I am the only contributor at this point.

CLA Notification Alias johnmelville@gmail.com

Assignment Model. I am ok with assignment and grantback license.

4.   Repository Layout

The .NET Foundation host guidance for new projects and details on recommended structure here: https://github.com/dotnet/home/tree/master/guidance

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 would be happy to make the required changes to conform to the .NET Foundation requirements. I would need to rename the Docs folder to Documentation. I would need to add .gitattributes, NOTICE.MD, and CONTRIBUTING.md files and am willing to do so.

5. Eligibility Criteria

Please complete the following for your project

• The project is built on the .NET platform and/or creates value within the .NET ecosystem.
• [X ] Yes
• [ ] No
• The project produces source code for distribution to the public at no charge.
• [ X] Yes
• [ ] No
• The project's code is easily discoverable and publicly accessible (preferably on GitHub).
• [ X] Yes
• [ ] No
• The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
• [ X] Yes
• [ ] No The project does not contain a build script per say -- but it does contain a VS solution file that builds the entire project from DotNet build command. If you need be to add a batch file that calls dotnet build I am willing to do so.
• When applicable, project must use reproducible build settings in its toolchain.
• [ X] Yes
• [ ] No
• The project uses Source Link.
• [ ] Yes
• [ ] No I am willing to use source link -- I just need a chance to figure this out/
• The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
• [ ] Yes
• [ ] No Am willing to do so -- just need to figure it out.
• The project code signs their artifacts as appropriate.
• [X ] Yes
• [ ] No Signing is not needed for this project.
• The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
• [ X] Yes
• [ ] No
• Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
• [ X] Yes
• [ ] No
• Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
• [ X] Yes
• [ ] No
• The copyright ownership of everything that the project produces is clearly defined and documented.
• [ X] Yes
• [ ] No
• The project has a public issue tracker where the status of any defect can be easily obtained.
• [ X] Yes
• [ ] No
• The project has a published Security Policy.
• [ ] Yes
• [ ] No Willing to write one -- right now I am the only committer and my email is available
• The project has a home page which provides high level information about its status and purpose.
• [X ] Yes
• [ ] No
• The project has a public communication channel where community members can engage with maintainers.
• [ X] Yes
• [ ] No
• The project has a publicly available location where members can review and contribute to documentation.
• [ X] Yes
• [ ] No

6.   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.

I am hoping that membership in the .NET foundation will help improve the visibility of the project. I do not have a specific PR plan.

7.   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?

None right now.

8.   Additional Notes

Please provide any additional information required or use this area for notes during the onboarding 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.

See the readme file on github.

[sbwalker]

The Project Committee Charter (https://github.com/dotnet-foundation/projects) contains activity criteria which is used to evaluate project applications. This project does not currently exhibit activity or adoption metrics at a level which would allow for an application approval- however based on the broad applicability and high commit totals, it will be included in the Seed category for consideration as a Member project in the future.

[sbwalker]

It will also be important to provide details around the open source dependencies - including the licensing for each dependency.

[DrJohnMelville]

Thank you for reviewing this application. I recognize the unacceptable risk of adopting a project with no current users, and am grateful to be offered a place in the seed category.

I fear that I am much better at programming than marketing. My efforts to reply even to very on topic questions online -- questions like "Is there a free library to render PDF in .NET" -- have been rejected as spam. I tried writing some online articles about my project, and no one is reading them. (It is quite demoralizing to be unable to give away what others are selling!) If there were any suggestions or resources that you could provide on how small open-source projects get noticed and adopted, I would be very appreciative.

All of the open source dependencies (all 4 of them) are listed in the Readme.MD file under "Who else contributed." I just added information about the licenses for those four libraries.

Thank you again,