Some feedback has been given related to Meegathon 'rules' and how the text is formatted. We will not change the nature of the competition anymore, but some approvements can be done so that it is more easy to read and understand. Here's the original - current - public version: <snip> Meegathon Competition Meegathon is a hacker type of competition, much like a hack-a-thon. The following competition will take place between Fri 12:00am and Sat 12:00am. In other words, teams have 24 hours time to finish their project. Meegathon is both a software development and hardware innovation competition, with the emphasis on software. Teams participating in the competition can choose their own topic or use the scenario provided below. The purpose of the competition is to produce new open innovative software or improvements to existing open source projects. The judges will expect the projects to be targeted at MeeGo but if the project is useful for the larger open source community - even better. On Saturday all teams will demonstrate their results to the judges. The best projects will be presented to summit participants by at least one team member. The best inventions and innovations will be awarded. Judges will evaluate projects according to three main categories. - Innovation; Create, renew or change something into new. - OSS contribution; Openness, Transparency and Consensus. - On-site hacking bonus While you can start working on your project today, we don’t want to see projects being ready before the summit. We really want to see on-site hacking and therefore we have added it as one of the project evaluation categories. Judges may give special nominations for best hardware innovation, best software innovation and best OSS contribution. The public’s favourite will be nominated as well. Project rules - At least one member of the project team needs to be at the summit. - Use MeeGo operating system version 1.1 or higher or equivalent platform. - The end product can be demoed with MeeGo reference hardware (Nokia N900, a netbook, or other equivalent) Team rules - max 3 developers. - no limitations to member origin (eg from corporate, hackerspaces, LUG's, etc) If the team is sponsored by corporation or includes only corporation employees, it MUST be stated in project description. Hacking spaces All teams have a dedicated space in which to build stuff on the second floor. The space is a big hall, which is divided into smaller areas. A separate space for small-scale crafting and possibly even welding will be created. If you know that your project needs tools, the best solution is to bring them with you. The space in which you will build your project, is monitored at all times. Prizes - Hardware from Nokia and Intel Reference project The competition reference project topic is AR.Drone and using it with MeeGo 1.1 or higher. Scenario Your solution (program, library, new hardware) will be used in a Quadricopter (Parrot Wi-Fi quadricopter). Solutions should contribute something new to controlling the device in different situations such as gaming, surveillance and new use cases. Solutions which replace existing ones with better ones are accepted and highly-valued. In other words, your solution /demo will run on some device, which in turn controls the quadricopter. You don’t have to start from the scratch. Some work has been done already: - AR.Drone open API (https://projects.ardrone.org/) includes SDK. - MAR-drone in Maemo (https://garage.maemo.org/scm/?group_id=1999) In an ideal world, all efforts would be aimed at producing a good AR-library, which could be used in other applications, create a AR-multiplayer hub and protocol. Features developed could be (but are not limited to): - guncam, - scoring system, - player position tracking, - damage system. Project subjects are related to Linux / Qt / QML / Qt MeeGo components. - Qt based AR library module/modules - Extending AR.Drone library with new features (including add-on type solutions) - Hardware hacking (AR, RC) - Own subject Additional info and safety regulations - keep the project size within reasonable limits, e.g. no monster cars or full scale helicopters. - In those projects, which are mostly HW, you are required to build as much as possible in advance. Ideally you just do assembly at the venue and make the final adjustments. Small-scale craftwork is possible at the venue. - All pyrotechnics and acid based solutions are forbidden! - Be prepared to present your innovation to the Summit audience/participants on Saturday afternoon. - And the last: Have Fun! All teams MUST register in advance to participate in the competition. The number of teams is limited, so be quick! Organizers reserve the right to make minor alternations to competition scenarios and judging categories. </snip> Comments given (below) in IRC (copy pasteing since it the channel is public channel after all). Hopefully jarkko^ is not offended. <snip> 13:07 < jarkko^> somehow the competition page coud state things in shorter form 13:07 < jarkko^> after reading the page i got confused because i thought the competition concerns only ardrone 13:07 < jarkko^> and that contradicts the longish introduction 13:08 < jarkko^> what is this competition about? what can be considered as a competition entry? and clear statement that ardrone is only an example of a possible project 13:08 < jarkko^> anwers to those short questions is scattered all around the document 13:09 < jarkko^> if i would not read the page through from start to end 13:09 < jarkko^> i would have only checked first "project rules" without reading the overly long introduction 13:10 < jarkko^> and then checked that aha you must make something for ardrone in this competition 13:10 < jarkko^> information is there but the page is not well structured 13:10 < jarkko^> this my pov from the perspective that i haven't read anything related to the competition from this channel 13:10 < jarkko^> only the competition page 13:14 < jarkko^> i'm not participating to the competitions but anyway i think better structuring could increase participation.. 13:19 < smoinen> jarkko^: points taken, we'll try to simplify things 13:20 < jarkko^> to put it short: it could use editing/refactoring round :) information is there, just restructure it 13:22 < smoinen> if you already have concrete ideas for the meegathon page, please share. it always speeds up things :) 13:23 < smoinen> how to refactor etc 13:32 < jarkko^> I would rename the chapter project rules to competition rules and explain there also what is a proper competition entry 13:32 < jarkko^> and cut the introduction as short as possible 13:33 < jarkko^> also i would use only one heading size (wikis tend to have almost same size for all headings) and just use bold for subheadings 13:34 < jarkko^> And I would rename the section topic "Reference" as "Example of an entry: improvemnts to the ardrone" 13:35 < jarkko^> maybe there could be one main section "Competition rules" that would contain subsections project structure, team and competition entry 13:36 < jarkko^> and after that another main section "Example:" </snip> Thanks for the feedback jarkko^. Any other comments before we adjust the text? I'd like to avoid multiple rounds in editing. This (feedback) would have been nice to have a month ago when we were formatting the text, but post release feedback is good too. /Jarkko -- --------------- Community Manager (MNFI, Meego Network Finland) Organizer (TMN, Tampere Meego Network) Email: jarkko dot moilanen at meegonetwork dot fi Location: Tampere, Finland More info: http://meegonetwork.fi Discussions: irc.freenode.net#meego-fi http://meego.ajatukseni.net/