January 2014 - openSUSE Project - openSUSE Mailing Lists

[opensuse-project] Re: [oSC14] Help with announcements needed
by Jos Poortvliet 09 Jan '14

09 Jan '14

On Sunday 05 January 2014 11:26:30 differentreality wrote: > On Thu, Dec 12, 2013 at 7:48 PM, differentreality > > <differentreality(a)gmail.com> wrote: > > Hey all, > > > > we are drafting the announcements for oSC14 here [1] and your help is > > highly needed and appreciated :) > > > > Several things we need to get out there: initial announcement for > > oSC14, CfP, and whatever comes along our way. > > > > We have already discussed some things during the conference meeting > > and as we get more info we will be adding them in the gdoc. If you > > could form them into more attractive announcements it would be > > a-w-e-s-o-m-e! > > > > Thanks, > > Stella > > > > [1] > > https://docs.google.com/document/d/1OXw9yZKNAtYQLxrv7hz0bKDE6jGaYwCoAXFc > > W1fX4TQ/edit# > Hello & Happy New Year to everybody! > > The Program Committee has decided on the tracks and submission types > for oSC14 as well as the dates for CfP [1]. > > We have created a draft announcement [2] and we would like your help > to refine it and send it out to the world! > > Thanks a lot! > Stella > > > [1] https://trello.com/c/Onesi7it/46-cfp-deadlines > > [2] Draft announcement: > https://docs.google.com/document/d/1OXw9yZKNAtYQLxrv7hz0bKDE6jGaYwCoAXFcW1f > X4TQ/edit?disco=AAAAAHqDFEI#heading=h.ekzo22sg55m0 First announcement: https://news.opensuse.org/?p=17485&preview=true (mixing your with Svebor's writing) Feedback welcome. This can go out whenever you want, it's a slow time :D

4 6

[opensuse-project] oSC15 location -- feedback request
by Robert Schweikert 08 Jan '14

08 Jan '14

Hi, At the deadline for oSC15 location proposals the board received a proposal from La Laguna on the Canary Islands. The message was also sent to this list but was filtered out, presumably because of the attachment. The proposal is solid and the team that has come forward to organize oSC has previously organized a KDE event. Following the timing we had established, due to lack of other proposals, La Laguna would be the default choice for oSC15. However, we have serious concerns about costs and location accessibility for everyone. With the location being on an island the choice to get there is by plane thus eliminating other, potentially cheaper, options such as bus or train. During the off season planes may also not fly as regularly as one would prefer. Things to keep in mind: - We chose the end of the year (2013) as a deadline for proposals to give us a chance to review proposals, make a decision in a timely manner, and get one person from the oSC15 organizing team to Dubrovnik - The time deadline was selected arbitrarily - We would very much like to have an independent oSC in 2015 Where we stand today: 1.) If we follow our arbitrary "rules" La Laguna would be the location by default, but we have concerns as mentioned above 2.) We can try and poke specific people in the hopes that someone is willing to form a team and run with oSC15, this would be bending our "rules" 3.) Consider co-locating oSC with another event in Europe, Linux-Tag, CLT (Chemnitzer Linux Tage), or other. This would also bend the "rules" and also requires people with feet on the ground. Those people have to be found. Bending the "rules" may send mixed messages to any team that may be interested in organizing oSC in the future, we are obviously concerned with the sustainability of the conference. Thus, this is an important point to consider. We, the board, would like to receive feedback from the community to get a general insight into the sentiment with respect to the 3 basic choices outlined above. There may be some nuances on the themes for option 2 and 3 and we do not need to discuss these in detail at this point. Please provide your feedback on the choices outlined above. Thanks you. Your openSUSE Board -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] Minutes of openSUSE Project Meeting of January 8th, 2014
by Vincent Untz 08 Jan '14

08 Jan '14

Here are the minutes of today's meeting. Cheers, Vincent Minutes: http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… Minutes (text): http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… Log: http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… =========================================== #opensuse-project: openSUSE Project Meeting =========================================== Meeting started by vuntz at 15:01:14 UTC. The full logs are available at http://community.opensuse.org/meetings/opensuse-project/2014/opensuse-proje… . Meeting summary --------------- * Situation with the forums (vuntz, 15:06:15) * oSC15 ideas about finding a location (vuntz, 15:16:00) * ACTION: robjo to take this topic to the opensuse-project mailing list to get more feedback (vuntz, 15:46:14) * New TSP Team (vuntz, 15:48:40) * Any other topic? (vuntz, 15:55:30) Meeting ended at 16:01:08 UTC. Action items, by person ----------------------- * robjo * robjo to take this topic to the opensuse-project mailing list to get more feedback People present (lines said) --------------------------- * vuntz (45) * warlordfff (41) * robjo (34) * kigurame (23) * coolo (18) * ilmehtar_ (13) * tigerfoot (11) * tux93 (3) * bugbot (2) * cwh_ (2) * ancorgs (1) * manugupt1 (1) Generated by `MeetBot`_ 0.1.4 -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] oSC14 fourth IRC meeting reminder - tomorrow, 17:00 CET
by Svebor Prstačić 08 Jan '14

08 Jan '14

Dear all, The proposed agenda for the next oSC14 meeting is here: http://en.opensuse.org/openSUSE:Conference_meeting#Agenda_for_Next_Meeting Please add a topic if you think there is something else we should talk about. ... and check your local meeting time here: http://www.timeanddate.com/worldclock/fixedtime.html?msg=oSC14%2C+fourth +IRC+meeting&iso=20140109T17&p1=281&ah=1 Hope to see you on #opensuse-project! Pozdrav, Svebor -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] CentOS Project joins forces with Red Hat, will this change SLES/openSUSE?
by Joop Boonen 08 Jan '14

08 Jan '14

Dear all, I've read this announcement: [CentOS-announce] CentOS Project joins forces with Red Hat http://lists.centos.org/pipermail/centos-announce/2014-January/020100.html Will this have any effect on SLES/openSUSE? Regards, Joop. -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] [reminder] openSUSE Project Meeting tomorrow at 15:00 UTC
by openSUSE Meeting Reminder 07 Jan '14

07 Jan '14

Hello all, The biweekly project meeting will be held tomorrow at 15:00 UTC in #opensuse-project on freenode. Everybody is invited to join and participate! Find out what time the meeting will be in your timezone: http://timeanddate.com/worldclock/fixedtime.html?day=8&month=1&year=2014&ho… Agenda of the meeting: http://en.opensuse.org/openSUSE:Project_meeting#Agenda_for_the_next_meeting If you cannot participate and want a specific question to be answered during the meeting, please add your question to: http://en.opensuse.org/openSUSE:Project_meeting#Questions_Section Minutes and logs of previous meetings can be found at: http://community.opensuse.org/meetings/opensuse-project/ Thanks, -- openSUSE Meeting Reminder -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0

[opensuse-project] Fosdem 2014 - Booth
by Bruno Friedmann 07 Jan '14

07 Jan '14

Happy new year & best green wishes to Geeko's We're now then less 4 weeks of Fosdem 2014 event This email summarize the points we need to clarify before next week. Materials : 2 all-in-one computer (normally one stay at Nuremberg, the second is located at Prague) Q : Who can locally check them, and be sure they arrive at Brussel the 1st Feb? Booth kits (or part of them due to the lacking final package) 2 or 3 Stand-up Roll-up Table cloth (green/orange) x2 Give away category Flyer Stickers Business cards (URL+Logo+QR-code) DVD (400) but which one ? Selling category T-Shirts Plush (the small one) usb sticks (Pre-loaded with?) Decide a price for each of them Special category Beers ? We could be asked by Fosdem to invent a system to have the bottle brought back to the booth. Bring the stuff to Brussels Hostel ? Q : I need a good soul to monitor the picking locally at Nuremberg Bring the stuff from Hostel to ULB (in time) ? Q: Transport, should we rent a van for Saturday morning? Ask local transport like last year? Once we are clear here in the ML, I will bring the elements on the Fosdem wiki page. Would be awesome if the Nü Geeko's knows how they go to Brussels this year. (Bus, Hostel location & so.) Thanks for all your support. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

2 1

[opensuse-project] Re: [oSC14] Help with announcements needed
by Jos Poortvliet 07 Jan '14

07 Jan '14

On Sunday 05 January 2014 11:26:30 differentreality wrote: > On Thu, Dec 12, 2013 at 7:48 PM, differentreality > > <differentreality(a)gmail.com> wrote: > > Hey all, > > > > we are drafting the announcements for oSC14 here [1] and your help is > > highly needed and appreciated :) > > > > Several things we need to get out there: initial announcement for > > oSC14, CfP, and whatever comes along our way. > > > > We have already discussed some things during the conference meeting > > and as we get more info we will be adding them in the gdoc. If you > > could form them into more attractive announcements it would be > > a-w-e-s-o-m-e! > > > > Thanks, > > Stella > > > > [1] > > https://docs.google.com/document/d/1OXw9yZKNAtYQLxrv7hz0bKDE6jGaYwCoAXFc > > W1fX4TQ/edit# > Hello & Happy New Year to everybody! > > The Program Committee has decided on the tracks and submission types > for oSC14 as well as the dates for CfP [1]. > > We have created a draft announcement [2] and we would like your help > to refine it and send it out to the world! > > Thanks a lot! > Stella > > > [1] https://trello.com/c/Onesi7it/46-cfp-deadlines > > [2] Draft announcement: > https://docs.google.com/document/d/1OXw9yZKNAtYQLxrv7hz0bKDE6jGaYwCoAXFcW1f > X4TQ/edit?disco=AAAAAHqDFEI#heading=h.ekzo22sg55m0 Editing :D /J

3 4

[opensuse-project] Suggestion Concerning Repository Structure and Metadata
by Antoine Saroufim 07 Jan '14

07 Jan '14

Good day, Currently, we have a fair amount of software in the default repositories that the user can utilize. If a user wants to install software that isn't present in the default repositories, he/she can look for it on OBS. The user can then proceed to add the targeted repository to his/her system via 1-click install, zypper, or YaST2. The current system works, but isn't quite perfect due to the following reasons: - Users can't install packages not available in the enabled repositories. If a user wants to install an application or library that isn't in the default repositories, the user has to resort to searching for the package on software.opensuse.org through a browser and then installing it or to installing OSC, searching for the package, adding a repository, and then installing the package. - Users may have to add many repositories to get all their needs. Repositories on OBS may host a single desktop environment, a small collection of apps, a single app, or even a patch. Over time, the user might end up with a large number of repositories in order to keep all his/her apps updated. Refreshing repositories might take longer every time due to this and it might cause confusion. The user will have to regularly check the enabled repositories and think of whether they are needed or not. Refreshing a large number of repositories might also take a while. Repositories can get deleted or altered often and the user will have to modify them at each deletion/alteration. It's impossible for a user to pick up the work of another user on certain repositories. Thus the new maintainer will have to make a different repository. - Users might get confused when apps are offered by multiple repositories. Not all repositories are tagged and it might be difficult to tell which repository has the most updated yet stable package. Zypper will warn the user if the added repository and package will rewrite anything that is already existing as it does whenever a vendor change is required. However, users might not heed the warning and they might not be able to tell if something actually works or not before installing it. What we currently have is not a broken structure. On the contrary, our current system works. However, even if it is not broken, and doesn't require fixing, it can be improved. I'll further demonstrate the limitations of the system by providing user cases. - Daniel wants to install package XYZ. However, package XYZ is not in the default repositories. Daniel goes to software.opensuse.org and searches for package XYZ but finds it listed under several repositories. Some have higher version than others. Daniel wants the highest stable version from a trusted repository. Which one of the repositories should Daniel choose? - Michael is a heavy gamer. He wants to play video games on his desktop. He adds games:tools to install Steam. He then proceeds to add Emulators to install ZSNES, and finally adds games to install SuperTux2. However, he notices that another game he wants is further updated on a home repository and has to add that too. Michael ends up with having too many repositories in order to get a few applications. - Christine is a fan of music. She has thoroughly tested most music applications but is dissatisfied with them. She adds KDE:Extra in order to update Clementine to a higher version, then downloads the .rpm of Rhythmbox from Factory so she can install it without adding the repo, and then adds GNOME:Apps to use an updated mplayer. Lastly, she adds Geeko123's repo because he created his own music player and uploaded it to his home project. One day, she wants to install Wayland dev packages. Unknown to her, Geeko123 has added his own unstable Wayland packages. Zypper pulls the Wayland packages from Geeko123's repo and Christine ends up with a broken Wayland because she had assumed that Geeko123's repo was solely for his music player and did not read the warnings. As such, I propose the following improvements: 1 - Create larger repositories and merge similar ones together. Games, game:tools, emulators, Documentation:Tools, KDE:Extra, GNOME:Apps, LibreOffice:Stable, Network, Network:Chromiun, Mozilla, Mozilla:Beta, Mozilla:Alpha, Utilites, Network:Utilities, Utilities, and other similar repositories can be merged together into one repository that offers extra software. We can call it "OSS Extra". The proprietary packages, like Steam, can be added to the Non-OSS repository. This can include different desktop environments as well instead of having to place XFCE, LXDE, MATE, and other desktop environments in their own repositories so long as their packages don't conflict. Naturally, certain projects have conflicting packages. For instance, Ayatana's packages override GNOME. For those projects we can make an alternative repository of their own. We'd cut down a large number of repositories and aggregate them into three separate ones. Multimedia libraries, security packages, server-oriented packages, and debugging and development tools can be added to a repository of their own. GNOME:Next, KDE:Unstable, KF5, and all the similar unstable packages can be kept in an Unstable repo. Factory can be aggregated into a Factory repo. Packages that are being tested can have their own Testing repo. If someone wants to submit a package to these repositories directly, he/she has to have permission to. Users can submit their packages but they won't appear unless the maintainers review them. Instead of having Calibre listed in 10 different repositories and each of them having a version, the packager who wants to update the software can silently submit the package and the maintainer can approve it or disapprove of it. This will save the maintainers some work if they don't have to package everything themselves. This also means that we can have more maintainers. Some people are willing to test but can't package stuff. Submitted packages can be tagged (GNOME, KDE, GTK, etc.) so maintainers can pick a tag to work on that follows their preferences. 2 - Create Community repository that is managed and run by the community. Home projects can remain a playground for packages and app developers. When their apps are ready, they can be moved into the Community repository. Instead of having one repository for Budgie, one for Elegance-colors, and one for Corebird, packages and builders can submit their packages to Community. If someone decides to quit maintaining a package, another maintainer can seamlessly take his/her place without setting up a new repository and forcing the user to update their sources. The community repository will be collaborative at its heart. - Add Reputation system. Installing packages from the Community repo can be a unsafe. However, if the uploader has been praised before, then the user might feel more trusting. That way, the user will have a better idea what is all right to install and what isn't. This will also give motivation to people. - Let the community maintain its own repository. By giving this repository a rating system, we can let the community maintain this repository on its own. Alternative Suggestions: 1 - Make zypper utilize smarter metadata. Zypper can be updated to read all the metadata from all the repositories and could suggest adding a repository if the desired package isn't in the currently enabled repository. People should be able to use zypper to find packages instead of having to resort to a browser to search through OBS. This way, users can use gnome-software to access all the software on OBS (in the future when a zypper plugin is written for gnome-software). 2 - Visibly tag repositories to show their stability. In order to help users choose the most stable repository, visible tags should be provided to indicate the stability before the user adds the repository. 3 - Make repositories collaborative. By allowing collaborative work we may end up seeing less repositories in general. If person X creates repo for package Y, person X is asked if repo is to be open for collaboration to everyone. If person X decides to quit, another maintainer can pick up the work on the same repository. 4 - Allow user to hide all "home" repositories. I firmly believe that we should make everything simpler. It isn't a matter of what can or can't be done, it's more about how easy it is to get things done. By clearing confusion and allowing collaborative work, we can help the users save precious time, give them an easier system, and help them make better decisions. With front-end GUIs for package managers, like Apper and gnome-software, on the rise, the traditional method of installing software is changing. The shortest distance between two points is a straight line. Thus, we should reduce the steps and complications of installing and managing software in order to appeal to more users and to further satisfy the ones we have. Improvement is what keeps projects interesting. I for one do not want a system that works. I want a system that works better than it did before. I hope you all consider my suggestions before judging them and think of the average users, not just of the advanced ones. Thank you for your time and I hope we can keep this thread civil. Sincerely, Antoine Saroufim (Vagrant232)" -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

8 31

[opensuse-project] GSoC Ideas on Ideas page
by Saurabh Sood 06 Jan '14

06 Jan '14

Hi, We have about a month before organization applications close. I request all interested mentors to add in their projects on our ideas page: https://en.opensuse.org/openSUSE:GSOC_ideas Hoping to see loads of ideas soon ;) -- Regards,. Saurabh Sood Have a lot of fun! -- To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org To contact the owner, email: opensuse-project+owner(a)opensuse.org

1 0