'''Discussed in 2016-01-28 meeting.'''

Positive reception to the BrickHack 2016 proposal. There are two local Ambassadors, myself and cprofitt (not confirmed), and there are a few others who are also interested in traveling. A call has been put out for active Ambassadors to add themselves to the wiki page on the [https://lists.fedoraproject.org/archives/list/ambassadors@lists.fedoraproject.org/thread/JCV3PSRNII5DKCORIV4MLXMNXFUHM7LL/ mailing list].

Next week, we will revisit this ticket and look at how many Ambassadors have signed up as well as look at some other logistics of attending this event.

'''Discussed in 2016-02-04 meeting.'''

FAmNA has voted to approve attending BrickHack this year for the negotiated sponsorship deal at $1.2k. This deal includes all of the following:

• Fedora branding on BrickHack merchandise
• Dedicated table for Fedora
• Permission to bring mentors for helping students programming on their projects
• Official sponsor of "Open Source" category (*)

(*) The last bullet is particularly interesting. Being a sponsor of a BrickHack category allows the sponsoring organization to define the rules and criteria for the category, and also allows us to award prizes to participants on our own criteria. This is an opportunity for Fedora to reach out to students by showing our own expertise and knowledge in open source and build a positive image and reputation among student programmers.

After discussing with a BrickHack organizer, I was given the date of '''Feb. 24th''' as the deadline for submitting this criteria to the organizers (week and a half before event). This part of the ticket deserves discussion and perhaps outside advice of just FAmNA for deciding how to go about planning this.

Fedora Project BrickHack 2016 Invoice
Fedora_Invoice_Feb_10_2016.pdf

== Current Status ==
BrickHack sent an invoice to me for the event sponsorship. I am still trying to wrangle details on budgeting with Tom Callaway and Joe Brockmeier, but many people are traveling out of the country and communication is slowed down as a result. Hoping to get the sponsorship process finished this week (?) so we can focus on the planning procedure ahead for sponsoring the open source category.

== Swag Shipping ==
BrickHack organizers also gave me an address to send swag to as a way to cut down on transportation costs. The address is as follows.

Brenda L Schlageter
159 Lomb Memorial Drive
Rochester NY 14623

P) 585-475-6464

= Fedora @ BrickHack =
Final details relating to budgeting will be handled this Friday or early next week once Ruth returns from Australia. BrickHack has sent us the invoice for the sponsorship, which is an attachment on this ticket.

Additionally, I plan to go to the BrickHack organizer's meeting next Tuesday to work on brainstorming category ideas and tasks with the BrickHack team for the open source category. We're hoping to get decause in the meeting too via video call.

= Project Proposals =
As the sponsor of the Open Source category, we are allowed to present projects, APIs, or other areas of contribution that participants could actively hack on. Without knowing more details, this could mean anywhere from twenty-five to hundreds of people actively hacking on Fedora software projects out in the open.

As a result, we need to propose some projects that we could present to participants over the course of the weekend. Looking at the [https://github.com/fedora-infra/ Fedora-Infra GitHub organization], there's several projects here that we could put out for participants. Some of these could be…
* [https://github.com/fedora-infra/mote møte] (Meetbot)
* [https://github.com/fedora-infra/anitya anitya] ([https://release-monitoring.org/ release-monitoring.org])
* [https://github.com/fedora-infra/pkgdb2 pkgdb2]
* [https://github.com/fedora-infra/bodhi bodhi]
* [https://github.com/fedora-infra/fedora-stats-tools fedora-stats-tools]
* And many more…

Additionally, there might also be some projects on [https://pagure.io/ Pagure], but I'd need someone closer involved with Infra / devel to help advise on what projects there might be good to present to student hackers.

= Rules =
We're in charge of coming up with the rules, regulations, and other guidelines for participants who wish to join in on the Open Source category. Having an idea of how we want to judge participation will be important and having these defined in advance is a '''must'''.

'''Potential Judgment Criteria''':
* Number of pull requests submitted
* Number of issues resolved
* Number of pull requests ''accepted'' (dependent on a project's team being available over this weekend)
* Net number of lines changed
* Badges earned (a-la Badge-a-thon?)
* Number of IRC karma cookies awarded… (?!)

'''Proposed Formula''':
($PULL_REQUESTS * $ISSUES_SOLVED) + ($NET_LINES_CHANGED / 4) + $BADGES_EARNED + (10 * $KARMA_COOKIES) = score

This formula has no actual research or theory behind it… but it could be a starting ground for coming up with a way to calculate final score. Obviously, karma cookies would not be something we would want to publicize to participants, but might be a score easter egg for those who really get involved and make an immediate and helpful impact in Fedora.

= Prizes =
We are also in charge of coming up with prizes for the Open Source category. A list of existing prizes for BrickHack can be found [https://www.hackerearth.com/sprints/brickhack-ii/prizes/ here].

The prizes we can contribute can be easy for us to provide (e.g. Fedora merch), but having some big ticket items might be a good idea as well. This will need to be voted on in FAmNA's meeting tonight to see if this can be appended to the budget.

Some prize ideas:
* Raspberry Pi 2 Model B ([https://www.element14.com/community/community/raspberry-pi/raspberrypi2?ICID=rpimain-feature-products $35 per unit])
* Raspberry Pi Zero ([http://www.microcenter.com/product/457746/Zero_Development_Board $5 per unit], REQUIRES PHYSICAL PICK-UP AT A MICROCENTER)
* MakeyMakey Kit ([http://shop.makeymakey.com/products/makey-makey-kit?variant=219582674 $50 per unit])
* Voucher for Bluehost VPS hosting (currently working with jsmith about seeing if this can be arranged)
* Other ideas welcome, or potential Fedora Friends who might like to give some stuff away

FAmNA will need to vote on a potential prize budget tonight to add to the proposal before we finalize details on Friday or early next week.

Also, see related: [https://badges.fedoraproject.org/badge/brickhack-2016-attendee BrickHack Badge]

Regarding rules section -- a few amendments

Add a quality check on the PRs (both submissions and acceptance -- sort of like the lines changed bit ---sure typo corrections are good but if that's all you have did you really benefit the project?

What kind of badges do we wanna have ? Some Ideas

-Best {%language} coder -- $PR*$ISSUES / ($LINES_CODE/CHANGES_IN_CODE)
-Best debugger --same as above
-Best mentor
-Best Packager
-Best Supporting member in above categories

On the bluehost I have some connections via hackhands | pluralsight (both which I support as a mentor) can poke around

Replying to [comment:7 corey84]:

Add a quality check on the PRs (both submissions and acceptance -- sort of like the lines changed bit ---sure typo corrections are good but if that's all you have did you really benefit the project?

I like the idea of having a quality check of some kind. The best one would be having people actively accepting the PRs or providing feedback as to why it can't be accepted. However, that depends on the availability of the maintainers. I feel like net changed lines maybe shouldn't be downplayed as much then?

What kind of badges do we wanna have ? Some Ideas

-Best {%language} coder -- $PR*$ISSUES / ($LINES_CODE/CHANGES_IN_CODE)
-Best debugger --same as above
-Best mentor
-Best Packager
-Best Supporting member in above categories

For the badge-a-thon, I was thinking of actually earning Fedora badges as the metric, but I like having different categories of winners too. However, maybe scratch Best Mentor and Best Packager. I'm not sure mentorship will be a huge aspect of this, but it might be? Might want to ask decause on that one.

Packaging might be out of the scope of this hackathon – I'm not sure we can people through the entire packaging process in the time window we're working with. :)

On the bluehost I have some connections via hackhands | pluralsight (both which I support as a mentor) can poke around

That's good to know – let's see what jsmith gets back to me for Bluehost with and we'll go from there. As for Hackhands and Pluralsight, I'm not familiar with either – would they be able to contribute prizes, you think?

'''Discussed in [https://meetbot.fedoraproject.org/fedora-meeting/2016-02-19/famna.2016-02-19-01.58.html 2016-02-19 meeting].'''

Additional funds were voted on for the prize fund for BrickHack. FAmNA agreed on $250 for a budget for prizes. This may include some of the above mentioned ones but might also include other ideas as we get closer. We also voted to approve travel for Nick Bebout, pending him adding all final costs to the wiki page for BrickHack.

This event cost should be absolutely finalized by Monday. No further changes can be made after then to the proposed budget.

This information will be relayed to the wiki page no later than Sunday evening.

'''Discussed in [https://meetbot.fedoraproject.org/fedora-meeting/2016-02-26/famna.2016-02-26-01.56.html 2016-02-25 meeting].'''

= Changes since last meeting =
* nb withdraws his request to attend BrickHack due to personal scheduling conflicts.

• MarkDude is removed from the attendees list as no information about his travel or lodging costs was added to the wiki in time.

• decause and jflory7 attended the BrickHack organizer's meeting on Tuesday and solidified plans for details of the Open Source track, prizes ideas, and other organizational ideas.

• jsmith contributed three different BlueHost hosting plans to the prize pool (thanks jsmith and BlueHost!!!).

• decause rounded up some OpenSource.com merchandise (more specifics on what that is soon).

• No travel costs since all attendees are local (exception: decause); other local Red Hatters should be in attendance and helping as Open Source track mentors.

= Invoice =
Invoice is still unpaid. Since this is next quarter, do we use next quarter's budget to cover this? We really need to get this paid or either arrive with check in hand... or at least know how this is going to be paid for. Andrew, do you have any ideas or thoughts on this?

= Event completed =

The event is now completed. Event reports can be found on the [https://fedoraproject.org/wiki/RIT_BrickHack/2016#Event_Report wiki]. The full, detailed event report that evaluates our impact is on the [https://communityblog.fedoraproject.org/brickhack-2016-event-report/ Community Blog]. Updated budget numbers are also in the wiki.