March 2015 - YaST Development - openSUSE Mailing Lists

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 09 Mar '15

09 Mar '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-bootloader: - unify on rubocop version 0.29.1 (6 days) https://github.com/yast/yast-bootloader/pull/225 Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (19 days) https://github.com/yast/yast-network/pull/284 - Autoyast: do not overwrite firewall settings (46 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (24 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (192 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (54 days) https://github.com/yast/yast-yast2/pull/310 Pending requests in repository yast-docker: - Start making this a gem (153 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] OBS: removing openSUSE-13.1 target in YaST:Head
by Ladislav Slezak 06 Mar '15

06 Mar '15

Hi, we still build YaST:Head project against openSUSE-13.1 build target, unfortunately there are currently many unresolvable dependencies (because of the updated rspec packages). Keeping the 13.1 build alive gets more and more difficult, Factory moves forward and the difference slowly but steadily increases. IMHO we do not need the 13.1 target anymore, there's been pretty long time to upgrade to 13.2. My plan is to remove the 13.1 build target unless there is a volunteer willing to fix the current issues and keeping it building for some more time. !!!!!!!!!!!!!!!!!!! If nobody is interested in 13.1 maintenance I'll remove the 13.1 build target and the extra packages built for 13.1 this Friday (Mar 6) around 4PM (CET). So if you want to maintain the 13.1 target let me know ASAP. !!!!!!!!!!!!!!!!!!! -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 2

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 06 Mar '15

06 Mar '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (16 days) https://github.com/yast/yast-network/pull/284 - Autoyast: do not overwrite firewall settings (43 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nfs-client: - [Do not merge] Fix #919061 and refactor dialog (9 days) https://github.com/yast/yast-nfs-client/pull/39 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (21 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (189 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (51 days) https://github.com/yast/yast-yast2/pull/310 Pending requests in repository yast-docker: - Start making this a gem (150 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] photo retouching introduction
by Jeff 05 Mar '15

05 Mar '15

We want to introduce our photo retouching/clipping path. Here are our offerings below: photo retouching, photo clipping path, jewellery photo retouching, ecommerce products photo editing, photo cut out and masking, beauty and skin retouching, wedding photos editing. You may send us a photo for free testing to check quality. Looking foroward to receive your soonest response. Thanks, Jeff Email: lovocontact(a)tom.com -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 05 Mar '15

05 Mar '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (15 days) https://github.com/yast/yast-network/pull/284 - Autoyast: do not overwrite firewall settings (42 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nfs-client: - [Do not merge] Fix #919061 and refactor dialog (8 days) https://github.com/yast/yast-nfs-client/pull/39 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (20 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (188 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (50 days) https://github.com/yast/yast-yast2/pull/310 Pending requests in repository yast-docker: - Start making this a gem (149 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] AutoYaST Integration Tests
by Stefan Schubert 04 Mar '15

04 Mar '15

Hi, I have written a little test framework for running AutoYaST integration tests by using veewee, vagrant and pennyworth. I have not written something new but have only taken already existing tools and workflows. Features * Building KVM images by using AutoYaST profiles. * Checking these KVM images with rspec tests. * Generating own installation ISOs with local built RPMs or the newest one from OBS. >From my point of view it helps me to make changes in AutoYaST and running complete integration tests before submitting the package to OBS/IBS. If you are interested please have a look to: https://github.com/schubi2/autoyast_test Greetings Stefan -- ******************************************************************************* Stefan Schubert e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX GmbH GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

5 7

[yast-devel] OBS: added SLE12 and SLE12-SP1 targets
by Ladislav Slezak 04 Mar '15

04 Mar '15

Hi all, I have added SLE12 build target to YaST:Head (OBS). And I also added SLE12-SP1 target to Devel:YaST:Head (IBS). (So far only 64-bit targets to save some build power, if you need e.g. i586 packages then feel free to enable them.) -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Pending Pull Requests
by yast-ci＠opensuse.org 04 Mar '15

04 Mar '15

This email is automatic generated from yast CI node. It lists of pull requests that have no activity more then three working days. If your module is listed, please check all pull request, why they are not merged yet. Pending requests in repository yast-iscsi-lio-server: - filter out scope link IPv6 address (Code 11 SP4) (7 days) https://github.com/yast/yast-iscsi-lio-server/pull/35 Pending requests in repository yast-network: - Fixed changing configuration name when adding new device (14 days) https://github.com/yast/yast-network/pull/284 - Autoyast: do not overwrite firewall settings (41 days) https://github.com/yast/yast-network/pull/275 Pending requests in repository yast-nfs-client: - [Do not merge] Fix #919061 and refactor dialog (7 days) https://github.com/yast/yast-nfs-client/pull/39 Pending requests in repository yast-nis-server: - Added command line support for Active Slave sync (19 days) https://github.com/yast/yast-nis-server/pull/6 Pending requests in repository yast-theme: - Install scalable icons & fix name of yast-yast-language.* to yast-language.* (187 days) https://github.com/yast/yast-theme/pull/45 Pending requests in repository yast-yast2: - Use native Ruby implementations in Yast::URL and Yast::IP (49 days) https://github.com/yast/yast-yast2/pull/310 Pending requests in repository yast-ycp-ui-bindings: - enhance example for Date/TimeField, add RELEASE.NOTES examples (6 days) https://github.com/yast/yast-ycp-ui-bindings/pull/24 Pending requests in repository yast-docker: - Start making this a gem (148 days) https://github.com/yast/yast-docker/pull/2 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0

[yast-devel] Topic days for the Yast team?
by Ladislav Slezak 03 Mar '15

03 Mar '15

Hi all, I have an interesting idea for the Yast team. What about starting "topic days" events regularly? Some upstream projects do for example "bug squashing days", we could do something similar. Pros: + whole team is focused on one topic, we could get more ideas, opinions, better find a solution which works for more yast modules... + doing the same in all modules at once means we use the same (or similar) solution in all Yast modules, we can easily unify the solution + doing the work in parallel for many developers mean it will be done fast (or finished in the end, sometimes I fix/improve something in one module but do not have enough time to do it in all other Yast repos...) + improves team spirit and team cooperation + the team as whole learns something new Cons: - the date and the topic needs to be set in advance - needs some preparation in advance, someone has to lead the project - does not work for all projects, the project needs to scale easily (i.e. it does not need any deep knowledge about the module, the task needs to be generic enough for all developers) The project should take max. few hours for each developer, the real power is in the massive[1] parallel work. I have some example topics/projects which we could try: - Improve Yast README files (as discussed in a separate thread) - Fix yardoc documentation comments. Many Yast modules print warnings when building the docs, usually there are typos (@return vs. @returns), obsoleted/missing parameters, typos in type names... which can be easily fixed without any knowledge of the module. - Convert old tests to RSpec - Use coveralls for code coverage status - Use rubocop for checking the code For tracking the status we could use a google docs spreadsheet, it worked well for us in the YCP killer project. We knew the overall progress, who was working on what (no conflicts)... Of course, your participation would not be mandatory, if you would not like a specific project or you would have something more important to do (L3s...) then you would not have to join. What do you think about it? Would you participate in such event? Do you have more ideas what projects we could do? Thanks for your response! [1] Well, with the rather small team we have it cannot be that "massive", but anyway... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

4 3

[yast-devel] Things software development teams should know about design
by Ladislav Slezak 03 Mar '15

03 Mar '15

Hi, I found a very interesting article by Garret about design and teams [1] which is really worth of reading. And the linked MSDN document "Usability in Software Design" [2] which someone mentioned in the discussion is also quite interesting. See the links below. (Maybe we could even link them from our developer documentation...) [1] http://linuxart.com/log/archives/2015/02/06/things-software-development-tea… [2] https://msdn.microsoft.com/en-us/library/windows/desktop/ff728829 -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak(a)suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: yast-devel+owner(a)opensuse.org

1 0