BuildAMation

1.   General Information

Project Name: BuildAMation

License: BSD3

Contributor (Company, Organization or individual name(s)): Mark Final

Existing OSS Project? (Yes/No): Yes

Source Code URL: https://github.com/markfinal/BuildAMation

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 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:
BuildAMation (BAM) is a build tool and project generator, using C# in a domain specific language, for desktop software development on Windows, Linux and macOS.

It defines an extensible package mechanism for providing new features/toolchains, wrapping existing OSS projects. e.g. there are already packages for Qt, Python, image file formats, data compression.

BAM supports a native (threaded) command line builder, VisualStudio project/solution generator, Xcode project/workspace generator, and MakeFile (GNU/NMAKE) generator currently.

Version 1.x is .NET Framework and Mono.
Version 2.x is .NET Core 2.1.

http://buildamation.com/

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

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: Mark Final
Email:
GitHub Profile URL: https://github.com/markfinal

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)

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.

CLA

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:
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

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.

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?

7.   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 hear and discuss with your .NET Foundation Contact.

This issue is a .NET Foundation onboarding application for BuildAMation rather than a defined code change. Start with the project description and source repository at https://github.com/markfinal/BuildAMation, then review the linked onboarding guidance; done would require completing the governance, repository, PR, infrastructure, and additional-notes sections.