https://en.opensuse.org/api.php?action=feedcontributions&user=Cbruckmayer&feedformat=atomopenSUSE Wiki - User contributions [en]2024-03-29T15:30:33ZUser contributionsMediaWiki 1.37.6https://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas_2016&diff=74191openSUSE:GSOC ideas 20162016-02-15T10:43:31Z<p>Cbruckmayer: </p>
<hr />
<div>From this year on we will handle all openSUSE GSoC projects on our brand new [http://101.opensuse.org/ openSUSE Developers Mentoring page]!</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas_2016&diff=73411openSUSE:GSOC ideas 20162015-12-17T16:26:20Z<p>Cbruckmayer: Replaced content with "From this year on we will handle all openSUSE GSoC projects on our brand new [https://opensuse.github.io/mentoring/ openSUSE Developers Mentoring page]!"</p>
<hr />
<div>From this year on we will handle all openSUSE GSoC projects on our brand new [https://opensuse.github.io/mentoring/ openSUSE Developers Mentoring page]!</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=User:Cbruckmayer&diff=73255User:Cbruckmayer2015-12-01T12:40:46Z<p>Cbruckmayer: Created page with "<big><big>'''Christian Bruckmayer'''</big></big> '''Contact:''' * E-Mail: [http://mailto:cbruckmayer@suse.de cbruckmayer@suse.de] * GitHub: [https://github.com/ChrisBr ChrisB..."</p>
<hr />
<div><big><big>'''Christian Bruckmayer'''</big></big><br />
<br />
'''Contact:'''<br />
* E-Mail: [http://mailto:cbruckmayer@suse.de cbruckmayer@suse.de]<br />
* GitHub: [https://github.com/ChrisBr ChrisBr]<br />
* Twitter: [https://twitter.com/bruckmayer @bruckmayer]<br />
<br />
'''Contributions:'''<br />
* [https://github.com/openSUSE/osem Open Source Event Manager (OSEM) developer] <br />
* [https://github.com/openSUSE/open-build-service Open Build Service developer]<br />
* [http://susestudio.com/ SUSE Studio developer]<br />
* [https://www.google-melange.com/gsoc/project/details/google/gsoc2014/cbruckmayer/5685265389584384 Google Summer of Code 2014 student]<br />
* [[Portal:GSOC|Google Summer of Code 2016 admin]]</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=Portal:GSoC/Join&diff=73186Portal:GSoC/Join2015-11-25T14:51:26Z<p>Cbruckmayer: </p>
<hr />
<div>For openSUSE there are several roles in this program and for each of these roles there are different things to do. You can take over any of these roles and make openSUSE's GSoC participation a success. Here is what you can do:<br />
<br />
{{Point here|[[File:Icon-user.png|48px|link=]]|'''Be a GSoC Student'''<br /><br />
<br />
* See which of the ideas you find interesting on our [[openSUSE:GSOC_ideas_2016]] list<br />
* Introduce yourself to the mentor and talk to him about the idea<br />
* Write an awesome proposal. You can find all about writing proposals on our [[openSUSE:GSoC_proposal_template]]<br />
* Mind and follow our [[openSUSE:GSOC_guidelines]]<br />
<br />
For more general information about what it means to be a GSoC student check the [http://en.flossmanuals.net/GSoCStudentGuide/ GSoC Student Guide].<br />
<br />
}}<br />
<br />
{{Point here|[[Image:Icon-keyboard.png|48px|link=]]|'''Be a GSoC Mentor'''<br /><br />
<br />
* Add interesting projects to our [[openSUSE:GSOC_ideas]] list<br />
* Once students contact you, help them to understand what your idea is about<br />
* Help your students to write awesome proposals. You can find all about writing proposals on our [[openSUSE:GSoC_proposal_template]]<br />
* Mind and follow our [[openSUSE:GSOC_guidelines]]<br />
<br />
For more general information about what it means to be a GSoC mentor check the [https://flossmanuals.net/GSoCMentoring/ GSoC Mentor Guide].<br />
<br />
}}<br />
<br />
{{Point here|[[Image:Applications-development.png|48px|link=]]|'''Be a GSoC Admin'''<br /><br />
<br />
If you want to take care of openSUSEs time in GSoC overall, you should join our admin team. You can help gather the list of ideas, work with Google on the [[openSUSE:GSOC_application_form|organization application]], pick students/mentors for the slots, write about the progress and in general take care that the participation of openSUSE in GSoC is a success. Joining is easy, just talk to one of our [[openSUSE:GSoC admins]]! They will tell you what to do.<br />
}}</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas_2015&diff=73185openSUSE:GSOC ideas 20152015-11-25T14:45:13Z<p>Cbruckmayer: Cbruckmayer moved page openSUSE:GSOC ideas 2015 to openSUSE:GSOC ideas 2016</p>
<hr />
<div>#REDIRECT [[openSUSE:GSOC ideas 2016]]</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas_2016&diff=73184openSUSE:GSOC ideas 20162015-11-25T14:45:13Z<p>Cbruckmayer: Cbruckmayer moved page openSUSE:GSOC ideas 2015 to openSUSE:GSOC ideas 2016</p>
<hr />
<div>{{Template:GSOC_navbar}}<br />
<br />
{{Intro|This is a list of ideas for projects which could be done for openSUSE as part of the Google Summer of Code program. If you have an idea and want to mentor it, please add it it to the list. You might also find inspiration on the [[Archive:GSOC_ideas_2014|GSoC 2014 Ideas]] page, [[Archive:GSOC_ideas_2015|GSoC 2015 Ideas]] page or [https://features.opensuse.org/ openFATE].}}<br />
<br />
If you are a student and want to work on an idea, please submit a proposal. You are not limited to the ideas listed here. If you have an own idea or want to approach an idea in a completely different way, feel free to submit this as proposal as well. Sometimes these are the best projects. Creativity and initiative are highly appreciated.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_ideas}}<br />
<br />
__TOC__<br />
<br />
[[Category:Google Summer of Code]]</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas&diff=73030openSUSE:GSOC ideas2015-11-13T13:54:34Z<p>Cbruckmayer: Cbruckmayer moved page Archive:GSOC ideas 2015 to openSUSE:GSOC ideas over redirect</p>
<hr />
<div>#REDIRECT [[openSUSE:GSOC ideas 2015]]</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas&diff=73029openSUSE:GSOC ideas2015-11-13T13:53:49Z<p>Cbruckmayer: Cbruckmayer moved page Archive:GSOC ideas 2015 to openSUSE:GSOC ideas 2015</p>
<hr />
<div>#REDIRECT [[openSUSE:GSOC ideas 2015]]</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas_2016&diff=73028openSUSE:GSOC ideas 20162015-11-13T13:53:49Z<p>Cbruckmayer: Cbruckmayer moved page Archive:GSOC ideas 2015 to openSUSE:GSOC ideas 2015</p>
<hr />
<div>{{Template:GSOC_navbar}}<br />
<br />
{{Intro|This is a list of ideas for projects which could be done for openSUSE as part of the Google Summer of Code program. If you have an idea and want to mentor it, please add it it to the list. You might also find inspiration on the [[Archive:GSOC_ideas_2014|GSoC 2014 Ideas]] page, [[Archive:GSOC_ideas_2015|GSoC 2015 Ideas]] page or [https://features.opensuse.org/ openFATE].}}<br />
<br />
If you are a student and want to work on an idea, please submit a proposal. You are not limited to the ideas listed here. If you have an own idea or want to approach an idea in a completely different way, feel free to submit this as proposal as well. Sometimes these are the best projects. Creativity and initiative are highly appreciated.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_ideas}}<br />
<br />
__TOC__<br />
<br />
[[Category:Google Summer of Code]]</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas_2016&diff=73027openSUSE:GSOC ideas 20162015-11-13T13:10:57Z<p>Cbruckmayer: </p>
<hr />
<div>{{Template:GSOC_navbar}}<br />
<br />
{{Intro|This is a list of ideas for projects which could be done for openSUSE as part of the Google Summer of Code program. If you have an idea and want to mentor it, please add it it to the list. You might also find inspiration on the [[Archive:GSOC_ideas_2014|GSoC 2014 Ideas]] page, [[Archive:GSOC_ideas_2015|GSoC 2015 Ideas]] page or [https://features.opensuse.org/ openFATE].}}<br />
<br />
If you are a student and want to work on an idea, please submit a proposal. You are not limited to the ideas listed here. If you have an own idea or want to approach an idea in a completely different way, feel free to submit this as proposal as well. Sometimes these are the best projects. Creativity and initiative are highly appreciated.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_ideas}}<br />
<br />
__TOC__<br />
<br />
[[Category:Google Summer of Code]]</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:GSOC_ideas_2016&diff=73025openSUSE:GSOC ideas 20162015-11-13T13:02:15Z<p>Cbruckmayer: Cbruckmayer moved page openSUSE:GSOC ideas to Archive:GSOC ideas 2015</p>
<hr />
<div>{{Template:GSOC_navbar}}<br />
<br />
{{Intro|This is a list of ideas for projects which could be done for openSUSE as part of the Google Summer of Code program. If you have an idea and want to mentor it, please add it it to the list. You might also find inspiration on the [[Archive:GSOC_ideas_2013|GSoC 2013 Ideas]] page, [[Archive:GSOC_ideas_2014|GSoC 2014 Ideas]] page or [https://features.opensuse.org/ openFATE].}}<br />
<br />
If you are a student and want to work on an idea, please submit a proposal. You are not limited to the ideas listed here. If you have an own idea or want to approach an idea in a completely different way, feel free to submit this as proposal as well. Sometimes these are the best projects. Creativity and initiative are highly appreciated.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_ideas}}<br />
<br />
__TOC__<br />
<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
== Native Ruby Interface for libyui ==<br />
<br />
* '''Description:'''<br />
There is libyui library which provides single interface for three toolkits (QT, GTK and ncurses). It is heavily used<br />
in YaST and also Mageia uses that for its configuration tool. YaST is now transpiled to ruby and libyui ruby bindings is simple 1:1 to its C++ API. Goal of this project is to design and implement native ruby API built on top of libyui.<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
It is expected that at the end of project there will be design of library, proposal for API and implementation for basic widgets.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[https://github.com/jreidinger Josef Reidinger]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' <br />
** knowledge of ruby idioms and basic ruby libraries - to have idea how good ruby design look like<br />
** API design<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
Looks at existing frameworks and its API like [https://github.com/shoes/shoes4 shoes], [https://github.com/glurp/dsl-gtk dsl-gtk] or [http://blog.rugui.org/2009/01/hello-rugui/ hello-rugui/] and then post to yast-devel@opensuse.org mailing list own proposal how new API can look like together with at least two examples of code that uses such API.<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Apache Initial Setup YaST Module ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
Write a new YaST module for apache that do initial setup of apache with given framework so it allows easy start. Module use cases are:<br />
<br />
** I want to quickly setup apache with static HTML<br />
** I want to quickly setup apache with PHP<br />
** I want to quickly setup apache with RoR<br />
** I want to quickly setup apache with django<br />
** I want to quickly setup apache with mocculus<br />
<br />
etc. with frameworks you are interested. Module is focused for newbies with basic setup. It is not intended to modify existing configuration. It should include also install of needed packages.<br />
<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
YaST module that can do initial setup with static html pages and at least one of frameworks. The module include documentation and tests.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[https://github.com/jreidinger/ Josef Reidinger]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' <br />
** Ruby<br />
** Rspec<br />
** Object oriented design<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Easy<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
Read new [http://yast.github.io/yast-journalctl-tutorial/ tutorial] and write question or suggestions how to improve it to yast-devel@opensuse.org mailing list.<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Deploy Scenarios for OSEM ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
The [http://osem.io Open Source Event Manager] is an event management app tailored to Free Software Conferences, it is developed in the [http://rubyonrails.org/ Ruby on Rails] web framework. There is currently next to no code/config/help for deploying OSEM to either develop, testing or using it in production. <br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
This project is about adding support for deploying OSEM with IaaS, PaaS or even SaaS providers Amazon EC2, Heroku or Arckcloud. This project includes adopting the OSEM code, developing and documenting strategies and packages/images/containers.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[[User:Hennevogel|Hennevogel]] ([[User talk:Hennevogel|talk]])<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' <br />
You know your way around a Ruby on Rails application and can tell the difference between a My and Postre SQL database. You have deployed applications to Heroku. Elastic Compute, Docker and Vagrant are not all Greek to you.<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Hard<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Volunteer Management for OSEM ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
The [http://osem.io Open Source Event Manager] is an event management app tailored to Free Software Conferences, it is developed in the [http://rubyonrails.org/ Ruby on Rails] web framework. Free Software conferences often depend on volunteers, recruited from the visitors, for on-site tasks like the registraition desk, room/track moderation, video taping or cleaning up. This project is about adding volunteer management to OSEM.<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
Design a volunteer management workflow and describe it in our RSpec test suite. Develop Ruby on Rails Model(s) that describe the volunteer data. Develop Ruby Rails Controller(s) that interact with the volunteer model(s). Design and Develop a HTML/CSS/Javascript interface for Volunteer Management.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[[User:Hennevogel|Hennevogel]] ([[User talk:Hennevogel|talk]])<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:'''<br />
** Ruby <br />
** Ruby on Rails<br />
** RSpec<br />
** HTML5, CSS3, Javascript<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
== Parser for SPEC file for spec-cleaner project ==<br />
* '''Description:'''<br />
spec-cleaner is a project hosted in [https://github.com/openSUSE/spec-cleaner github] that is planned to be replacement for "osc service localrun format_spec_file". It is intended to provide same or better features in order for us to be able to unify all the spec files in obs.<br />
<br />
The current implementation use a set of regular expression to detect certain patterns that can be improved by the spec-cleaner tools. The limitation of a regular expression is that is complex (or impossible) to express certain transformation in the document. A better approximation is create a parser that understand the grammar of the spec file, and create the AST tree that reflect the original file. In this way, the refactorization process can be done in the AST tree directly, instead of using regex for that.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[http://en.opensuse.org/User:aplanas aplanas]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:'''<br />
** Python<br />
** Knowledge the spec file<br />
** How to make a parser<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
** Medium to hard<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Alternatives YaST Module ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
openSUSE, as other distributions, includes the command [http://linux.die.net/man/8/update-alternatives update-alternatives] in order to allow users to choose which program they want to be the default for every given function (which text editor, which Java implementation and so on). Being quite prominent in other distributions, update-alternatives does not get the attention it deserves in openSUSE. The project consists on implementing a [http://yast.github.io/ YaST] module for managing the alternatives and their priority, offering an easy and guided interface on top of plain update-alternatives.<br />
<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
A YaST module offering a clear overview of all the alternatives in the system and a convenient way to manage their configuration and priorities. The module must conform to the [http://yast.github.io/guidelines.html YaST development guidelines], which means, among other things, that it must include unit tests (RSpec).<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[https://github.com/ancorgs/ Ancor González Sosa]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' <br />
** Ruby<br />
** Rspec<br />
** Object oriented design<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Easy<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
Read the new [http://yast.github.io/yast-journalctl-tutorial/ YaST tutorial] and write question or suggestions on how to improve it to yast-devel@opensuse.org mailing list.<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
-<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Build Service: Add ARM64 ILP32 support for obs ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
This idea want the ilp32 support in obs which make life easier to make LP64 rootfs + ILP32 libs and/or pure ILP32 rootfs.<br />
<br />
ILP32 is a method for running 32bit application on 64bit platform, such binary is elf32 with aarch64 assembly and is compiled by 64bit compiler. It is the alternative ABI supported by arm64. The default ABI on arm64 is LP64. X32 is the ILP32 implementation on x86_64(x86_64 platform support i386, x32, and x86_64).<br />
<br />
There are gcc(upsteamed), kernel(during review) and glibc(during review) support for ilp32. And yocto for ILP32 is in process.<br />
<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
Basically, it is expected that at the end of project there will be a ILP32 support in JeOS(pure ILP32 JeOS and/or LP64 root with ILP32 libs).<br />
<br />
Further more, some testbench(such as LTP, lmbench) could be compiled in ILP32 in order to test ilp32 support status.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[[User:Bamvor|Bamvor]] ([[User talk:Bamvor|talk]])<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:'''<br />
** Knowledge in deply obs server.<br />
** Knowledge in arm64 architecture.<br />
** Familiar osc, rpm and relative command.<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
Add ilp32 support for rpm. reference x32 support for rpm:<br />
https://sites.google.com/site/x32abi/x32-patches/rpm-4.11-x32-1.patch<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
== Zorp ==<br />
=== IDS/IPS Integration ===<br />
<br />
* '''Description:''' The goal of this project is to integrate the Suricata IDS/IPS system with an application level firewall to combine the advantages of the two different technologies.<br />
* '''Deliverable:''' An integrated system where<br />
** Suricate uses Zorp as an SSL terminator<br />
** Zorp uses Suricata automatic protocol detection feature to start the necessary proxy<br />
** Zorp passes extracted data to Suricata for further analysis<br />
* '''Mentor:''' Szilárd Pfeiffer<br />
* '''Skills:''' <br />
** willingness to learn new stuff<br />
** computer networks<br />
** network security<br />
** Linux networking<br />
* '''Skill Level:''' Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
=== Authentication as Rule Condition ===<br />
* '''Description:''' The goal of this project is to make it possible to set up firewall rules what can contain authentication as condition.<br />
* '''Deliverable:'''<br />
** a user space daemon which can handle authentication request coming from kZorp<br />
** an implementation of package queuing which can delay packets during authentication<br />
** modified kZorp module capable making decisions depending on authentication results<br />
* '''Mentor:''' Szilárd Pfeiffer<br />
* '''Skills:''' <br />
** willingness to learn new stuff<br />
** computer networks<br />
** network security<br />
** Linux network programming<br />
** Linux kernel programming<br />
** daemon programming<br />
** Python<br />
* '''Skill Level:''' High<br />
* '''Byte Sized tasks for students to get involved:'''<br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Code Review tool Github and Trello based ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
We have a tool for assigning reviewer for a particular pull request [1]<br />
We need to extend that tool to be able to run standalone and as a Rails engine.That requires re-factoring of the codebase to <br />
be able to use internal model of Rails and be able to run via Sequel backed database.<br />
[1] https://github.com/jschmid1/reviewlette<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
New version of a gem which can be used both in standalone mode and in Rails engine mode.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
[https://github.com/kalabiyau Artem Chernikov]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' <br />
** Ruby<br />
** RSpec<br />
** Rails<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
* Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
** Come up with idea of the re-factoring phases. What should be done first, what next.<br />
** Refactor application to be easily extendable<br />
** Implement Database abstraction which will allow to use either standalone DB or Rails backed DB<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Build an openSUSE version ad-hoc for x86_64 tablets shipped with UEFI at 32 bits ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
The idea should consist in building an openSUSE version ad-hoc for<br />
x86_64 tablets shipped with UEFI at 32 bits (i.e. Asus Transformer<br />
Book T100 and so on). This is an interesting issue since currently no<br />
distribution offer support for this kind of tablets (the only one I've<br />
heard to work is GParted live!). On the other hand, this kind of<br />
tablets cost less than an ultrabook and similar. So they are a<br />
growing market for both Linux in general and openSUSE in particular.<br />
<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
Build an openSUSE version ad-hoc for x86_64 tablets shipped with UEFI at 32 bits <br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' mailto:glin@suse.com<br />
<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' C, Linux Kernel, Grub<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
A new kernel option, CONFIG_EFI_MIXED, was added recently, and it allows<br />
the 64-bit kernel to be loaded from 32-bit UEFI. I didn't check the details,<br />
but this might be a good start. If this works, the rest would be the structure<br />
of the ISO image and the modification of the installation process.<br />
<br />
https://bugzilla.suse.com/show_bug.cgi?id=901061<br />
<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== ownCloud : API client libraries ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
ownCloud provides several APIs like WebDAV and OCS to do operations like accessing files, managing shares, managing users, etc. To make it easier for developers to integrate their external applications or scripts with ownCloud, API client libraries should be developed that provide classes/functions that call such APIs in a way that is easy to use for the library user. Such a library should be developed for other programming languages like Ruby, Go, Javascript (Node JS), etc. One example is the [https://github.com/PVince81/pyocclient Python ownCloud client library]. Ideally such libraries should have a similar class/module structure and use similar function names and signatures, for consistency. Test suites must be present to test the provided functions against real ownCloud instances.<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
Write an API client library for a chosen target language that cover files, sharing (and optionally users management too)<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
Vincent Petry (PVince81 on IRC freenode: #ownCloud-dev)<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:'''<br />
Knowledge about the said chosen language and about calling REST APIs<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== ownCloud: New App Store ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
The current App Store suffers from multiple problems, the biggest being maintainability, ergonomics and duplication. In order to ease app publishing and installation, a new solution should be developed based on Node.js because the traffic is mainly IO intensive. This App Store offers a user signup page and a RESTful API to publish and unpublish apps and retrieve apps and zips. The initial implementation should handle only GitHub but should be extendable by plugins. [https://github.com/Raydiation/appstore-ng A spec is already available] but can always be adjusted.<br />
A testsuite for the API should be created and unit tests should be written using jasmine<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
A RESTful API for managing applications with a web signup for app devs<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
Bernhard Posselt (Raydiation on IRC freenode : #ownCloud-dev)<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:'''<br />
Node.js, Node.js frameworks, RESTful APIs, Git, TDD, BDD, Jasmine<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Medium<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== ownCloud: Reference Management App (similar to [https://www.zotero.org/ Zotero]) ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
[https://en.wikipedia.org/wiki/Reference_management_software Reference management software] helps researchers to keep their personal libraries organised. One of the most used reference manager is [https://www.zotero.org/ Zotero]. Whereas it is already possible to keep the files stored by Zotero synced through ownCloud via webDAV, the sync of meta-data requires an Zotero server. The ownCloud reference app will help the users to collect, handle and sync metadata of papers that are uploaded to ownCloud storage. For details see [https://www.zotero.org/support/sync this page] the Zotero and [https://mail.kde.org/pipermail/owncloud/2012-April/002838.html this discussion] on the ownCloud mailing list.<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
The project consists of implementing an ownCloud app to store metadata from research articles and, if time permits, a browser (Firefox/Chrome) plugin that interfaces the app. The ownCloud app needs to do at least the following things:<br />
# scan ownCloud filesystem (or a selected folder) for PDF files.<br />
# extract metadata from these files using some PHP library, such as [https://github.com/smalot/pdfparser pdfparser].<br />
# allow the user to annotate pdf files and store annotations (the format of which needs to be decided)<br />
<br />
* '''Alternative Suggestion:'''<br />
Making ownCloud based UI for native Zotero WebDAV data. Zotero already excels in web clipping and organising, but lacks comfortable data storage solutions, and still has no independent web interface. ownCloud app could fill the gap.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
Alessandro Cosentino (cosenal on IRC : freenode : #ownCloud-dev)<br />
<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:'''<br />
minimal: PHP and Javascript<br />
preferred: AngularJS<br />
It's definitely a plus if the student has experience with reference management software.<br />
<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Medium<br />
<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== ownCloud : ownCloud as backend for web apps ==<br />
<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
* '''Description:'''<br />
An [https://unhosted.org/ unhosted] web app is an application that runs entirely in the browser. Since unhosted web apps do not have a database or storage server of their own, they rely on the user to connect their own per-user storage at runtime. Also when an application does have a server, it can be more efficient to let the client-side code communicate directly with an API, instead of letting all traffic go via the application server as an extra hop. The idea of this GSoC project is to<br />
<br />
# add CORS headers to the API<br />
# add support for the implicit-grant flow to ownCloud's OAuth dialog<br />
# publish a small javascript library that makes it easy to use the ownCloud API in an unhosted web app.<br />
<br />
To get an idea of what this would look like, check out the JavaScript libraries provided by for instance [https://developers.google.com/api-client-library/javascript/ Google Drive] or [https://blogs.dropbox.com/tech/2012/08/some-love-for-javascript-applications-2/ Dropbox].<br />
<br />
<!-- Expectations from the student at the end of the project--><br />
* '''Deliverable:'''<br />
Support for cross-origin API access in ownCloud, a small JavaScript library, and some documentation, aimed at html5 app developers, describing how to use it. With this, it will be possible to "log in" to a website with your ownCloud instance as your personal data storage, and all user data on this website will come from, and be saved to, your ownCloud account.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
# @michielbdejong on Github<br />
# Jan-Christoph Borchardt (@jancborchardt on Github, jancborchardt on IRC freenode : #ownCloud-dev)<br />
<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:'''<br />
JavaScript, PHP, basic understanding of HTTP debugging (browser developer tools as well as WireShark or similar), capacity to understand the complex request flows of both CORS and OAuth.<br />
<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:'''<br />
Medium / Difficult<br />
<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
<br />
== Trello command line client ==<br />
<!-- General information about the project (Avoid one Liners, Description should be as detailed as possible)--><br />
=== Description ===<br />
[https://github.com/openSUSE/trollolo Trollolo] is a command line client for [http://trello.com Trello]. It can be used to retrieve data in various ways. Its two main features are generation of burndown for teams using Scrum and backup of Trello boards. These features can be improved quite a bit and there is virtually unlimited opportunity to come up with other interesting ideas how to improve the tool and add support for interesting additional use cases.<br />
<br />
For the generation of burndown charts possible tasks and projects could be:<br />
<br />
* Automatic upload of burndown charts<br />
* Tracking velocity<br />
* Better configurability to be able to adapt to a wider variety of projects<br />
* Support for sprint planning<br />
* Support for agile estimation techniques<br />
* Displaying history of project<br />
* ...<br />
<br />
For the backup of Trello boards possible tasks and projects could be:<br />
<br />
* Restoring boards<br />
* Show diffs between different versions of the board<br />
* Handling attachments<br />
* Store backups under version control<br />
* Display of backups on the command line<br />
* ...<br />
<br />
Other projects could be:<br />
<br />
* Membership management for organizations<br />
* Generator for board templates from existing boards<br />
* Validator of boards according to given criteria (given lists, format of titles, existence of checklists)<br />
* Cross-referencer to create and validate two-way links between cards. This would be useful for cases where you have hierarchies of cards distributed between different lists and you want to keep the link status up to date without manual work. Use case could be managing requirements where you go from vision over high-level user scenarios to low-level use cases.<br />
* ...<br />
<br />
As an interesting twist all these projects could be done in a self-hosting way by managing the project with the tools which are developed.<br />
<br />
<!-- Expectations from the student at the end of the project--><br />
=== Deliverable===<br />
<br />
Tested, working, released version of Trollolo containing shiny new feature.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
=== Mentor ===<br />
Cornelius Schumacher <cschum@suse.de><br />
<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
=== Skills ===<br />
<br />
* Ruby<br />
* RSpec<br />
* TDD<br />
* Command line tools<br />
* REST APIs<br />
* JSON<br />
<br />
<!-- Easy, Medium, Hard--><br />
=== Skill Level ===<br />
<br />
Medium<br />
<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
=== Byte Sized tasks for students to get involved ===<br />
<br />
* Take an issue of CodeClimate and refactor the code to fix it<br />
* Add a test for a method which isn't tested yet<br />
* Add a new sub command of your choice which does something useful<br />
<br />
== Puppet: openSUSE improvements in puppet modules ==<br />
<br />
* '''Description:'''<br />
[http://puppetlabs.com Puppet] is configuration management tool. Its recent best practises allows us to structure our modules in [http://garylarizza.com/blog/2014/02/17/puppet-workflow-part-2/ Base, Profiles and Roles], for better use of third party modules from the [https://forge.puppetlabs.com forge]. Most of the forge modules though have limited to no openSUSE support.<br />
<br />
* '''Deliverable:'''<br />
Popular forge modules should have openSUSE support, along with proper tests. Also, openSUSE specific modules like [http://forge.puppetlabs.com/darin/zypprepo zypprepo] should be improved.<br />
<br />
* '''Mentor:'''<br />
Theo Chatzimichos <tampakrap@opensuse.org><br />
<br />
* '''Skills:''' <br />
Ruby, Puppet DSL, Puppet Types and Providers, RSpec, rspec-puppet<br />
<br />
* '''Skill Level:'''<br />
Medium<br />
<br />
<!-- Byte Sized tasks that mentors may want to suggest students so that they can start contributing to the code base as soon as possible --><br />
* '''Byte Sized tasks for students to get involved:'''<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
== MATE Desktop ==<br />
<br />
The MATE Desktop Environment is the continuation of GNOME 2. It provides an intuitive and attractive desktop environment using traditional metaphors for Linux and other Unix-like operating systems.<br />
<br />
Read the page to learn how to get started with MATE Desktop development.<br />
<br />
* http://wiki.mate-desktop.org/contribute<br />
<br />
If you have questions or suggestions, you could contact MATE developers through IRC or our mailing list.<br />
<br />
* '''IRC:''' #mate-dev channel on irc.freenode.net.<br />
* '''Mailing list:''' MATE development mailing list web interface is located at http://ml.mate-desktop.org/listinfo/mate-dev<br />
<br />
=== MATE Desktop media casting ===<br />
* '''Description:''' Create a Caja plugin that can be used to cast audio and video content via DLNA/uPNP, Chromecast and Miracast protocols. <br />
* '''Deliverable:''' A plugin that supports GTK2 and GTK3 which extends the Send-to context menu in Caja when right clicking on audio and video so that they can be cast to compatible device on the local network.<br />
* '''Mentors:'''<br />
** Stefano Karapetsas (stefano-k in IRC)<br />
** Martin Wimpress (flexiondotorg in IRC)<br />
* '''Skills:''' Most MATE applications are written in C. We have also few applications and applets written in Python. Almost all applications have Python bindings generated with [https://live.gnome.org/GObjectIntrospection GObject introspection].<br />
** C<br />
** Python<br />
** GLib<br />
** GTK<br />
** Knowledge of GStreamer, DLNA/uPNP and Chromecast and Miracast protocols is advantageous.<br />
* '''Skill Level:''' Hard<br />
* '''References:'''<br />
** https://developers.google.com/cast/<br />
** http://www.freedesktop.org/wiki/Software/miracle/libwfd/<br />
** https://github.com/albfan/miraclecast<br />
** http://coherence.beebits.net/wiki/Nautilus<br />
** https://github.com/palfrey/coherence<br />
* '''Student:'''<br />
<br />
=== MATE Desktop mobile device integration ===<br />
* '''Description:''' Create a panel applet that can interact with notifications from mobile devices.<br />
* '''Deliverable:''' It shall be possible to receive to incoming messages from Android devices on the MATE desktop. It shall also be possible to transfer links, text snippets and files, using Caja Send-to, between MATE desktop and Android devices. The panel applet should also display the Android device power and signal status. The implementation should be flexible so that other mobile platforms (such as iOS, Ubuntu Touch and Sailfish) can be supported in the future. If technically feasible, add support for composing messages and replying to messages directly from MATE desktop. Ideally work directly with KDEConnect to add MATE support to KDEConnect rather than create a separate project or fork. The implementation must support GTK2 and GTK3.<br />
* '''Mentors:'''<br />
** Stefano Karapetsas (stefano-k in IRC)<br />
** Martin Wimpress (flexiondotorg in IRC)<br />
* '''Skills:''' Most MATE applications are written in C. We have also few applications and applets written in Python. Almost all applications have Python bindings generated with [https://live.gnome.org/GObjectIntrospection GObject introspection].<br />
** C<br />
** Python<br />
** GLib<br />
** GTK<br />
** Qt and KDE would be advantageous given KDEConnect currently relies on both.<br />
* '''Skill Level:''' Medium<br />
* '''References:'''<br />
** https://community.kde.org/KDEConnect<br />
** https://github.com/vikoadi/indicator-kdeconnect<br />
** https://albertvaka.wordpress.com/<br />
* https://github.com/hauckwill/linconnect-server<br />
** https://github.com/hauckwill/linconnect-client<br />
* '''Student:'''<br />
<br />
=== MATE Window Manager (Marco) GPU accelerated compositing ===<br />
* '''Description:''' Add GPU accelerated compositing to Marco, the MATE window manager to supplement (but not replace) the existing software compositor. <br />
* '''Deliverable:''' MATE is planning to add Wayland support in the future and this would be an important step towards that. While full Wayland support is not possible within the scope of this project, the design and implementation shall be mindful of future Wayland compatibility. A screen magnifier shall also be added that will function with compositing (software or hardware) enabled or disabled and be integrated with the accessibility key bindings in mate-settings-daemon. Better compatibility/integration with Client Side Decorations (CSD or header bar) shall be added to Marco ideally this should not be dependent on a compositor being enabled. The implementation must support GTK2 and GTK3.<br />
* '''Mentors:'''<br />
** Stefano Karapetsas (stefano-k in IRC)<br />
** Martin Wimpress (flexiondotorg in IRC)<br />
* '''Skills:''' Most MATE applications are written in C. We have also few applications and applets written in Python. Almost all applications have Python bindings generated with [https://live.gnome.org/GObjectIntrospection GObject introspection].<br />
** C<br />
** Python<br />
** GLib<br />
** GDK<br />
** GTK<br />
* '''Skill Level:''' Hard<br />
* '''References:'''<br />
** https://github.com/chjj/compton<br />
** https://git.gnome.org/browse/mutter/<br />
** https://git.gnome.org/browse/metacity/<br />
** https://github.com/linuxmint/muffin<br />
** https://projects.kde.org/projects/kde/workspace/kwin<br />
** http://git.r-36.net/xzoom/<br />
** CSD compatibility<br />
*** https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744249 - Discussion and a proposed design that would require upstream GTK involvement<br />
*** https://github.com/linuxmint/muffin/commit/57680ced5d0989ff0810317e4ff0e2333b449488<br />
*** https://github.com/linuxmint/muffin/commit/d627d8f100ecd6abfafcd207975f5e9e89aba8c5<br />
* '''Student:'''<br />
<br />
=== MATE Panel Renovation ===<br />
* '''Description:''' The MATE Panel is the principle component for user interaction with the MATE Desktop and it requires several usability enhancements, improvements and fixes. <br />
* '''Deliverable:''' <br />
** Panels arranged in a vertical orientation need an improved look and feel.<br />
*** https://github.com/mate-desktop/mate-panel/issues/157<br />
*** https://github.com/mate-desktop/mate-panel/issues/269<br />
** Panel applets get displaced when screen resolutions are changed, this shall be fixed.<br />
*** https://github.com/mate-desktop/mate-panel/issues/84<br />
*** https://github.com/mate-desktop/mate-panel/issues/255<br />
** Panels should leverage compositors (when they are enabled) for auto hiding and applying transparencies. In the case of auto hiding panels this will stop the hidden panels from “hiding” to the adjacent screen, and therefore always visible in multi monitor configurations.<br />
** MPRIS2 integrated sound applet. The Sound Indicator in Ubuntu can interact with MPRIS2 compatible media player, with play/pause, track skip and access to media applications and sound preferences. This shall be added the existing MATE sound applet.<br />
** Alternative menu with integrated launcher. MATE already provides two menus but lacks an integrated launcher. A new menu applet shall be developed that include tranditional menu navigation and a launcher.<br />
** There are some applets (mate-netspeed, mate-indicator-applet) that live outside the mate-applet repository, they shall be consolidated in to mate-applets<br />
** There is duplicate functionality in various panel applets (Calendar and Weather both have weather for example, the is a power manager and battery applet). Duplicate functionality should be consolidated into one applet.<br />
** mate-indicator-applet is currently compatible with GTK2 but shall be made compatible with GTK2 and GTK3.<br />
** Squash bugs in https://mate-desktop.org/mate-desktop/mate-panel/<br />
** The implementation must support GTK2 and GTK3.<br />
* '''Mentors:'''<br />
** Stefano Karapetsas (stefano-k in IRC)<br />
** Martin Wimpress (flexiondotorg in IRC)<br />
* '''Skills:''' Most MATE applications are written in C. We have also few applications and applets written in Python. Almost all applications have Python bindings generated with [https://live.gnome.org/GObjectIntrospection GObject introspection].<br />
** C<br />
** Python<br />
** GLib<br />
** GDK<br />
** GTK<br />
* '''Skill Level:''' Medium<br />
* '''References:'''<br />
** Sound applet<br />
*** https://code.launchpad.net/indicator-sound<br />
** Menu with launcher GNOME main menu (now maintained by MATE) has a basic launcher functionality.<br />
*** https://git.gnome.org/browse/gnome-main-menu<br />
*** http://gottcode.org/xfce4-whiskermenu-plugin/<br />
** Indicator GTK2 and GTK3 compatibility<br />
** http://goodies.xfce.org/projects/panel-plugins/xfce4-indicator-plugin<br />
** https://code.launchpad.net/ubuntu/+source/xfce4-indicator-plugin<br />
* '''Student:'''</div>Cbruckmayerhttps://en.opensuse.org/index.php?title=openSUSE:BetaPizzaPartyNBGAttendees&diff=72133openSUSE:BetaPizzaPartyNBGAttendees2015-09-28T13:59:13Z<p>Cbruckmayer: </p>
<hr />
<div>__NOTOC__<br />
Please add yourself to the list below if you run our openSUSE-Leap-42.1-Beta (or Factory) and want to join our [[openSUSE:BetaPizzaParty]] in Nürnberg.<br />
This is needed to plan the amount of Pizza.<br />
<br />
<br />
===What: BetaPizzaParty===<br />
===Where: Germany, Nuremberg, Maxfeldstr. 5, EBC===<br />
[http://maps.google.de/maps?q=49.45958,11.0825&hl=de&ll=49.459608,11.08252&spn=0.0007,0.002064&sll=49.459772,11.082665&sspn=0.0014,0.004128&vpsrc=6&gl=de&t=h&z=20 map]<br />
<br />
===When: 2015-10-02 13:00 UTC (15:00 CEST) ===<br />
<br />
===Who: all openSUSE-Leap-42.1-Beta-users===<br />
===Why: fun & food===<br />
<br />
{|style="border:3px solid #aaa;" border="1" class="wikitable sortable"<br />
!Attendee<br />
!# Machines running Leap-42.1-Beta<br />
|-<br />
|[[User:ddemaio|Douglas DeMaio]]<br />
|1<br />
|-<br />
|[[User:aplanas|Alberto Planas]]<br />
|0<br />
|-<br />
|[[User:a_faerber|Andreas Färber]]<br />
|0; Factory: 13<br />
|-<br />
|[[User:bmwiedemann|Bernhard Wiedemann]]<br />
|0 (soon 1); Factory: 3<br />
|-<br />
|[[User:msmeissn|Marcus Meissner]]<br />
|0; Tumbleweed: 2<br />
|-<br />
|[[User:BenniBrunner|Benjamin Brunner]]<br />
|0; Factory: 2<br />
|-<br />
|[[User:trenn|Thomas Renninger]]<br />
|Factory: 1;<br />
|-<br />
|[[User:favogt|Fabian Vogt]]<br />
|2; Factory: 2;<br />
|-<br />
|[[User:cschum|Cornelius Schumacher]]<br />
|Tumbleweed: 1<br />
|-<br />
|[[User:guohouzuo|Howard Guo]]<br />
|Tumbleweed: 4, Leap: 1.<br />
|-<br />
|[[User:jdsn|Daniel Schmidt]]<br />
|Leap: 0 (soon 1)<br />
|-<br />
|[[User:noiz777|Mauro Morales]]<br />
|Tumbleweed: 1<br />
|-<br />
|[[User:cbruckmayer|Christian Bruckmayer]]<br />
|Tumbleweed: 1<br />
|-<br />
|[[User:wengel|Wolfgang Engel]]<br />
|Leap: 1<br />
|-<br />
|}</div>Cbruckmayer