openSUSE:Board meeting

tagline: From openSUSE

Contents 1 Meeting 2013-06-17 1.1 Agenda 2 Meeting 2013-06-03 2.1 Agenda 2.2 Minutes 3 Meeting 2013-05-20 3.1 Agenda 3.2 Minutes 4 Meeting 2013-05-06 5 Meeting 2013-04-22 5.1 Agenda 5.2 Minutes 6 Meeting 2013-04-06 & 07 6.1 Agenda 6.2 Minutes 7 Meeting 2013-03-25 7.1 Agenda 7.2 Minutes 8 Meeting 2013-03-11 8.1 Agenda 8.2 Minutes 9 Meeting 2013-02-25 9.1 Agenda 9.2 Minutes 10 Meeting 2013-02-11 10.1 Agenda 10.2 Minutes 11 Meeting 2013-01-28 11.1 Agenda 11.2 Minutes

Meeting 2013-06-17

Agenda

1. Action item review
   1. Face to Face actions
   2. Message to SUSE about refund for local material through TSP (done)
   3. Message to oSC14 potential organizers (done)
   4. Lets enumerate everything that's open or we'll drop it
2. oSC13 (1 month away, everyone booked)
3. oSC14
   1. We have to proposals and answers from both teams to all our questions, decision time

Meeting 2013-06-03

Agenda

1. Action items
2. Board signed certificates for oSC
3. Responsiveness of @admin
4. Funds for Marketing Material via TSP
5. oSC 14

Minutes

Present: Andrew, Richard, Robert Absent: Raymond, Vincent, Will

1.) Action items

Nothing new on the face to face action items. Message to oSC13 team has been sent.

2.) Board signed certificates for oSC

At the oSC13 meeting the idea was floated to provide board "signed" certificates to all attendees. Should we do this?

We agree that the board, as individuals or group, does not want to sign any "Attendee Certificate" for oSC. We think this is generally tacky and of no value.

3.) Responsiveness of @admin

Responsiveness from @admin is very slow. While we are aware that a Redmine based ticketing system is supposed to be implemented, the time line is unknown.

AI: Vincent follow up with Lars on implementation time line for ticketing system AI: Vincent follow up on potential decommissioning of Lizards

4.) Funds for Marketing Material via TSP

It has come to our attention that the TSP reimbursement for locally produced materials has somehow been changed and information about the program appears to have disappeared. There is confusion, it is the boards impression that based on the new shipping procedure and the launch of the new Coordinator this money is essential to handle smaller events. The removal of the information from wiki and message received from TSP coordinator do not match the goals.

AI: Richard draft message to SUSE follow up on marketing funds through TSP

5.) oSC14

Received official e-mail of interest from French team, we now have a choice of location. We still want someone from organization committee of oSC14 to be at oSC13 and we would like to announce the oSC14 location at oSC13. Thus we need to get this moving.

AI: Robert draft e-mail to both groups with required info

Due date is June 14, this gives us a few days to review and make a decision while leaving about 3 weeks for someone to make travel arrangements and prepare a presentation.

Meeting 2013-05-20

Agenda

1. Action Items Review
2. 58 days to oSC13: Progress-Work done-Things that need to be done

Minutes

Present: Richard, Robert, Vincent Absent: Andrew, Raymond, Will (Holiday)

1.) Action items

No progress on the action items from the Face to Face meeting, we need to double down and get these done

2.) oSC13

The board has been asked to be "more involved" in the organization of oSC13. However, we do not see the completion of tasks for the conference organization as a part of the board's function. If we were intimately involved with the organization of events we would never get anything else done.

AI: Robert draft message to oSC13 orga team and explain the board point of view, sent when we agree on the wording.

We agree that someone from the board should be present if the oSC13 committee has IRC meetings.

AI: Richard and Robert to participate in next oSC13 IRC meeting

Meeting 2013-05-06

Canceled, vacation and holiday's decimated the number of board members able to attend

Meeting 2013-04-22

Agenda

1. Meeting Time
2. Action Items Review
3. Trademark Approval Requests
4. New Merchandising Plan
5. Ambassador program revamp
6. Infrastructure Policy

Minutes

Present: Richard, Andrew, Robert, Vincent, Will

Absent: Raymond - Company Meeting

1.) Meeting time

With the time change we will move the meeting back by 1 hour, this works better for everyone

2.) Action items review from Face to Face meeting

• Richard: Double check Summit Artwork for copyrights -- Done
• Vincent: Follow up with Guillaume about French community organizing oSC14 -- Done -- They do not need help at this time.
• Robert: Followed up on details about the current openSUSE store
  • It is easy to manage, basically no work
  • We get about $100 per quarter from sales
    • Need to chase where the money goes and this need to be integrated into the new openSUSE cost center
• Andrew: Collected all names of people effected by very slow reimbursement process
  • Vincent needs to follow up with SUSE to get the money out the door
• All other Face to Face action items outstanding

3.) Trademark usage request

• openSUSE Magazine (Online) - no objections will work out approval wording on ML
• openSUSE Book - no objections
• openSUSE T-shirt printing re-newel - no objections

AI: Vincent to follow up with all requesters and give go ahead

4.) New Merchandising plan

AI: Richard coordinate with Jos to announce new Local Coordinator program and new merchandising plan

5.) New Ambassador program

Basically ready to go, Richard work on announcement and coordinate with Jos

6.) Infrastructure Policy

AI: Robert to transcribe policy and pass back to Lars

Meeting 2013-04-06 & 07

Board Face to Face Meeting in Nuermberg

Agenda

1. How do we interact with openSUSE team
2. Event orginisation help
   1. oSC13
   2. oSC14
   3. Summit
3. Roland joins board discussion
4. Agustin Presentation - openSUSE Team
5. Lars Presnetation - Infrastructure
6. Ambassador program revamp
   1. Richard presentation
   2. Jos presentation on SUSE Team supplied merchendising/shipping materials
7. Web store
8. Reimbursement
9. TSP
10. Foundation
11. Strategy

Minutes

Present: Richard, Andrew, Robert, Vincent, Will

Absent: Raymond - Business Trip

How do we interact with the openSUSE team and SUSE

With the reorganization of dedicated SUSE employees that work within the openSUSE community from the Boosters team to the openSUSE team with new leadership the dynamic has changed. This might call for different ways of communication.

• The appointed chairman (Vincent) may be considered as a "more formal" way to communicate with the team
  • but SUSE team members are members of the community like everyone else, thus a "formal/special channel" of communication should not be required
  • board considers chairman as a communication channel to SUSE management
• The directed team approach of the SUSE team under the new org will require the board to communicate to the community the changes in communication paths
  • The directed team approach would provide a good opportunity to have the SUSE team send activities reports to the community
    • But SUSE team is not special, thus other teams should also provide activities reports
      • The Board is looking for individuals to help Bootstrap team reports, including
        • GNOME
        • Artwork
        • ARM
        • KDE
        • TSP
        • Board
        • Marketing
      • The long term goal is to have a project report on a monthly basis

AI: All make effort to bootstrap team activity reports by as many teams as possible

AI: Robert draft message to project concerning changes in communication with SUSE team using examples

Events

The board agrees with the premise that at most, if not all, events it is inevitable that openSUSE representatives receive questions about SUSE. We cannot expect community members representing the project and the community to answer these questions. This is an opportunity for SUSE to take advantage of the existing synergies. Thus, the board will ask SUSE to consider encouraging SUSE employees to participate in events. The advantage to the community is that we will have additional help at the events, the advantage to SUSE is the representation.

oSC13

• Event organization appears to be on track and we expect a great event
  • We did not have sufficient submissions by the deadline to fill the program, CfP deadline has been extended
  • A preliminary schedule will be created an published in 2-3 weeks
  • We need to schedule time for project meeting and reports
    • Live project meeting (90 or 120 minutes?)
    • Team reports (60 or 90 minutes?)
    • These should be scheduled in the middle of the core days

Summit 13

• Artwork is mostly done (by Andi).
• Bryen will take care of website.
• New volunteer Steve Dorries will take care of local outreach.
• Chuck Payne will work on finding a keynote speaker
• Robert is running CfP plus following up with people
• We will have an openSUSE booth at SUSECon

Problem

• We have single point of failure for all activities
• Not enough bandwidth to follow up and/or take over for activities left undone

Solution

• Call for more volunteers (we do not expect success with a renewed call)
• Trust the people now working on oSC will help with Summit once oSC work is wrapped up
• Try to contract someone

AI: Vincent to double-check with Agustin he’s handling the request for the booth

AI: Richard to double check Artwork for legal

AI: Vincent to discuss with Kent about costs on openSUSE side for organizing the Summit

AI: Vincent to go to Agustin/Roland and see if there’s money in the openSUSE budget for contracting

AI: Robert to seek potential contract person

oSC14

• No contact from anyone regarding hosting of oSC14 on board list
• French community is potentially interested

Event Organisation Help

• Concern that in the long run event organization in the present form is not sustainable for our own events
• Organization of openSUSE presence at events is not well coordinated either

We agree that we want to formally request the openSUSE team develop the capacity to have an even organization person that can help with events such as CLT, Linux Tag and provide a rallying point for the community to organize oSC and the Summit.

If we cannot get a rallying point we have to continue as we do now, keeping in mind that we may not be able to pull our events together.

AI: Andrew to push Guillaume send mail to Board@ to start conversation

AI: Vincent to talk to Kent & Elisa to see if they can help french team in organizing oSC14

AI: Robert write draft e-mail of request

AI: Approach Kostas to give a talk at oSC about organizing oSC

AI: We need to ensure one person from next years local organization committee attends oSC13

AI: Vincent to contact SUSE event team to see if someone can join oSC and give feedback on organization, and participate in training session

Meeting with Roland

Roland Haidl is the Director Operations & Services at SUSE and the openSUSE team at SUSE works in his team.

• The work of the Boosters is considered successful
  • Contributions to the openSUSE project have been growing and this was a major goal of the unidirectional boosting the Boosters team was chartered with
• The organizational change is intended to change the SUSE involvement in the community
  • Goal is to have a more focused directed approach to have a more positive impact in areas of focus
  • Spend effort in areas that are perceived to need significant improvement
• An openSUSE cost center has been created
  • There will be a budget and the board will have control over a certain amount of money
  • Details still need to be worked out

Meeting with Agustin

Agustin is the manager of the openSUSE team at SUSE. The re-organisation from the Boosters to the openSUSE team is now almost a year in the making. The transition has not been easy, from a company and community perspective.

• The openSUSE team lost a number of members that were well known within the community
  • These members have taken on other responsibilities within SUSE
  • New team members are new to the openSUSE community or new to open source communities, thus it will take a while to get the word out and have the team members establish themselves within the community
• Statistics collection and data evaluation shows that
  • our download number for releases is pretty stable
  • non SUSE employed contributors to the project are experiencing a steady growth (>100% over the last 3 years)
  • we can probably refine the data collected and the presentation to be more representative of the overall growth of the project and not just focus on Factory
  • more details will be provided in a presentation at oSC13
• Overall the vision is to transfer more responsibility to the board and the community
  • Budget discussions are underway and a cost center for openSUSE has already been set up
  • SUSE has to make some tough internal decisions
  • Transferring more responsibility to the community and board is not easy and will require a period of time
    • to this point some responsibility has been transferred but not communicated properly leaving things in an undesirable state
    • communication will be key to the success of the transfer
• The board will want to publicly account for the funds available
  • SUSE has no issue with this and will leave it to the boards discretion
• The openSUSE team does not want to be the "team of last resort" or the "default team" to ask for help
  • this implies that communication paths within the community have to change
    • messages about things previously addressed by the boosters should probably be addressed to the board and or the revamped ambassador program leaders
    • board needs to address this and send a message with changes to the -project list

Meeting with Lars

Lars Vogdt is the team leader for the System Services Team at SUSE and his team is responsible for the maintenance of openSUSE dedicated hardware.

• At present SUSE is the primary sponsor for the hardware that runs the openSUSE infrastructure
  • cost is significant
  • we need more hardware and we need to look for sponsors
  • SUSE is happy to host any sponsored hardware in Nuremberg
• We encouraged Lars to provide the information presented as a presentation at oSC13
  • not many people in the community are aware of the commitment being extended on the hardware side
  • not many people have an understanding of services available
• The team will set up a ticketing system
  • this will help resolve issues quicker
  • help people that run services not controlled by the system team to be alerted when there is an issue with their service
• Proposal of a systems team policy to be shared with the community
  • allow people to better understand what is possible as far as running services on openSUSE infrastructure
• If there are any questions about requests Lars will interact with the board

AI: board review proposed Infrastructure policy and get back to Lars

Ambassador Program Revamp

Richard presents the current state of affairs and why we need to change things up.

• 160+ ambassadors but we have no definition of what is expected of ambassadors, most are not active.
  • Reason for inactivity is most likely that we have no definition about expectations.
• Ambassadors should be members, for 40 or so ambassadors nothing changes, just apply for membership, for those that do nothing the barrier of entry increases
• We should bootstrap a new program rather than try to re-work the existing program. We need a small team of people who would lead that (these people can also act as liaison between the program & the board, work on reports, etc.).
  • reference: https://fedoraproject.org/wiki/Fedora_Ambassadors_Steering_Committee

AI: Richard circulate concrete proposal for discussion

AI: Board create new framework

AI: Approach 3 or 4 members of community directly to help bootstrap the new program

Jos presentation concerning merchandising

• We ship many items to remote locations
  • Often shipping costs outweigh the value of the material
  • It is at times unknown whether the material actually arrives in time or at all
  • Often the event for which the material is shipped is not well defined
  • We ship from various places in an uncoordinated effort
  • Current state is not sustainable, cost and effort
• Going forward we want to have "standard" boxes of promotional material
  • boxes matched to event sizes (small medium, large)
  • content to be determined
  • eventually we can stop shipping "non-perishable" content such as banners
• We need to track who gets boxes
  • allows us to send only version specific content over time and reduce shipping cost
• For smaller events we might want to create a general budget for local production of items

AI: Jos talk with Ancor about integrating promo materials tracking in TSP web app

AI Jos bootstrap list of events we want to send stuff to, and updated it based on feedback

'Web Shop

• We want to be able to
  • have a donate button
  • sell additional items (community designed shirts, plushies)
• But we do not want to create a lot of extra work
• Open questions
  • how to integrate with spreadshirt
  • how to handle logistics
  • how much do we sell currently
  • how does money come back to the project from spreadshirt
  • what is the agreement

AI: Robert initiate conversation with SUSE WebShop team (shop.suse.com) about using instance for shop.opensuse.org

AI: Robert follow up with Henne on Spreadshirt deal

Reimbursement

At present the reimbursement of costs for event attendance and other approved expenses is very slow, we need to find way to improve the process and shorten the time it takes to pay back the money.

• It’s important to make sure that receipts are sent with the reimbursement requests.
• There’s a TSP web app being developed by the openSUSE Team at SUSE that will help track everything, including reimbursement. Should make sure that nothing get lost/forgotten. The new app should go live at the end of the month.
• Current cases need to be addressed on an individual basis

AI: Andrew & Richard to find who’s affected by issues.

AI: Vincent to follow up internally.

Travel Support Program

Izabel is a bit alone in there, and has mentioned several times she might move on. Would be a shame to lose her (because of all the knowledge she accumulated about people & events). New TSP web app should make it easier for others to step up, and should also help Izabel by making her life easier. (Note: Izabel has seen the web app and sent feedback already)

AI: we need to find new volunteers

Foundation

We perceive the primary drivers for a foundation to have been financial transparency/control and increased independence.

• Independence implies more responsibility is to be carried by the community, this process is already underway, although it is under communicated
• Financial transparency/control is closer to realization with the establishment of openSUSE cost center
• Foundation requires paperwork etc. that no one really wants to do
• There would also be an issue of trademarks with SUSE unlikely willing to assign trademark rights to a Foundation that uses the name openSUSE
• Can we get a promise from SUSE about transferring the openSUSE brand should SUSE no longer be interested in the project or fall off the face off the planet?

AI: Robert write draft Foundation report to community

AI: Vincent explore with SUSE to create a promise about maintaining cost center and financial commitment to openSUSE in the long run

Meeting 2013-03-25

Agenda

1. Review action Items
2. Collect topics for Face to Face meeting
3. Bugzilla category for accessibility issues
   1. Issue raised on board mailing list
   2. This is a technical issue, but also says something about us as a community

Minutes

Present: Richard, Andrew, Robert

Missing: Raymond - Company Meeting, Vincent - Customer call, Will - Helping out at home, ill family members

1.) Review Action Items - No board report :( - CLT issues followed up

2.) Face to Face Meeting Agenda - Items collected, ready to post first draft of the agenda to the wiki

3.) Accessibility issue - The proposal raised on the board list is to add a new category to our Bugzilla to clearly mark accessibility issues as such.

There are two main concerns, one is that this is a technical issue and thus the board should keep its fingers out of this issue. The second concern is that creating a specific category may make it easier for people to "pass the buck" by expecting someone in the non existent accessibility team to fix the problem.

Having a separate category for accessibility (a11y) on the other hand will send a clear message that we as the openSUSE community care about people with disabilities. While we have no specific resources to address a11y issues it is important to acknowledge that an a11y issues can easily make the system unusable for a handicapped person.

While adding to the bug category list is definitely a technical issue, the a11y topic has a very large community component and thus the board thinks it is appropriate to act in this area. We can certainly not dictate any action, however a message will be sent to the -factory mailing list asking for consideration of the topic by the developers.

The argument was made that a11y bugs should fit into the categories we already have and that we might easier fall into a "pass the buck" situation with a new category. It is the consensus that we should be able to address the "pass the buck" issue with a policy/procedure. As far as using existing categories is concerned the problem might be that we get into a priority flip flop situation if we do not have a separate category. A person with a disability might mark a bug as Critical, but a developer not fully understanding the consequences might relabel it as category 2 or 3. Having an a11y category would address such priority flip/flop issues.

The board will, after additional discussion on the board list, send a proposal to the -factory list for consideration by the developer community. The proposal will recommend the addition of an a11y category to Bugzilla and a proposal on how to handle the bugs.

Meeting 2013-03-11

Agenda

1. Review Action items
2. CLT issues brought to boards attention

Minutes

Present: Richard, Vincent, Will, Robert, Andrew

Missing: Raymond, on a business trip

1.) Review Action Items

• No progress on board report, Vincent will work on this today
• No reply yet from events team on help request concerning Hackathon organization
• Announcement concerning Pascal's resignation completed

2.) CLT issues

An issue regarding CLT has been brought to the boards attention. It appears that a few things went awry with respect to getting people energized to give talks, man the booth and have hardware available.

One of the underlying issues appears to be a communication and expectation issue. After the reorg at SUSE from the Boosters team to the openSUSE team we have not done a great job in setting expectations and communicated the new channels of communication. The board needs to address this and provide better information to the community. The board will make this one of the topics to be discussed extensively at the face to face meeting in April.

Robert to communicate with the CLT participants that raised the issue about the board discussion and next action items.

We definitely want community members to pick up the ball for events such as CLT and somehow there was an issue in getting everything worked out. We have to improve on the process and make things easier for community members.

Meeting 2013-02-25

Agenda

1. Review Action items
2. Face to Face board meeting
3. Events oSC13, Summit, oSC14
4. Lack of volunteers

Minutes

Present: Vincent, Raymond, Robert, Will

Andrew is participating in a seminar and could not call in

1.) Review Action items

• Board report, no progress yet. Vincent will try to get this done ASAP
• Hackathon organization
  • openSUSE team will help with local organization
  • message from Robert to -project did not result in any volunteers
• Summit
  • Andy is working on Artwork
  • Robert asked Bryan to manage summit.opensuse.org, waiting for response
  • Robert asked Peter Linnell to manage local outreach program, waiting for response
  • Robert will ask Chuck about running keynote speaker search and organize the keynote

2.) Board Face to Face meeting

Everyone is still OK with the dates (April 6 & 7), funds have been approved by SUSE.

Everyone should make their travel arrangements, please arrive Friday PM or early Saturday morning. Inform Vincent of arrival dates so he can book the Hotel.

Meeting will be held in the SUSE Nuremberg offices.

3.) Events

• oSC13
  • looks as if everything is on track
  • CfP was announced last week
• Summit
  • the wheels are starting to roll, see AI review above
• oSC14
  • we have a draft for a location search anouncement everyone needs to review and chime in
  • should go out next Tuesday

4.) Lack of volunteers The call for volunteers to organize Hackathons has resulted in no response. The call for volunteers to help with the Summit had a low response and it appears that it is difficult to get people to step up and be more engaged with non technical issues.

• Should we try to broadcast searches for volunteers to a wider audience then just sending things to the -project list. It appears that we always go back to the same group and always the same people step up (or not).
  • Broadcasting these searches on news.o.o is definitely worth a shot.
  • We should reach out to Universities and advertise the organization of a Hackathon as a course project to business students.

• How can we get more people trained/enthusiastic in organizing events such as a Hackathon?

• All Ambasadors should have a list of things where the openSUSE project is looking for help and show the list at events openSUSE ambassadors participate in.

• Can we find a good place on the wiki or front page to show advertise a "Help wanted" list

Next meeting: 2013-03-11

Meeting 2013-02-11

Agenda

1. Review Action items
2. Face to Face board meeting
3. Monthly board report
4. Hackathon (how do we go about the organization?)
5. openSUSE Summit
6. Sponsor opportunity status update

Minutes

Present: Andrew, Will, Vincent, Robert, Raymond

1.) Review action items

Everything form last meeting complete, spare mediation follow up scheduled two weeks from now.

2.) Face to Face meeting

Waiting for confirmation from SUSE about travel fund availability

3.) Monthly board report

We announced the reports to be on a regular basis, what should "regular basis" be? Every month, every other month, quarterly?

We will stick to a two month report for now to see how things go.

AI: Vincent to send draft to board list by end of this week.

4.) Hackathon organization

The last event was organized by the openSUSE team at SUSE. This group of people does not want to be the main focus to organize Hackathons.

Such sprints should ideally be organized by individual teams, such as KDE, GNOME, etc. However, at this point we do not have the culture within the community to run these events. Until we establish a cadence and culture of hackathons we might need to lean on the openSUSE team to keep organizing the events for a while longer.

As long as Hackathons are on SUSE premises a SUSE employ must be present, thus the openSUSE team will most likely be involved anyway.

AI: Vincent to discuss with SUSE to have someone who enjoys organizing events and has expertise. This does not have to be a full time position.

AI: Robert send a message to -project asking for volunteers

5.) openSUSE Summit

We know that the event is scheduled. We have 3 volunteers at this point but we do not have anyone who is ready to step up and run the show similar to the way Bryan did last year. Robert is willing to run the program committee.

AI: Robert start kicking the tires

6.) OBS sponsorship

We will get 12 ARM boards for OBS, but sponsor will remain anonymous, i.e. their name will not be spread across opensuse.org pages.

Next meeting: 2013-02-25

Meeting 2013-01-28

Agenda

1. Regular board calls
2. Board communication
3. Board action and interaction to community
4. Mediation request
5. Face to Face meeting

Minutes

Board Meeting 01/28/2013: Present: Vincent, Ray, Andrew, Will, Robert

1.) Regular call schedule: This time appears to work for everyone, thus we will stick with :

Monday at 10:00 A.M. EST, 16:00 CEST, 15:00 UTC

Call every other week, cancel if not needed

AI: Vincent setup automatic reminder.

2.) Board communication Communication on the list has been slow at times.

We agree that everyone should respond to messages on the board mailing list within 3 days. If someone is traveling or not able to respond in a timely fashion the team member will notify the list accordingly.

3.) Board action and interaction to community During recent election campaign and prior to the campaign community voiced concern about visibility of the board within the community.

Board Activities page is considered useful by everyone and a good communication tool to the community. We currently do not see the need to have a shared action item tracker. The goal is to reach a level of cohesion within the team such that when a board member is away someone else can step in upon request.

We commit to have public board meeting minutes. Board will post minutes to a wiki within 3 day of the meeting.

AI: Robert will announce the activities page to the -project list this week

4.) Mediation request The board has been asked to mediate a misunderstanding.

Action has been taken and the consensus is to let things rest for a while and see how they play out.

AI: Robert send follow message to involved parties in about 4 weeks.

5.) Face to Face meeting of the board

We agree tat a face to face meeting would be very useful and that waiting until oSC13 is a bit too far out. We will try and arrange a meeting on the weekend of April 6 & 7 in the Nuremberg office.

AI: All members provide travel cost estimates to Vincent AI: Vincent discuss budget with SUSE

6.) Andrew has found a HW sponsorship opportunity

There is an opportunity for the project to get a considerable donation in HW for the openSUSE infrastructure. Review of the current process and some discussions revealed that we probably need to review our sponsorship documents.

AI: Andrew follow up with sponsor to understand their expectations

7.) Hackfest

The recent Hackfest was mostly organized by the openSUSE team at SUSE. It is the desire to have a number of Hackfests throughout the year. However, the openSUSE team at SUSE would prefer the events be organized by the community. We did not come to a conclusion on a good approach to this topic. The board itself cannot organize such events as we would quickly be overwhelmed. This is a topic for the next board meeting.

Meeting concludes 11:05 EST

Next meeting February 11, 2013