I love the idea, but I think it will be a logistical nightmare if we were to organise the multi-city model all by ourselves. We could have participants self organize their own sites to facilitate other online participants from their location, but there are associated concerns regarding participant safety and the like, so we’d also need to make it clear that such arrangements are done completely autonomously.
But it is completely plausible that, say a college FOSS Cell decides to open up their facilities for participants to come and hack from their venue and the participants would in my opinion have a blast!
We post guidelines and examples for the kind of projects that are encouraged, list down do’s and dont’s. This year, we can post the winning projects from the last two years. That should give participants a reasonable picture of the kind of quality to aim for. The submissions will always be a mixed bag though, which is fine.
Absolutely. This should run fully decentralised. I think what we could do is create a page with a few bullet point guidelines and share it with institutions / student clubs. MEC Kochi, IGDTUW Delhi, Reva Bangalore, RV Bangalore, TinkerHub community etc. come to mind who may be interested.
Had a call with @Sejal_Jain on how we are planning to handle FOSS Hack Talks and Mentorship programs
We plan on scheduling talks a week prior to the conference, in fully online mode with some talks being scheduled during the hack weekend to be streamed from the venue, for the convenience of remote participants(focused workshops?).
Sejal will start looking out for interesting speakers(keeping a bias towards people from diverse backgrounds) and also contact organizers of events such as Hill Hacks and Anthill Hacks to figure out how we an integrate remote communities into the program, providing them a ground to represent the work they are doing at the fringes of society.
We need to open a form for FOSS maintainers and people who are interested in mentoring participants through the mentorship program and probably revive https://t.me/first_commit for a full on mentorship program where we can connect people in sub groups there to the right maintainer or resource person and have them get started in their contributor journeys. Mentors need not be at the venue and even for offline teams we can connect them to the relevant mentor via tg.
We are yet to figure out the timelines for FOSS Hack CFP for talks, but we think it’d be better get started ASAP and have the form out along with the website.
Are there any thoughts or suggestions for these ideas or does it look like we are good to go?
Thinking through the requirements from design for Foss hack 2.0 | Link to sheet
Off the top of my head, we need:
A website design like Fosshack 2021 - as source of truth for rules, sponsers, community partners and so on.
Social posts for announcing
2.1 Event details
2.2 Mentor-volunteers
2.3 Sponsors.
Venue
3.1 Event Schedule
3.2 Signage
Is there anything i missed ?
To kick things off - can we use the same template as foss hack 2021 and make change to graphics for 22 ? There’s a lot of ai art generaters out today - we can try and use some clever prompts to make our banners
In the previous two editions, most projects that built during the hackathon were new PoCs. For example in 2021, there was only contribution to an existing project.
Most likely, the reason for this is that it takes time to become familliar with an open source project. And then finding something meaningful that the maintainers would want is another challenge. A mentorship program would prove helpful in this case.
These conditions should be met from the program:
participants should have enough time to become familiar with the project and make a non-trivial contribution
participants should get adequate mentorship. contributing to a new project is tough, this process should be eased by the mentor, maybe by pairing on some smaller issues.
mentors should have incentives to participate
they shouldn’t be spammed with PRs of shallow fixes
there should be a chance that these participants come back to contribute again
perhaps certificates or monetary compensation?
We need to take a call on these decisions:
Are participants allowed to start work on the project before the hackathon? Or can they only pair on some other issues during that time?
the latter
How many participants can one organization take on for mentorship?
open participation? participants are free to move to another org if they feel that one org is too saturated.
How long before the hackathon do we match mentors and participants?
we can ask mentors to commit some time each day (1-2 hrs?) for the duration of the mentorship program (5 days) to onboard participants and for code review. And then some more during the event.
we should allow participants to hop on for mentorship later too (for example, in case their first picked project is too complicated for them).
What do we expect from mentors?
Some time commitment each day - for onboarding and code review
Some "good first issue"s for getting familiar with the codebase
Some non trivial issues that can potentially be used for the hackathon. Mentors can decide if they want to reserve these issues for the hackathon or allow work on it on the days leading up to it.
If the judges want to know about the significance of some contribution, they should talk to the mentors about it.
We had a brainstorming session today and came up with a list of tasks which will serve as a blueprint/overview for further development/discussion. Suggestions are welcome.
Social media challenges
Content bank for Instagram, LinkedIn and Twitter
Twitter Info threads could be made use of
Create a design system
Effective use of hashtags
Some topics for threads/posts:
Intro lines - make it interesting
What is FOSS Hack?
Why should you participate?
Who can take part?
Venue details
Website release
What can you build?
Do you have to build a project from scratch?
How can we help you?
Speakers | Partners | Sponsors
Prizes
Decentralised local chapter hackathon guidelines and templates
Website: A page to filter mentors based on skills Evaluation: Give a nudge (email reminder) to all the participants for the project review. Talks: Pre-event- Recorded talks, During events - Workshop, Lightning talks in classroom/auditorium. Volunteer: Participants Managers Newsletter: Rules, Evaluation, CoC, Mentorship FOSS Hack Local: Get details of the hackathon - Are they charging? if yes, what’s the ticket price, capacity of the venue, are they looking for mentors to join in-person, Is overnight hack possible? We can only approve the Local edition if the venue is confirmed. Outreach: Create a list of tech groups/organizations to reach out to for community partnerships. Ask Volunteers to contribute to that. @mriya11 can add details of our hackathon grantee and @nikochiko can add details of previous community partners. Social Media: Announce Hackathon, CFP, and Sponsorship, FOSS Hack Local Design: Website design, Social media announcement posters.
A few points we discussed regarding FOSS Hack local in the last meeting.
distributed format
preferably informal
basic requirements:
internet connection
projector
cleanliness
good restrooms/sanitation facilities
max grant we can offer: 10k
for food and other expenses
expecting at-least around 10-20 people ?
preferably we could have seniors/experienced programmers to act as mentors
To Do
Create a structured/doc/set of rules for local partners. (maybe @KaranGandhi can help?)
what exactly they can offer
what we can offer
Clearly ensure that for offline participants, FOSS United doesn’t hold any responsibility.
if they are not participating physically in Bangalore venue, you are considered online.
If they are participating in FOSSHack Local the responsibility should be falling on the local organizers only
Create database of contacts and send email with the doc
Verify the credibility of the organizer
Release the final list of venues (at-least 3 weeks before) the final event
Suggestion: Ask each host to send a contact link (preferably one containing a form) and have this link be published in the website. The link given so as for the hosts to track the number of participants who’ll be attending.
FOSSUnited will not be responsible for tracking or any further management.
Regarding the choosing of local Venues
Don’t have too much communities be concentrated in any particular region
Make it maximum distributed.
The aim should be for those already communities who are already interested to host the hackathon to do so with the grant being provided by us.
Since this is the first time, we’re doing a distributed local hackathon, keep only small number of organizers whom we can trust.
maybe keep max local partners per state as 3?
Should be really based on trust. So ensure proper verification/background check is done before finalising the host.
Other Factors to consider when choosing host
Location of the host
see how many people they can accommodate
understand the potential of that location.
TBD
how exactly to offer the money to the local organisers
based on some estimates (advance + other afterwards) ?
maybe ask them to get funding from them too ?
a doc from them describing their facilities, what the can offer
