Step 1 → Submission of Project Proposal(s)
Deadline for submission: **January 19**
You can submit your Project Proposal(s) through the ‘Project Proposal Submission for Review’ Typeform (linked below), answering multiple questions on your idea and how you see it working for a project team during the Project Phase.
Some of the questions you’ll need to answer in your pitch: What's the problem you are trying to solve? What's your idea for a solution to the given "problem"? Which tracks do you think could be involved? What are the most important challenges & bottlenecks of your project? What are the most important success factors of your project?
You can also link any resources (datasets, links, videos, etc) and/or a Google Slide deck link to support your idea.
Don't worry if you don't have all the answers yet, don't let that block you from submitting an idea! The Track Leads can help you figure out all the details for final approval.
SUBMISSION - WS23/24 Project Proposal Submission for Review
Step 2 → Proposal Reviews by the Journey Team
Ongoing until **January 19**
After your submission, the Track Leads will review your proposal to meet the TechLabs Project Phase requirements - e.g. feasibly, tracks involved, number of team members, etc. They may add extra requirements or to-do-tasks for final approval.
We will create a Git Issue for each idea submitted to start public discussion in Step 3.
Issues · TechLabs-Berlin/project_proposals
Step 3 → Public Discussion with your fellow Techies (Scoping)
Ongoing until **January 19**
If/once approved, a Track Lead will make your idea public on the Slack channel #bl-project_ideas and Github for discussion between all Techies:
Step 4 → Final Approval and Team Constitution Submission
Deadline for submission: **January 26**
If/when your proposal complies with all the requirements and you found a team to work with, you’ll need to submit a final Typeform (link coming soon) with your team’s constitution to advance to the Project Phase.
If you were not able to find a project team, regardless of the reasons behind it, you’ll need to submit you failed to do so. This means you’ll be assigned to a random project team.
<aside> 🚨 If you fail to submit either your team’s constitution or that your were not able to find a team by January 26, you will be removed from the program.
</aside>
All open project proposals will be added to a Github repo using GitHub issues, and the original pitcher will be assigned to their proposal issue.
This repo will give you an overview for all open project ideas and their status, so you can engage in discussion in the ideas that are interesting to you and have been reviewed by the Track Leads.
Statuses of Project Proposals on Gitbhub
When a proposal is submitted it will be added to the repo with the status proposal.
Once it’s reviewed by Track Leads, it moves to scoping status, where extra tasks might be requested to fulfil all the project requirements and discussion and team formation is expected between the original pitcher and techies interested in working on that idea.
When the idea is approved and ready for development in Project Phase, including having (the majority of) team members attached to it, it will receive the accepted status for final submission of team constitution.
Do I need to submit a project proposal?
No, it’s not mandatory to submit a proposal to gain your certificate, but we encourage you to share your ideas with the community, something great can come out of it!