https://en.opensuse.org/api.php?action=feedcontributions&user=Wwarlock&feedformat=atomopenSUSE Wiki - User contributions [en]2024-03-29T13:00:05ZUser contributionsMediaWiki 1.37.6https://en.opensuse.org/index.php?title=User:Wwarlock&diff=62215User:Wwarlock2013-07-29T07:34:08Z<p>Wwarlock: putting up a redirect</p>
<hr />
<div>#REDIRECT [[User:Shayonj]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=59075Archive:GSOC ideas 20142013-03-11T12:31:07Z<p>Wwarlock: /* Discussion System for the Open Build Service */</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_2012|GSoC 2012 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 />
<!-- Problem description short enough to catch attention. --><br />
== Port bento to twitter bootstrap ==<br />
<!-- General information, as much as needed, but not more. --><br />
* '''Description:''' The [https://github.com/openSUSE/opensuse-themes/tree/master/bento openSUSE bento] theme was supposed to be the great UI unification of all our web-pages. But it only came so far as adding a unified theming and some UI elements, most notably the top bar. Nowadays there is a great collection of HTML UI "libs" like twitter bootstrap that achieve way more. If we could port bento over to bootstrap we would reach the initial goal we set out to reach. The mentors would prefer to use the [http://openbuildservice.org Open Build Service (OBS)] as reference implementation for this project.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [https://connect.opensuse.org/pg/profile/hennevogel Henne Vogelsang], [https://connect.opensuse.org/pg/profile/coolo Stephan Kulow]<br />
<!-- Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' HTML, CSS, Javascript, Ruby on Rails, GIT<br />
<!-- Easy, Medium, Hard --><br />
* '''Skill Level:'''Medium<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Problem description short enough to catch attention. --><br />
<br />
== Discussion System for the Open Build Service ==<br />
<!-- General background information, as much as needed, but not more. --><br />
* '''Description:''' There are a lot of "objects" like packages, projects, patches etc. in the [http://openbuildservice.org Open Build Service] that would greatly benefit from user feedback. The goal of this project is to add some way of discussing those objects in the OBS by means of either an external commenting system like [https://github.com/phusion/juvia juvia] or by adding the functionality to the OBS objects directly. <br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [https://connect.opensuse.org/pg/profile/hennevogel Henne Vogelsang], [https://connect.opensuse.org/pg/profile/coolo Stephan Kulow]<br />
<!-- Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' HTML/CSS, Javascript, Ruby on Rails, GIT<br />
<!-- Easy, Medium, Hard --><br />
* '''Skill Level:'''Medium/Hard (depends on the implementation route)<br />
<!-- Student name goes here --><br />
* '''Student:'''[[User:wwarlock|Shayon Mukherjee]](Interested)<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
<br />
== Tar Extractor ==<br />
<!-- General information about the project--><br />
* '''Description:''' When I was starting with Linux, I found the concept of dealing with tar.gz files rather archaic. I believe a GUI could be produced to handle the functions necessary to perform these actions making a simple procedure even easier and less daunting to new Linux users. Concept preview: [https://docs.google.com/file/d/0B-CAUbBxV6ZuMFhiUGlGel9FVXc/edit?usp=sharing Concept GUI]<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' ?<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' ?<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' ?Medium<br />
<!-- Student name goes here --><br />
* '''Student:''' Scott DuBois<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== A GNOME3 like package manager module for YaST ==<br />
<!-- General information about the project--><br />
* '''Description:''' The package manager module is arguably the most used module in YaST. Unfortunately the present gtk(-3.0) version of the package manager module (libyui-gtk4), looks and feels a little from the yesteryear. It would be an educative as well as exciting project to develop a more GNOME3 like GUI based package manager from the scratch using the latest GNOME3 tools. In this regard, the excellent GNOME documents application can serve as a good template for the interface, but the package manager should in addition also provide filters for showing packages by category, repository, etc.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' Javascript, gtk3, libyui (the yast libraries)<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' Hard<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== openSUSE News/Planet on Android ==<br />
<!-- General information about the project--><br />
* '''Description: '''openSUSE news and planet are a great source of information on what is happening in the project, and what the contributors are upto. It would be great to have an Android app, which would notify users about new posts on these platforms. There could also be an option to watch posts by specific authors, and view by languages. A good interface would be integral to the app.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''[https://connect.opensuse.org/pg/profile/manugupt1 Manu Gupta]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills: '''Android<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level: '''Easy - Medium<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
== [[Portal:Build_Service|Open Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== SUSE Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio. Think git for [http://www.susestudio.com SUSE Studio]. You checkout an appliance, make some changes for it (locally) and once you are happy with the appliance you commit the changes to [http://www.susestudio.com SUSE Studio].<br />
<br />
Example use case<br />
<source lang="bash" style="overflow:auto"><br />
$ ssc appliance create web_server --source-id=SOURCE_APPLIANCE_ID --username=USERNAME --password=PASSWORD<br />
$ cd web_server<br />
$ ssc package list<br />
$ ssc package add apache<br />
$ ssc file add /etc/apache2/apache2.conf<br />
$ ssc commit<br />
</source><br />
<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Essential: Community involvement, introduce yourself on the opensuse-project mailing list. (this probably applies to all other projects as well)<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
=== SUSE Studio Java Client SDK ===<br />
<br />
[https://github.com/susestudio/susestudio-lib-java SUSE Studio Java Client] is a Java based library to interact with the [http://susestudio.com SUSE Studio] image store and appliances toolkit. The library is supposed to enable developers to easily implement SUSE Studio client applications in Java, even for mobile platforms like Android. The implementation however is at the moment still a work in progress and only very basic parts of the [http://susestudio.com/help/api/v2 REST API] are currently covered.<br />
<br />
The project goal is therefore to bring on the development of this library as much as possible, while ideally the whole API functionality should be covered by the implementation. The interface should be designed in a way so that developers will be able to write beautiful code using this library. Further it would be nice to have a suite of unit tests, so we can automatically ensure the overall functionality of the code and data model at any time using continuous integration tools like Jenkins.<br />
<br />
It would be a big plus for your application, if you propose to implement new software based on this SDK instead of just working on the library itself. This might be a mobile app for Android, a new web application or anything else, as far as it makes sense. Feel free to come up with your own ideas!<br />
<br />
Please find the existing code and documentation [https://github.com/susestudio/susestudio-lib-java here] and the SUSE Studio API documentation [http://susestudio.com/help/api/v2 here].<br />
<br />
'''Required knowledge:''' Java, HTTP and REST, unit testing and continuous integration<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
=== SUSE Studio Amazon EC2 scripts ===<br />
<br />
SUSE Studio allows you to easily build customized Amazon EC2 AMIs (Amazon Machine Images). While you can directly push and launch them from Studio to Amazon EC2, it is sometimes preferred to download the raw images and do this yourself. For example, you can automate a deployment workflow with Studio's WebHook API to download a new AMI when it is available, and then automatically push it to all EC2 regions, launch, test and swap them out for production use.<br />
<br />
The project at https://github.com/susestudio/susestudio-ec2 allows one to easily upload and create these AMIs from the downloaded Studio images. This project is to extend the existing code.<br />
<br />
'''Required knowledge:''' Bash/Shell scripting, Amazon EC2 knowledge preferred.<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== SUSE StudioCheck ===<br />
<br />
[[http://en.opensuse.org/openSUSE:GSOC_ideas#SUSE_Studio:_StudioCheck_automated_test_framework | See entry in section QA]]<br />
----<br />
<br />
==Cross-distribution topics==<br />
The openSUSE project is proudly pushing cross-distribution collaboration.<br />
<br />
=== Compositor Colour Management ===<br />
Colour Management has to be easy for casual developers and automatic for users. To get there it is an good idea to have all applications colour corrected inside the window manager. On the other side graphics applications, want to do own colour management and should be able to say a window shall not be colour managed. To do so easily exists the [http://www.freedesktop.org/wiki/OpenIcc#X_Color_Management_spec X Color Management] spec and the implementation of this protocol in libXcm.<br />
<br />
The ICC based colour correction is easy for compositing window managers, as they support mostly shaders. Shaders run on the GPU and allow for a very fast and efficient colour correction.<br />
<br />
The project targets at providing colour management inside a compositing window manager of your choice. The protocol part to be implemented is the Baseline spec with _ICC_COLOR_OUTPUTS and additional the _ICC_COLOR_PROFILES atom.<br />
<br />
This implementation prepared a easy transition into Wayland compositor colour management, which will as well be window based.<br />
<br />
A good and very fast start is the update the [http://compicc.sf.net CompICC] plug for Compiz-0.8, to use the _ICC_COLOR_OUTPUTS atom.<br />
<br />
'''Required knowledge:''' OpenGL, GPU shaders, Oyranos, C<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Gtk Front End to Oyranos ===<br />
The [http://www.oyranos.org Oyranos project] is a cross desktop and cross OS colour management system (CMS) to provide easy to use and while robust colour management services to applications. The main goal of Oyranos is to provide colour management without user interaction. But in some situations and especially experts might want to configure and tweak the various settings manually.<br />
<br />
Front ends exist in Qt and for KDE. For Gtk based Desktop Environments it is currently only possible to use the Qt front end. For a better appearance and integration it makes sense to provide a native Gtk GUI for settings and configuration.<br />
<br />
'''Required knowledge:''' Gtk, Oyranos, C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== OpenICC Colour Configuration Data Base ===<br />
Users, who configure their colour management system (CMS) behaviour and devices, want to share these settings on one host without any intervention among installed CMSes. The project will introduce the OpenICC data base into CMSes like ArgyllCMS, Oyranos and colord and replaces existing own DB access code.<br />
<br />
device DB example: http://www.freedesktop.org/wiki/Specifications/icc_meta_tag_for_monitor_profiles<br />
<br />
existing code: http://openicc.git.sourceforge.net/git/gitweb.cgi?p=openicc/openicc;a=tree<br />
<br />
'''Required knowledge:''' C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
'''Links:'''<br />
<br />
=== On-demand Symbolic Memory ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem is that often the input to a program (or its part) is unknown in advance. So checkers use a hack that they pass large symbolic buffer as input and hope that it is large enough.<br />
<br />
This is slow, inconvenient and does not help in cases where the buffer is a structure or an array of them. The members of the structure, especially pointers, are uninitialized and point to NULL.<br />
<br />
Instead, an on-demand symbolic buffer should be created. That ensures that NULL members are allocated on-the-fly and input arrays extended as needed. This was described in a paper called "Practical, low-effort equivalence verification of real code". Unfortunately the source code is not available. So the task of the student here is to implement this to klee, present that it works on examples provided by the mentor (parts of the Linux kernel code) and make the tool available to wide public.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Concolic Symbolic Execution ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem with symbolic execution is that it gets lost very early if the code uses non-linear computations like comparing integers to hashes of other inputs or finding a number 'x' where x^3 == ~0.<br />
<br />
The cure for this is a parallel symbolic and concrete execution. If the symbolic execution cannot reason about some input, it asks the concrete one and vice versa. It is well-described in some papers.<br />
<br />
The student should implement this technique to klee and demonstrate how it improves performance of the symbolic execution.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:'''<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== MirrorBrain: buffer-cache-friendly mirror selection ===<br />
<br />
MirrorBrain is the framework that openSUSE uses to redirect downloads to mirror servers. <br />
<br />
It would be possible to select mirrors intelligently with the purpose of optimizing the usage of the buffer caches of the mirrors. Right now, if openSUSE is released, all CD/DVD images are downloaded from all mirror servers. It would need many GB of buffer cache on the mirrors to keep the images in memory, usually more than physically available. Now, it would be very clever if the redirector could send redirects for DVD 1 to a certain mirror (group of mirrors), and send requests to DVD 2 to another mirror (group of mirrors). The question is how to recognize situations where this is possible, and how make this happen without administrative effort. A solution has been proposed (http://postr.poeml.de/a-buffer-cache-friendly-mirror-selection-algo) and it seems to work by proof-of-concept testing. <br />
<br />
To implement this, some hacking on mod_mirrorbrain.c is needed. A prerequisite is to understand how the current mirror selection works and how to add the further algorithm to it.<br />
<br />
Mirrors (and thereby, indirectly, its users, i.e. all of us) should benefit from this selection algorithm, because they would need to read less data from their disks.<br />
<br />
'''Required knowledge:''' C programming, HTTP and networking<br />
<br />
'''Skill level:''' intermediate (high?)<br />
<br />
'''Mentor:'''<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
== QA ==<br />
=== SUSE Studio: StudioCheck automated test framework ===<br />
<br />
This project is a abstraction of the Studio API to have the ability of creating test cases using a gherkin syntax. A prototype of the core system was created and is working, now the remaining items are the creation of abstraction steps and some reporting interface to get more than just a list of results for easier consumption.<br />
<br />
'''Required knowledge:''' Ruby, Rails, gherkin/BDL based tests<br />
<br />
'''Skill level:''' Depending on task Easy to Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:'''<br />
<br />
=== LTP:Fix/Implement automated kernel/glibc tests ===<br />
<br />
The [http://sourceforge.net/projects/ltp/ Linux Test Project] is huge collection of testcases aiming to test stability and correctness of kernel/glibc implementation and as the time goes by, some of the testcases needs polishing and testcases for newly introduced features should be written.<br />
<br />
'''Required knowledge:''' C, low level Linux/POSIX interface<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement alternative backends ===<br />
<br />
The [http://openqa.opensuse.org/ openQA/OS-autoinst testing framework] provides reliable continuous quality feedback about current openSUSE-Factory, Debian (and potentially other distributions).<br />
Currently the service relies on kvm for the testing (an alternative VirtualBox backend exists), but to test things, that need real hardware such as NVidia/ATI drivers, it needs a different backend. One idea is to use Net::VNC to interact with the machine-under-test and another is to use HDMI-capturing hardware (e.g. from Blackmagic for 200€) and hardware that can generate keystrokes to emulate user-input.<br />
<br />
'''Required knowledge:''' perl<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement web-based test creator ===<br />
(for description of openQA see above)<br />
Creating/modifying test modules currently requires people to use a text-editor to create/change perl module files.<br />
Having an interactive web-based test-module editor/creator (could be similar to a user-input recorder) would allow easier creation of test-modules.<br />
<br />
'''Required knowledge:''' perl, AJAX<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
== openSUSE System Management ==<br />
=== Automatic resizing of LVM volumes and filesystems ===<br />
<br />
openSUSE currently provides good support for creating LVM volumes and installing the OS<br />
on these volumes. However, if the filesystem becomes full, the user/administrator has to increase the volume size and contained filesystem capacity manually.<br />
<br />
The goal of this project would be to implement automatic resizing of LVM <br />
volumes and contained filesystems. This resizing would be triggered e.g.<br />
by the package manager before installing the packages, if the free space drops<br />
before certain threshold etc. The installer should be modified to compute the <br />
necessary space needed for installing the selected set of packages and allocate<br />
the LVM volumes 'just big enough' for the installation. With future automatic<br />
resizing of the LVM/FS, this would save storage capacity in the volume group<br />
which would otherwise be unnecessarily allocated for /, /usr etc.<br />
<br />
'''Required knowledge:''' At least basic experience with C/C++, RPM, scripting<br />
(Python, bash). Understanding of LVM is a plus, but not necessary. Willingness to learn and investigate is a must.<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
== Implementing Accurate XML Code Formatting ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
* ''Create Readable Source Code Formatting for XML''<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
* '''Background:'''<br />
There are some tools which can format XML/HTML sourcecode (tidy, xmlformat, ...). <br />
For example, xmlformat splits elements in an inline, block, and verbatim (=code) category. In most cases this works fine, but sometimes it fails.<br />
<br />
This tool could be improved by, for example using XPath expressions or by<br />
reading schemas (DTD, RNG, ...) to know more about the structure<br />
and how to format it. This would (hopefully) lead to a more exact<br />
formatting (think of mixed contents)<br />
<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
* '''Mentor:''' <br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
* '''Skill Level:''' Intermediate<br />
<br />
Perl or C experience. Knowledge of XML and/or XPath is desirable. Depending on the project plan, DTD would also be useful.<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
* '''Student:''' STUDENT NEEDED<br />
<br />
== Virtualization ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
===Upstream Xen Support for Libvirt===<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
The libvirt project provide a common and stable layer for different virtualization technology, including Xen, KVM, qemu and other hypervisors. Xen is one of the most important virtualization technology supported by openSUSE. But there are lots of changes from Xen-unstable, which lead to libvirt unused in lots of occasion. <br />
<br />
The gual of this project is to update libvirt for the xen-unstable. Most of the work may be update for the latest xenlight driver in libvirt. <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:'''<br />
<br />
'''Required knowledge:''' C<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Intermediate<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
<br />
== Code review for projects on GitHub ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
The goal of this project is to extend [https://github.com/b4mboo/git-review git-review] to make code review from the command line interface even simpler.<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
A lot of our projects have moved their code to [https://github.com GitHub]. Using pull requests is a comfortable way to collaborate on projects hosted there and if done in a browser there is also a nice UI for it. <br />
However, since most developers use the command line for all of their git operations anyways, git-review was created to add some commands to git and thus enable developers to handle code review from the command line, too.<br />
<br />
For productive use git-review needs code coverage and added functionality that allows developers to work on different forks of a project.<br />
For further information please take a look at the project's list of open [https://github.com/b4mboo/git-review/issues issues].<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:'''<br />
<br />
'''Required knowledge:''' Ruby, Git, RSpec<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Medium<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Project Title ==<br />
<!-- General information about the project--><br />
* '''Description:''' The openSUSE project provides the most choice in software stacks at many levels compared to other distributions. We would like to continue this "tradition" in the Cloud management infrastructure area. We already have OpenNebula and OpenStack. OpenNebula is the most complete offering with packages documentation and an appliance example. The OpenStack packages are building and the framework has been tested, yet we lack documentation around setup and configuration. For Eucalyptus and OpenStack our packages are way behind upstream and work is needed to move the packages forward. For both OpenStack and Eucalyptus the project includes everything from beginning to end until we have a presentable solution along the lines of the OpenNebula setup shown at https://en.opensuse.org/SDB:Cloud_OpenNebula<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [[User:rjschwei|Robert Schweikert]]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' Packaging, Perl, Python, Java<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' Medium<br />
<!-- Student name goes here --><br />
* '''Student:''' needed</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=59074Archive:GSOC ideas 20142013-03-11T12:30:55Z<p>Wwarlock: /* Port bento to twitter bootstrap */</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_2012|GSoC 2012 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 />
<!-- Problem description short enough to catch attention. --><br />
== Port bento to twitter bootstrap ==<br />
<!-- General information, as much as needed, but not more. --><br />
* '''Description:''' The [https://github.com/openSUSE/opensuse-themes/tree/master/bento openSUSE bento] theme was supposed to be the great UI unification of all our web-pages. But it only came so far as adding a unified theming and some UI elements, most notably the top bar. Nowadays there is a great collection of HTML UI "libs" like twitter bootstrap that achieve way more. If we could port bento over to bootstrap we would reach the initial goal we set out to reach. The mentors would prefer to use the [http://openbuildservice.org Open Build Service (OBS)] as reference implementation for this project.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [https://connect.opensuse.org/pg/profile/hennevogel Henne Vogelsang], [https://connect.opensuse.org/pg/profile/coolo Stephan Kulow]<br />
<!-- Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' HTML, CSS, Javascript, Ruby on Rails, GIT<br />
<!-- Easy, Medium, Hard --><br />
* '''Skill Level:'''Medium<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Problem description short enough to catch attention. --><br />
<br />
== Discussion System for the Open Build Service ==<br />
<!-- General background information, as much as needed, but not more. --><br />
* '''Description:''' There are a lot of "objects" like packages, projects, patches etc. in the [http://openbuildservice.org Open Build Service] that would greatly benefit from user feedback. The goal of this project is to add some way of discussing those objects in the OBS by means of either an external commenting system like [https://github.com/phusion/juvia juvia] or by adding the functionality to the OBS objects directly. <br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [https://connect.opensuse.org/pg/profile/hennevogel Henne Vogelsang], [https://connect.opensuse.org/pg/profile/coolo Stephan Kulow]<br />
<!-- Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' HTML/CSS, Javascript, Ruby on Rails, GIT<br />
<!-- Easy, Medium, Hard --><br />
* '''Skill Level:'''Medium/Hard (depends on the implementation route)<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Tar Extractor ==<br />
<!-- General information about the project--><br />
* '''Description:''' When I was starting with Linux, I found the concept of dealing with tar.gz files rather archaic. I believe a GUI could be produced to handle the functions necessary to perform these actions making a simple procedure even easier and less daunting to new Linux users. Concept preview: [https://docs.google.com/file/d/0B-CAUbBxV6ZuMFhiUGlGel9FVXc/edit?usp=sharing Concept GUI]<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' ?<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' ?<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' ?Medium<br />
<!-- Student name goes here --><br />
* '''Student:''' Scott DuBois<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== A GNOME3 like package manager module for YaST ==<br />
<!-- General information about the project--><br />
* '''Description:''' The package manager module is arguably the most used module in YaST. Unfortunately the present gtk(-3.0) version of the package manager module (libyui-gtk4), looks and feels a little from the yesteryear. It would be an educative as well as exciting project to develop a more GNOME3 like GUI based package manager from the scratch using the latest GNOME3 tools. In this regard, the excellent GNOME documents application can serve as a good template for the interface, but the package manager should in addition also provide filters for showing packages by category, repository, etc.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' Javascript, gtk3, libyui (the yast libraries)<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' Hard<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== openSUSE News/Planet on Android ==<br />
<!-- General information about the project--><br />
* '''Description: '''openSUSE news and planet are a great source of information on what is happening in the project, and what the contributors are upto. It would be great to have an Android app, which would notify users about new posts on these platforms. There could also be an option to watch posts by specific authors, and view by languages. A good interface would be integral to the app.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''[https://connect.opensuse.org/pg/profile/manugupt1 Manu Gupta]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills: '''Android<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level: '''Easy - Medium<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
== [[Portal:Build_Service|Open Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== SUSE Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio. Think git for [http://www.susestudio.com SUSE Studio]. You checkout an appliance, make some changes for it (locally) and once you are happy with the appliance you commit the changes to [http://www.susestudio.com SUSE Studio].<br />
<br />
Example use case<br />
<source lang="bash" style="overflow:auto"><br />
$ ssc appliance create web_server --source-id=SOURCE_APPLIANCE_ID --username=USERNAME --password=PASSWORD<br />
$ cd web_server<br />
$ ssc package list<br />
$ ssc package add apache<br />
$ ssc file add /etc/apache2/apache2.conf<br />
$ ssc commit<br />
</source><br />
<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Essential: Community involvement, introduce yourself on the opensuse-project mailing list. (this probably applies to all other projects as well)<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
=== SUSE Studio Java Client SDK ===<br />
<br />
[https://github.com/susestudio/susestudio-lib-java SUSE Studio Java Client] is a Java based library to interact with the [http://susestudio.com SUSE Studio] image store and appliances toolkit. The library is supposed to enable developers to easily implement SUSE Studio client applications in Java, even for mobile platforms like Android. The implementation however is at the moment still a work in progress and only very basic parts of the [http://susestudio.com/help/api/v2 REST API] are currently covered.<br />
<br />
The project goal is therefore to bring on the development of this library as much as possible, while ideally the whole API functionality should be covered by the implementation. The interface should be designed in a way so that developers will be able to write beautiful code using this library. Further it would be nice to have a suite of unit tests, so we can automatically ensure the overall functionality of the code and data model at any time using continuous integration tools like Jenkins.<br />
<br />
It would be a big plus for your application, if you propose to implement new software based on this SDK instead of just working on the library itself. This might be a mobile app for Android, a new web application or anything else, as far as it makes sense. Feel free to come up with your own ideas!<br />
<br />
Please find the existing code and documentation [https://github.com/susestudio/susestudio-lib-java here] and the SUSE Studio API documentation [http://susestudio.com/help/api/v2 here].<br />
<br />
'''Required knowledge:''' Java, HTTP and REST, unit testing and continuous integration<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
=== SUSE Studio Amazon EC2 scripts ===<br />
<br />
SUSE Studio allows you to easily build customized Amazon EC2 AMIs (Amazon Machine Images). While you can directly push and launch them from Studio to Amazon EC2, it is sometimes preferred to download the raw images and do this yourself. For example, you can automate a deployment workflow with Studio's WebHook API to download a new AMI when it is available, and then automatically push it to all EC2 regions, launch, test and swap them out for production use.<br />
<br />
The project at https://github.com/susestudio/susestudio-ec2 allows one to easily upload and create these AMIs from the downloaded Studio images. This project is to extend the existing code.<br />
<br />
'''Required knowledge:''' Bash/Shell scripting, Amazon EC2 knowledge preferred.<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== SUSE StudioCheck ===<br />
<br />
[[http://en.opensuse.org/openSUSE:GSOC_ideas#SUSE_Studio:_StudioCheck_automated_test_framework | See entry in section QA]]<br />
----<br />
<br />
==Cross-distribution topics==<br />
The openSUSE project is proudly pushing cross-distribution collaboration.<br />
<br />
=== Compositor Colour Management ===<br />
Colour Management has to be easy for casual developers and automatic for users. To get there it is an good idea to have all applications colour corrected inside the window manager. On the other side graphics applications, want to do own colour management and should be able to say a window shall not be colour managed. To do so easily exists the [http://www.freedesktop.org/wiki/OpenIcc#X_Color_Management_spec X Color Management] spec and the implementation of this protocol in libXcm.<br />
<br />
The ICC based colour correction is easy for compositing window managers, as they support mostly shaders. Shaders run on the GPU and allow for a very fast and efficient colour correction.<br />
<br />
The project targets at providing colour management inside a compositing window manager of your choice. The protocol part to be implemented is the Baseline spec with _ICC_COLOR_OUTPUTS and additional the _ICC_COLOR_PROFILES atom.<br />
<br />
This implementation prepared a easy transition into Wayland compositor colour management, which will as well be window based.<br />
<br />
A good and very fast start is the update the [http://compicc.sf.net CompICC] plug for Compiz-0.8, to use the _ICC_COLOR_OUTPUTS atom.<br />
<br />
'''Required knowledge:''' OpenGL, GPU shaders, Oyranos, C<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Gtk Front End to Oyranos ===<br />
The [http://www.oyranos.org Oyranos project] is a cross desktop and cross OS colour management system (CMS) to provide easy to use and while robust colour management services to applications. The main goal of Oyranos is to provide colour management without user interaction. But in some situations and especially experts might want to configure and tweak the various settings manually.<br />
<br />
Front ends exist in Qt and for KDE. For Gtk based Desktop Environments it is currently only possible to use the Qt front end. For a better appearance and integration it makes sense to provide a native Gtk GUI for settings and configuration.<br />
<br />
'''Required knowledge:''' Gtk, Oyranos, C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== OpenICC Colour Configuration Data Base ===<br />
Users, who configure their colour management system (CMS) behaviour and devices, want to share these settings on one host without any intervention among installed CMSes. The project will introduce the OpenICC data base into CMSes like ArgyllCMS, Oyranos and colord and replaces existing own DB access code.<br />
<br />
device DB example: http://www.freedesktop.org/wiki/Specifications/icc_meta_tag_for_monitor_profiles<br />
<br />
existing code: http://openicc.git.sourceforge.net/git/gitweb.cgi?p=openicc/openicc;a=tree<br />
<br />
'''Required knowledge:''' C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
'''Links:'''<br />
<br />
=== On-demand Symbolic Memory ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem is that often the input to a program (or its part) is unknown in advance. So checkers use a hack that they pass large symbolic buffer as input and hope that it is large enough.<br />
<br />
This is slow, inconvenient and does not help in cases where the buffer is a structure or an array of them. The members of the structure, especially pointers, are uninitialized and point to NULL.<br />
<br />
Instead, an on-demand symbolic buffer should be created. That ensures that NULL members are allocated on-the-fly and input arrays extended as needed. This was described in a paper called "Practical, low-effort equivalence verification of real code". Unfortunately the source code is not available. So the task of the student here is to implement this to klee, present that it works on examples provided by the mentor (parts of the Linux kernel code) and make the tool available to wide public.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Concolic Symbolic Execution ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem with symbolic execution is that it gets lost very early if the code uses non-linear computations like comparing integers to hashes of other inputs or finding a number 'x' where x^3 == ~0.<br />
<br />
The cure for this is a parallel symbolic and concrete execution. If the symbolic execution cannot reason about some input, it asks the concrete one and vice versa. It is well-described in some papers.<br />
<br />
The student should implement this technique to klee and demonstrate how it improves performance of the symbolic execution.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:'''<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== MirrorBrain: buffer-cache-friendly mirror selection ===<br />
<br />
MirrorBrain is the framework that openSUSE uses to redirect downloads to mirror servers. <br />
<br />
It would be possible to select mirrors intelligently with the purpose of optimizing the usage of the buffer caches of the mirrors. Right now, if openSUSE is released, all CD/DVD images are downloaded from all mirror servers. It would need many GB of buffer cache on the mirrors to keep the images in memory, usually more than physically available. Now, it would be very clever if the redirector could send redirects for DVD 1 to a certain mirror (group of mirrors), and send requests to DVD 2 to another mirror (group of mirrors). The question is how to recognize situations where this is possible, and how make this happen without administrative effort. A solution has been proposed (http://postr.poeml.de/a-buffer-cache-friendly-mirror-selection-algo) and it seems to work by proof-of-concept testing. <br />
<br />
To implement this, some hacking on mod_mirrorbrain.c is needed. A prerequisite is to understand how the current mirror selection works and how to add the further algorithm to it.<br />
<br />
Mirrors (and thereby, indirectly, its users, i.e. all of us) should benefit from this selection algorithm, because they would need to read less data from their disks.<br />
<br />
'''Required knowledge:''' C programming, HTTP and networking<br />
<br />
'''Skill level:''' intermediate (high?)<br />
<br />
'''Mentor:'''<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
== QA ==<br />
=== SUSE Studio: StudioCheck automated test framework ===<br />
<br />
This project is a abstraction of the Studio API to have the ability of creating test cases using a gherkin syntax. A prototype of the core system was created and is working, now the remaining items are the creation of abstraction steps and some reporting interface to get more than just a list of results for easier consumption.<br />
<br />
'''Required knowledge:''' Ruby, Rails, gherkin/BDL based tests<br />
<br />
'''Skill level:''' Depending on task Easy to Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:'''<br />
<br />
=== LTP:Fix/Implement automated kernel/glibc tests ===<br />
<br />
The [http://sourceforge.net/projects/ltp/ Linux Test Project] is huge collection of testcases aiming to test stability and correctness of kernel/glibc implementation and as the time goes by, some of the testcases needs polishing and testcases for newly introduced features should be written.<br />
<br />
'''Required knowledge:''' C, low level Linux/POSIX interface<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement alternative backends ===<br />
<br />
The [http://openqa.opensuse.org/ openQA/OS-autoinst testing framework] provides reliable continuous quality feedback about current openSUSE-Factory, Debian (and potentially other distributions).<br />
Currently the service relies on kvm for the testing (an alternative VirtualBox backend exists), but to test things, that need real hardware such as NVidia/ATI drivers, it needs a different backend. One idea is to use Net::VNC to interact with the machine-under-test and another is to use HDMI-capturing hardware (e.g. from Blackmagic for 200€) and hardware that can generate keystrokes to emulate user-input.<br />
<br />
'''Required knowledge:''' perl<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement web-based test creator ===<br />
(for description of openQA see above)<br />
Creating/modifying test modules currently requires people to use a text-editor to create/change perl module files.<br />
Having an interactive web-based test-module editor/creator (could be similar to a user-input recorder) would allow easier creation of test-modules.<br />
<br />
'''Required knowledge:''' perl, AJAX<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
== openSUSE System Management ==<br />
=== Automatic resizing of LVM volumes and filesystems ===<br />
<br />
openSUSE currently provides good support for creating LVM volumes and installing the OS<br />
on these volumes. However, if the filesystem becomes full, the user/administrator has to increase the volume size and contained filesystem capacity manually.<br />
<br />
The goal of this project would be to implement automatic resizing of LVM <br />
volumes and contained filesystems. This resizing would be triggered e.g.<br />
by the package manager before installing the packages, if the free space drops<br />
before certain threshold etc. The installer should be modified to compute the <br />
necessary space needed for installing the selected set of packages and allocate<br />
the LVM volumes 'just big enough' for the installation. With future automatic<br />
resizing of the LVM/FS, this would save storage capacity in the volume group<br />
which would otherwise be unnecessarily allocated for /, /usr etc.<br />
<br />
'''Required knowledge:''' At least basic experience with C/C++, RPM, scripting<br />
(Python, bash). Understanding of LVM is a plus, but not necessary. Willingness to learn and investigate is a must.<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
== Implementing Accurate XML Code Formatting ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
* ''Create Readable Source Code Formatting for XML''<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
* '''Background:'''<br />
There are some tools which can format XML/HTML sourcecode (tidy, xmlformat, ...). <br />
For example, xmlformat splits elements in an inline, block, and verbatim (=code) category. In most cases this works fine, but sometimes it fails.<br />
<br />
This tool could be improved by, for example using XPath expressions or by<br />
reading schemas (DTD, RNG, ...) to know more about the structure<br />
and how to format it. This would (hopefully) lead to a more exact<br />
formatting (think of mixed contents)<br />
<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
* '''Mentor:''' <br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
* '''Skill Level:''' Intermediate<br />
<br />
Perl or C experience. Knowledge of XML and/or XPath is desirable. Depending on the project plan, DTD would also be useful.<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
* '''Student:''' STUDENT NEEDED<br />
<br />
== Virtualization ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
===Upstream Xen Support for Libvirt===<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
The libvirt project provide a common and stable layer for different virtualization technology, including Xen, KVM, qemu and other hypervisors. Xen is one of the most important virtualization technology supported by openSUSE. But there are lots of changes from Xen-unstable, which lead to libvirt unused in lots of occasion. <br />
<br />
The gual of this project is to update libvirt for the xen-unstable. Most of the work may be update for the latest xenlight driver in libvirt. <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:'''<br />
<br />
'''Required knowledge:''' C<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Intermediate<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
<br />
== Code review for projects on GitHub ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
The goal of this project is to extend [https://github.com/b4mboo/git-review git-review] to make code review from the command line interface even simpler.<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
A lot of our projects have moved their code to [https://github.com GitHub]. Using pull requests is a comfortable way to collaborate on projects hosted there and if done in a browser there is also a nice UI for it. <br />
However, since most developers use the command line for all of their git operations anyways, git-review was created to add some commands to git and thus enable developers to handle code review from the command line, too.<br />
<br />
For productive use git-review needs code coverage and added functionality that allows developers to work on different forks of a project.<br />
For further information please take a look at the project's list of open [https://github.com/b4mboo/git-review/issues issues].<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:'''<br />
<br />
'''Required knowledge:''' Ruby, Git, RSpec<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Medium<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Project Title ==<br />
<!-- General information about the project--><br />
* '''Description:''' The openSUSE project provides the most choice in software stacks at many levels compared to other distributions. We would like to continue this "tradition" in the Cloud management infrastructure area. We already have OpenNebula and OpenStack. OpenNebula is the most complete offering with packages documentation and an appliance example. The OpenStack packages are building and the framework has been tested, yet we lack documentation around setup and configuration. For Eucalyptus and OpenStack our packages are way behind upstream and work is needed to move the packages forward. For both OpenStack and Eucalyptus the project includes everything from beginning to end until we have a presentable solution along the lines of the OpenNebula setup shown at https://en.opensuse.org/SDB:Cloud_OpenNebula<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [[User:rjschwei|Robert Schweikert]]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' Packaging, Perl, Python, Java<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' Medium<br />
<!-- Student name goes here --><br />
* '''Student:''' needed</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=59073Archive:GSOC ideas 20142013-03-11T12:30:33Z<p>Wwarlock: </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_2012|GSoC 2012 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 />
<!-- Problem description short enough to catch attention. --><br />
== Port bento to twitter bootstrap ==<br />
<!-- General information, as much as needed, but not more. --><br />
* '''Description:''' The [https://github.com/openSUSE/opensuse-themes/tree/master/bento openSUSE bento] theme was supposed to be the great UI unification of all our web-pages. But it only came so far as adding a unified theming and some UI elements, most notably the top bar. Nowadays there is a great collection of HTML UI "libs" like twitter bootstrap that achieve way more. If we could port bento over to bootstrap we would reach the initial goal we set out to reach. The mentors would prefer to use the [http://openbuildservice.org Open Build Service (OBS)] as reference implementation for this project.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [https://connect.opensuse.org/pg/profile/hennevogel Henne Vogelsang], [https://connect.opensuse.org/pg/profile/coolo Stephan Kulow]<br />
<!-- Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' HTML, CSS, Javascript, Ruby on Rails, GIT<br />
<!-- Easy, Medium, Hard --><br />
* '''Skill Level:'''Medium<br />
<!-- Student name goes here --><br />
* '''Student:'''[[User:wwarlock|Shayon Mukherjee]](Interested)<br />
<br />
<!-- Problem description short enough to catch attention. --><br />
== Discussion System for the Open Build Service ==<br />
<!-- General background information, as much as needed, but not more. --><br />
* '''Description:''' There are a lot of "objects" like packages, projects, patches etc. in the [http://openbuildservice.org Open Build Service] that would greatly benefit from user feedback. The goal of this project is to add some way of discussing those objects in the OBS by means of either an external commenting system like [https://github.com/phusion/juvia juvia] or by adding the functionality to the OBS objects directly. <br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [https://connect.opensuse.org/pg/profile/hennevogel Henne Vogelsang], [https://connect.opensuse.org/pg/profile/coolo Stephan Kulow]<br />
<!-- Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' HTML/CSS, Javascript, Ruby on Rails, GIT<br />
<!-- Easy, Medium, Hard --><br />
* '''Skill Level:'''Medium/Hard (depends on the implementation route)<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Tar Extractor ==<br />
<!-- General information about the project--><br />
* '''Description:''' When I was starting with Linux, I found the concept of dealing with tar.gz files rather archaic. I believe a GUI could be produced to handle the functions necessary to perform these actions making a simple procedure even easier and less daunting to new Linux users. Concept preview: [https://docs.google.com/file/d/0B-CAUbBxV6ZuMFhiUGlGel9FVXc/edit?usp=sharing Concept GUI]<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' ?<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' ?<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' ?Medium<br />
<!-- Student name goes here --><br />
* '''Student:''' Scott DuBois<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== A GNOME3 like package manager module for YaST ==<br />
<!-- General information about the project--><br />
* '''Description:''' The package manager module is arguably the most used module in YaST. Unfortunately the present gtk(-3.0) version of the package manager module (libyui-gtk4), looks and feels a little from the yesteryear. It would be an educative as well as exciting project to develop a more GNOME3 like GUI based package manager from the scratch using the latest GNOME3 tools. In this regard, the excellent GNOME documents application can serve as a good template for the interface, but the package manager should in addition also provide filters for showing packages by category, repository, etc.<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' Javascript, gtk3, libyui (the yast libraries)<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' Hard<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== openSUSE News/Planet on Android ==<br />
<!-- General information about the project--><br />
* '''Description: '''openSUSE news and planet are a great source of information on what is happening in the project, and what the contributors are upto. It would be great to have an Android app, which would notify users about new posts on these platforms. There could also be an option to watch posts by specific authors, and view by languages. A good interface would be integral to the app.<br />
<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:'''[https://connect.opensuse.org/pg/profile/manugupt1 Manu Gupta]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills: '''Android<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level: '''Easy - Medium<br />
<!-- Student name goes here --><br />
* '''Student:'''<br />
<br />
== [[Portal:Build_Service|Open Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== SUSE Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio. Think git for [http://www.susestudio.com SUSE Studio]. You checkout an appliance, make some changes for it (locally) and once you are happy with the appliance you commit the changes to [http://www.susestudio.com SUSE Studio].<br />
<br />
Example use case<br />
<source lang="bash" style="overflow:auto"><br />
$ ssc appliance create web_server --source-id=SOURCE_APPLIANCE_ID --username=USERNAME --password=PASSWORD<br />
$ cd web_server<br />
$ ssc package list<br />
$ ssc package add apache<br />
$ ssc file add /etc/apache2/apache2.conf<br />
$ ssc commit<br />
</source><br />
<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Essential: Community involvement, introduce yourself on the opensuse-project mailing list. (this probably applies to all other projects as well)<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED<br />
<br />
=== SUSE Studio Java Client SDK ===<br />
<br />
[https://github.com/susestudio/susestudio-lib-java SUSE Studio Java Client] is a Java based library to interact with the [http://susestudio.com SUSE Studio] image store and appliances toolkit. The library is supposed to enable developers to easily implement SUSE Studio client applications in Java, even for mobile platforms like Android. The implementation however is at the moment still a work in progress and only very basic parts of the [http://susestudio.com/help/api/v2 REST API] are currently covered.<br />
<br />
The project goal is therefore to bring on the development of this library as much as possible, while ideally the whole API functionality should be covered by the implementation. The interface should be designed in a way so that developers will be able to write beautiful code using this library. Further it would be nice to have a suite of unit tests, so we can automatically ensure the overall functionality of the code and data model at any time using continuous integration tools like Jenkins.<br />
<br />
It would be a big plus for your application, if you propose to implement new software based on this SDK instead of just working on the library itself. This might be a mobile app for Android, a new web application or anything else, as far as it makes sense. Feel free to come up with your own ideas!<br />
<br />
Please find the existing code and documentation [https://github.com/susestudio/susestudio-lib-java here] and the SUSE Studio API documentation [http://susestudio.com/help/api/v2 here].<br />
<br />
'''Required knowledge:''' Java, HTTP and REST, unit testing and continuous integration<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
=== SUSE Studio Amazon EC2 scripts ===<br />
<br />
SUSE Studio allows you to easily build customized Amazon EC2 AMIs (Amazon Machine Images). While you can directly push and launch them from Studio to Amazon EC2, it is sometimes preferred to download the raw images and do this yourself. For example, you can automate a deployment workflow with Studio's WebHook API to download a new AMI when it is available, and then automatically push it to all EC2 regions, launch, test and swap them out for production use.<br />
<br />
The project at https://github.com/susestudio/susestudio-ec2 allows one to easily upload and create these AMIs from the downloaded Studio images. This project is to extend the existing code.<br />
<br />
'''Required knowledge:''' Bash/Shell scripting, Amazon EC2 knowledge preferred.<br />
<br />
'''Skill level:''' beginner - intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== SUSE StudioCheck ===<br />
<br />
[[http://en.opensuse.org/openSUSE:GSOC_ideas#SUSE_Studio:_StudioCheck_automated_test_framework | See entry in section QA]]<br />
----<br />
<br />
==Cross-distribution topics==<br />
The openSUSE project is proudly pushing cross-distribution collaboration.<br />
<br />
=== Compositor Colour Management ===<br />
Colour Management has to be easy for casual developers and automatic for users. To get there it is an good idea to have all applications colour corrected inside the window manager. On the other side graphics applications, want to do own colour management and should be able to say a window shall not be colour managed. To do so easily exists the [http://www.freedesktop.org/wiki/OpenIcc#X_Color_Management_spec X Color Management] spec and the implementation of this protocol in libXcm.<br />
<br />
The ICC based colour correction is easy for compositing window managers, as they support mostly shaders. Shaders run on the GPU and allow for a very fast and efficient colour correction.<br />
<br />
The project targets at providing colour management inside a compositing window manager of your choice. The protocol part to be implemented is the Baseline spec with _ICC_COLOR_OUTPUTS and additional the _ICC_COLOR_PROFILES atom.<br />
<br />
This implementation prepared a easy transition into Wayland compositor colour management, which will as well be window based.<br />
<br />
A good and very fast start is the update the [http://compicc.sf.net CompICC] plug for Compiz-0.8, to use the _ICC_COLOR_OUTPUTS atom.<br />
<br />
'''Required knowledge:''' OpenGL, GPU shaders, Oyranos, C<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Gtk Front End to Oyranos ===<br />
The [http://www.oyranos.org Oyranos project] is a cross desktop and cross OS colour management system (CMS) to provide easy to use and while robust colour management services to applications. The main goal of Oyranos is to provide colour management without user interaction. But in some situations and especially experts might want to configure and tweak the various settings manually.<br />
<br />
Front ends exist in Qt and for KDE. For Gtk based Desktop Environments it is currently only possible to use the Qt front end. For a better appearance and integration it makes sense to provide a native Gtk GUI for settings and configuration.<br />
<br />
'''Required knowledge:''' Gtk, Oyranos, C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== OpenICC Colour Configuration Data Base ===<br />
Users, who configure their colour management system (CMS) behaviour and devices, want to share these settings on one host without any intervention among installed CMSes. The project will introduce the OpenICC data base into CMSes like ArgyllCMS, Oyranos and colord and replaces existing own DB access code.<br />
<br />
device DB example: http://www.freedesktop.org/wiki/Specifications/icc_meta_tag_for_monitor_profiles<br />
<br />
existing code: http://openicc.git.sourceforge.net/git/gitweb.cgi?p=openicc/openicc;a=tree<br />
<br />
'''Required knowledge:''' C, good communication<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
'''Links:'''<br />
<br />
=== On-demand Symbolic Memory ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem is that often the input to a program (or its part) is unknown in advance. So checkers use a hack that they pass large symbolic buffer as input and hope that it is large enough.<br />
<br />
This is slow, inconvenient and does not help in cases where the buffer is a structure or an array of them. The members of the structure, especially pointers, are uninitialized and point to NULL.<br />
<br />
Instead, an on-demand symbolic buffer should be created. That ensures that NULL members are allocated on-the-fly and input arrays extended as needed. This was described in a paper called "Practical, low-effort equivalence verification of real code". Unfortunately the source code is not available. So the task of the student here is to implement this to klee, present that it works on examples provided by the mentor (parts of the Linux kernel code) and make the tool available to wide public.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== Concolic Symbolic Execution ===<br />
<br />
There are free symbolic execution tools like klee which perform symbolic execution on a code to find bugs. The problem with symbolic execution is that it gets lost very early if the code uses non-linear computations like comparing integers to hashes of other inputs or finding a number 'x' where x^3 == ~0.<br />
<br />
The cure for this is a parallel symbolic and concrete execution. If the symbolic execution cannot reason about some input, it asks the concrete one and vice versa. It is well-described in some papers.<br />
<br />
The student should implement this technique to klee and demonstrate how it improves performance of the symbolic execution.<br />
<br />
'''Required knowledge:''' C, static analysis (symbolic execution), writing clean code<br />
<br />
'''Skill level:''' advanced<br />
<br />
'''Mentor:'''<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== MirrorBrain: buffer-cache-friendly mirror selection ===<br />
<br />
MirrorBrain is the framework that openSUSE uses to redirect downloads to mirror servers. <br />
<br />
It would be possible to select mirrors intelligently with the purpose of optimizing the usage of the buffer caches of the mirrors. Right now, if openSUSE is released, all CD/DVD images are downloaded from all mirror servers. It would need many GB of buffer cache on the mirrors to keep the images in memory, usually more than physically available. Now, it would be very clever if the redirector could send redirects for DVD 1 to a certain mirror (group of mirrors), and send requests to DVD 2 to another mirror (group of mirrors). The question is how to recognize situations where this is possible, and how make this happen without administrative effort. A solution has been proposed (http://postr.poeml.de/a-buffer-cache-friendly-mirror-selection-algo) and it seems to work by proof-of-concept testing. <br />
<br />
To implement this, some hacking on mod_mirrorbrain.c is needed. A prerequisite is to understand how the current mirror selection works and how to add the further algorithm to it.<br />
<br />
Mirrors (and thereby, indirectly, its users, i.e. all of us) should benefit from this selection algorithm, because they would need to read less data from their disks.<br />
<br />
'''Required knowledge:''' C programming, HTTP and networking<br />
<br />
'''Skill level:''' intermediate (high?)<br />
<br />
'''Mentor:'''<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]<br />
<br />
== QA ==<br />
=== SUSE Studio: StudioCheck automated test framework ===<br />
<br />
This project is a abstraction of the Studio API to have the ability of creating test cases using a gherkin syntax. A prototype of the core system was created and is working, now the remaining items are the creation of abstraction steps and some reporting interface to get more than just a list of results for easier consumption.<br />
<br />
'''Required knowledge:''' Ruby, Rails, gherkin/BDL based tests<br />
<br />
'''Skill level:''' Depending on task Easy to Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:'''<br />
<br />
=== LTP:Fix/Implement automated kernel/glibc tests ===<br />
<br />
The [http://sourceforge.net/projects/ltp/ Linux Test Project] is huge collection of testcases aiming to test stability and correctness of kernel/glibc implementation and as the time goes by, some of the testcases needs polishing and testcases for newly introduced features should be written.<br />
<br />
'''Required knowledge:''' C, low level Linux/POSIX interface<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement alternative backends ===<br />
<br />
The [http://openqa.opensuse.org/ openQA/OS-autoinst testing framework] provides reliable continuous quality feedback about current openSUSE-Factory, Debian (and potentially other distributions).<br />
Currently the service relies on kvm for the testing (an alternative VirtualBox backend exists), but to test things, that need real hardware such as NVidia/ATI drivers, it needs a different backend. One idea is to use Net::VNC to interact with the machine-under-test and another is to use HDMI-capturing hardware (e.g. from Blackmagic for 200€) and hardware that can generate keystrokes to emulate user-input.<br />
<br />
'''Required knowledge:''' perl<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
=== openQA:Implement web-based test creator ===<br />
(for description of openQA see above)<br />
Creating/modifying test modules currently requires people to use a text-editor to create/change perl module files.<br />
Having an interactive web-based test-module editor/creator (could be similar to a user-input recorder) would allow easier creation of test-modules.<br />
<br />
'''Required knowledge:''' perl, AJAX<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
== openSUSE System Management ==<br />
=== Automatic resizing of LVM volumes and filesystems ===<br />
<br />
openSUSE currently provides good support for creating LVM volumes and installing the OS<br />
on these volumes. However, if the filesystem becomes full, the user/administrator has to increase the volume size and contained filesystem capacity manually.<br />
<br />
The goal of this project would be to implement automatic resizing of LVM <br />
volumes and contained filesystems. This resizing would be triggered e.g.<br />
by the package manager before installing the packages, if the free space drops<br />
before certain threshold etc. The installer should be modified to compute the <br />
necessary space needed for installing the selected set of packages and allocate<br />
the LVM volumes 'just big enough' for the installation. With future automatic<br />
resizing of the LVM/FS, this would save storage capacity in the volume group<br />
which would otherwise be unnecessarily allocated for /, /usr etc.<br />
<br />
'''Required knowledge:''' At least basic experience with C/C++, RPM, scripting<br />
(Python, bash). Understanding of LVM is a plus, but not necessary. Willingness to learn and investigate is a must.<br />
<br />
'''Skill level:''' Intermediate<br />
<br />
'''Mentor:''' <br />
<br />
'''Student:''' <br />
<br />
== Implementing Accurate XML Code Formatting ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
* ''Create Readable Source Code Formatting for XML''<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
* '''Background:'''<br />
There are some tools which can format XML/HTML sourcecode (tidy, xmlformat, ...). <br />
For example, xmlformat splits elements in an inline, block, and verbatim (=code) category. In most cases this works fine, but sometimes it fails.<br />
<br />
This tool could be improved by, for example using XPath expressions or by<br />
reading schemas (DTD, RNG, ...) to know more about the structure<br />
and how to format it. This would (hopefully) lead to a more exact<br />
formatting (think of mixed contents)<br />
<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
* '''Mentor:''' <br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
* '''Skill Level:''' Intermediate<br />
<br />
Perl or C experience. Knowledge of XML and/or XPath is desirable. Depending on the project plan, DTD would also be useful.<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
* '''Student:''' STUDENT NEEDED<br />
<br />
== Virtualization ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
===Upstream Xen Support for Libvirt===<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
The libvirt project provide a common and stable layer for different virtualization technology, including Xen, KVM, qemu and other hypervisors. Xen is one of the most important virtualization technology supported by openSUSE. But there are lots of changes from Xen-unstable, which lead to libvirt unused in lots of occasion. <br />
<br />
The gual of this project is to update libvirt for the xen-unstable. Most of the work may be update for the latest xenlight driver in libvirt. <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:'''<br />
<br />
'''Required knowledge:''' C<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Intermediate<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
<br />
== Code review for projects on GitHub ==<br />
<br />
<!-- <br />
Problem description short enough to catch attention.<br />
--><br />
The goal of this project is to extend [https://github.com/b4mboo/git-review git-review] to make code review from the command line interface even simpler.<br />
<br />
<!-- <br />
General background information, as much as needed, but not more. <br />
--><br />
A lot of our projects have moved their code to [https://github.com GitHub]. Using pull requests is a comfortable way to collaborate on projects hosted there and if done in a browser there is also a nice UI for it. <br />
However, since most developers use the command line for all of their git operations anyways, git-review was created to add some commands to git and thus enable developers to handle code review from the command line, too.<br />
<br />
For productive use git-review needs code coverage and added functionality that allows developers to work on different forks of a project.<br />
For further information please take a look at the project's list of open [https://github.com/b4mboo/git-review/issues issues].<br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
'''Mentor:'''<br />
<br />
'''Required knowledge:''' Ruby, Git, RSpec<br />
<br />
<!-- <br />
Easy, Medium, Hard<br />
--><br />
'''Skill Level:''' Medium<br />
<br />
<!-- <br />
Student name goes here<br />
--><br />
'''Student:''' STUDENT NEEDED<br />
<br />
<!-- Project title, short enough to catch attention.--><br />
== Project Title ==<br />
<!-- General information about the project--><br />
* '''Description:''' The openSUSE project provides the most choice in software stacks at many levels compared to other distributions. We would like to continue this "tradition" in the Cloud management infrastructure area. We already have OpenNebula and OpenStack. OpenNebula is the most complete offering with packages documentation and an appliance example. The OpenStack packages are building and the framework has been tested, yet we lack documentation around setup and configuration. For Eucalyptus and OpenStack our packages are way behind upstream and work is needed to move the packages forward. For both OpenStack and Eucalyptus the project includes everything from beginning to end until we have a presentable solution along the lines of the OpenNebula setup shown at https://en.opensuse.org/SDB:Cloud_OpenNebula<br />
<!-- Mentor name and/or link with contact information --><br />
* '''Mentor:''' [[User:rjschwei|Robert Schweikert]]<br />
<!--Which skills are needed? Programming languages, frameworks, concepts --><br />
* '''Skills:''' Packaging, Perl, Python, Java<br />
<!-- Easy, Medium, Hard--><br />
* '''Skill Level:''' Medium<br />
<!-- Student name goes here --><br />
* '''Student:''' needed</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_room_board&diff=52778openSUSE:Summit room board2012-08-07T14:56:20Z<p>Wwarlock: /* Find your room mate! */</p>
<hr />
<div>The rooms at the hotel at the openSUSE Summit are not very cheap. You can save some dimes by sharing a room, however. This also gives you a chance to get to know some other people a bit better!<br />
<br />
To make it easier to find room mates, we made the table below. Add your name if you are looking to share a room with someone - or pick someone who already added themselves to share a room with them! You will have to take care of the organization yourself: contact the hotel and book a room for the two of you. Therefor we recommend that you add your mail address or a link to your user page (with mail address!) so the other person can contact you!<br />
<br />
==Available room types==<br />
{| class="wikitable"<br />
|-<br />
! scope="col"| Room Type<br />
! scope="col"| bed<br />
! scope="col"| Price<br />
|-<br />
! scope="row"| 1 King<br />
| King-sized bed with sofa bed<br />
| $129 + $16.12 tax<br />
|-<br />
! scope="row"| Queen<br />
| 2 Queen-sized beds with sofa bed<br />
| $129 + $16.12 tax<br />
|-<br />
! scope="row"| Villa Suite<br />
| King-sized bed, 2 queen-sized beds, 1 sofa bed<br />
| $179 + $22.37 tax<br />
|}<br />
<br />
Above rate is each night. Up to people to figure out the actual<br />
per-person rate depending on how many people in the room.<br />
<br />
Each bed = 1 person unless people sleep together in bed, so 1. = 2<br />
people, 2. = 3 people, 3. = 4 people (or up to double each room type.)<br />
<br />
Gender = All Male, All Female, Undeclared<br />
<br />
==Find your room mate!==<br />
Add your name below to a group or create a new one.<br />
<br />
{| class="wikitable"<br />
|-<br />
! scope="col"| Group name<br />
! scope="col"| Gender<br />
! scope="col"| Room Type<br />
! scope="col"| Name1<br />
! scope="col"| Name2<br />
! scope="col"| Name3<br />
! scope="col"| Name4<br />
|-<br />
! scope="col"| Crazy Geekos<br />
| .<br />
| Villa Suite<br />
| .<br />
| .<br />
| .<br />
| .<br />
|-<br />
! scope="col"| Green Crazies<br />
| .<br />
| Villa Suite<br />
| .<br />
| .<br />
| .<br />
| .<br />
|-<br />
! scope="col"| Awesome Apes<br />
| .<br />
| Queen<br />
| Shayon Mukherjee (sj@opensuse.org)<br />
| .<br />
| .<br />
| nvt<br />
|-<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_room_board&diff=51061openSUSE:Summit room board2012-04-18T18:51:23Z<p>Wwarlock: </p>
<hr />
<div>{| class="wikitable"<br />
|-<br />
! scope="col"| Room Type<br />
! scope="col"| Name<br />
! scope="col"| Duration<br />
|-<br />
! scope="row"| King-sized bed<br />
| XYZ<br />
| XYZ<br />
|-<br />
! scope="row"| Queen-sized bed<br />
| XYZ<br />
| XYZ<br />
|-<br />
! scope="row"| Villa Suite<br />
| XYZ<br />
| XYZ<br />
|}<br />
<br />
# 1 King-sized bed with sofa bed $129 + $16.12 tax<br />
# 2 Queen-sized bed with sofa bed $129 + $16.12 tax<br />
# Villa Suite - 1 King-sized bed, 2 queen-sized beds, 1 sofa bed $179<br />
+ $22.37 tax<br />
<br />
Above rate is each night. Up to people to figure out the actual<br />
per-person rate depending on how many people in the room.<br />
<br />
Each bed = 1 person unless people sleep together in bed, so 1. = 2<br />
people, 2. = 3 people, 3. = 4 people (or up to double each room type.)</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_room_board&diff=51060openSUSE:Summit room board2012-04-18T18:45:33Z<p>Wwarlock: Created page with "{| class="wikitable" !colspan="6"|Shopping List |- |rowspan="2"|Bread & Butter |Pie |Buns |Danish |colspan="2"|Croissant |- |Cheese |colspan="2"|Ice cream |Butter |Yoghurt |}"</p>
<hr />
<div>{| class="wikitable"<br />
!colspan="6"|Shopping List<br />
|-<br />
|rowspan="2"|Bread & Butter<br />
|Pie<br />
|Buns<br />
|Danish<br />
|colspan="2"|Croissant<br />
|-<br />
|Cheese<br />
|colspan="2"|Ice cream<br />
|Butter<br />
|Yoghurt<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Splashscreen&diff=50354openSUSE:Splashscreen2012-03-19T04:51:39Z<p>Wwarlock: </p>
<hr />
<div>{{Artwork navbar}}<br />
<br />
[[File:SplashScreen.png|center]]<br />
<br />
<p>Hello artists and enthusiasts. We have been hard at working with our artwork for 12.2 and now it is the time to style the distribution a little more. Since the most of artwork that we have now is a derivative of the official wallpaper, created by Richard Brown and Marcus Moeller, there is a big portion of our styling done for the distribution. However, there are a few other elements that need your creative collaboration. Splash screens for a few programs that we use can be greatly enhanced by your artistic inspiration.</p><br />
<br />
<ol><br />
<li>Libre Office</li><br />
<li>Scribus</li><br />
<li>Amarok</li><br />
<li>Calligra</li><br />
<li>Krita</li><br />
<li>Blender</li> <br />
</ol><br />
<br />
<p>The idea of this contest is that we can integrate the new chosen wallpaper into these splash screens for the release of 12.2.These are the sizes</p><br />
<br />
*LibreOffice [http://wiki.documentfoundation.org/Design Guidelines]<br />
440x480<br />
*GIMP [http://www.gimp.org/ Guidelines]<br />
320x480<br />
*Scribus [http://wiki.scribus.net/canvas/Promotion_material Guidelines]<br />
391x295<br />
*Amarok [http://amarok.kde.org/wiki/File:Amarok_logo.svg Official Logo]<br />
550x412<br />
*Calligra [http://community.kde.org/Calligra/Logos Guidelines]<br />
440x286<br />
*Krita [http://es.wikipedia.org/wiki/Archivo:Krita_Application_Logo.svg Logo Example]<br />
440x286<br />
*Blender [https://svn.blender.org/svnroot/bf-blender/trunk/blender/release/datafiles/splash.png Official Logo]<br />
501x282 (Only work the area at the bottom. Leave top as is.)<br />
<br />
== Guidelines ==<br />
<br />
<ol><br />
<li>Use the default wallpaper as part of the image. [http://dl.dropbox.com/u/1363018/test3.jpg]</li><br />
<li>Refer to the official artwork guidelines in how to use logos for these different applications.</li><br />
<li>Restrict your creation to the specified sizes.</li><br />
<li>Provide the sources of your work if chosen.</li><br />
<li>Present/submit your artwork to [http://en.opensuse.org/openSUSE:Splashscreen]</li> <br />
</ol><br />
<br />
== Title, Artist ==<br />
<br />
{|<br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]]<br />
<br />
|-<br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]]<br />
|}<br />
<br />
== Title, Artist ==<br />
<br />
{|<br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]]<br />
|-<br />
<br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]] <br />
| [[image:Libre-andi.png|235x250px]]<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Splashscreen&diff=50346openSUSE:Splashscreen2012-03-19T02:55:58Z<p>Wwarlock: </p>
<hr />
<div>== Title, Artist ==<br />
<br />
{|<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
<br />
|-<br />
<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
|}<br />
<br />
== Title, Artist ==<br />
<br />
{|<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
<br />
|-<br />
<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Splashscreen&diff=50345openSUSE:Splashscreen2012-03-19T02:51:46Z<p>Wwarlock: </p>
<hr />
<div>== Title, Artist ==<br />
<br />
{|<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
|-<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
|}<br />
== Title, Artist ==<br />
<br />
<br />
{|<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
|-<br />
| [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]] || [[image:Libre-andi.png|235x250px]]<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Splashscreen&diff=50344openSUSE:Splashscreen2012-03-19T02:48:10Z<p>Wwarlock: </p>
<hr />
<div>== Title, Artist ==<br />
<br />
{|<br />
| [[image:Libre-andi.png|100x150px]] || [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]|| [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]<br />
|-<br />
| [[image:Libre-andi.png|100x150px]] || [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]|| [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]<br />
|}<br />
== Title, Artist ==<br />
<br />
<br />
{|<br />
| [[image:Libre-andi.png|100x150px]] || [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]|| [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]<br />
|-<br />
| [[image:Libre-andi.png|100x150px]] || [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]|| [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Splashscreen&diff=50343openSUSE:Splashscreen2012-03-19T02:46:42Z<p>Wwarlock: </p>
<hr />
<div>== Title, Artist ==<br />
<br />
{|<br />
| [[image:Libre-andi.png|100x150px]] || [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]|| [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]<br />
<br />
|}<br />
== Title, Artist ==<br />
<br />
<br />
{|<br />
| [[image:Libre-andi.png|100x150px]] || [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]|| [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]<br />
<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Splashscreen&diff=50342openSUSE:Splashscreen2012-03-19T02:45:50Z<p>Wwarlock: </p>
<hr />
<div>== Title, Artist ==<br />
<br />
<br />
== Title, Artist ==<br />
<br />
<br />
{|<br />
| [[image:Libre-andi.png|100x150px]] || [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]|| [[image:Blender203.png|100x150px]] || [[image:Blender203.png|100x150px]]<br />
<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Splashscreen&diff=50341openSUSE:Splashscreen2012-03-19T02:31:54Z<p>Wwarlock: Created page with "== Title, Artist == image:Libre-andi.png == Title, Artist == image:Blender203.png"</p>
<hr />
<div>== Title, Artist ==<br />
[[image:Libre-andi.png]]<br />
<br />
== Title, Artist ==<br />
[[image:Blender203.png]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=File:Blender203.png&diff=50340File:Blender203.png2012-03-19T02:31:48Z<p>Wwarlock: </p>
<hr />
<div></div>Wwarlockhttps://en.opensuse.org/index.php?title=File:Libre-andi.png&diff=50339File:Libre-andi.png2012-03-19T02:30:57Z<p>Wwarlock: </p>
<hr />
<div></div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_General_Committees&diff=49898openSUSE:Summit General Committees2012-03-05T03:01:41Z<p>Wwarlock: /* Website notes */</p>
<hr />
<div>{{Box-header| Promotions Committee }}<br />
* Tech: [[User:Wwarlock| Shayon Mukherjee 'shayonj']]<br />
* Tech: [[User:Digitaltomm| Thomas Schmidt 'digitltom']]<br />
* Venue: [[User:Druonysus| Drew Adams 'druonysus']]<br />
* Venue: [[User:CarlosAlbertoNovell| Carlos Ribeiro 'CarlosRibeiro']]<br />
* SUSE Liaison: [[User:Jospoortvliet| Jos Poortvliet 'jospoortvliet']]<br />
* SUSE Liaison: Alan Clark 'AlanClark'<br />
<br />
== Tech Committee ==<br />
<br />
The Tech Committee handles the online presence of the Summit including the registration site, main Summit site, and mobile apps.<br />
<br />
* Conference registration + CFP submissions will be handled by [[openSUSE:Summit_Program_Committee| Program Committee]] via Indico.<br />
* Android conference App - <br />
** Thomas Schmidt reports that the existing app from osc11 can be found at: https://github.com/digitaltom/OSCFahrplan .He can help in making it ready for the next conference.<br />
* Nanoc Setup (Main Conference Website) - [[User:Wwarlock|shayon]]<br />
** Request sent to Boosters Team 13-Feb-2012<br />
** Content should include:<br />
*** Link to Summit Registration and CFP via Indico<br />
*** Hotel Site + Nearby Area information<br />
*** Travel information (nearest airports, VISA advisories, etc.)<br />
*** Key dates information<br />
*** Link to SUSECon??<br />
* [[User:Wwarlock|shayon]] will work with [[openSUSE:Summit_Promotion_Committee | Artwork team]] for banner and other design considerations<br />
<br />
<br />
=== Tech Notes ===<br />
==== Website notes ====<br />
*Link to the draft [http://suse2.shayon.me http://suse2.shayon.me]<br />
* Added some basic content. Will work on reorganizing the content and add some more related content like, event dates and venue.<br />
* Have sent a request to Admin@ about the deployment details on summit.o.o<br />
<br />
== Venue Committee ==<br />
<br />
The Venue Committee handles the physical aspects of the Summit including setup/teardown of the venue, "concierge" services for attendees and handling all day-to-day matters during the conference. This committee is responsible to ensure needs (e.g., equipment, decorations, etc.) are well-defined prior to the Summit, including budgetary needs.<br />
<br />
* Venue Setup<br />
** Pre-Arrival tasks (Setup)<br />
*** Decorations<br />
** Summit Staff (During Summit days)<br />
*** Registration Desk - CarlosRibeiro<br />
*** Session Chairs - Druonysus<br />
**** Introduce session speakers<br />
**** Ensure room is organized before each session<br />
**** Provide helpful information to attendees<br />
**** Provide technical assistance (lighting, projectors, etc.)<br />
*** Number of Chairs needed will be conveyed by Program Committee<br />
** Session Video Recording and Post-Production<br />
** Post-Summit tasks (Cleanup)<br />
** SUSE Liaisons - AlanClark, jospoortvliet<br />
<br />
=== Materials ===<br />
* Badges (Will be provided by SUSECon)<br />
* Bag <br />
* Program Guide<br />
* T-Shirts<br />
* Geeko Plushies<br />
* Other Giveaways<br />
<br />
=== Venue Notes ===<br />
<br />
<br />
* The openSUSE event registration will occur through indico. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
<br />
* * Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available.<br />
<br />
* Each room will be equipped with a projector and screen. Additional equipment will need to be requested prior to the event. <br />
<br />
* SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup. <br />
<br />
* All questions about venue sevices and SUSE services/equipment are the be sent to AlanClakr or jospoortvliet, as they are the official liaisons.<br />
<br />
* SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
<br />
<br />
[[Category:Conference]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_General_Committees&diff=49897openSUSE:Summit General Committees2012-03-05T03:01:27Z<p>Wwarlock: </p>
<hr />
<div>{{Box-header| Promotions Committee }}<br />
* Tech: [[User:Wwarlock| Shayon Mukherjee 'shayonj']]<br />
* Tech: [[User:Digitaltomm| Thomas Schmidt 'digitltom']]<br />
* Venue: [[User:Druonysus| Drew Adams 'druonysus']]<br />
* Venue: [[User:CarlosAlbertoNovell| Carlos Ribeiro 'CarlosRibeiro']]<br />
* SUSE Liaison: [[User:Jospoortvliet| Jos Poortvliet 'jospoortvliet']]<br />
* SUSE Liaison: Alan Clark 'AlanClark'<br />
<br />
== Tech Committee ==<br />
<br />
The Tech Committee handles the online presence of the Summit including the registration site, main Summit site, and mobile apps.<br />
<br />
* Conference registration + CFP submissions will be handled by [[openSUSE:Summit_Program_Committee| Program Committee]] via Indico.<br />
* Android conference App - <br />
** Thomas Schmidt reports that the existing app from osc11 can be found at: https://github.com/digitaltom/OSCFahrplan .He can help in making it ready for the next conference.<br />
* Nanoc Setup (Main Conference Website) - [[User:Wwarlock|shayon]]<br />
** Request sent to Boosters Team 13-Feb-2012<br />
** Content should include:<br />
*** Link to Summit Registration and CFP via Indico<br />
*** Hotel Site + Nearby Area information<br />
*** Travel information (nearest airports, VISA advisories, etc.)<br />
*** Key dates information<br />
*** Link to SUSECon??<br />
* [[User:Wwarlock|shayon]] will work with [[openSUSE:Summit_Promotion_Committee | Artwork team]] for banner and other design considerations<br />
<br />
<br />
=== Tech Notes ===<br />
==== Website notes ====<br />
Link to the draft [http://suse2.shayon.me http://suse2.shayon.me]<br />
* Added some basic content. Will work on reorganizing the content and add some more related content like, event dates and venue.<br />
* Have sent a request to Admin@ about the deployment details on summit.o.o<br />
<br />
== Venue Committee ==<br />
<br />
The Venue Committee handles the physical aspects of the Summit including setup/teardown of the venue, "concierge" services for attendees and handling all day-to-day matters during the conference. This committee is responsible to ensure needs (e.g., equipment, decorations, etc.) are well-defined prior to the Summit, including budgetary needs.<br />
<br />
* Venue Setup<br />
** Pre-Arrival tasks (Setup)<br />
*** Decorations<br />
** Summit Staff (During Summit days)<br />
*** Registration Desk - CarlosRibeiro<br />
*** Session Chairs - Druonysus<br />
**** Introduce session speakers<br />
**** Ensure room is organized before each session<br />
**** Provide helpful information to attendees<br />
**** Provide technical assistance (lighting, projectors, etc.)<br />
*** Number of Chairs needed will be conveyed by Program Committee<br />
** Session Video Recording and Post-Production<br />
** Post-Summit tasks (Cleanup)<br />
** SUSE Liaisons - AlanClark, jospoortvliet<br />
<br />
=== Materials ===<br />
* Badges (Will be provided by SUSECon)<br />
* Bag <br />
* Program Guide<br />
* T-Shirts<br />
* Geeko Plushies<br />
* Other Giveaways<br />
<br />
=== Venue Notes ===<br />
<br />
<br />
* The openSUSE event registration will occur through indico. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
<br />
* * Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available.<br />
<br />
* Each room will be equipped with a projector and screen. Additional equipment will need to be requested prior to the event. <br />
<br />
* SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup. <br />
<br />
* All questions about venue sevices and SUSE services/equipment are the be sent to AlanClakr or jospoortvliet, as they are the official liaisons.<br />
<br />
* SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
<br />
<br />
[[Category:Conference]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_General_Committees&diff=49860openSUSE:Summit General Committees2012-03-02T08:06:53Z<p>Wwarlock: /* Tech Committee */</p>
<hr />
<div>{{Box-header| Promotions Committee }}<br />
* Tech: [[User:Wwarlock| Shayon Mukherjee 'shayonj']]<br />
* Tech: [[User:Digitaltomm| Thomas Schmidt 'digitltom']]<br />
* Venue: [[User:Druonysus| Drew Adams 'druonysus']]<br />
* Venue: [[User:CarlosAlbertoNovell| Carlos Ribeiro 'CarlosRibeiro']]<br />
* SUSE Liaison: [[User:Jospoortvliet| Jos Poortvliet 'jospoortvliet']]<br />
* SUSE Liaison: Alan Clark 'AlanClark'<br />
<br />
== Tech Committee ==<br />
<br />
The Tech Committee handles the online presence of the Summit including the registration site, main Summit site, and mobile apps.<br />
<br />
* Conference registration + CFP submissions will be handled by [[openSUSE:Summit_Program_Committee| Program Committee]] via Indico.<br />
* Android conference App - <br />
** Thomas Schmidt reports that the existing app from osc11 can be found at: https://github.com/digitaltom/OSCFahrplan .He can help in making it ready for the next conference.<br />
* Nanoc Setup (Main Conference Website) - [[User:Wwarlock|shayon]]<br />
** Request sent to Boosters Team 13-Feb-2012<br />
** Content should include:<br />
*** Link to Summit Registration and CFP via Indico<br />
*** Hotel Site + Nearby Area information<br />
*** Travel information (nearest airports, VISA advisories, etc.)<br />
*** Key dates information<br />
*** Link to SUSECon??<br />
* [[User:Wwarlock|shayon]] will work with [[openSUSE:Summit_Promotion_Committee | Artwork team]] for banner and other design considerations<br />
<br />
<br />
=== Tech Notes ===<br />
<br />
== Venue Committee ==<br />
<br />
The Venue Committee handles the physical aspects of the Summit including setup/teardown of the venue, "concierge" services for attendees and handling all day-to-day matters during the conference. This committee is responsible to ensure needs (e.g., equipment, decorations, etc.) are well-defined prior to the Summit, including budgetary needs.<br />
<br />
* Venue Setup<br />
** Pre-Arrival tasks (Setup)<br />
*** Decorations<br />
** Summit Staff (During Summit days)<br />
*** Registration Desk - CarlosRibeiro<br />
*** Session Chairs - Druonysus<br />
**** Introduce session speakers<br />
**** Ensure room is organized before each session<br />
**** Provide helpful information to attendees<br />
**** Provide technical assistance (lighting, projectors, etc.)<br />
*** Number of Chairs needed will be conveyed by Program Committee<br />
** Session Video Recording and Post-Production<br />
** Post-Summit tasks (Cleanup)<br />
** SUSE Liaisons - AlanClark, jospoortvliet<br />
<br />
=== Materials ===<br />
* Badges (Will be provided by SUSECon)<br />
* Bag <br />
* Program Guide<br />
* T-Shirts<br />
* Geeko Plushies<br />
* Other Giveaways<br />
<br />
=== Venue Notes ===<br />
<br />
<br />
* The openSUSE event registration will occur through indico. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
<br />
* * Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available.<br />
<br />
* Each room will be equipped with a projector and screen. Additional equipment will need to be requested prior to the event. <br />
<br />
* SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup. <br />
<br />
* All questions about venue sevices and SUSE services/equipment are the be sent to AlanClakr or jospoortvliet, as they are the official liaisons.<br />
<br />
* SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
<br />
<br />
[[Category:Conference]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_General_Committees&diff=49859openSUSE:Summit General Committees2012-03-02T08:06:18Z<p>Wwarlock: </p>
<hr />
<div>{{Box-header| Promotions Committee }}<br />
* Tech: [[User:Wwarlock| Shayon Mukherjee 'shayonj']]<br />
* Tech: [[User:Digitaltomm| Thomas Schmidt 'digitltom']]<br />
* Venue: [[User:Druonysus| Drew Adams 'druonysus']]<br />
* Venue: [[User:CarlosAlbertoNovell| Carlos Ribeiro 'CarlosRibeiro']]<br />
* SUSE Liaison: [[User:Jospoortvliet| Jos Poortvliet 'jospoortvliet']]<br />
* SUSE Liaison: Alan Clark 'AlanClark'<br />
<br />
== Tech Committee ==<br />
<br />
The Tech Committee handles the online presence of the Summit including the registration site, main Summit site, and mobile apps.<br />
<br />
* Conference registration + CFP submissions will be handled by [[openSUSE:Summit_Program_Committee| Program Committee]] via Indico.<br />
* Android conference App - <br />
** Thomas Schmidt reports that the existing app from osc11 can be found at: https://github.com/digitaltom/OSCFahrplan .He can help in making it ready for the next conference.<br />
* Nanoc Setup (Main Conference Website) - shayonj<br />
** Request sent to Boosters Team 13-Feb-2012<br />
** Content should include:<br />
*** Link to Summit Registration and CFP via Indico<br />
*** Hotel Site + Nearby Area information<br />
*** Travel information (nearest airports, VISA advisories, etc.)<br />
*** Key dates information<br />
*** Link to SUSECon??<br />
* Shayon will work with [[openSUSE:Summit_Promotion_Committee | Artwork team]] for banner and other design considerations<br />
<br />
<br />
=== Tech Notes ===<br />
<br />
== Venue Committee ==<br />
<br />
The Venue Committee handles the physical aspects of the Summit including setup/teardown of the venue, "concierge" services for attendees and handling all day-to-day matters during the conference. This committee is responsible to ensure needs (e.g., equipment, decorations, etc.) are well-defined prior to the Summit, including budgetary needs.<br />
<br />
* Venue Setup<br />
** Pre-Arrival tasks (Setup)<br />
*** Decorations<br />
** Summit Staff (During Summit days)<br />
*** Registration Desk - CarlosRibeiro<br />
*** Session Chairs - Druonysus<br />
**** Introduce session speakers<br />
**** Ensure room is organized before each session<br />
**** Provide helpful information to attendees<br />
**** Provide technical assistance (lighting, projectors, etc.)<br />
*** Number of Chairs needed will be conveyed by Program Committee<br />
** Session Video Recording and Post-Production<br />
** Post-Summit tasks (Cleanup)<br />
** SUSE Liaisons - AlanClark, jospoortvliet<br />
<br />
=== Materials ===<br />
* Badges (Will be provided by SUSECon)<br />
* Bag <br />
* Program Guide<br />
* T-Shirts<br />
* Geeko Plushies<br />
* Other Giveaways<br />
<br />
=== Venue Notes ===<br />
<br />
<br />
* The openSUSE event registration will occur through indico. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
<br />
* * Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available.<br />
<br />
* Each room will be equipped with a projector and screen. Additional equipment will need to be requested prior to the event. <br />
<br />
* SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup. <br />
<br />
* All questions about venue sevices and SUSE services/equipment are the be sent to AlanClakr or jospoortvliet, as they are the official liaisons.<br />
<br />
* SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
<br />
<br />
[[Category:Conference]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=49238Archive:GSOC ideas 20142012-02-16T15:10:52Z<p>Wwarlock: /* End user oriented obs web interface */</p>
<hr />
<div>==GSOC 2012 Idea list==<br />
<br />
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 [[openSUSE:GSOC_2011_Ideas|GSoC 2011 Ideas]] page. The openSUSE GSOC 2012 page is [[openSUSE:GSOC_2012|here]]<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 />
A great source for openSUSE related ideas is [https://features.opensuse.org/ openFATE].<br />
<br />
There have been a [[openSUSE:Derivate_Ideas|couple of ideas]] about more [[Derivates|openSUSE derivates]] but it was decided that they are not good GSOC ideas as the coding part is not primal.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_2012_Ideas}}<br />
<br />
----<br />
<br />
== General ideas==<br />
* Limited GUI support in text mode for multimedia & browsers.<br />
* develop a way for GTK apps to use a KDE file dialog in a Plasma Desktop<br />
* develop a way for KDE apps to use a GTK filedialog in a GTK desktop (GNOME, XFCE, LXDE)<br />
* Zypper to be able to talk to the 'osc' world so we can do zypper se on osc packages and trivially add repos, and install packages.<br />
* [http://en.opensuse.org/openSUSE:Easy-LTSP_GSoC_ideas LTSP-GSOC Ideas]<br />
* GRUB2 yast module<br />
* Remastersys or mylivecd for openSUSE<br />
* WebPin<br />
* Integration of owncloud<br />
* Improvements to KNetworkManager<br />
* Integrate Ksplice for reboot less kernel upgrades<br />
* FATE: Work on the KDE 4 client<br />
FATE is the feature tracking framework of Novell/openSUSE. The user visible part of this is [http://features.opensuse.org openFATE], the place where different projects of openSUSE track their feature requests. There also exists a KDE3 client, which should get ported to QT4.<br />
<br />
----<br />
<br />
===Ideas coming from openFATE===<br />
<br />
Overview: [https://features.opensuse.org/query/tag?tag=gsoc_2011 Features on openFATE tagged with 'gsoc_2011']<br />
<br />
* [https://features.opensuse.org/308314 better wine integration]<br />
* [https://features.opensuse.org/310232 kde addressbook integration in openoffice/libreoffice via akonadi connector]<br />
* [https://features.opensuse.org/310913 Add YAST module to set up multiseat installations]<br />
* [https://features.opensuse.org/307254 Use POSIX capabilities instead of suid]<br />
* [https://features.opensuse.org/310516 YaST2 DNSSEC]<br />
<br />
----<br />
<br />
== [[openSUSE:Connect|openSUSE Connect]] ==<br />
<br />
=== openSUSE Karma plugin for openSUSE Connect ===<br />
<br />
Implement Karma concept in openSUSE Connect that will collect points from wiki edits, bugzilla entries, planet.opensuse.org posts, distribution changelogs and possibly other sources and store them in the Connect. Also implement some UI to make it possible to send points. Create per group badget that will grow according of the number of skilled members automatically. Karma points should have some categorie - developer karma/marketing karma/... And it it would be also great to make it accessible though connect API (to trustworthy external applications (log transactions so in case of security breach it can be reverted)).<br />
<br />
'''Required knowledge:''' PHP basics<br />
<br />
'''Skill level:''' Basic<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]]<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[http://michal.hrusecky.net/2010/08/ideas-about-karma-in-opensuse-connect/ Blog post about karma idea]<br />
<br />
[http://michal.hrusecky.net/2011/03/gsoc-2011-ideas-karma-plugin-for-opensuse-connect/ GSoC blog post about karma idea]<br />
<br />
----<br />
<br />
== [[Portal:Build_Service|openSUSE Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]] (feel free to replace me)<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
=== End user oriented obs web interface ===<br />
<br />
The web interface of the Build Service is currently focused on developers. End users could benefit from exposing the work of individuals more. Displaying recent changes, a global history, activity and rating overview. Also a new user home page (similar to what Facebook or GitHub has) are ideas worth thinking about. Currently the ability to visually inspect the work of others is limited (mostly) to user's membership in projects/groups, their recent requests and what info they provide about themselves. The user's home page could be expanded by interests, external URL links (to an ohloh.net profile or blog). <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
*'''Mentor:''' [[User:saschpe|Sascha Peilicke]], Adrian Schröter, Markus Rückert, [[User:digitaltomm|Thomas Schmidt]]<br />
<br />
* '''Required skills:''' Ruby and Ruby on Rails, to integrate the new features into the web user interface<br />
<br />
* '''Student:''' one candidate available <br />
<br />
----<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== Suse Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio.<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:mess110|Cristian Mircea Messel]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=49237Archive:GSOC ideas 20142012-02-16T15:09:28Z<p>Wwarlock: /* End user oriented obs web interface */</p>
<hr />
<div>==GSOC 2012 Idea list==<br />
<br />
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 [[openSUSE:GSOC_2011_Ideas|GSoC 2011 Ideas]] page. The openSUSE GSOC 2012 page is [[openSUSE:GSOC_2012|here]]<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 />
A great source for openSUSE related ideas is [https://features.opensuse.org/ openFATE].<br />
<br />
There have been a [[openSUSE:Derivate_Ideas|couple of ideas]] about more [[Derivates|openSUSE derivates]] but it was decided that they are not good GSOC ideas as the coding part is not primal.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_2012_Ideas}}<br />
<br />
----<br />
<br />
== General ideas==<br />
* Limited GUI support in text mode for multimedia & browsers.<br />
* develop a way for GTK apps to use a KDE file dialog in a Plasma Desktop<br />
* develop a way for KDE apps to use a GTK filedialog in a GTK desktop (GNOME, XFCE, LXDE)<br />
* Zypper to be able to talk to the 'osc' world so we can do zypper se on osc packages and trivially add repos, and install packages.<br />
* [http://en.opensuse.org/openSUSE:Easy-LTSP_GSoC_ideas LTSP-GSOC Ideas]<br />
* GRUB2 yast module<br />
* Remastersys or mylivecd for openSUSE<br />
* WebPin<br />
* Integration of owncloud<br />
* Improvements to KNetworkManager<br />
* Integrate Ksplice for reboot less kernel upgrades<br />
* FATE: Work on the KDE 4 client<br />
FATE is the feature tracking framework of Novell/openSUSE. The user visible part of this is [http://features.opensuse.org openFATE], the place where different projects of openSUSE track their feature requests. There also exists a KDE3 client, which should get ported to QT4.<br />
<br />
----<br />
<br />
===Ideas coming from openFATE===<br />
<br />
Overview: [https://features.opensuse.org/query/tag?tag=gsoc_2011 Features on openFATE tagged with 'gsoc_2011']<br />
<br />
* [https://features.opensuse.org/308314 better wine integration]<br />
* [https://features.opensuse.org/310232 kde addressbook integration in openoffice/libreoffice via akonadi connector]<br />
* [https://features.opensuse.org/310913 Add YAST module to set up multiseat installations]<br />
* [https://features.opensuse.org/307254 Use POSIX capabilities instead of suid]<br />
* [https://features.opensuse.org/310516 YaST2 DNSSEC]<br />
<br />
----<br />
<br />
== [[openSUSE:Connect|openSUSE Connect]] ==<br />
<br />
=== openSUSE Karma plugin for openSUSE Connect ===<br />
<br />
Implement Karma concept in openSUSE Connect that will collect points from wiki edits, bugzilla entries, planet.opensuse.org posts, distribution changelogs and possibly other sources and store them in the Connect. Also implement some UI to make it possible to send points. Create per group badget that will grow according of the number of skilled members automatically. Karma points should have some categorie - developer karma/marketing karma/... And it it would be also great to make it accessible though connect API (to trustworthy external applications (log transactions so in case of security breach it can be reverted)).<br />
<br />
'''Required knowledge:''' PHP basics<br />
<br />
'''Skill level:''' Basic<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]]<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[http://michal.hrusecky.net/2010/08/ideas-about-karma-in-opensuse-connect/ Blog post about karma idea]<br />
<br />
[http://michal.hrusecky.net/2011/03/gsoc-2011-ideas-karma-plugin-for-opensuse-connect/ GSoC blog post about karma idea]<br />
<br />
----<br />
<br />
== [[Portal:Build_Service|openSUSE Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]] (feel free to replace me)<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
=== End user oriented obs web interface ===<br />
<br />
The web interface of the Build Service is currently focused on developers. End users could benefit from exposing the work of individuals more. Displaying recent changes, a global history, activity and rating overview. Also a new user home page (similar to what Facebook or GitHub has) are ideas worth thinking about. Currently the ability to visually inspect the work of others is limited (mostly) to user's membership in projects/groups, their recent requests and what info they provide about themselves. The user's home page could be expanded by interests, external URL links (to an ohloh.net profile or blog). <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
*'''Mentor:''' [[User:saschpe|Sascha Peilicke]], Adrian Schröter, Markus Rückert, [[User:digitaltomm|Thomas Schmidt]]<br />
<br />
* '''Required skills:''' Ruby and Ruby on Rails, to integrate the new features into the web user interface<br />
<br />
* one candidate available <br />
<br />
----<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== Suse Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio.<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:mess110|Cristian Mircea Messel]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=49235Archive:GSOC ideas 20142012-02-16T14:48:57Z<p>Wwarlock: /* End user oriented obs web interface */</p>
<hr />
<div>==GSOC 2012 Idea list==<br />
<br />
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 [[openSUSE:GSOC_2011_Ideas|GSoC 2011 Ideas]] page. The openSUSE GSOC 2012 page is [[openSUSE:GSOC_2012|here]]<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 />
A great source for openSUSE related ideas is [https://features.opensuse.org/ openFATE].<br />
<br />
There have been a [[openSUSE:Derivate_Ideas|couple of ideas]] about more [[Derivates|openSUSE derivates]] but it was decided that they are not good GSOC ideas as the coding part is not primal.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_2012_Ideas}}<br />
<br />
----<br />
<br />
== General ideas==<br />
* Limited GUI support in text mode for multimedia & browsers.<br />
* develop a way for GTK apps to use a KDE file dialog in a Plasma Desktop<br />
* develop a way for KDE apps to use a GTK filedialog in a GTK desktop (GNOME, XFCE, LXDE)<br />
* Zypper to be able to talk to the 'osc' world so we can do zypper se on osc packages and trivially add repos, and install packages.<br />
* [http://en.opensuse.org/openSUSE:Easy-LTSP_GSoC_ideas LTSP-GSOC Ideas]<br />
* GRUB2 yast module<br />
* Remastersys or mylivecd for openSUSE<br />
* WebPin<br />
* Integration of owncloud<br />
* Improvements to KNetworkManager<br />
* Integrate Ksplice for reboot less kernel upgrades<br />
* FATE: Work on the KDE 4 client<br />
FATE is the feature tracking framework of Novell/openSUSE. The user visible part of this is [http://features.opensuse.org openFATE], the place where different projects of openSUSE track their feature requests. There also exists a KDE3 client, which should get ported to QT4.<br />
<br />
----<br />
<br />
===Ideas coming from openFATE===<br />
<br />
Overview: [https://features.opensuse.org/query/tag?tag=gsoc_2011 Features on openFATE tagged with 'gsoc_2011']<br />
<br />
* [https://features.opensuse.org/308314 better wine integration]<br />
* [https://features.opensuse.org/310232 kde addressbook integration in openoffice/libreoffice via akonadi connector]<br />
* [https://features.opensuse.org/310913 Add YAST module to set up multiseat installations]<br />
* [https://features.opensuse.org/307254 Use POSIX capabilities instead of suid]<br />
* [https://features.opensuse.org/310516 YaST2 DNSSEC]<br />
<br />
----<br />
<br />
== [[openSUSE:Connect|openSUSE Connect]] ==<br />
<br />
=== openSUSE Karma plugin for openSUSE Connect ===<br />
<br />
Implement Karma concept in openSUSE Connect that will collect points from wiki edits, bugzilla entries, planet.opensuse.org posts, distribution changelogs and possibly other sources and store them in the Connect. Also implement some UI to make it possible to send points. Create per group badget that will grow according of the number of skilled members automatically. Karma points should have some categorie - developer karma/marketing karma/... And it it would be also great to make it accessible though connect API (to trustworthy external applications (log transactions so in case of security breach it can be reverted)).<br />
<br />
'''Required knowledge:''' PHP basics<br />
<br />
'''Skill level:''' Basic<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]]<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[http://michal.hrusecky.net/2010/08/ideas-about-karma-in-opensuse-connect/ Blog post about karma idea]<br />
<br />
[http://michal.hrusecky.net/2011/03/gsoc-2011-ideas-karma-plugin-for-opensuse-connect/ GSoC blog post about karma idea]<br />
<br />
----<br />
<br />
== [[Portal:Build_Service|openSUSE Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]] (feel free to replace me)<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
=== End user oriented obs web interface ===<br />
<br />
The web interface of the Build Service is currently focused on developers. End users could benefit from exposing the work of individuals more. Displaying recent changes, a global history, activity and rating overview. Also a new user home page (similar to what Facebook or GitHub has) are ideas worth thinking about. Currently the ability to visually inspect the work of others is limited (mostly) to user's membership in projects/groups, their recent requests and what info they provide about themselves. The user's home page could be expanded by interests, external URL links (to an ohloh.net profile or blog). <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
*'''Mentor:''' [[User:saschpe|Sascha Peilicke]], Adrian Schröter, Markus Rückert, [[User:digitaltomm|Thomas Schmidt]]<br />
<br />
* '''Required skills:''' Ruby and Ruby on Rails, to integrate the new features into the web user interface<br />
<br />
* '''Student :''' [[User:wwarlock|Shayon]]<br />
<br />
----<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== Suse Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio.<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:mess110|Cristian Mircea Messel]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=49234Archive:GSOC ideas 20142012-02-16T14:48:47Z<p>Wwarlock: /* End user oriented obs web interface */</p>
<hr />
<div>==GSOC 2012 Idea list==<br />
<br />
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 [[openSUSE:GSOC_2011_Ideas|GSoC 2011 Ideas]] page. The openSUSE GSOC 2012 page is [[openSUSE:GSOC_2012|here]]<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 />
A great source for openSUSE related ideas is [https://features.opensuse.org/ openFATE].<br />
<br />
There have been a [[openSUSE:Derivate_Ideas|couple of ideas]] about more [[Derivates|openSUSE derivates]] but it was decided that they are not good GSOC ideas as the coding part is not primal.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_2012_Ideas}}<br />
<br />
----<br />
<br />
== General ideas==<br />
* Limited GUI support in text mode for multimedia & browsers.<br />
* develop a way for GTK apps to use a KDE file dialog in a Plasma Desktop<br />
* develop a way for KDE apps to use a GTK filedialog in a GTK desktop (GNOME, XFCE, LXDE)<br />
* Zypper to be able to talk to the 'osc' world so we can do zypper se on osc packages and trivially add repos, and install packages.<br />
* [http://en.opensuse.org/openSUSE:Easy-LTSP_GSoC_ideas LTSP-GSOC Ideas]<br />
* GRUB2 yast module<br />
* Remastersys or mylivecd for openSUSE<br />
* WebPin<br />
* Integration of owncloud<br />
* Improvements to KNetworkManager<br />
* Integrate Ksplice for reboot less kernel upgrades<br />
* FATE: Work on the KDE 4 client<br />
FATE is the feature tracking framework of Novell/openSUSE. The user visible part of this is [http://features.opensuse.org openFATE], the place where different projects of openSUSE track their feature requests. There also exists a KDE3 client, which should get ported to QT4.<br />
<br />
----<br />
<br />
===Ideas coming from openFATE===<br />
<br />
Overview: [https://features.opensuse.org/query/tag?tag=gsoc_2011 Features on openFATE tagged with 'gsoc_2011']<br />
<br />
* [https://features.opensuse.org/308314 better wine integration]<br />
* [https://features.opensuse.org/310232 kde addressbook integration in openoffice/libreoffice via akonadi connector]<br />
* [https://features.opensuse.org/310913 Add YAST module to set up multiseat installations]<br />
* [https://features.opensuse.org/307254 Use POSIX capabilities instead of suid]<br />
* [https://features.opensuse.org/310516 YaST2 DNSSEC]<br />
<br />
----<br />
<br />
== [[openSUSE:Connect|openSUSE Connect]] ==<br />
<br />
=== openSUSE Karma plugin for openSUSE Connect ===<br />
<br />
Implement Karma concept in openSUSE Connect that will collect points from wiki edits, bugzilla entries, planet.opensuse.org posts, distribution changelogs and possibly other sources and store them in the Connect. Also implement some UI to make it possible to send points. Create per group badget that will grow according of the number of skilled members automatically. Karma points should have some categorie - developer karma/marketing karma/... And it it would be also great to make it accessible though connect API (to trustworthy external applications (log transactions so in case of security breach it can be reverted)).<br />
<br />
'''Required knowledge:''' PHP basics<br />
<br />
'''Skill level:''' Basic<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]]<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[http://michal.hrusecky.net/2010/08/ideas-about-karma-in-opensuse-connect/ Blog post about karma idea]<br />
<br />
[http://michal.hrusecky.net/2011/03/gsoc-2011-ideas-karma-plugin-for-opensuse-connect/ GSoC blog post about karma idea]<br />
<br />
----<br />
<br />
== [[Portal:Build_Service|openSUSE Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]] (feel free to replace me)<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
=== End user oriented obs web interface ===<br />
<br />
The web interface of the Build Service is currently focused on developers. End users could benefit from exposing the work of individuals more. Displaying recent changes, a global history, activity and rating overview. Also a new user home page (similar to what Facebook or GitHub has) are ideas worth thinking about. Currently the ability to visually inspect the work of others is limited (mostly) to user's membership in projects/groups, their recent requests and what info they provide about themselves. The user's home page could be expanded by interests, external URL links (to an ohloh.net profile or blog). <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
*'''Mentor:''' [[User:saschpe|Sascha Peilicke]], Adrian Schröter, Markus Rückert, [[User:digitaltomm|Thomas Schmidt]]<br />
<br />
* '''Required skills:''' Ruby and Ruby on Rails, to integrate the new features into the web user interface<br />
<br />
* '''Student :''' [[User:wwarlock|Shayon]<br />
<br />
----<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== Suse Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio.<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:mess110|Cristian Mircea Messel]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Archive:GSOC_ideas_2014&diff=49233Archive:GSOC ideas 20142012-02-16T14:48:36Z<p>Wwarlock: /* End user oriented obs web interface */</p>
<hr />
<div>==GSOC 2012 Idea list==<br />
<br />
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 [[openSUSE:GSOC_2011_Ideas|GSoC 2011 Ideas]] page. The openSUSE GSOC 2012 page is [[openSUSE:GSOC_2012|here]]<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 />
A great source for openSUSE related ideas is [https://features.opensuse.org/ openFATE].<br />
<br />
There have been a [[openSUSE:Derivate_Ideas|couple of ideas]] about more [[Derivates|openSUSE derivates]] but it was decided that they are not good GSOC ideas as the coding part is not primal.<br />
<br />
{{GSOC new task|pagename=openSUSE:GSOC_2012_Ideas}}<br />
<br />
----<br />
<br />
== General ideas==<br />
* Limited GUI support in text mode for multimedia & browsers.<br />
* develop a way for GTK apps to use a KDE file dialog in a Plasma Desktop<br />
* develop a way for KDE apps to use a GTK filedialog in a GTK desktop (GNOME, XFCE, LXDE)<br />
* Zypper to be able to talk to the 'osc' world so we can do zypper se on osc packages and trivially add repos, and install packages.<br />
* [http://en.opensuse.org/openSUSE:Easy-LTSP_GSoC_ideas LTSP-GSOC Ideas]<br />
* GRUB2 yast module<br />
* Remastersys or mylivecd for openSUSE<br />
* WebPin<br />
* Integration of owncloud<br />
* Improvements to KNetworkManager<br />
* Integrate Ksplice for reboot less kernel upgrades<br />
* FATE: Work on the KDE 4 client<br />
FATE is the feature tracking framework of Novell/openSUSE. The user visible part of this is [http://features.opensuse.org openFATE], the place where different projects of openSUSE track their feature requests. There also exists a KDE3 client, which should get ported to QT4.<br />
<br />
----<br />
<br />
===Ideas coming from openFATE===<br />
<br />
Overview: [https://features.opensuse.org/query/tag?tag=gsoc_2011 Features on openFATE tagged with 'gsoc_2011']<br />
<br />
* [https://features.opensuse.org/308314 better wine integration]<br />
* [https://features.opensuse.org/310232 kde addressbook integration in openoffice/libreoffice via akonadi connector]<br />
* [https://features.opensuse.org/310913 Add YAST module to set up multiseat installations]<br />
* [https://features.opensuse.org/307254 Use POSIX capabilities instead of suid]<br />
* [https://features.opensuse.org/310516 YaST2 DNSSEC]<br />
<br />
----<br />
<br />
== [[openSUSE:Connect|openSUSE Connect]] ==<br />
<br />
=== openSUSE Karma plugin for openSUSE Connect ===<br />
<br />
Implement Karma concept in openSUSE Connect that will collect points from wiki edits, bugzilla entries, planet.opensuse.org posts, distribution changelogs and possibly other sources and store them in the Connect. Also implement some UI to make it possible to send points. Create per group badget that will grow according of the number of skilled members automatically. Karma points should have some categorie - developer karma/marketing karma/... And it it would be also great to make it accessible though connect API (to trustworthy external applications (log transactions so in case of security breach it can be reverted)).<br />
<br />
'''Required knowledge:''' PHP basics<br />
<br />
'''Skill level:''' Basic<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]]<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[http://michal.hrusecky.net/2010/08/ideas-about-karma-in-opensuse-connect/ Blog post about karma idea]<br />
<br />
[http://michal.hrusecky.net/2011/03/gsoc-2011-ideas-karma-plugin-for-opensuse-connect/ GSoC blog post about karma idea]<br />
<br />
----<br />
<br />
== [[Portal:Build_Service|openSUSE Build Service ]] ==<br />
<br />
=== Support for [http://bitbake.berlios.de/manual/ Bitbake] in OBS ===<br />
[http://bitbake.berlios.de/manual/ Bitbake] is class based build system. It uses <tt>.bb</tt> recipes and it is able to create rpm, deb and other formats. All from one recipe. openSUSE Build Service supports building packages on variety of distributions. Support for Bitbake would make it easier to package software and hopefully later to make it possible to build it for all distributions from one recipe. Among other tasks student would need to add support for <tt>.bb</tt> in obs, get list of dependencies from Bitbake to provide it to Build Service and create staging tree using binary packages provided by obs.<br />
<br />
'''Required knowledge:'''<br />
* Python (Bitbake is written in it)<br />
* Shell, Perl (obs use these)<br />
* Basic packaging knowledge<br />
* Good orientation in ugly code<br />
* Ability to create creative hacks<br />
<br />
'''Skill level:''' Advanced<br />
<br />
'''Mentor:''' [[User:-miska-|Michal Hrušecký]] (feel free to replace me)<br />
<br />
'''Student:''' 2 candidates available<br />
<br />
[https://michal.hrusecky.net/2011/03/gsoc-2011-ideas-support-for-bitbake-in-obs/ Blog post about this idea]<br />
<br />
=== End user oriented obs web interface ===<br />
<br />
The web interface of the Build Service is currently focused on developers. End users could benefit from exposing the work of individuals more. Displaying recent changes, a global history, activity and rating overview. Also a new user home page (similar to what Facebook or GitHub has) are ideas worth thinking about. Currently the ability to visually inspect the work of others is limited (mostly) to user's membership in projects/groups, their recent requests and what info they provide about themselves. The user's home page could be expanded by interests, external URL links (to an ohloh.net profile or blog). <br />
<br />
<!-- <br />
Mentor name and/or link with contact information <br />
--><br />
*'''Mentor:''' [[User:saschpe|Sascha Peilicke]], Adrian Schröter, Markus Rückert, [[User:digitaltomm|Thomas Schmidt]]<br />
<br />
* '''Required skills:''' Ruby and Ruby on Rails, to integrate the new features into the web user interface<br />
<br />
* '''Student :''' [[User:wwarlock]|Shayon]<br />
<br />
----<br />
<br />
== [[Portal:SUSE_Studio|Appliances/SUSE Studio]] ==<br />
<br />
=== Suse Studio Command Line Client (ssc) ===<br />
<br />
With [http://www.susestudio.com SUSE Studio] users can easily create openSUSE based systems in their web browser. But when running such a system, there is still missing a convenient way how to feed back changes in the system to Studio, so that with the next build on the Studio web site these changes are incorporated.<br />
<br />
The idea of this project is to extend the Studio command line client [http://github.com/susestudio/ssc ssc] by this functionality. This could be modeled similar to how the openSUSE Build Service command line client osc works, with commands to list packages, and overlay files, to show diffs, and to commit changes back to Studio.<br />
<br />
Goal: get some workflow going, which can be used to track changes within an appliance and selectively apply them back to Studio.<br />
<br />
Find more details on the [[openSUSE:SUSE Studio command line client|SUSE Studio command line client]] page.<br />
<br />
'''Required knowledge:''' Ruby<br />
<br />
'''Skill level:''' intermediate<br />
<br />
'''Mentor:''' [[User:mess110|Cristian Mircea Messel]]<br />
<br />
'''Student:''' STUDENT NEEDED.<br />
<br />
[[Category:Google Summer of Code]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_General_Committees&diff=49145openSUSE:Summit General Committees2012-02-14T14:56:29Z<p>Wwarlock: </p>
<hr />
<div>{{Box-header| Promotions Committee }}<br />
* Tech: [[User:Wwarlock| Shayon Mukherjee 'shayonj']]<br />
* Tech: [[User:Digitaltomm| Thomas Schmidt 'digitltom']]<br />
* Venue: [[User:Druonysus| Drew Adams 'druonysus']]<br />
* Venue: [[User:CarlosAlbertoNovell| Carlos Ribeiro 'CarlosRibeiro']]<br />
* SUSE Liaison: [[User:Jospoortvliet| Jos Poortvliet 'jospoortvliet']]<br />
* SUSE Liaison: Alan Clark 'AlanClark'<br />
<br />
== Tech Committee ==<br />
<br />
The Tech Committee handles the online presence of the Summit including the registration site, main Summit site, and mobile apps.<br />
<br />
* Conference registration + CFP submissions will be handled by [[openSUSE:Summit_Program_Committee| Program Committee]] via Indico.<br />
* Android conference App - shayonj<br />
** Thomas Schmidt reports that the existing app from osc11 can be found at: https://github.com/digitaltom/OSCFahrplan .He can help in making it ready for the next conference.<br />
* Nanoc Setup (Main Conference Website) - shayonj<br />
** Request sent to Boosters Team 13-Feb-2012<br />
** Content should include:<br />
*** Link to Summit Registration and CFP via Indico<br />
*** Hotel Site + Nearby Area information<br />
*** Travel information (nearest airports, VISA advisories, etc.)<br />
*** Key dates information<br />
*** Link to SUSECon??<br />
* Shayon will work with [[openSUSE:Summit_Promotion_Committee | Artwork team]] for banner and other design considerations<br />
<br />
<br />
=== Tech Notes ===<br />
<br />
== Venue Committee ==<br />
<br />
The Venue Committee handles the physical aspects of the Summit including setup/teardown of the venue, "concierge" services for attendees and handling all day-to-day matters during the conference. This committee is responsible to ensure needs (e.g., equipment, decorations, etc.) are well-defined prior to the Summit, including budgetary needs.<br />
<br />
* Venue Setup<br />
** Pre-Arrival tasks (Setup)<br />
*** Decorations<br />
** Summit Staff (During Summit days)<br />
*** Registration Desk - CarlosRibeiro<br />
*** Session Chairs - Druonysus<br />
**** Introduce session speakers<br />
**** Ensure room is organized before each session<br />
**** Provide helpful information to attendees<br />
**** Provide technical assistance (lighting, projectors, etc.)<br />
*** Number of Chairs needed will be conveyed by Program Committee<br />
** Session Video Recording and Post-Production<br />
** Post-Summit tasks (Cleanup)<br />
** SUSE Liaisons - AlanClark, jospoortvliet<br />
<br />
=== Materials ===<br />
* Badges (Will be provided by SUSECon)<br />
* Bag <br />
* Program Guide<br />
* T-Shirts<br />
* Geeko Plushies<br />
* Other Giveaways<br />
<br />
=== Venue Notes ===<br />
<br />
<br />
* The openSUSE event registration will occur through indico. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
<br />
* * Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available.<br />
<br />
* Each room will be equipped with a projector and screen. Additional equipment will need to be requested prior to the event. <br />
<br />
* SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup. <br />
<br />
* All questions about venue sevices and SUSE services/equipment are the be sent to AlanClakr or jospoortvliet, as they are the official liaisons.<br />
<br />
* SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
<br />
<br />
[[Category:Conference]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_planning&diff=48915openSUSE:Summit planning2012-02-08T20:44:50Z<p>Wwarlock: /* Add your name here to volunteer to help with the planning */</p>
<hr />
<div>SUSE has decided to donate space following their SUSECon conference in Orlando Florida. The main conference is September 18-21, and openSUSE has the facilities from September 21-23. Planning communication will be through the project IRC and mailing list<br />
<br />
* When: September 21-23, 2011<br />
* Where: [http://www.thecaribeorlando.com/ Caribe Royale Hotel] Orlando, FL<br />
<br />
<br />
== [http://bit.ly/xjGuee Vote for the name of the event today! Deadline 11-Feb-2012] ==<br />
<br />
<br />
== Add your name here to volunteer to help with the planning ==<br />
More than one person can be on any task. One person can be on multiple tasks.<br />
* Promotion Committee:<br />
** Artwork: CarlosRibeiro, anditosan, Itxshell<br />
** Social Media Bryen Yunashko, [[User:MMcCallister|workingwriter]]<br />
** Press: Jos, Amie@suse, [[User:MMcCallister|workingwriter]]<br />
** Contact local LUGS, user groups<br />
:::: Pensacola Linux Users Group, http://www.pcolalug.org Pensacola, Florida<br />
:::: Jacksonville Linux Users Group (JaxLUG), http://www.jaxlug.org Jacksonville, Florida<br />
:::: GatorLUG, http://www.gatorlug.org Gainesville, Florida<br />
:::: Linux Enthusiasts And Professionals, Inc., http://www.leap-cf.org Central Florida<br />
:::: Melbourne Linux User Group, http://www.mlinux.org Melbourne, Florida<br />
:::: Florida Linux Users Group, http://www.flalug.org Clearwater, Florida<br />
:::: Suncoast Linux Users Group (SLUG), http://www.suncoastlug.org Tampa Bay, Florida<br />
:::: Southwest Florida Linux Users Group (SWFLUG) , http://www.swflug.org Ft. Myers, Florida<br />
:::: Palm Beach County LUG (PBLUG) , http://www.pbclug.org West Palm Beach, Florida<br />
:::: FLUX: The Florida Linux User Xchange, http://www.flux.org Fort Lauderdale, Florida<br />
:::: Miami Linux Users Group (MIALUG), http://www.mialug.org Miami Florida<br />
:::: Miami Linux User Group, http://www.mialinux.org Miami, Florida<br />
:::: Linux Users Group at UCF, http://www2.mmae.ucf.edu/wiki/LUG<br />
* Technical Committee:<br />
** Indico setup: suseROCKS, AlanClark, Dragotin<br />
*** Registrations<br />
*** CFP Submissions<br />
** Android Setup: Prusnak <br />
::: Thomas Schmidt reports that the existing app from osc11 can be found at: https://github.com/digitaltom/OSCFahrplan .He can help in making it ready for the next conference.<br />
** Wordpress Setup: [[User:wwarlock|Sj]] (but looking for some more information)<br />
*** General Attendee Information<br />
* Program committee: suseROCKs, AlanClark, Druonysus, itxshell, differentreality<br />
::: Those that register by September 15 will be invited to attend the Friday SUSECon sessions and closing keynote.<br />
::: A suggest program format is:<br />
::::Friday September 21 9:00 - 12:00 SUSECon sessions and keynote<br />
::::Friday September 21 14:00 - 17:00 openSUSE Event sessions<br />
::::Friday September 21 18:00 - 22:00 openSUSE Event Evening Celebration<br />
::::Saturday September 22 9:00 - 10:00 openSUSE Event Keynote<br />
::::Saturday September 22 10:00 - 17:00 openSUSE Event sessions<br />
::::Saturday September 22 18:00 - 22:00 openSUSE Event Evening Party<br />
* Evening Entertainment Committee:<br />
** Friday Night<br />
** Saturday Night<br />
* Onsite Committee:<br />
** Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available. <br />
<br />
** Registration Desk: CarlosRibeiro<br />
:: The openSUSE event registration will occur through indigo. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
** Presentation Room Chairs: Druonysus<br />
** General Floor Staff<br />
** Session Video Recording<br />
** Materials<br />
*** Badges<br />
*** Bag <br />
*** Program Guide<br />
*** Other giveaways<br />
* Sponsorship Committee<br />
** Finding event sponsors:<br />
** Travel sponsorship: Handled through the travel program<br />
* Miscellaneous<br />
** hotel room block, discount codes: AlanClark<br />
** Coordination with SUSECon Staff: AlanClark, Jos<br />
<br />
== Feb 1, Kick off meeting agenda ==<br />
* [http://bit.ly/yAPh4A Meeting Transcript]<br />
* [http://lists.opensuse.org/opensuse-project/2012-02/msg00020.html Meeting Summary]<br />
* 18:00 UTC (1 p.m. Eastern/10 a.m. Pacific)<br />
* [irc://freenode.net/#opensuse-project #openSUSE-Project IRC Channel]<br />
<br />
# Define the target audience for this event<br />
## (Notes from the last project meeting:<br />
### a great opportunity to fly in folks from Central America, Mexico and Canada, not just focused on US.<br />
### appeal for new contributors who are in florida to join just for this event<br />
### more of the uber-techs are in EU than in US<br />
### who would a marketing event speak to? susecon attendees staying on? press? suse fans who are not contributors?<br />
# We need to name this event<br />
## suggested names:<br />
### openSUSE Camp<br />
### openSUSE Fellowship<br />
### openSUSE Forum<br />
### openSUSE Huddle<br />
### openSUSE LiveCon<br />
### openSUSE Summit<br />
### openSUSE Symposium<br />
#### Note: We should probably come up with a name that is more universal so that similar events which might occur in other countries gain similar branding recognition<br />
# Breaking down the planning; what needs to be planned?<br />
## Create a schedule of milestones to be completed<br />
### Identify Action Items to be listed below<br />
### Identify Questions to be addressed below<br />
# Call for volunteers<br />
<br />
== Open Action Items ==<br />
<br />
# Website for Conference information and registration.<br />
## Suggest that we use indico. It is the tool used for osc11.<br />
# SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
# Artwork needed!<br />
## Needs to be completed by March 1 so we can advertise at majority of events.<br />
### Posters<br />
### Online Banners<br />
### Flyers to hand out at events<br />
<br />
== Open Questions ==<br />
# What kind of funding can we assume for this event? Especially as it is close to the main oSC event and thus budget-competitive. <br />
# Do we want to provide exhibit space? <br /> '''Note:''' Need to confer with hotel about exhibit rules and equipment (e.g. table rentals)<br />
# What kind of funding will SUSE help out with and do we want to charge a nominal fee (typical of many US events) for registrations to offset costs?<br />
# Do we want to provide discount registrations to SUSECon for registered openSUSE members who wish to attend both events?<br />
# What hours do we want to provide? All day Fri-Sun?<br />
#Travel considerations for arrival and departure need to be noted<br />
# Do we want to make the event bi-lingual to attract more people from Spanish-speaking countries?<br />
# What should we use to entice people to register early? Having an early registration count will help with planning and will help mitigate expenses.<br />
<br />
== FAQ ==<br />
# Hotel Room Availability: <br /> SUSE has blocked a large number of rooms for this event. This block of rooms will open in April. The room rate will be around $129/night. (The hotel has over 1300 rooms.)<br />
# What resources are available at the venue?<br />
## Number of rooms and size: <br /> There are at least 8 breakout rooms of varying sizes available.<br /> The ballroom for main events. <br />Rooms for storage. <br />See [http://www.thecaribeorlando.com/caribe-royale/meetings-events/floor-plans-capacity-charts/ Caribe Royal flor plan] for the venue floor plan. <br /><br />
## Equipment Availability: <br /> Each room will be equipped with a projector and screen. <br />Additional equipment will need to be requested prior to the event.<br />
## SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup.<br />
<br />
== Planning Calendar ==<br />
<br />
=== February ===<br />
* 1 February - Kickoff Meeting on IRC <br />
* 3 February - Announcement of poll to name the event<br />
* 11 February - Closing of poll to name the event<br />
* 1-8 February - Formation of teams<br />
<br />
=== March ===<br />
* 1 March - Deadline to complete artwork and submit to printers<br />
* 3 March - [irc://freenode.net/#opensuse-project IRC Status Update Meeting] 18:00 UTC <br />
* 6 March - Formal announcement to the world about our Event<br />
** Press Releases<br />
** Email to Announce-opensuse@o.o<br />
** Article on news.opensuse.org</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_planning&diff=48847openSUSE:Summit planning2012-02-06T20:05:42Z<p>Wwarlock: /* Add your name here to volunteer to help with the planning */</p>
<hr />
<div>SUSE has decided to donate space following their SUSECon conference in Orlando Florida. The main conference is September 18-21, and openSUSE has the facilities from September 21-23. Planning communication will be through the project IRC and mailing list<br />
<br />
* When: September 21-23, 2011<br />
* Where: [http://www.thecaribeorlando.com/ Caribe Royale Hotel] Orlando, FL<br />
<br />
<br />
== [http://bit.ly/xjGuee Vote for the name of the event today! Deadline 11-Feb-2012] ==<br />
<br />
<br />
== Add your name here to volunteer to help with the planning ==<br />
More than one person can be on any task. One person can be on multiple tasks.<br />
* Promotion Committee:<br />
** Artwork: CarlosRibeiro, anditosan<br />
** Social Media Bryen Yunashko<br />
** Press: Jos, Amie@suse<br />
** Contact local LUGS, user groups<br />
* Technical Committee:<br />
** Indico setup: suseROCKS, AlanClark, Dragotin<br />
*** Registrations<br />
*** CFP Submissions<br />
** Android Setup: Prusnak , [[User:wwarlock|Sj]] (but looking for some more information)<br />
** Wordpress Setup: [[User:wwarlock|Sj]] (but looking for some more information)<br />
*** General Attendee Information<br />
* Program committee: suseROCKs, AlanClark, Druonysus<br />
::: Those that register by September 15 will be invited to attend the Friday SUSECon sessions and closing keynote.<br />
::: A suggest program format is:<br />
::::Friday September 21 9:00 - 12:00 SUSECon sessions and keynote<br />
::::Friday September 21 14:00 - 17:00 openSUSE Event sessions<br />
::::Friday September 21 18:00 - 22:00 openSUSE Event Evening Celebration<br />
::::Saturday September 22 9:00 - 10:00 openSUSE Event Keynote<br />
::::Saturday September 22 10:00 - 17:00 openSUSE Event sessions<br />
::::Saturday September 22 18:00 - 22:00 openSUSE Event Evening Party<br />
* Evening Entertainment Committee:<br />
** Friday Night<br />
** Saturday Night<br />
* Onsite Committee:<br />
** Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available. <br />
<br />
** Registration Desk: CarlosRibeiro<br />
:: The openSUSE event registration will occur through indigo. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
** Presentation Room Chairs: Druonysus<br />
** General Floor Staff<br />
** Session Video Recording<br />
** Materials<br />
*** Badges<br />
*** Bag <br />
*** Program Guide<br />
*** Other giveaways<br />
* Sponsorship Committee<br />
** Finding event sponsors:<br />
** Travel sponsorship: Handled through the travel program<br />
* Miscellaneous<br />
** hotel room block, discount codes: AlanClark<br />
** Coordination with SUSECon Staff: AlanClark, Jos<br />
<br />
== Feb 1, Kick off meeting agenda ==<br />
* [http://bit.ly/yAPh4A Meeting Transcript]<br />
* [http://lists.opensuse.org/opensuse-project/2012-02/msg00020.html Meeting Summary]<br />
* 18:00 UTC (1 p.m. Eastern/10 a.m. Pacific)<br />
* [irc://freenode.net/#opensuse-project #openSUSE-Project IRC Channel]<br />
<br />
# Define the target audience for this event<br />
## (Notes from the last project meeting:<br />
### a great opportunity to fly in folks from Central America, Mexico and Canada, not just focused on US.<br />
### appeal for new contributors who are in florida to join just for this event<br />
### more of the uber-techs are in EU than in US<br />
### who would a marketing event speak to? susecon attendees staying on? press? suse fans who are not contributors?<br />
# We need to name this event<br />
## suggested names:<br />
### openSUSE Camp<br />
### openSUSE Fellowship<br />
### openSUSE Forum<br />
### openSUSE Huddle<br />
### openSUSE LiveCon<br />
### openSUSE Summit<br />
### openSUSE Symposium<br />
#### Note: We should probably come up with a name that is more universal so that similar events which might occur in other countries gain similar branding recognition<br />
# Breaking down the planning; what needs to be planned?<br />
## Create a schedule of milestones to be completed<br />
### Identify Action Items to be listed below<br />
### Identify Questions to be addressed below<br />
# Call for volunteers<br />
<br />
== Open Action Items ==<br />
<br />
# Website for Conference information and registration.<br />
## Suggest that we use indico. It is the tool used for osc11.<br />
# SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
# Artwork needed!<br />
## Needs to be completed by March 1 so we can advertise at majority of events.<br />
### Posters<br />
### Online Banners<br />
### Flyers to hand out at events<br />
<br />
== Open Questions ==<br />
# What kind of funding can we assume for this event? Especially as it is close to the main oSC event and thus budget-competitive. <br />
# Do we want to provide exhibit space? <br /> '''Note:''' Need to confer with hotel about exhibit rules and equipment (e.g. table rentals)<br />
# What kind of funding will SUSE help out with and do we want to charge a nominal fee (typical of many US events) for registrations to offset costs?<br />
# Do we want to provide discount registrations to SUSECon for registered openSUSE members who wish to attend both events?<br />
# What hours do we want to provide? All day Fri-Sun?<br />
#Travel considerations for arrival and departure need to be noted<br />
# Do we want to make the event bi-lingual to attract more people from Spanish-speaking countries?<br />
# What should we use to entice people to register early? Having an early registration count will help with planning and will help mitigate expenses.<br />
<br />
== FAQ ==<br />
# Hotel Room Availability: <br /> SUSE has blocked a large number of rooms for this event. This block of rooms will open in April. The room rate will be around $129/night. (The hotel has over 1300 rooms.)<br />
# What resources are available at the venue?<br />
## Number of rooms and size: <br /> There are at least 8 breakout rooms of varying sizes available.<br /> The ballroom for main events. <br />Rooms for storage. <br />See [http://www.thecaribeorlando.com/caribe-royale/meetings-events/floor-plans-capacity-charts/ Caribe Royal flor plan] for the venue floor plan. <br /><br />
## Equipment Availability: <br /> Each room will be equipped with a projector and screen. <br />Additional equipment will need to be requested prior to the event.<br />
## SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup.<br />
<br />
== Planning Calendar ==<br />
<br />
=== February ===<br />
* 1 February - Kickoff Meeting on IRC <br />
* 3 February - Announcement of poll to name the event<br />
* 11 February - Closing of poll to name the event<br />
* 1-8 February - Formation of teams<br />
<br />
=== March ===<br />
* 1 March - Deadline to complete artwork and submit to printers<br />
* 3 March - [irc://freenode.net/#opensuse-project IRC Status Update Meeting] 18:00 UTC <br />
* 6 March - Formal announcement to the world about our Event<br />
** Press Releases<br />
** Email to Announce-opensuse@o.o<br />
** Article on news.opensuse.org</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock&diff=48846User:Wwarlock2012-02-06T19:54:14Z<p>Wwarlock: </p>
<hr />
<div><div style="width:76%; float:left"><br />
{{Box-header|About Me|{{FULLPAGENAME}}|}}<br />
<br />
'''Intro'''<br />
<br />
* I am Shayon Mukherjee a.k.a SJ (you can call me that) and i really love contributing to openSUSE in which ever possible way i can. <br />
* I havent been active in the openSUSE for quite a long time. But finding ways to get into the community<br />
<br />
'''Interests'''<br />
* Free time : I love hacking into codes, mess up my deployments and create some nice patches/apps, or work on the existing ones.<br />
*Other interest which i enjoy and cherish is Photography , Videography and sports like badminton,cricket,hockey and football.<br />
<br />
'''Skills/languages'''<br />
Ruby on Rails, Javascript, Sever handling, HTML5 and CSS3<br />
<br />
'''Linux Experience'''<br />
<br />
My linux expereince started with openSUSE 11.1 and is on :) . I came to know about it from one of my teachers who uses it to teach graphic design in my School.And from that day i very much like to work on it and try to contribute in some or the other way<br />
<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:22%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
<center>[[File:SJ-Final.png|60px]]</center><br />
<br />
'''Contact'''<br />
<br />
[mailto:its@shayon.me its@shayon.me]<br />
<br />
Shayonj on [[Help:Communication/IRC|IRC]]<br />
<br />
{{Box-footer|}}<br />
</div></div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Summit_planning&diff=48845openSUSE:Summit planning2012-02-06T19:51:18Z<p>Wwarlock: </p>
<hr />
<div>SUSE has decided to donate space following their SUSECon conference in Orlando Florida. The main conference is September 18-21, and openSUSE has the facilities from September 21-23. Planning communication will be through the project IRC and mailing list<br />
<br />
* When: September 21-23, 2011<br />
* Where: [http://www.thecaribeorlando.com/ Caribe Royale Hotel] Orlando, FL<br />
<br />
<br />
== [http://bit.ly/xjGuee Vote for the name of the event today! Deadline 11-Feb-2012] ==<br />
<br />
<br />
== Add your name here to volunteer to help with the planning ==<br />
More than one person can be on any task. One person can be on multiple tasks.<br />
* Promotion Committee:<br />
** Artwork: CarlosRibeiro, anditosan<br />
** Social Media Bryen Yunashko<br />
** Press: Jos, Amie@suse<br />
** Contact local LUGS, user groups<br />
* Technical Committee:<br />
** Indico setup: suseROCKS, AlanClark, Dragotin<br />
*** Registrations<br />
*** CFP Submissions<br />
** Android Setup: Prusnak , [[User:wwarlock|Sj]] (but looking for some more information)<br />
** Wordpress Setup: [[User:wwarlock|Sj]]<br />
*** General Attendee Information<br />
* Program committee: suseROCKs, AlanClark, Druonysus<br />
::: Those that register by September 15 will be invited to attend the Friday SUSECon sessions and closing keynote.<br />
::: A suggest program format is:<br />
::::Friday September 21 9:00 - 12:00 SUSECon sessions and keynote<br />
::::Friday September 21 14:00 - 17:00 openSUSE Event sessions<br />
::::Friday September 21 18:00 - 22:00 openSUSE Event Evening Celebration<br />
::::Saturday September 22 9:00 - 10:00 openSUSE Event Keynote<br />
::::Saturday September 22 10:00 - 17:00 openSUSE Event sessions<br />
::::Saturday September 22 18:00 - 22:00 openSUSE Event Evening Party<br />
* Evening Entertainment Committee:<br />
** Friday Night<br />
** Saturday Night<br />
* Onsite Committee:<br />
** Venue Setup<br />
:: The venue has plenty of conference rooms for sessions, parties... SUSECon will keep the keynote stage setup for us for a Saturday morning keynote.<br />
:::1 large room with stage for keynote sessions<br />
:::4 session rooms, with projector, screen, and audio system (Suggest 3 rooms for sessions, 1-2 rooms for BoFs)<br />
:::1 social lounge (We will need to decide how what we want in this room)<br />
:::1 speaker ready room, with computers, project and printers<br />
:::2 storage, conference prep rooms<br />
:::1 Registration booth, with computers and printer<br />
:::For evening events, we have the large ballroom or areas outside the convention hall. I saw Jos' note about wanting to play chef. I asked Alexia to check with the venue to see what options are available. <br />
<br />
** Registration Desk: CarlosRibeiro<br />
:: The openSUSE event registration will occur through indigo. SUSECon will have computers, printers setup for their registration system. On September 16th, we should plan to transfer the registered names from indigo into the SUSECon systems to print the conference badges SUSECon will supply the badge holders, notebook and pen. It will be up to use to supply additional materials such as printed programs or conference bags. <br />
** Presentation Room Chairs: Druonysus<br />
** General Floor Staff<br />
** Session Video Recording<br />
** Materials<br />
*** Badges<br />
*** Bag <br />
*** Program Guide<br />
*** Other giveaways<br />
* Sponsorship Committee<br />
** Finding event sponsors:<br />
** Travel sponsorship: Handled through the travel program<br />
* Miscellaneous<br />
** hotel room block, discount codes: AlanClark<br />
** Coordination with SUSECon Staff: AlanClark, Jos<br />
<br />
== Feb 1, Kick off meeting agenda ==<br />
* [http://bit.ly/yAPh4A Meeting Transcript]<br />
* [http://lists.opensuse.org/opensuse-project/2012-02/msg00020.html Meeting Summary]<br />
* 18:00 UTC (1 p.m. Eastern/10 a.m. Pacific)<br />
* [irc://freenode.net/#opensuse-project #openSUSE-Project IRC Channel]<br />
<br />
# Define the target audience for this event<br />
## (Notes from the last project meeting:<br />
### a great opportunity to fly in folks from Central America, Mexico and Canada, not just focused on US.<br />
### appeal for new contributors who are in florida to join just for this event<br />
### more of the uber-techs are in EU than in US<br />
### who would a marketing event speak to? susecon attendees staying on? press? suse fans who are not contributors?<br />
# We need to name this event<br />
## suggested names:<br />
### openSUSE Camp<br />
### openSUSE Fellowship<br />
### openSUSE Forum<br />
### openSUSE Huddle<br />
### openSUSE LiveCon<br />
### openSUSE Summit<br />
### openSUSE Symposium<br />
#### Note: We should probably come up with a name that is more universal so that similar events which might occur in other countries gain similar branding recognition<br />
# Breaking down the planning; what needs to be planned?<br />
## Create a schedule of milestones to be completed<br />
### Identify Action Items to be listed below<br />
### Identify Questions to be addressed below<br />
# Call for volunteers<br />
<br />
== Open Action Items ==<br />
<br />
# Website for Conference information and registration.<br />
## Suggest that we use indico. It is the tool used for osc11.<br />
# SUSECon has a roomblock, which will be made available in April. AlanClark has asked the SUSECon team to supply us with the html code needed to link to the roomblock registration from our event website.<br />
# Artwork needed!<br />
## Needs to be completed by March 1 so we can advertise at majority of events.<br />
### Posters<br />
### Online Banners<br />
### Flyers to hand out at events<br />
<br />
== Open Questions ==<br />
# What kind of funding can we assume for this event? Especially as it is close to the main oSC event and thus budget-competitive. <br />
# Do we want to provide exhibit space? <br /> '''Note:''' Need to confer with hotel about exhibit rules and equipment (e.g. table rentals)<br />
# What kind of funding will SUSE help out with and do we want to charge a nominal fee (typical of many US events) for registrations to offset costs?<br />
# Do we want to provide discount registrations to SUSECon for registered openSUSE members who wish to attend both events?<br />
# What hours do we want to provide? All day Fri-Sun?<br />
#Travel considerations for arrival and departure need to be noted<br />
# Do we want to make the event bi-lingual to attract more people from Spanish-speaking countries?<br />
# What should we use to entice people to register early? Having an early registration count will help with planning and will help mitigate expenses.<br />
<br />
== FAQ ==<br />
# Hotel Room Availability: <br /> SUSE has blocked a large number of rooms for this event. This block of rooms will open in April. The room rate will be around $129/night. (The hotel has over 1300 rooms.)<br />
# What resources are available at the venue?<br />
## Number of rooms and size: <br /> There are at least 8 breakout rooms of varying sizes available.<br /> The ballroom for main events. <br />Rooms for storage. <br />See [http://www.thecaribeorlando.com/caribe-royale/meetings-events/floor-plans-capacity-charts/ Caribe Royal flor plan] for the venue floor plan. <br /><br />
## Equipment Availability: <br /> Each room will be equipped with a projector and screen. <br />Additional equipment will need to be requested prior to the event.<br />
## SUSECon will hold sessions and keynotes on September 21. The openSUSE event will begin on that date after SUSECon has ended. We will leverage the room setup from SUSECon. We will need to co-ordinate any additional setup.<br />
<br />
== Planning Calendar ==<br />
<br />
=== February ===<br />
* 1 February - Kickoff Meeting on IRC <br />
* 3 February - Announcement of poll to name the event<br />
* 11 February - Closing of poll to name the event<br />
* 1-8 February - Formation of teams<br />
<br />
=== March ===<br />
* 1 March - Deadline to complete artwork and submit to printers<br />
* 3 March - [irc://freenode.net/#opensuse-project IRC Status Update Meeting] 18:00 UTC <br />
* 6 March - Formal announcement to the world about our Event<br />
** Press Releases<br />
** Email to Announce-opensuse@o.o<br />
** Article on news.opensuse.org</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Wiki_team&diff=33350openSUSE:Wiki team2011-01-23T17:30:25Z<p>Wwarlock: </p>
<hr />
<div>__NOTOC__<br />
<br />
<center>[[Image:Icon-wiki.png|48px]]</center><br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
=== Introduction ===<br />
</div><br />
Anyone with a user account can edit the wiki, and be a wiki editor. However, few of them help, contribute and maintain the wiki on a daily basis. We do and that makes us the ''Wiki Team''. We provide high quality product information, clear documentation and a place for collaboration on projects. All of this in a well structured, standardized and easy readable way. By the way: If you are looking for help about this wiki you should head over to the [[Portal:Wiki|Wiki Portal]] and continue from there.<br />
<br />
{{Info|'''Note:''' Our first current goal is to make old links to work. So do not remove redirects that do just that, temporarily fix links that worked in old English wiki. We will go trough them and remove those that are not used, but right now they make transition easier.}}<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
<br />
=== Communicate ===<br />
</div><br />
These are the way to contact us:<br />
* IRC: [irc://irc.opensuse.org/opensuse-wiki #opensuse-wiki]<br />
* Forums: [http://forums.opensuse.org/english/community/opensuse-wiki-discussions/ Wiki discussions].<br />
* Wiki: [[Help:Message_board|Message board]].<br />
{{Mailinglist|opensuse-wiki|For openSUSE wiki related topics}}<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== Members ===<br />
</div><br />
<!--Please place in alphabetic order by wiki username --><br />
*{{User|digitaltomm}}<br />
*{{User|Fsundermeyer}}<br />
*{{User|Hennevogel}}<br />
*{{User|Jonathan_R}}<br />
*{{User|Muhlemmer}}<br />
*{{User|Rajko_m}}<br />
*{{User|Saigkill}}<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
<br />
=== How to join ===<br />
</div><br />
You want to join us in our efforts? Just swing by our communication channels and become a regular. Pick up maintenance tasks, hang out, have fun. <br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
=== Tasks ===<br />
</div><br />
'''These tasks are always in need of attention'''<br />
<br />
*[[:Category:Pages_that_are_obsolete|Obsolete pages]]&mdash;<small>Pages that are not needed anymore because they describe obsolete stuff.</small><br />
*[[:Category:Pages to cleanup|Pages to cleanup]]&mdash;<small>Pages that don't currently meet our high standard of excellence.</small><br />
*[[:Category:Pages to merge|Pages to merge]]&mdash;<small>Pages that need to be merged with other pages.</small><br />
*[[:Category:Pages that need expanding|Pages to expand]]&mdash;<small>Pages that need to be expanded to fully cover a topic.</small><br />
*[[:Category:Pages for SDB|Pages to move to the SDB]]&mdash;<small>Pages that should be polished to adhere the [[SDB:Howto|Support Database (SDB) standards]] and be moved to the category [[:Category:SDB|SDB]].</small><br />
*[[:Category:Pages to delete|Pages to delete]]&mdash;<small>Pages that have been marked for deletion.</small><br />
*[[Special:Lonelypages|Lonely pages]]&mdash;<small> These are pages are not linked to from any other page, and thus inaccessible without the use of the search engine.</small><br />
*[[Special:Wantedpages|Wanted pages]]&mdash;<small> These pages don't exist, but there are two or more links to them. In other words, if you want to write article that people need check this list first. </small><br />
*[[Special:DoubleRedirects|Double redirects]]&mdash;<small> Redirects that redirect to a redirect</small><br />
*[[Special:BrokenRedirects|Broken redirects]]&mdash;<small> Redirects that redirect to a non-existing page</small><br />
*[[Special:Categories|Categories]]<br />
*[[Special:Unusedcategories|Unused categories]]&mdash;<small> Categories with no pages in it</small><br />
*[[Special:Uncategorizedpages|Uncategorized pages]]&mdash;<small> Pages that are not in any category</small><br />
*[[Special:WantedCategories|Wanted Categories]] &mdash;<small> Used categories without description and without being a member of an other category (=without being a subcategry)</small><br />
<br />
[[Category:Team pages]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Board_election_2010_platform_psankar&diff=32571openSUSE:Board election 2010 platform psankar2011-01-06T17:26:47Z<p>Wwarlock: </p>
<hr />
<div>{{Board navbar}}<br />
== Platform ==<br />
{{Info|'''Note:''' This page is used by the candidate of the board election as a platform to show his views and answer some standard questions. }}<br />
<br />
==Introduction and Biography== <br />
I am Sankar. I have been associated with the openSUSE project ever since its inception. I am from India/APAC. <br />
<br />
I am a '''programmer''' at heart. I like Packaging and Community building. I love Legal things. I enjoy philosophy and psychology. I am one of the members of the '''opensource review board''' in Novell, which specializes in copyrights, licensing, usage of open-source software in Novell products etc. I intend to get a part-time legal degree as well in the future, so as to supplement my engineering skills. <br />
<br />
In the past I have worked as the maintainer of Evolution mailer. I relicensed Evolution from GPL to LGPL. I am working as an ambassador of openSUSE and is involved in marketing of it. I have '''authored an edition of Linux Identity''' - an English magazine out of France, for [http://psankar.blogspot.com/2009/03/book-on-opensuse-111-linuxidentity.html openSUSE 11.1 release] . In the Indian state of Tamil Nadu, I worked with the state Government to decide the syllabus for a paper named open-source in Indian Engineering colleges. I also worked with the engineering college lecturers to train them on Linux and openSUSE. I have talked about openSUSE and distributed hundreds of DVDs to various college students. <br />
<br />
Currently, I am working as part of the openSUSE GNOME and Marketing teams. I am known to be forthright and speaking my mind yet not affecting any individual in the community personally. I will continue to remain so. <br />
<br />
From a technical perspective, Working with teams: I migrated evolution summary storage from flatfile to sqlite db, implemented support to write Evolution plugins using C#, Patch to bootchart to know which processes grind your disk on boot how long, implemented sqlite-commander, worked on both '''kernel space and user space'''.<br />
<br />
I have a blog as well and I tend to get proud of my writings and reader-count at times, even though it is not spectacular always ;) <br />
<br />
In my free time, I enjoy reading a lot and once made a crazy video as well: <br />
http://vimeo.com/11321891<br />
<br />
== Short Term Tasks ==<br />
The near-future high priority tasks (as opposed to major Issues) that I believe the board will be involved with are:<br />
<br />
+ Setting up the Foundation<br />
<br />
+ Transfer of copyrights & trademarks<br />
<br />
+ Putting up the new processes for the functioning of the new board and the foundation<br />
<br />
+ Bridging the community and the new owner of Novell (Attachmate).<br />
<br />
+ Supporting the two new initiatives of Tumbleweed and Evergreen. May be if Tumbleweed succeeds on a longer term, we may not need Evergreen. But as for the foreseeable future, we need both the projects.<br />
<br />
== Long Term Tasks ==<br />
The long term tasks which are equally valuable, that I believe the board (and not just me), if I get elected, will pursue are: <br />
<br />
+ Maintain a healthy community with no discomfort based on race, gender or religion and create a place where everyone feels comfortable.<br />
<br />
+ Improve the communication of stakeholders. Improve the signal-to-noise ratio in the mailing lists, forums etc.<br />
<br />
+ Make openSUSE an attractive development platform for all types of programmers (Android App. writers, Web developers, Java developers etc.)<br />
<br />
+ Do what it takes to improve the participation of women in our community. This involves things like Making our conferences compliant to http://geekfeminism.org/2010/11/29/get-your-conference-anti-harassment-policy-here/ <br />
<br />
Women t-shirts on our events, resurrection of the mailing list, providing mentorship in events like GSOC, etc. Ubuntu-women community seems to be doing good and we could learn a lesson or two from there. It will be best done by Women than Men and the board should assist it in all the ways. We have capable women in our community, who can do these activities. (For me, the idea of improve women participation and harassment-prevention became interesting, when a person whom I admire, Kathy Sierra stopped her work due to harassment)<br />
<br />
+ Ensure our distro is very accessibility friendly and can be used by people who are differently abled. <br />
<br />
+ Eliminate Poisonous people who are unskilled and causes splits. Disinfect the people who are skilled but affected.<br />
<br />
+ Make sure openSUSE Marketing and Weekly-News teams get good interactions with the rest of the teams for a better external image of our distro. <br />
<br />
+ Don't Panic ;-)<br />
<br />
== Ideas for the board ==<br />
We should make our distro more developer friendly and look for new opportunities to expand. Having strategic partnerships with people like github, google-code etc. to work with OBS is one example of it, Making OBS accessible via open-id etc.<br />
<br />
We should resume Bryen's initiative of HelpingHands, where who work upstream from openSUSE to talk and share about their product.<br />
<br />
Improve our videos section. Get the events like openSUSE conferences videotapped and help them reach a wider audience, who cannot afford to travel.<br />
<br />
== GNOME & KDE ==<br />
I have been involved with GNOME more than KDE in openSUSE and so I have added this section, as it is one of the sensitive topics of openSUSE (and a perennial problem as well) <br />
<br />
Applications constitute a desktop. Each desktop has its own set of applications and strengths. GNOME has focussed more on usability and solving the needs of a typical office/home user. Exchange Server, Novell GroupWise connectivity, ability to see one's appointments for the day from the tray Calendar, Buying music online from media player, LibreOffice interaction, Tomboy etc. are some examples of its strengths. KDE otoh has a lot of developer friendly applications. It has a rich repertoire of developer tools that no other desktop has, such as KCachegrind, Kompare, KScope etc. It does not restrict you and allows to customize anything and everything. Compare preferences page of Kate and gedit. <br />
<br />
Both desktops have their share of weaknesses. The browsers of both desktops are far from considering for daily usage. Both of them lack a decent offline blogging client (check windows live writer before you suggest the existing solutions). Both of them don't hug the cloud data nicely yet. (no reliable out-of-the-box way to manipulate Google Docs list in Nautilus/konqueror for eg.)<br />
<br />
Most of the serious developers I know of use applications from both desktops. Also, they use external applications like Skype which doesn't belong to either of GNOME or KDE. I, personally, login to a GNOME desktop, and use applications of: thunar (xfce file manager), gnome-do app. launcher (mono), chromium (google) or FF (mozilla), kompare patchviewer (KDE), Wally (kde), vim, git etc. As Linus once said, I use the right tool that does the job best.<br />
<br />
Most of the arguments on GNOME vs KDE (vs instead of &) happens because of blind fanboys. These are the people who take sides and sees the world in Black and white and eat only one flavor of icecream. Most of the times, the people who catalyze these fights are of no practical use to the distribution and are intent on promoting their personal agenda. Just like how politicians polarize people into a "It's Us vs Them" during wars, these people also drag the real contributors of our distro into a war mode. It is saddening that we as a distro has lost a lot of valuable time in these desktop wars. The desktop wars have already alienated some key contributors and we should not lose anymore.<br />
<br />
If I am elected as a board member, I would like to work on spreading the unique nature of distro, to offer the best GNOME and KDE desktops. I personally believe that Linux on Desktop is understaffed by almost all the Linux companies and focus is more on the servers. I am optimistic that we as a distro is capable of generating enough enthusiasm for desktop linux, Reasons: We have both the desktops that appeal to all geographies, people are no longer sticking to their windows apps. and want to move to the cloud, the price of hardware is falling down making it hard to hide the cost of windows, etc. <br />
<br />
Another goal of mine will be to terminate these wars in the beginning stage itself, by concluding poisonous mail threads as and when they are started, by summoning the interested parties in an IRC meeting instead of fighting over mails, and attracting poisonous people.<br />
<br />
==Mono==<br />
Another topic that at times gains some talk is about Mono. My opinion on mono is as follows. There are two perspectives given. Feel free to read/ignore any section as you wish.<br />
<br />
From a '''programmer perspective''': C is a tough language to write applications which have to be managed for long. As a programmer from India, where a lot of maintenance projects are sent, I know how cruel C can be. For a company, If the project you are going to develop is not going to be as impactful as the linux kernel, both financially and performance wise, it is better to implement it in a language which takes care of memory management thus eliminating lots of crashes and leaks. <br />
<br />
Anyone who has written or maintained large scale code, can tell you, type-safety is a very very vital part of programming. C# provides this as opposed to languages like python, out of the box. Also, it provides certain modern elements of programming like humongous collection of classes in a rich Library, LINQ, Generics, Delegates, ParallelExtensions, Platform Independence, Async etc. These are geek porn. IMHO, C# is the Chuck Norris of programming languages. Stackoverflow stats have shown that queries on C# are increasing every year. So, I have all reasons to love the Mono project. <br />
<br />
From a '''political perspective''': <br />
In our current scenario, C# is a much safer language than Java, politically.<br />
<br />
A claim that is often made is, MSFT may sue if you use Mono. It is wrong. Please refer to ECMA specifications and the MSFT community commitment. Also, if MSFT wants to sue, they can sue not just Mono, they can sue any language, say Python, Java, etc. MSFT even made official statements that using Moonlight or Monodroid will not be sued by them.<br />
<br />
A considerable number of corporate and college intranet servers run ASP.NET. We need to provide a way to switch these people to Linux without asking them to rewrite their web applications. <br />
<br />
So politically as well I believe we benefit by Mono and we should love it. Infact, openSUSE should be the best distribution for mono development. <br />
<br />
Are there things to improve synergistically between Mono and openSUSE ? Yes, A lot.<br />
<br />
==Why you should vote for me?==<br />
Primary Reason: I feel I am qualified to be a board member with my expertise on community building, legal aspects, communication skills and technology. <br />
<br />
Auxiliary Reason: A board (or any organization for that matter) needs to have good diversity for a healthy life. I believe I am unique and different from the rest of the board members on few key aspects. <br />
<br />
Though Programming or FOSS-Licensing is not a requirement to be a board member, a board will benefit from having a programmer. AFAICS, I am the '''only person''' who is a '''programmer''' in my day job among the current list of contestants and board members. Programming is very relevant to a board's job but not a direct requirement.<br />
<br />
Almost all of the current board members and contestants are from the western world. I am from the eastern world. Electing me will help having atleast one board member online 24x7 and will add to the cultural and geographical diversity of the board.<br />
<br />
== Endorsements ==<br />
If you like to endorse me, this area is for you :-)<br />
<br />
Psankar: awesome. What you do for openSUSE, despite all the push back you get - incredible. I deeply respect you for it and would place my trust in you as openSUSE Board member - jospoortvliet<br />
<br />
Psankar: If anyone talks about openSUSE in India, they start with mentioning you being the ambassador :) FACE of openSUSE in India. For people with the power to vote, pitch in for Sankar. The commitment that Sankar brings to the project would add a lot of value. A crazy guy whose life revolves around getting things done with/for openSUSE. - abharath<br />
<br />
Sankar: I can see openSUSE's future with you being the Board Member. We definitely need at least one programmer on board. All the best ;) . --Shayon 10:26, 6 January 2011 (MST)</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:11.4_Marketing_Hackfest&diff=32339openSUSE:11.4 Marketing Hackfest2011-01-03T17:35:46Z<p>Wwarlock: </p>
<hr />
<div>openSUSE 11.4 is slated for release in March. Let's get together and dedicate four days face-to-face to hack out what we need to do for promoting the release. We would like to have this event in Los Angelos, USA, during the 4 days before SCALE: 21-24 Feb (scale is from 25-27 feb)<br />
<br />
A request on the marketing ML has gone out to send Jos Poortvliet your travel cost estimates etc before 4 January, 2011.<br />
<br />
The mail needs to contain:<br />
- Name (like in passport), address, phone (international!)<br />
- most up to date travel costs in USD<br />
- how much reimbursement you would need to be able to come (50/80/100%)<br />
- if you can afford to pay and get reimbursement later<br />
- a short description/explanation of why you should be there - what do you <br />
intend to contribute and what are your contributions to date.<br />
<br />
Below those who have indicated interest in attending. THe list will be replaced with the actual attendees once the decisions have been made.<br />
<br />
{|style="background:#d9e5bf;font-size:100%; border:1px solid #aaa;" border="1" cellpadding="2" cellspacing="3"<br />
!style="background:#fff;color:#669900"| Interested Attendees<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
|-<br />
!style="background:#669900;color:#fff"| Name <br />
!style="background:#669900;color:#fff"| Travel from:<br />
!style="background:#669900;color:#fff"| Sponsorship Req?<br />
!style="background:#669900;color:#fff"| Preferred Date<br />
|-<br />
| Manu Gupta<br />
| India<br />
| Yes<br />
| Later, the Better<br />
|-<br />
| Bryen Yunashko<br />
| Chicago, Il<br />
| Yes<br />
| Feb 3-4<br />
|-<br />
|-<br />
| Jos Poortvliet<br />
| Netherlands<br />
| Yes<br />
| Feb 3-4<br />
|-<br />
|<br />
|-<br />
| Bruno Friedmann<br />
| Switzerland<br />
| Yes<br />
| Feb 20-27<br />
|-<br />
|-<br />
|Izabel Valverde<br />
|Brazil<br />
|Yes<br />
|Flexible<br />
|-<br />
|Carlos Ribeiro<br />
|Brazil<br />
|Yes<br />
|Feb 3-4<br />
|-<br />
|-<br />
|Sankar P<br />
|India<br />
|Yes<br />
|The later the better, personally.<br />
|-<br />
|-<br />
|Javier Llorente<br />
|Spain?<br />
|Yes<br />
|Feb 3-4<br />
|-<br />
|-<br />
|Helen South<br />
|Sydney +<br />
|Yes<br />
|flexible, later<br />
|-<br />
|Kostas Koudaras<br />
|Greece<br />
|Yes<br />
|Flexible<br />
|-<br />
|Gnokii<br />
|Germany<br />
|Yes (Hotel, Travel depends on place)<br />
|until 15th March<br />
|-<br />
<br />
|}<br />
Below is our proposed agenda. Please feel free to submit your ideas for topics to cover.<br />
<br />
{|style="background:#d9e5bf;font-size:100%; border:1px solid #aaa;" border="1" cellpadding="2" cellspacing="3"<br />
!style="background:#fff;color:#669900"| Proposed Agenda<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
|-<br />
!style="background:#669900;color:#fff"| Name <br />
!style="background:#669900;color:#fff"| Topic<br />
!style="background:#669900;color:#fff"| Description<br />
|-<br />
| Manu <br />
| Web & Social Media Appearance, Helping Hands, Offcourse India<br />
| Help with writing work, New Promo videos and learn a lot <br />
|-<br />
| Bryen Yunashko<br />
| Writing<br />
| Prepare announcements, articles, etc.<br />
|-<br />
|-<br />
| Jos Poortvliet<br />
| Write a feature guide together based on prepared feature list<br />
| Just hard work :D<br />
|-<br />
|-<br />
| gnokii<br />
| Write and prepare marketing materials<br />
| Just hard work :D<br />
|-<br />
|-ww <br />
| Bruno Friedmann<br />
| Just hard work<br />
| Help Kostas's objectives<br />
|-<br />
|-<br />
| Izabel Valverde<br />
| Helping hands<br />
| Announcements, articles, Spreading PR, etc...<br />
|-<br />
| Carlos Ribeiro<br />
| Helping Hands with Ambassadors Marketing Materials <br />
| Announcements, articles, how to setup demos, finish Ambassadors Kit, etc...<br />
|-<br />
| Sankar P<br />
| Share experiences on marketing from India, past releases, general discussion etc.<br />
|-<br />
| Javier Llorente<br />
| Marketing through localization.<br />
| Identifying key elements that should be translated.<br />
|- <br />
| Kostas Koudaras<br />
| Helping Hands with Ambassadors Marketing Materials, Marketing through localization<br />
| Announcements, articles, how to setup demos, finish Ambassadors Kit, Identifying key elements that should be translated<br />
|-<br />
|}</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:11.4_Marketing_Hackfest&diff=31638openSUSE:11.4 Marketing Hackfest2010-12-20T17:09:24Z<p>Wwarlock: </p>
<hr />
<div>openSUSE 11.4 is slated for release in March. Let's get together and dedicate two days face-to-face to hack out what we need to do for promoting the release. We would like to have this event either two days before FOSDEM in Brussels, Belgium or two days after. <br />
<br />
We need to know who is interested in attending and what date is preferable. Deadline to state your intent is 7 January, 2011<br />
<br />
Proposed dates:<br />
A. 3-4 February, 2011 (maybe 1-4 feb)<br />
B. 7-8 February, 2011 (maybe 7-9 feb)<br />
<br />
If you are interested in attending, please indicate below:<br />
<br />
{|style="background:#d9e5bf;font-size:100%; border:1px solid #aaa;" border="1" cellpadding="2" cellspacing="3"<br />
!style="background:#fff;color:#669900"| Interested Attendees<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
|-<br />
!style="background:#669900;color:#fff"| Name <br />
!style="background:#669900;color:#fff"| Travel from:<br />
!style="background:#669900;color:#fff"| Sponsorship Req?<br />
!style="background:#669900;color:#fff"| Preferred Date<br />
|-<br />
| Bryen Yunashko<br />
| Chicago, Il<br />
| Yes<br />
| Feb 3-4<br />
|-<br />
|-<br />
| Jos Poortvliet<br />
| Netherlands<br />
| Yes<br />
| Feb 3-4<br />
|-<br />
|<br />
|-<br />
| Bruno Friedmann<br />
| Switzerland<br />
| Yes (Hotel)<br />
| Feb 3-4<br />
|-<br />
|-<br />
|Izabel Valverde<br />
|Brazil<br />
|Yes<br />
|Feb 3-4<br />
|-<br />
|Carlos Ribeiro<br />
|Brazil<br />
|Yes<br />
|Feb 3-4<br />
|-<br />
|-<br />
|Sankar P<br />
|India<br />
|Yes<br />
|The later the better, personally.<br />
|-<br />
|-<br />
|Javier Llorente<br />
|Spain?<br />
|Yes<br />
|Feb 3-4<br />
|-<br />
|-<br />
|Shayon Mukherjee<br />
|US (Green Bay)<br />
|Yep<br />
|Flexible<br />
|}<br />
<br />
Below is our proposed agenda. Please feel free to submit your ideas for topics to cover.<br />
<br />
{|style="background:#d9e5bf;font-size:100%; border:1px solid #aaa;" border="1" cellpadding="2" cellspacing="3"<br />
!style="background:#fff;color:#669900"| Proposed Agenda<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
|-<br />
!style="background:#669900;color:#fff"| Name <br />
!style="background:#669900;color:#fff"| Topic<br />
!style="background:#669900;color:#fff"| Description<br />
|-<br />
| Bryen Yunashko<br />
| Writing<br />
| Prepare announcements, articles, etc.<br />
|-<br />
|-<br />
| Jos Poortvliet<br />
| Write a feature guide together based on prepared feature list<br />
| Just hard work :D<br />
|-<br />
|-<br />
| gnokii<br />
| Write and prepare marketing materials<br />
| Just hard work :D<br />
|-<br />
|-ww <br />
| Bruno Friedmann<br />
| Testing Writing Howto ?<br />
| Helping in communication (french translation)<br />
|-<br />
|-<br />
| Izabel Valverde<br />
| Helping hands<br />
| Announcements, articles, Spreading PR, etc...<br />
|-<br />
| Carlos Ribeiro<br />
| Helping Hands with Ambassadors Marketing Materials <br />
| Announcements, articles, how to setup demos, finish Ambassadors Kit, etc...<br />
|-<br />
| Sankar P<br />
| Share experiences on marketing from India, past releases, general discussion etc.<br />
|-<br />
| Javier Llorente<br />
| Marketing through localization.<br />
| Identifying key elements that should be translated. <br />
|}<br />
<br />
Bruno Friedmann (tigerfoot) prefer Brussel if before the fosdem<br />
Sankar P (psankar) prefers Nuremberg</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:11.4_Marketing_Hackfest&diff=31637openSUSE:11.4 Marketing Hackfest2010-12-20T17:08:51Z<p>Wwarlock: </p>
<hr />
<div>openSUSE 11.4 is slated for release in March. Let's get together and dedicate two days face-to-face to hack out what we need to do for promoting the release. We would like to have this event either two days before FOSDEM in Brussels, Belgium or two days after. <br />
<br />
We need to know who is interested in attending and what date is preferable. Deadline to state your intent is 7 January, 2011<br />
<br />
Proposed dates:<br />
A. 3-4 February, 2011 (maybe 1-4 feb)<br />
B. 7-8 February, 2011 (maybe 7-9 feb)<br />
<br />
If you are interested in attending, please indicate below:<br />
<br />
{|style="background:#d9e5bf;font-size:100%; border:1px solid #aaa;" border="1" cellpadding="2" cellspacing="3"<br />
!style="background:#fff;color:#669900"| Interested Attendees<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
|-<br />
!style="background:#669900;color:#fff"| Name <br />
!style="background:#669900;color:#fff"| Travel from:<br />
!style="background:#669900;color:#fff"| Sponsorship Req?<br />
!style="background:#669900;color:#fff"| Preferred Date<br />
|-<br />
| Bryen Yunashko<br />
| Chicago, Il<br />
| Yes<br />
| Feb 3-4<br />
|-<br />
|-<br />
| Jos Poortvliet<br />
| Netherlands<br />
| Yes<br />
| Feb 3-4<br />
|-<br />
|<br />
|-<br />
| Bruno Friedmann<br />
| Switzerland<br />
| Yes (Hotel)<br />
| Feb 3-4<br />
|-<br />
|-<br />
|Izabel Valverde<br />
|Brazil<br />
|Yes<br />
|Feb 3-4<br />
|-<br />
|Carlos Ribeiro<br />
|Brazil<br />
|Yes<br />
|Feb 3-4<br />
|-<br />
|-<br />
|Sankar P<br />
|India<br />
|Yes<br />
|The later the better, personally.<br />
|-<br />
|-<br />
|Javier Llorente<br />
|Spain?<br />
|Yes<br />
|Feb 3-4<br />
|Shayon Mukherjee<br />
|US (Green Bay)<br />
|Yep<br />
|Flexible<br />
|}<br />
<br />
Below is our proposed agenda. Please feel free to submit your ideas for topics to cover.<br />
<br />
{|style="background:#d9e5bf;font-size:100%; border:1px solid #aaa;" border="1" cellpadding="2" cellspacing="3"<br />
!style="background:#fff;color:#669900"| Proposed Agenda<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
!style="background:#fff;color:#669900"|<br />
|-<br />
!style="background:#669900;color:#fff"| Name <br />
!style="background:#669900;color:#fff"| Topic<br />
!style="background:#669900;color:#fff"| Description<br />
|-<br />
| Bryen Yunashko<br />
| Writing<br />
| Prepare announcements, articles, etc.<br />
|-<br />
|-<br />
| Jos Poortvliet<br />
| Write a feature guide together based on prepared feature list<br />
| Just hard work :D<br />
|-<br />
|-<br />
| gnokii<br />
| Write and prepare marketing materials<br />
| Just hard work :D<br />
|-<br />
|-ww <br />
| Bruno Friedmann<br />
| Testing Writing Howto ?<br />
| Helping in communication (french translation)<br />
|-<br />
|-<br />
| Izabel Valverde<br />
| Helping hands<br />
| Announcements, articles, Spreading PR, etc...<br />
|-<br />
| Carlos Ribeiro<br />
| Helping Hands with Ambassadors Marketing Materials <br />
| Announcements, articles, how to setup demos, finish Ambassadors Kit, etc...<br />
|-<br />
| Sankar P<br />
| Share experiences on marketing from India, past releases, general discussion etc.<br />
|-<br />
| Javier Llorente<br />
| Marketing through localization.<br />
| Identifying key elements that should be translated. <br />
|}<br />
<br />
Bruno Friedmann (tigerfoot) prefer Brussel if before the fosdem<br />
Sankar P (psankar) prefers Nuremberg</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock/test1&diff=27423User:Wwarlock/test12010-10-08T20:00:59Z<p>Wwarlock: /* FAQ */</p>
<hr />
<div>= Design Guidelines =<br />
<br />
'''The below guidelines are as mentioned by Spreadshirt. We very much want you to go by them.Without which we cannot upload them to our shop'''.<br />
<br />
There are two types of designs – <u>''Vector and Pixel''</u> , you can make your artwork accordingly.<br />
<br />
'''Note:''' <br />
*Save vector designs as .eps <br />
*Only elements which are part of the final design should be included in your uploaded file. <br />
*All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
*Save pixel designs as .jpg, .gif, .png, or .bmp<br />
*Size of pixel designs: max. 10 MB and min. 200 dpi (buttons: 400 dpi) <br />
*Pixel designs may not exceed 3000 x 3000 pixels<br />
<br />
'''Also please mention the number of colors if you want to upload a vector graphic.'''<br />
<br />
=== Requirements for Vector Designs ===<br />
<br />
In order to use plot printing, your vector design must follow a few guidelines (check the FAQ below) i.e. comply with the minimum line thickness, have minimum negative space, have no more than three colors and no color gradients.<br />
<br />
The Spreadshirt Team will review whether or not you have met these requirements before approving your design for release. Most designs are reviewed within 2 business days. If your design does not meet the given requirements, we will send you an e-mail informing you that it has been denied.<br />
<br />
=== Requirements for Pixel Designs ===<br />
<br />
It is currently only possible to upload pixel designs into the T-shirt Designer. By submitting your pixel designs, you assure that no third party rights (copyrights) have been violated. Any designs with violations will be rejected and an e-mail will be sent to you. More information on pixel design requirements can be found in the below helpful FAQ .<br />
<br />
== FAQ ==<br />
# '''Q:How do I create a vector design that will meet all the requirements for a plot printing (Flex / Flock) format?'''<br />
<br />
'''A:''' Vector designs can be created with Corel Draw, Inkscape, or Adobe Illustrator. Please take note of the following tips:<br />
<br />
Convert all design elements and text into curves (paths.) <br />
<br />
''' Adobe Illustrator '''<br />
<br />
The first step is to delete all pixel (bitmap) information. Do this by selecting the pixel information and pressing the delete button on your keyboard. After the pixel information has been deleted, you will need to select all of the design elements (Ctrl A.) Then in the top menu bar, go to Object/Flatten Transparency. On the settings, slide the bar to 100% vector, and check the Convert all Text to Outlines and also check the Convert all Strokes to Outlines . Next, go to the Pathfinder and click on the Merge option. If you don’t see the Pathfinder palette, go to Window/Pathfinder. To finish up, go to Object/Path/Clean Up, and check all three boxes and click OK. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Corel Draw '''<br />
The first step in Corel Draw is to open your Object Manager from the Tools, so that you can see all elements of your design. Second, delete all pixel information by selecting the bitmap element (shown in your Object Manager,) and clicking on the trash can at the bottom of the Object Manager window. Select all design elements, right-click, and select convert into curves . Delete all empty , or no-fill curves . Then select all curves of the same color by pressing the Control (Command) key and clicking on the curves of the same color. Once these curves are selected, combine them by right-clicking and selecting combine , or use the key command Control (Command) L. Repeat this step until all colors have been combined into one curve per color. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Proof the minimum size of the object '''<br />
<br />
After the conversion into curves (or paths,) it is necessary to proof every object in the design for a minimum size of .06 inches. It is helpful to draw a small circle or square with dimensions of .06 in. x .06 in. and drag it over the thinnest elements of the design. If the design element is larger than the .06 in shape, then the design will be able to be printed. If the design element is smaller than the .06 in. shape, then the design will not be able to be printed. <br />
<br />
''' Save/Export designs as .eps '''<br />
<br />
Only elements which are part of the final design should be included in your uploaded file. All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
Before uploading, your design should be saved or exported into .eps format. <br />
<br />
When using Adobe Illustrator, go to File/Save As, and select EPS (make sure the box for "include CMYK PostScript in RGB files" is unchecked before saving.) When using Corel Draw this can be done by going to File/Export/Encapsulated PostScript (EPS.) <br />
<br />
A common mistake occurs when the pixel design is opened in a vector graphic program (such as Adobe Illustrator or Corel Draw,) and is then saved with the .eps file extension. This does not mean the content of the .eps file is vector, it is still a pixel design and will need to be vectorized before saving. <br />
<br />
# '''Q How do I create a pixel design (e.g. from a photo) that meets all requirements for digital printing?''' <br />
<br />
Printing on Clothing <br />
<br />
'''A:''' In order to have a digital image printed successfully, your design must<br />
* be saved as .png, .jpg, .bmp, or .gif (transparent formats, i.e. .gif or .png, are preferred)<br />
* be at least 200 dpi<br />
* not be larger than 4000 x 4000 pixels<br />
* not be larger than 10 MB<br />
<br />
Be aware that the design size should fit by 11.8 x 11.8 inches. Minimizing the design is always a possibility without losing picture quality, however, enlargements are not since the design will appear "pixelated".<br />
<br />
<br />
---- <br />
<br />
= Project specific Guidelines (openSUSE) =<br />
We</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock/test1&diff=27422User:Wwarlock/test12010-10-08T20:00:38Z<p>Wwarlock: </p>
<hr />
<div>= Design Guidelines =<br />
<br />
'''The below guidelines are as mentioned by Spreadshirt. We very much want you to go by them.Without which we cannot upload them to our shop'''.<br />
<br />
There are two types of designs – <u>''Vector and Pixel''</u> , you can make your artwork accordingly.<br />
<br />
'''Note:''' <br />
*Save vector designs as .eps <br />
*Only elements which are part of the final design should be included in your uploaded file. <br />
*All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
*Save pixel designs as .jpg, .gif, .png, or .bmp<br />
*Size of pixel designs: max. 10 MB and min. 200 dpi (buttons: 400 dpi) <br />
*Pixel designs may not exceed 3000 x 3000 pixels<br />
<br />
'''Also please mention the number of colors if you want to upload a vector graphic.'''<br />
<br />
=== Requirements for Vector Designs ===<br />
<br />
In order to use plot printing, your vector design must follow a few guidelines (check the FAQ below) i.e. comply with the minimum line thickness, have minimum negative space, have no more than three colors and no color gradients.<br />
<br />
The Spreadshirt Team will review whether or not you have met these requirements before approving your design for release. Most designs are reviewed within 2 business days. If your design does not meet the given requirements, we will send you an e-mail informing you that it has been denied.<br />
<br />
=== Requirements for Pixel Designs ===<br />
<br />
It is currently only possible to upload pixel designs into the T-shirt Designer. By submitting your pixel designs, you assure that no third party rights (copyrights) have been violated. Any designs with violations will be rejected and an e-mail will be sent to you. More information on pixel design requirements can be found in the below helpful FAQ .<br />
<br />
== FAQ ==<br />
# '''Q:How do I create a vector design that will meet all the requirements for a plot printing (Flex / Flock) format?'''<br />
<br />
'''A:''' Vector designs can be created with Corel Draw, Inkscape, or Adobe Illustrator. Please take note of the following tips:<br />
<br />
Convert all design elements and text into curves (paths.) <br />
<br />
''' Adobe Illustrator '''<br />
<br />
The first step is to delete all pixel (bitmap) information. Do this by selecting the pixel information and pressing the delete button on your keyboard. After the pixel information has been deleted, you will need to select all of the design elements (Ctrl A.) Then in the top menu bar, go to Object/Flatten Transparency. On the settings, slide the bar to 100% vector, and check the Convert all Text to Outlines and also check the Convert all Strokes to Outlines . Next, go to the Pathfinder and click on the Merge option. If you don’t see the Pathfinder palette, go to Window/Pathfinder. To finish up, go to Object/Path/Clean Up, and check all three boxes and click OK. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Corel Draw '''<br />
The first step in Corel Draw is to open your Object Manager from the Tools, so that you can see all elements of your design. Second, delete all pixel information by selecting the bitmap element (shown in your Object Manager,) and clicking on the trash can at the bottom of the Object Manager window. Select all design elements, right-click, and select convert into curves . Delete all empty , or no-fill curves . Then select all curves of the same color by pressing the Control (Command) key and clicking on the curves of the same color. Once these curves are selected, combine them by right-clicking and selecting combine , or use the key command Control (Command) L. Repeat this step until all colors have been combined into one curve per color. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Proof the minimum size of the object '''<br />
<br />
After the conversion into curves (or paths,) it is necessary to proof every object in the design for a minimum size of .06 inches. It is helpful to draw a small circle or square with dimensions of .06 in. x .06 in. and drag it over the thinnest elements of the design. If the design element is larger than the .06 in shape, then the design will be able to be printed. If the design element is smaller than the .06 in. shape, then the design will not be able to be printed. <br />
<br />
''' Save/Export designs as .eps '''<br />
<br />
Only elements which are part of the final design should be included in your uploaded file. All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
Before uploading, your design should be saved or exported into .eps format. <br />
<br />
When using Adobe Illustrator, go to File/Save As, and select EPS (make sure the box for "include CMYK PostScript in RGB files" is unchecked before saving.) When using Corel Draw this can be done by going to File/Export/Encapsulated PostScript (EPS.) <br />
<br />
A common mistake occurs when the pixel design is opened in a vector graphic program (such as Adobe Illustrator or Corel Draw,) and is then saved with the .eps file extension. This does not mean the content of the .eps file is vector, it is still a pixel design and will need to be vectorized before saving. <br />
<br />
# '''Q How do I create a pixel design (e.g. from a photo) that meets all requirements for digital printing?''' <br />
<br />
Printing on Clothing <br />
<br />
'''A:''' In order to have a digital image printed successfully, your design must<br />
* be saved as .png, .jpg, .bmp, or .gif (transparent formats, i.e. .gif or .png, are preferred)<br />
* be at least 200 dpi<br />
* not be larger than 4000 x 4000 pixels<br />
* not be larger than 10 MB<br />
<br />
Be aware that the design size should fit by 11.8 x 11.8 inches. Minimizing the design is always a possibility without losing picture quality, however, enlargements are not since the design will appear "pixelated".<br />
<br />
<br />
---- <br />
<br />
Project specific Guidelines (openSUSE)<br />
We</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock/test1&diff=27421User:Wwarlock/test12010-10-08T19:56:59Z<p>Wwarlock: /* FAQ */</p>
<hr />
<div>= Design Guidelines =<br />
<br />
'''The below guidelines are as mentioned by Spreadshirt. We very much want you to go by them.Without which we cannot upload them to our shop'''.<br />
<br />
There are two types of designs – <u>''Vector and Pixel''</u> , you can make your artwork accordingly.<br />
<br />
'''Note:''' <br />
*Save vector designs as .eps <br />
*Only elements which are part of the final design should be included in your uploaded file. <br />
*All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
*Save pixel designs as .jpg, .gif, .png, or .bmp<br />
*Size of pixel designs: max. 10 MB and min. 200 dpi (buttons: 400 dpi) <br />
*Pixel designs may not exceed 3000 x 3000 pixels<br />
<br />
'''Also please mention the number of colors if you want to upload a vector graphic.'''<br />
<br />
=== Requirements for Vector Designs ===<br />
<br />
In order to use plot printing, your vector design must follow a few guidelines (check the FAQ below) i.e. comply with the minimum line thickness, have minimum negative space, have no more than three colors and no color gradients.<br />
<br />
The Spreadshirt Team will review whether or not you have met these requirements before approving your design for release. Most designs are reviewed within 2 business days. If your design does not meet the given requirements, we will send you an e-mail informing you that it has been denied.<br />
<br />
=== Requirements for Pixel Designs ===<br />
<br />
It is currently only possible to upload pixel designs into the T-shirt Designer. By submitting your pixel designs, you assure that no third party rights (copyrights) have been violated. Any designs with violations will be rejected and an e-mail will be sent to you. More information on pixel design requirements can be found in the below helpful FAQ .<br />
<br />
== FAQ ==<br />
# '''Q:How do I create a vector design that will meet all the requirements for a plot printing (Flex / Flock) format?'''<br />
<br />
'''A:''' Vector designs can be created with Corel Draw, Inkscape, or Adobe Illustrator. Please take note of the following tips:<br />
<br />
Convert all design elements and text into curves (paths.) <br />
<br />
''' Adobe Illustrator '''<br />
<br />
The first step is to delete all pixel (bitmap) information. Do this by selecting the pixel information and pressing the delete button on your keyboard. After the pixel information has been deleted, you will need to select all of the design elements (Ctrl A.) Then in the top menu bar, go to Object/Flatten Transparency. On the settings, slide the bar to 100% vector, and check the Convert all Text to Outlines and also check the Convert all Strokes to Outlines . Next, go to the Pathfinder and click on the Merge option. If you don’t see the Pathfinder palette, go to Window/Pathfinder. To finish up, go to Object/Path/Clean Up, and check all three boxes and click OK. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Corel Draw '''<br />
The first step in Corel Draw is to open your Object Manager from the Tools, so that you can see all elements of your design. Second, delete all pixel information by selecting the bitmap element (shown in your Object Manager,) and clicking on the trash can at the bottom of the Object Manager window. Select all design elements, right-click, and select convert into curves . Delete all empty , or no-fill curves . Then select all curves of the same color by pressing the Control (Command) key and clicking on the curves of the same color. Once these curves are selected, combine them by right-clicking and selecting combine , or use the key command Control (Command) L. Repeat this step until all colors have been combined into one curve per color. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Proof the minimum size of the object '''<br />
<br />
After the conversion into curves (or paths,) it is necessary to proof every object in the design for a minimum size of .06 inches. It is helpful to draw a small circle or square with dimensions of .06 in. x .06 in. and drag it over the thinnest elements of the design. If the design element is larger than the .06 in shape, then the design will be able to be printed. If the design element is smaller than the .06 in. shape, then the design will not be able to be printed. <br />
<br />
''' Save/Export designs as .eps '''<br />
<br />
Only elements which are part of the final design should be included in your uploaded file. All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
Before uploading, your design should be saved or exported into .eps format. <br />
<br />
When using Adobe Illustrator, go to File/Save As, and select EPS (make sure the box for "include CMYK PostScript in RGB files" is unchecked before saving.) When using Corel Draw this can be done by going to File/Export/Encapsulated PostScript (EPS.) <br />
<br />
A common mistake occurs when the pixel design is opened in a vector graphic program (such as Adobe Illustrator or Corel Draw,) and is then saved with the .eps file extension. This does not mean the content of the .eps file is vector, it is still a pixel design and will need to be vectorized before saving. <br />
<br />
# '''Q How do I create a pixel design (e.g. from a photo) that meets all requirements for digital printing?''' <br />
<br />
Printing on Clothing <br />
<br />
'''A:''' In order to have a digital image printed successfully, your design must<br />
<br />
* be saved as .png, .jpg, .bmp, or .gif (transparent formats, i.e. .gif or .png, are preferred)<br />
* be at least 200 dpi<br />
* not be larger than 4000 x 4000 pixels<br />
* not be larger than 10 MB<br />
<br />
Be aware that the design size should fit by 11.8 x 11.8 inches. Minimizing the design is always a possibility without losing picture quality, however, enlargements are not since the design will appear "pixelated".<br />
<br />
<br />
---- <br />
<br />
Project specific Guidelines (openSUSE)<br />
We</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock/test1&diff=27420User:Wwarlock/test12010-10-08T19:54:25Z<p>Wwarlock: /* Requirements for Vector Designs */</p>
<hr />
<div>= Design Guidelines =<br />
<br />
'''The below guidelines are as mentioned by Spreadshirt. We very much want you to go by them.Without which we cannot upload them to our shop'''.<br />
<br />
There are two types of designs – <u>''Vector and Pixel''</u> , you can make your artwork accordingly.<br />
<br />
'''Note:''' <br />
*Save vector designs as .eps <br />
*Only elements which are part of the final design should be included in your uploaded file. <br />
*All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
*Save pixel designs as .jpg, .gif, .png, or .bmp<br />
*Size of pixel designs: max. 10 MB and min. 200 dpi (buttons: 400 dpi) <br />
*Pixel designs may not exceed 3000 x 3000 pixels<br />
<br />
'''Also please mention the number of colors if you want to upload a vector graphic.'''<br />
<br />
=== Requirements for Vector Designs ===<br />
<br />
In order to use plot printing, your vector design must follow a few guidelines (check the FAQ below) i.e. comply with the minimum line thickness, have minimum negative space, have no more than three colors and no color gradients.<br />
<br />
The Spreadshirt Team will review whether or not you have met these requirements before approving your design for release. Most designs are reviewed within 2 business days. If your design does not meet the given requirements, we will send you an e-mail informing you that it has been denied.<br />
<br />
=== Requirements for Pixel Designs ===<br />
<br />
It is currently only possible to upload pixel designs into the T-shirt Designer. By submitting your pixel designs, you assure that no third party rights (copyrights) have been violated. Any designs with violations will be rejected and an e-mail will be sent to you. More information on pixel design requirements can be found in the below helpful FAQ .<br />
<br />
== FAQ ==<br />
'''Q:'''How do I create a vector design that will meet all the requirements for a plot printing (Flex / Flock) format?<br />
<br />
'''A:''' Vector designs can be created with Corel Draw, Inkscape, or Adobe Illustrator. Please take note of the following tips:<br />
<br />
Convert all design elements and text into curves (paths.) <br />
<br />
''' Adobe Illustrator '''<br />
<br />
The first step is to delete all pixel (bitmap) information. Do this by selecting the pixel information and pressing the delete button on your keyboard. After the pixel information has been deleted, you will need to select all of the design elements (Ctrl A.) Then in the top menu bar, go to Object/Flatten Transparency. On the settings, slide the bar to 100% vector, and check the Convert all Text to Outlines and also check the Convert all Strokes to Outlines . Next, go to the Pathfinder and click on the Merge option. If you don’t see the Pathfinder palette, go to Window/Pathfinder. To finish up, go to Object/Path/Clean Up, and check all three boxes and click OK. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Corel Draw '''<br />
The first step in Corel Draw is to open your Object Manager from the Tools, so that you can see all elements of your design. Second, delete all pixel information by selecting the bitmap element (shown in your Object Manager,) and clicking on the trash can at the bottom of the Object Manager window. Select all design elements, right-click, and select convert into curves . Delete all empty , or no-fill curves . Then select all curves of the same color by pressing the Control (Command) key and clicking on the curves of the same color. Once these curves are selected, combine them by right-clicking and selecting combine , or use the key command Control (Command) L. Repeat this step until all colors have been combined into one curve per color. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Proof the minimum size of the object '''<br />
<br />
After the conversion into curves (or paths,) it is necessary to proof every object in the design for a minimum size of .06 inches. It is helpful to draw a small circle or square with dimensions of .06 in. x .06 in. and drag it over the thinnest elements of the design. If the design element is larger than the .06 in shape, then the design will be able to be printed. If the design element is smaller than the .06 in. shape, then the design will not be able to be printed. <br />
<br />
''' Save/Export designs as .eps '''<br />
<br />
Only elements which are part of the final design should be included in your uploaded file. All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
Before uploading, your design should be saved or exported into .eps format. <br />
<br />
When using Adobe Illustrator, go to File/Save As, and select EPS (make sure the box for "include CMYK PostScript in RGB files" is unchecked before saving.) When using Corel Draw this can be done by going to File/Export/Encapsulated PostScript (EPS.) <br />
<br />
A common mistake occurs when the pixel design is opened in a vector graphic program (such as Adobe Illustrator or Corel Draw,) and is then saved with the .eps file extension. This does not mean the content of the .eps file is vector, it is still a pixel design and will need to be vectorized before saving. <br />
<br />
---- <br />
<br />
Project specific Guidelines (openSUSE)<br />
We</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock/test1&diff=27419User:Wwarlock/test12010-10-08T19:53:17Z<p>Wwarlock: /* Design Guidelines */</p>
<hr />
<div>= Design Guidelines =<br />
<br />
'''The below guidelines are as mentioned by Spreadshirt. We very much want you to go by them.Without which we cannot upload them to our shop'''.<br />
<br />
There are two types of designs – <u>''Vector and Pixel''</u> , you can make your artwork accordingly.<br />
<br />
'''Note:''' <br />
*Save vector designs as .eps <br />
*Only elements which are part of the final design should be included in your uploaded file. <br />
*All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
*Save pixel designs as .jpg, .gif, .png, or .bmp<br />
*Size of pixel designs: max. 10 MB and min. 200 dpi (buttons: 400 dpi) <br />
*Pixel designs may not exceed 3000 x 3000 pixels<br />
<br />
'''Also please mention the number of colors if you want to upload a vector graphic.'''<br />
<br />
=== Requirements for Vector Designs ===<br />
<br />
In order to use plot printing, your vector design must follow a few guidelines (check the FAQ below) i.e. comply with the minimum line thickness, have minimum negative space, have no more than three colors and no color gradients.<br />
<br />
The Spreadshirt Team will review whether or not you have met these requirements before approving your design for release. Most designs are reviewed within 2 business days. If your design does not meet the given requirements, we will send you an e-mail informing you that it has been denied. <br />
<br />
== FAQ ==<br />
'''Q:'''How do I create a vector design that will meet all the requirements for a plot printing (Flex / Flock) format?<br />
<br />
'''A:''' Vector designs can be created with Corel Draw, Inkscape, or Adobe Illustrator. Please take note of the following tips:<br />
<br />
Convert all design elements and text into curves (paths.) <br />
<br />
''' Adobe Illustrator '''<br />
<br />
The first step is to delete all pixel (bitmap) information. Do this by selecting the pixel information and pressing the delete button on your keyboard. After the pixel information has been deleted, you will need to select all of the design elements (Ctrl A.) Then in the top menu bar, go to Object/Flatten Transparency. On the settings, slide the bar to 100% vector, and check the Convert all Text to Outlines and also check the Convert all Strokes to Outlines . Next, go to the Pathfinder and click on the Merge option. If you don’t see the Pathfinder palette, go to Window/Pathfinder. To finish up, go to Object/Path/Clean Up, and check all three boxes and click OK. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Corel Draw '''<br />
The first step in Corel Draw is to open your Object Manager from the Tools, so that you can see all elements of your design. Second, delete all pixel information by selecting the bitmap element (shown in your Object Manager,) and clicking on the trash can at the bottom of the Object Manager window. Select all design elements, right-click, and select convert into curves . Delete all empty , or no-fill curves . Then select all curves of the same color by pressing the Control (Command) key and clicking on the curves of the same color. Once these curves are selected, combine them by right-clicking and selecting combine , or use the key command Control (Command) L. Repeat this step until all colors have been combined into one curve per color. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Proof the minimum size of the object '''<br />
<br />
After the conversion into curves (or paths,) it is necessary to proof every object in the design for a minimum size of .06 inches. It is helpful to draw a small circle or square with dimensions of .06 in. x .06 in. and drag it over the thinnest elements of the design. If the design element is larger than the .06 in shape, then the design will be able to be printed. If the design element is smaller than the .06 in. shape, then the design will not be able to be printed. <br />
<br />
''' Save/Export designs as .eps '''<br />
<br />
Only elements which are part of the final design should be included in your uploaded file. All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
Before uploading, your design should be saved or exported into .eps format. <br />
<br />
When using Adobe Illustrator, go to File/Save As, and select EPS (make sure the box for "include CMYK PostScript in RGB files" is unchecked before saving.) When using Corel Draw this can be done by going to File/Export/Encapsulated PostScript (EPS.) <br />
<br />
A common mistake occurs when the pixel design is opened in a vector graphic program (such as Adobe Illustrator or Corel Draw,) and is then saved with the .eps file extension. This does not mean the content of the .eps file is vector, it is still a pixel design and will need to be vectorized before saving. <br />
<br />
---- <br />
<br />
Project specific Guidelines (openSUSE)<br />
We</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock/test1&diff=27418User:Wwarlock/test12010-10-08T19:49:59Z<p>Wwarlock: Draft for Shop and Design guidelines</p>
<hr />
<div>= Design Guidelines =<br />
<br />
'''The below guidelines are as mentioned by Spreadshirt. We very much want you to go by them.Without which we cannot upload them to our shop'''.<br />
<br />
There are two types of designs – <u>''Vector and Pixel''</u> , you can make your artwork accordingly.<br />
<br />
'''Note:''' <br />
*Save vector designs as .eps <br />
*Only elements which are part of the final design should be included in your uploaded file. <br />
*All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
*Save pixel designs as .jpg, .gif, .png, or .bmp<br />
*Size of pixel designs: max. 10 MB and min. 200 dpi (buttons: 400 dpi) <br />
*Pixel designs may not exceed 3000 x 3000 pixels<br />
<br />
'''Also please mention the number of colors if you want to upload a vector graphic.'''<br />
<br />
== FAQ ==<br />
'''Q:'''How do I create a vector design that will meet all the requirements for a plot printing (Flex / Flock) format?<br />
<br />
'''A:''' Vector designs can be created with Corel Draw, Inkscape, or Adobe Illustrator. Please take note of the following tips:<br />
<br />
Convert all design elements and text into curves (paths.) <br />
<br />
''' Adobe Illustrator '''<br />
<br />
The first step is to delete all pixel (bitmap) information. Do this by selecting the pixel information and pressing the delete button on your keyboard. After the pixel information has been deleted, you will need to select all of the design elements (Ctrl A.) Then in the top menu bar, go to Object/Flatten Transparency. On the settings, slide the bar to 100% vector, and check the Convert all Text to Outlines and also check the Convert all Strokes to Outlines . Next, go to the Pathfinder and click on the Merge option. If you don’t see the Pathfinder palette, go to Window/Pathfinder. To finish up, go to Object/Path/Clean Up, and check all three boxes and click OK. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Corel Draw '''<br />
The first step in Corel Draw is to open your Object Manager from the Tools, so that you can see all elements of your design. Second, delete all pixel information by selecting the bitmap element (shown in your Object Manager,) and clicking on the trash can at the bottom of the Object Manager window. Select all design elements, right-click, and select convert into curves . Delete all empty , or no-fill curves . Then select all curves of the same color by pressing the Control (Command) key and clicking on the curves of the same color. Once these curves are selected, combine them by right-clicking and selecting combine , or use the key command Control (Command) L. Repeat this step until all colors have been combined into one curve per color. <br />
<br />
{{Info|Note that vector designs are limited to 3 colors and should not exceed 11.8 x 11.8 inches.}}<br />
<br />
''' Proof the minimum size of the object '''<br />
<br />
After the conversion into curves (or paths,) it is necessary to proof every object in the design for a minimum size of .06 inches. It is helpful to draw a small circle or square with dimensions of .06 in. x .06 in. and drag it over the thinnest elements of the design. If the design element is larger than the .06 in shape, then the design will be able to be printed. If the design element is smaller than the .06 in. shape, then the design will not be able to be printed. <br />
<br />
''' Save/Export designs as .eps '''<br />
<br />
Only elements which are part of the final design should be included in your uploaded file. All elements which should not appear in the design, such as backgrounds, should first be removed before submission. <br />
Before uploading, your design should be saved or exported into .eps format. <br />
<br />
When using Adobe Illustrator, go to File/Save As, and select EPS (make sure the box for "include CMYK PostScript in RGB files" is unchecked before saving.) When using Corel Draw this can be done by going to File/Export/Encapsulated PostScript (EPS.) <br />
<br />
A common mistake occurs when the pixel design is opened in a vector graphic program (such as Adobe Illustrator or Corel Draw,) and is then saved with the .eps file extension. This does not mean the content of the .eps file is vector, it is still a pixel design and will need to be vectorized before saving. <br />
<br />
---- <br />
<br />
Project specific Guidelines (openSUSE)<br />
We</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:GNOME_team&diff=20553openSUSE:GNOME team2010-08-04T08:50:23Z<p>Wwarlock: </p>
<hr />
<div>__NOTOC__<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
=== Introduction ===<br />
</div><br />
As part of the openSUSE project, we fully support the [[openSUSE:Guiding principles]] and goals of the project as a whole. In addition we wish to:<br />
<br />
*Create the best distribution of GNOME<br />
*Build an openSUSE community around the GNOME desktop<br />
*Attract upstream GNOME developers and users to openSUSE<br />
*Contribute to upstream GNOME development<br />
*Create a positive community atmosphere throughout openSUSE<br />
*Contribute to improving openSUSE as whole<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#000000"><br />
=== Communicate ===<br />
</div><br />
* Chat with us on IRC in the [irc://irc.freenode.org/opensuse-gnome #opensuse-gnome] channel<br />
{{Mailinglist|opensuse-gnome|Or mail us on the openSUSE GNOME mailing list}}<br />
<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
=== Members ===<br />
</div><br />
* [[User:Aaronbockover|Aaron Bockover]] (abock on IRC - Boston, MA, USA)<br />
* [[User:Sbrabec|Stanislav Brabec]] (sbrabec on IRC - Prague, Czech Republic)<br />
* [[User:madlewing| Larry Ewing]] (lewing on IRC - Austin, TX, USA)<br />
* [[User:Hpjansson| Hans Petter Jansson]] ([http://hpjansson.org/ Blog] - hpj on IRC - Xalapa, Mexico)<br />
* [[User:Federico-mena|Federico Mena-Quintero]] ([http://www.gnome.org/~federico/news.html Blog] - federico1 on IRC - Xalapa, Mexico)<br />
* [[User:rodrigomoya|Rodrigo Moya]] ([http://blogs.gnome.org/rodrigo Blog]) rodrigo on IRC - Navarra, Spain)<br />
* [[User:Riggwelter|James Ogley]] ([http://jamesthevicar.com Blog], Riggwelter on IRC - Southampton, UK)<br />
* [[User:Mauropm|Mauro Parra-Miranda]] (mauropm on IRC, Mexico DF, Mexico)<br />
* [[User:Jproseve|JP Rosevear]] ([http://blog.jprosevear.org Blog], jpr on IRC - Toronto, Canada)<br />
* [[User:Maw|Michael Wolf]] ([http://nachosetcrayons.blogspot.com/ Blag] - mw on IRC - Mexico City, Mexico)<br />
* [[User:Albertop|Alberto Passalacqua]] (AlbertoP on IRC)<br />
* [[User:Sreeves1|Scott Reeves]] (sreeves on IRC - Provo, UT, USA)<br />
* [[User:MBoman|Magnus Boman]] (captain_magnus on IRC) ([http://timeanddate.com/worldclock/results.html?query=sydney Sydney, Australia])<br />
* [[User:Munkiii|Dean Sawash]] ([http://munkii.wordpress.com Blog] munkii on IRC)<br />
* [[User:Vuntz|Vincent Untz]] ([http://www.vuntz.net/journal/ Blog] vuntz on IRC - Grenoble, France)<br />
* [[User:FunkyPenguin|Andrew Wafaa]] ([http://www.wafaa.eu/ Blog] FunkyPenguin on IRC)<br />
* [[User:byunashko|Bryen Yunashko]] ([http://www.bryen.com Blog] suseROCKS on IRC), Chicago, IL, USA<br />
* [[User:Lmedinas|Luis Medinas]] ([http://lmedinas.livejournal.com Blog] metalgod on IRC), Aveiro, Portugal<br />
* [[User:Hobbsc|Christopher M. Hobbs]] ([http://altbit.org Blog] hobbsc on IRC), Siloam Springs, AR, USA<br />
* [[User:Hfiguiere|Hubert Figuiere]] ([http://www.figuiere.net/hub/blog/ Blog], hub on IRC - Hull, QC, Canada)<br />
* [[User:Dimstar|Dominique Leuenberger]] ([http://dominique.leuenberger.net/blog Blog], DimStar on IRC - Amsterdam, Netherlands)<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
=== How to join ===<br />
</div><br />
Just talk to us<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
=== Tasks===<br />
</div><br />
==== Tasks For Everyone (Yes, that includes you) ====<br />
<br />
{|border="1" cellpadding="5" cellspacing="0" align="center"<br />
|-<br />
! width="80%" style="background:#d9e5bf" | Task<br />
! width="20%" style="background:#d9e5bf" | Mentor<br />
|-<br />
| Update the [[GNOME/Acronyms | Acronyms page]] || [[User:MBoman|captain_magnus]]<br />
|-<br />
| Write HOWTOs about GNOME under [[HOWTOs|HOWTOs]] || [[User:Jproseve|jpr]]<br />
|-<br />
| Review http://en.opensuse.org/Wishlist_Gnome. Also, see [[Packaging/Packaging_Day]] || [[User:Maw|mw]]<br />
|-<br />
| Search and tag [[GNOME/Bugs#Policy_for_bug_triaging | gnome-accessibility bugs]] || [[User:byunashko|suseROCKS]]<br />
|-<br />
| Improve our package summaries and descriptions || [[User:Maw|mw]]<br />
|-<br />
| [[GNOME/Bugs#How_to_classify_bugs | Categorize all the bugs and add 11.0 categories]] || [[User:federico|federico]], [[User:rodrigo|rodrigo]]<br />
|}<br />
<br />
<br />
==== Assigned Tasks ====<br />
<br />
{|border="1" cellpadding="5" cellspacing="0" align="center"<br />
|-<br />
! width="60%" style="background:#e11c1c;" | Tasks That Are Overdue<br />
! width="10%" style="background:#e11c1c;" | Status<br />
! width="10%" style="background:#e11c1c;" | ETA<br />
! width="20%" style="background:#e11c1c;" | Assignee<br />
|-<br />
| n/a<br />
|-<br />
! width="60%" style="background:#fff336;" | Tasks To Be Completed Before Next Meeting<br />
! width="10%" style="background:#fff336;" | Status<br />
! width="10%" style="background:#fff336;" | ETA<br />
! width="20%" style="background:#fff336;" | Assignee<br />
|-<br />
| n/a<br />
|-<br />
! width="60%" style="background:#2bd92b;" | Tasks That Are On Track<br />
! width="10%" style="background:#2bd92b;" | Status<br />
! width="10%" style="background:#2bd92b;" | ETA<br />
! width="20%" style="background:#2bd92b;" | Assignee<br />
|-<br />
| n/a<br />
|-<br />
! width="60%" style="background:#ff8f3d;" | Tasks That Are Assigned But Have No ETA<br />
! width="10%" style="background:#ff8f3d;" | Status<br />
! width="10%" style="background:#ff8f3d;" | ETA<br />
! width="20%" style="background:#ff8f3d;" | Assignee<br />
|-<br />
| Update the [[GNOME/Acronyms | Acronyms page]] || Not Started || No ETA || [[User:MBoman|captain_magnus]]<br />
|-<br />
| Determine where to keep openSUSE GNOME specific code || Not Started || No ETA || [[User:hpj|hpj]]<br />
|-<br />
| Review current GNOME:Community packages to match the G:C Policy|| Not Started || No ETA || [[User:maw|mw]],[[User:riggwelter|riggwelter]]<br />
|-<br />
| Propose a date and organize a multi-screen hackfest || Done || || [[User:Federico-mena|federico]]<br />
|-<br />
| Organize Bug Fixing Week for Beginners || Not Started || No ETA || [[User:Federico-mena|federico]]<br />
|-<br />
| Schedule review of GNOME related patterns || Done || || [[User:MBoman|captain_magnus]]<br />
|-<br />
| Research openSUSE speaking possibilities @ Utah-based CS Departments || Not Started || No ETA || [[user:btimothy|btimothy]]<br />
|-<br />
| Grep for desktop policy changes, update wiki and mail the list to start discussion || Done || || [[user:vuntz|vuntz]]<br />
|-<br />
| Add conduit to GNOME:Community || Done || No ETA || [[User:maw|mw]]<br />
|-<br />
| Look for and remove unnecessary gnome-vfs2 requirements || Not Started || No ETA || [[User:maw|mw]]<br />
|}<br />
<br />
<br />
<div style="background-color:#E5E5E6;text-align:center;color:#0b5147"><br />
=== Additions (optional)===<br />
</div><br />
Wondering whom to ask about what? Check out our [[openSUSE:GNOME competence directory]]<br />
<br />
----<br />
[[Category:Team pages]]<br />
[[Category:GNOME]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock&diff=13954User:Wwarlock2010-07-12T19:03:34Z<p>Wwarlock: </p>
<hr />
<div><div style="width:76%; float:left"><br />
{{Box-header|About Me|{{FULLPAGENAME}}|}}<br />
<br />
'''Intro'''<br />
<br />
* I am Shayon Mukherjee a.k.a SJ (you can call me that) and i really love contributing to openSUSE in which ever possible way i can. <br />
* Well,i am adventurous by nature and like to do mountaineering ,rappelling ,para-gliding,trekking a lot,etc.(Kinda adventurous).This gives me a great satisfaction as i love thrilling experiences and the Himalayas :) <br />
<br />
'''Interests'''<br />
* Whenever i am free i always search for new things,Customize Websites for my friends,my organizations and for other non-monetary purposes- which could make living easy in some or the other way, and other such stuffs <br />
*Other interest which i enjoy and cherish is Photography , Videography and sports like badminton,cricket,hockey and football.<br />
<br />
'''openSUSE'''<br />
*Wiki contributor <b>[http://connect.opensuse.org/groups/26-wiki-team Wiki Team]</b><br />
*Spread the word <b>[http://connect.opensuse.org/groups/44-marketing Marketing]</b><br />
*Help editing videos (if required)<br />
<br />
'''Skills'''<br />
Working on this :-)<br />
<br />
'''Linux Experience'''<br />
<br />
My linux expereince started with openSUSE 11.1 and is on :) . I came to know about it from one of my teachers who uses it to teach graphic design in my School.And from that day i very much like to work on it and try to contribute in some or the other way<br />
<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:22%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
<center>[[File:SJ-Final.png|60px]]</center><br />
<br />
'''Contact'''<br />
<br />
[mailto:sj@opensuse.org sj@opensuse.org]<br />
<br />
SJ on [[Help:Communication/IRC|IRC]]<br />
<br />
{{Box-footer|}}<br />
</div></div>Wwarlockhttps://en.opensuse.org/index.php?title=User:Wwarlock&diff=13953User:Wwarlock2010-07-12T19:01:34Z<p>Wwarlock: </p>
<hr />
<div><div style="width:76%; float:left"><br />
{{Box-header|About Me|{{FULLPAGENAME}}|}}<br />
<br />
'''Intro'''<br />
<br />
* I am Shayon Mukherjee a.k.a SJ (you can call me that) and i really love contributing to openSUSE in which ever possible way i can. <br />
* Well,i am adventurous by nature and like to do mountaineering ,rappelling ,para-gliding,trekking a lot,etc.(Kinda adventurous).This gives me a great satisfaction as i love thrilling experiences and the Himalayas :) <br />
<br />
'''Interests'''<br />
* Whenever i am free i always search for new things,Customize Websites for my friends,my organizations and for other non-monetary purposes- which could make living easy in some or the other way, and other such stuffs <br />
*Other interest which i enjoy and cherish is Photography , Videography and sports like badminton,cricket,hockey and football.<br />
<br />
'''openSUSE'''<br />
*Wiki contributor <b>[http://connect.opensuse.org/groups/26-wiki-team Wiki Team]</b><br />
*Spread the word <b>[http://connect.opensuse.org/groups/44-marketing Marketing]</b><br />
*Help editing videos (if required)<br />
<br />
'''Skills'''<br />
<br />
<br />
'''Linux Experience'''<br />
<br />
My linux expereince started with openSUSE 11.1 and is on :) . I came to know about it from one of my teachers who uses it to teach graphic design in my School.And from that day i very much like to work on it and try to contribute in some or the other way<br />
<br />
{{Box-footer|}}<br />
</div><br />
<div style="width:22%; float:right"><br />
{{Box-header|Contact|{{FULLPAGENAME}}|}}<br />
<center>[[File:SJ-Final.png|60px]]</center><br />
<br />
'''Contact'''<br />
<br />
[mailto:sj@opensuse.org sj@opensuse.org]<br />
<br />
SJ on [[Help:Communication/IRC|IRC]]<br />
<br />
{{Box-footer|}}<br />
</div></div>Wwarlockhttps://en.opensuse.org/index.php?title=Main_Page&diff=9939Main Page2010-06-15T19:37:38Z<p>Wwarlock: changes needs to be done to other too</p>
<hr />
<div>[[File:OpenSUSE_11.2_728x90.png|center|link=Portal:11.2|openSUSE 11.2 out now!]]<br />
==Project==<br />
{{Point here|[[File:icon-community.png|48px|link=Portal:Project|Project]]|{{Portal:Project/Intro}}}}<br />
==Distribution==<br />
{{Point here|[[Image:Icon-distribution.png|48px|link=Portal:Distribution|Distribution]]|{{Portal:Distribution/Intro}}<br />
}}<br />
==Wiki==<br />
{{Point here|[[File:Icon-wiki.png|link=Portal:Wiki|Wiki]]|{{Portal:Wiki/Intro}}}}<br />
<br />
__NOTOC____NOEDITSECTION__</div>Wwarlockhttps://en.opensuse.org/index.php?title=Main_Page&diff=9938Main Page2010-06-15T19:35:38Z<p>Wwarlock: test - just in case no one paid attention :-)</p>
<hr />
<div>[[File:OpenSUSE_11.2_728x90.png|center|link=Portal:11.2|openSUSE 11.2 out now!]]<br />
==Project==<br />
{{Point here|[[File:icon-community.png|link=Portal:Project|Project]]|{{Portal:Project/Intro}}}}<br />
==Distribution==<br />
{{Point here|[[Image:Icon-distribution.png|48px|link=Portal:Distribution|Distribution]]|{{Portal:Distribution/Intro}}<br />
}}<br />
==Wiki==<br />
{{Point here|[[File:Icon-wiki.png|link=Portal:Wiki|Wiki]]|{{Portal:Wiki/Intro}}}}<br />
<br />
__NOTOC____NOEDITSECTION__</div>Wwarlockhttps://en.opensuse.org/index.php?title=Category:Marketing_meetings&diff=9254Category:Marketing meetings2010-06-02T14:31:23Z<p>Wwarlock: Created page with 'Category:Marketing team'</p>
<hr />
<div>[[Category:Marketing team]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=openSUSE:Marketing_meetings&diff=9253openSUSE:Marketing meetings2010-06-02T14:31:06Z<p>Wwarlock: </p>
<hr />
<div><!-- Template:Navbar is used to connect similar articles in one easy to navigate group --><br />
{{Navbar|TITLE=[[openSUSE:Article Template|Article Templates]]|CONTENT=[[Article 1]] - [[Article 2]] - [[Article 3]] - [[Article 4]] - [[Article 5]] - [[Article 6]]}}<br />
<br />
<!-- Template:Intro is used to mark short and clear intro to article topic. Create it short and clear, just as it would be article description in some index --><br />
{{Intro|{{Lorem ipsum}} }}<br />
<br />
<!-- Template:Knowledge is used to highlight articles and topics that are precondition to understand this article --><br />
<br />
{{Knowledge|<br />
*[[Portal:11.3|11.3]]<br />
*[[Portal:11.2|11.2]]<br />
*[[Portal:11.1|11.1]]<br />
|<br />
*[[Main page]]<br />
*[[Main page]]<br />
*[[Main page]]<br />
|<br />
*[[Main page]]<br />
*[[Main page]]<br />
*[[Main page]]<br />
}}<br />
<br />
__TOC__<br />
<br />
<!-- Article Tag templates --><br />
{{Info|Please refer to [[Help:Editing]] in order to write a quality approved article.}}<br />
<!-- Below is a body of the article --><br />
==Heading 1==<br />
===Sub-heading===<br />
===Sub-heading===<br />
----<br />
==Heading 2==<br />
===Sub-heading===<br />
===Sub-heading===<br />
----<br />
==Heading 3==<br />
===Sub-heading===<br />
===Sub-heading===<br />
<br />
----<br />
==Communication==<br />
<br />
===Team members===<br />
<!--Please use alphabetic order by wiki username --><br />
*{{User|User1}}<br />
*{{User|User2}}<br />
*{{User|User3}}<br />
<br />
===Mailing list===<br />
{{Mailinglist|opensuse-list|Short description of the mailing list}}<br />
<!--End of article body --><br />
----<br />
<br />
==See also==<br />
=== Related articles ===<br />
*[[Main page]]<br />
*[[Main page]]<br />
*[[Main page]]<br />
*[[Main page]]<br />
<br />
===External links===<br />
* [http://www.opensuse-community.org Links]<br />
* [http://www.opensuse-community.org Links]<br />
<br />
<!-- Interwiki link --><br />
{{IW|openSUSE:Article Template}}<br />
<br />
<noinclude><br />
<br />
----<br />
<br />
{{{{FULLPAGENAME}}/doc}}<br />
</noinclude><br />
<br />
<br />
[[Category:Marketing meetings]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Category:Marketing_team&diff=9250Category:Marketing team2010-06-02T14:29:02Z<p>Wwarlock: Created page with 'Category:Marketing'</p>
<hr />
<div>[[Category:Marketing]]</div>Wwarlockhttps://en.opensuse.org/index.php?title=Category:Ambassador&diff=9248Category:Ambassador2010-06-02T14:27:50Z<p>Wwarlock: </p>
<hr />
<div>[[Category:Marketing resources]]</div>Wwarlock