Versions Compared

Old Version 9

changes.mady.by.user Casey Cain

Saved on

compared with

New Version Current

changes.mady.by.user Casey Cain

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Below are additional details about how to fill out the above presentation:


Project Vitals

Basic information about the candidate project.

This slide is an overview of the fundamental information about your project.

  • Project Name: Please fill in the official name of the project. This is the name that will be used in all official documentation and communication.

  • Project Creation Date: Enter the date when the project was officially started or initiated.

  • Project License: Specify the license under which your project is distributed. Examples include Apache 2.0, MIT, GPL, etc. If you have multiple licenses, please list them all.

  • Contributing Organizations: Here, you should list all organizations that are actively contributing to the project. This includes companies, academic institutions, non-profits, etc.

  • Seed Code Availability: Enter the date when the seed code, or initial codebase, of your project will be or was made available. Also, list the repositories where this code can be found.
  • Release Schedule: This is where you detail the timeline of your project's release. It might include dates for the start of development, feature freeze, code freeze, testing periods, and the final release date. If you have a consistent release cycle (e.g., every 6 months), you can specify that here.

...

  1. Wiki: Share a link to your project's wiki page, if applicable. This is where you can house essential project documentation, updates, and information.

  2. Code Repositories: Include a link to where your code is hosted. This could be a platform like GitHub, GitLab, or BitBucket.

  3. Bug Tracking: Specify the tool you're using to track bugs and issues, such as JIRA, GitHub Issues, or Bugzilla. Include a link to your project's specific bug tracking page or system.

  4. Code Review: Indicate what system or tool you're using for code reviews. This could be Gerrit, GitHub PRs, etc. Don't forget to provide a link to where these reviews take place.

  5. Documentation: Share where the project's technical and user documentation is stored and accessible. This could be on a dedicated website, within the code repository, or elsewhere.

  6. CI/CD Tooling: Specify the continuous integration/continuous deployment (CI/CD) tooling you use. This could be Jenkins, GitLab CI, Travis CIGitHub Actions, etc.

  7. Collaboration tools: Mention any tools you use for project communication and collaboration. This could include mailing lists, forums, chat platforms (e.g., Slack, Teams), video conferencing tools, etc.

...