The following table lists all the fields in the Project Details panel of the Project Application:
(Required) Name of the project. CommunityBridge supports one administrator per project who serves as the administrator of that project within Funding—no one else can claim this project for Funding. This project name will appear on your project page.
Note: This name must be unique—no other project can exist in Funding with the same name. However, funds of a different type can use the same name. For example, a Travel Fund and a Project fund can use the same name.
Topic / Category
(Required) Type of industry that relates to your repository. For example, the Cloud topic is appropriate for an Express Gateway project. Click in the field to open a list of names to choose from. Click after you select a category from the list. Note: The category/categories are reflected in the List of categories you have added... field after you add a category.
(Required) Brief statement of why your project is important to support.
(Required) URL of the GitHub repository. CommunityBridge uses this URL to display the repository statistics on your project page, and to provide a link to the project’s repository. Note: If you choose Add GITHUB Repository from the options while applying, your GitHub repository is automatically reflected in this field.
(Optional) The Website address that you want to associate with the fund.
CII Project ID
(Optional) The Core Infrastructure Initiative (CII) Badge Program Project ID number, for example: 24.
The CII Badge Program is an open source secure development maturity model. Projects that have a CII badge showcase the project’s commitment to security. Examples of criteria include basic open source development practices (website, open source license, and user engagement), use of change control tools, attention to quality (automated test suite), and focus on security (secure project delivery method, use of dynamic and static analysis tools, as appropriate for the project). Consumers of the badge are able to quickly assess which open source projects care about security-conscious development. Although participating in the CII Badge Program is optional, we encourage you to enroll in the program within the first 90 days from your application submission. The badge displays on your project dashboard to showcase your project’s status and progress on security and other metrics.
Click Apply for CII to get a badge and CII Project ID number if your project does not have one. You answer a questionnaire to be awarded a Best Practices Badge and a CII Project ID if you are approved. A questionnaire snippet follows:
Code of Conduct URL
(Optional) An agreement that describes the rules of behavior for the members of the project. Specify a URL for your code of conduct or create a code of conduct by clicking Start from a template. A default Contributor Covenant appears and you can use it as a template. Click Add Custom Website to add a website to your project by entering a website name and URL.
The following table lists all the fields in the Project Branding panel of the Project Application:
(Optional) A symbol or other design adopted by your organization that identifies your project. Click Browse to upload a file. Preview shows the logo that you uploaded. Note: File type- JPG, PNG, SVG File size- 2MB (maximum)
(Required) The hexadecimal number for the color that you want to use as your project brand, for example, #008000 is green. Enter a hexadecimal number or click in the field to open the color picker. Use the picker by clicking inside the color field to pick a color. You can use the up/down arrows to refine the color by editing the color values. The gray field refreshes to match your selection.
Beneficiaries are individuals who work on a project and then request reimbursement for their time and expenses. You can add names of individuals who you want to submit travel expense for the project related travel such as attending events.
The following table lists all the fields in the Project Beneficiaries panel of the Project Application:
The name of the person who you want to designate as a beneficiary of funds.
The email of the project beneficiary.
After you enter the name and email address of a person, click +Add beneficiary to add the person to the list. To add more beneficiaries, click + Add beneficiary and complete the fields that appear.
When you submit the project, and after the project is approved, the Linux Foundation finance team sets up individual Expensify accounts for each beneficiary. Then, each beneficiary receives an email notification from the finance team that includes a link to their Expensify account. Beneficiaries are invited to join the custom Expensify policy as part of their participation in CommunityBridge. After accepting the invitation, beneficiaries have access to the policy where they can submit expenses for reimbursement from CommunityBridge funds.
The finance team also works with the project administrator to set up a specific expense policy that applies to the project. All the beneficiary and project expenses are gated through the expense policy. For example, the policy might state a hotel price range that is acceptable for a beneficiary or a per diem food allowance.
Only the project administrator can add or remove beneficiaries. The finance team is notified and adjusts the Expensify accounts accordingly.
Annual Project Funding is a total project funding goal amount for the year. The Annual Funding Goal amount is the sum of the individual goal amounts.
Fund Distribution enables goals for how you want to distribute funds in your project. Complete the fields that appear—see the example below. Enter a percentage of your Annual Funding Goal amount to designate towards the selected goal. You can use the up/down arrows to select a percentage also. Goal amounts have no target limit, so you can continue raising money beyond your goal amount. As you see progress in one or more goals, you can (and should) update the goals to reflect how you plan to utilize these additional funds.
Be clear to potential sponsors about how you intend to use the funds. You can designate funds towards different types of expenses, such as Marketing, Travel, Bug Bounty, and so on. Following are various goals towards which you can distribute your fund:
Development Goal: You can use funds allocated for this category to pay top developers for contributing codes, adding features, fixing bugs, and training and bringing in new talents to the community.
Marketing Goal: You can use funds allocated for this category to promote and grow your project through the development of collateral, website design, t-shirts to wear at events, and so on.
Meetups Goal: You can use funds allocated for this category to socially connect with your community through local meetups, annual summits, or big industry events.
Bug Bounty Goal: You can use funds allocated for this category to run bug bounty programs (for example, through HackerOne or other program), and pay community to help you identify bugs.
Travel Goal: You can use funds allocated for this category to sponsor travel for project members to attend conferences, meetups, or customer meetings.
Documentation Goal: You can use funds allocated for this category to drive specific documentation initiatives, such as paying technical writers, purchasing subscription premiums, and so on.
The Financial Summary shows the annual financial goal and progress towards it by individual goal. It shows a distribution report based on your selection from the Fund Distribution panel.
Select the checkbox