Carleton-Blueprint / bluebot-dev

Testing Repo for the development of Bluebot
GNU General Public License v3.0
1 stars 0 forks source link

[project] sdf: Stage 1/5 - REPLACE WITH LABEL #49

Closed cublueprint-bot[bot] closed 2 weeks ago

cublueprint-bot[bot] commented 2 weeks ago

Stage 1: Outreach

Task

Reach out to the nonprofit organization and follow this email template.

Make sure to double check the contents before sending out the email. This template is automatically generated, and is not guaranteed to work perfectly always.

Subject

Opportunity for Collaboration with Carleton Blueprint

Body

Dear asdf Team,

I hope this message finds you well! My name is asdf, and I’m the Vice President of Projects at Carleton Blueprint. We’re a passionate organization based in Carleton University dedicated to supporting amazing non-profits like asdf by offering pro-bono tech solutions development, for free. We accomplish this by recruiting and training volunteer student developers for each project that we take on.

We recently came across asdf and were truly inspired by your mission and the impactful work you’re doing. We know that non-profits often have unique challenges and opportunities that can be greatly enhanced with the right tech solutions. That’s why we’re reaching out to see if there’s any way we can assist asdf with your current technical needs.

We’d love to chat with you about how our talented team of developers can help streamline your operations and boost your outreach efforts. During our conversation, we can discuss potential projects, expected outcomes, and how our collaboration can make a real difference for asdf.

Could we schedule a time to meet in the next week or two? We’re very flexible and happy to work around your schedule. If you have any immediate questions or need more information, please don’t hesitate to reach out.

Looking forward to the possibility of working together and supporting your incredible mission!

Warm regards,

Project Selection Criteria

Impact

Projects are evaluated based on their potential impact on the community. Blueprint prefers projects that provide maximal benefit to their target community. This does not necessarily mean affecting the largest number of people; a project with significant benefits to a small group may be considered more impactful than one with minimal benefits to a larger group.

Necessity

The project’s importance to the non-profit organization (NPO) and the NPO’s ability to complete the project independently are assessed. Blueprint prioritizes working with NPOs that genuinely need its help and lack the resources to seek alternative solutions.

Scope

The size of the project must be appropriate for the timeline. Projects that are too large or too small may not meet Blueprint’s standards or may not be necessary. The VP of Projects works with NPOs during the proposal process to determine an appropriately sized project.

Technical Fit

Projects must effectively leverage Blueprint’s technological skills. Blueprint seeks projects that are neither too trivial nor too difficult, ensuring the partnership is mutually beneficial.

Credibility

Evidence of the project’s potential for implementation is required. NPOs must provide data or history demonstrating the project’s usefulness. Blueprint aims to avoid developing projects that will not be utilized.

Preflight Checklist

Metadata

{
  "client": "asdf",
  "author": "asdf",
  "clientTag": "sdf",
  "stage": 1
}
cublueprint-bot[bot] commented 2 weeks ago

Summary