#184 HackMIT 2017 sponsorship
Closed: Completed 3 years ago Opened 3 years ago by jflory7.

Wiki page

Phenomenon

MIT has its own hackathon each year, HackMIT. It is a larger hackathon fitting close to 1,000 hackers at MIT for a weekend. HackMIT happens on the weekend of September 16-17, 2017 this year.

Budget request

The full line-item budget is available on the wiki.

At a glance, the total estimated amount for the event as of today is $1345.37 USD, which includes a special negotiated sponsorship rate of $750 USD. The rest includes travel and logistic estimates.

I am still looking for another Ambassador to attend this event with me. The travel costs could change depending on the distance and travel for another Ambassador.

Why we should do it

This event is full of some of the brightest hackers from around the country. With over 1,000 university students in attendance, there is a large potential to make an impact with open source and Fedora at HackMIT. There is a longer justification on the wiki page – that section is excerpted here for convenience:

  • What is the focus of the event from a Fedora point of view?

The goal of Fedora at HackMIT is unique from a traditional Linux event. This a university-organized hackathon, where students from the country (and at this one, even the world) gather for one weekend to learn new technology and build cool projects that have a vision and an impact. For many students with ambitious plans, open source is potentially a tangential part of their goals to accomplish this.

Fedora is not just an operating system, but also a community of people and resources. Fedora attending this event helps promote the Fedora community as a platform for building applications and also finding ways to extend a students' own ambitions by connecting them to the wider open source community. Based on last year's experience, it's a great opportunity to influence and introduce open source, Linux, and Fedora to students for the first time (or build on top of the knowledge they already have).

  • How does our attendance at this event build users of or contributors to the Fedora platform overall?

Fedora's attendance at this event aims for users over contributors. Ideally, since most students either haven't used Linux or still experimenting around, there's a potential to influence them about the project and excite them with some of its cutting-edge development features (this is an angle we went for last year, since students come to events like these with the intent to try new tech or to try learning something new).

In the long-term, we would ideally accomplish two things:

  1. Introduce students to the Fedora operating system, not just as workstation but in other ways (like with containers!)
  2. Connect students and their projects to open source with the intent of exposing them to the reasons of "why we FOSS" and why that's so cool and exciting
  • How does our attendance at this event build users of or contributors to specific Fedora solutions — and why are those particular solutions strategically important?

Since hackathons are intentionally marketed to students as a chance to try something new or crazy or to work with tech that is out of the norm, it would be a good audience for us to promote Fedora and some of the exciting things happening in the community. If possible, using containers to build and develop applications would be one possibility, where we can introduce Fedora Atomic. Otherwise, we can focus on Fedora Workstation as a development operating system for normal day-to-day work.

From last year, the mentorship opportunity was vital to why it felt like a successful event for us. Even if Fedora itself wasn't the primary focus at times, we as Ambassadors had unique conversations and individual interactions with students on their projects. We were able to offer advice, insight, and help support them in their goals to build their projects. This left a powerfully positive impression of the Fedora community and led students back to our table to take a break from their project and talk with us about various tech topics (which can be used to connect back to Fedora's technical and non-technical goals).

  • How will success be measured? If the event doesn't meet its benchmarks, how will we adjust?

Last year, we used a Fedora Badge (see here), which we had available at the booth and passed around handouts at tables we visited. It only had eight students scan the badge, with one of them showing activity on their account after the event.

While I would like to have a badge again this year, I'd rather focus on making individual connections with students that we can follow up on after the event. In particular, I want to create a Google Drive form for students to enter their contact info if they'd like to keep up-to-date on Fedora news or hear about opportunities to get involved. I haven't thought beyond this, but I think it would improve our likelihood of post-event engagement / interaction of the students with the Fedora community, if there was a personalized follow-up.


Metadata Update from @jflory7:
- Issue assigned to jflory7
- Issue priority set to: normal (3-4 weeks)
- Issue set to the milestone: Fedora 27 (to Nov. 2017)
- Issue tagged with: event, meeting

3 years ago

As a note, the HackMIT organizers requested a confirmation of sponsorship by August 11th, 2017. I've tagged this ticket as meeting so we can discuss and vote on it at the next FAmNA meeting this Thursday.

Without comment on the ticket or event, I want to say I do like the idea of trying to get contact information to ensure that we can follow up with people. I am concerned that if you collect a lot of leads it will be to many for just @jflory7 and @cprofitt but we can cross that bridge when we get there.

@jflory7 is the person from last year's even still active? Could they be a point of contact for students from this year?

@bex The only activity by the student was reactivating their FAS account in March 2017 and updating some information in their account. Ultimately, I don't think badges alone were an effective tool to measure our impact at this event, which is why I thought building a list of emails to do personalized follow-up could be more effective. I don't know what the uptake would be if we had something like this at our booth, but it could be a good trial experiment.

Also, due to a change of plans with @cprofitt, he is no longer able to attend this event. Right now, I am actively looking for other NA Ambassadors on the US east coast who could attend this event.

@bex and @jflory7 - while I can not attend in-person this year I would be able to assist with reaching out to any contacts gathered this year.

I think one of the things that might spark some interest is having a good presentation about how Fedora is involved with Google Summer of Code. Many of the students that attend HackMIT are from other schools and this is a great chance to use another well known event and tie it in to Fedora.

@bex and @jflory7 - while I can not attend in-person this year I would be able to assist with reaching out to any contacts gathered this year.

I think this is a huge leap forward for our ambassador model and would love to see more of this.

I think one of the things that might spark some interest is having a good presentation about how Fedora is involved with Google Summer of Code. Many of the students that attend HackMIT are from other schools and this is a great chance to use another well known event and tie it in to Fedora.

The GSoC final reports are due at the end of August. This is our chance to build this presentation. Can you outline what you'd want to know and maybe we can even get video to use in the presentation of the actual students talking. Here is a starter on some questions for them:

  • Why did you choose to apply to GSoC?
  • Why did you choose the Fedora organization?
  • What is the biggest challenge you had?
  • What is the greatest thing you learned?
  • Would you do this again? Will you keep contributing?

@bex
I like the idea of a video -- easier to engage participants at Hack-A-Thons as they can watch the video at our table and/or talk to a Fedora Ambassador. Having a live presentation for events that allow us to speak would be good too.

Here are some videos I found on the web... I am wondering about your thoughts on these.

https://www.youtube.com/watch?v=S6IP_6HG2QE&feature=youtu.be

https://www.youtube.com/watch?v=iGRS3lmWevU


To your questions I might add:
How do you think working with Fedora and GSoC will help you in your career?
What was your favorite part of working with Fedora and GSoC?

Another idea would be to organize a key signing party. (assuming having a signed key is still used for GSoC)

Discussed in the 2017-08-10 meeting.

Ambassadors in attendance

In tonight's meeting, @mikedep333 confirmed his availability to attend the event via train from Pennsylvania to Boston. Together, he and I hope to attend HackMIT together.

FAmNA approval

In our meeting, we voted to approve $1750.00 USD for this event. The current estimate places it at $1345.37 USD, but the extra amount is in case of any unexpected issues with travel or other fees (the intention is to stay as close to or below the estimate as possible). This information is currently reflected on the wiki page.

Council ticket filed

Since the proposed budget for this event is over $1000 USD, I filed a Fedora Council ticket here for final approval on this event. In the meanwhile, I am reaching out to event organizers to request an additional week for a final decision.

@cprofitt I haven't completely watched the videos you posted, but in general the concept is good. The challenge is how do we make this a Fedora thing and not an ad for GSoC? I think we need to figure out how to interview our own GSoC students ... which is a large undertaking. We can def start here to test the concept though.

I'd really like to see more conversation from NA Ambassadors about follow up and how to do it. I think this goes way beyond this event and we will only be successful with follow up if we have buy in from the majority of the 120+ NA Ambassadors.

@bex said…
I'd really like to see more conversation from NA Ambassadors about follow up and how to do it. I think this goes way beyond this event and we will only be successful with follow up if we have buy in from the majority of the 120+ NA Ambassadors.

I wanted to acknowledge the above – will work on filing a new ticket to discuss / define a more abstract strategy that can be used and applied across events. Will try to get it filed before this Thursday, but it might end up happening during / after Flock because I am traveling for the next week.

Metadata Update from @award3535:
- Issue untagged with: meeting
- Issue tagged with: budget

3 years ago

@jflory7 I dont remember seeing an event report for this event. I was out of town and unavailable due to Hurricane Irma, so can you please update this ticket where the report is located

@award3535 Thanks for your patience on a reply. I missed this comment in my email or I would have replied sooner.

In CommOps, we're working through the Community Blog drafts queue and getting articles published. The HackMIT 2017 event report is here:

https://communityblog.fedoraproject.org/fedora-returns-hackmit-2017/

It publishes Tuesday, Dec. 5 at 08:30 UTC. If you're reading this comment before then, a temporary preview is here.

@mikedep333 also published an event report on his personal blog. You can find his report here:

https://mikedep333.blogspot.com/2017/11/fedora-hackmit-2017-wrap-up.html

I'm going to close this ticket as complete. I forgot this event is still pending final payment since they decided to take a paper check as the payment option. I'm going to keep it open and re-assign it to @bex to update when he has completed the payment.

Metadata Update from @jflory7:
- Issue assigned to bex (was: jflory7)
- Issue priority set to: happening now (was: normal (3-4 weeks))
- Issue tagged with: blocked

3 years ago

Metadata Update from @award3535:
- Issue untagged with: blocked, new event

3 years ago

Reports and reimbursements made for individual. closing ticket

Metadata Update from @award3535:
- Issue close_status updated to: Completed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata