Hi all,
Yesterday I published a short blog post about recording a screencast
(a desktop session) to create a video or an animated image.
So if you want to have nice animated images in READMES [1] or in pull requests [2]
then check this post [3].
Enjoy!
[1] https://github.com/lslezak/build-rake/blob/master/README.md
[2] https://github.com/yast/yast-registration/pull/240
[3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html
--
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
Hi,
I have noticed a quite interesting GitHub feature which allows to protect
the specified branches. A short summary from [1]:
A protected branch:
- Can't be force pushed
- Can't be deleted
- Can't have changes merged into it until required status checks pass
- Can't have changes merged into it until required reviews are approved
- Can't be edited or have files uploaded to it from the web
See [1] and [2] for more details.
AFAIK some developers use forks mainly because they are afraid of messing
the original repositories. With protected branches that should not happen.
Additionally it would strictly enforce PR reviews (we do that already
so I see no problem with that).
IMHO a nice feature, I'm just not sure which branches we could protect.
Obviously the old maintenance branches, I'm not sure about the "master"
branch, maybe it would be too strict.
What do you think about it? Should we use this GitHub feature?
We could use the agile approach, try it in a few selected repos and see
how it works...
Comments?
[1] https://help.github.com/articles/about-protected-branches/
[2] https://help.github.com/articles/configuring-protected-branches/
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
...I want to make sure there is a solution that I simply have not yet found.
Expected (OK) fonts results (e.g.):
sw_single @120 DPI in KDE3 on 13.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOK131kde3-120.png
sw_single @132 DPI in KF5 on TW:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesOKtwkde5-132.png
Not expected (undersized) fonts results (e.g.):
sw_single @108 DPI in TDE on 13.2:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall132tde-108.png
sw_single @120 DPI in KDE3 on 42.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-120.p…
sw_single @168 DPI in KDE3 on 42.1:
http://fm.no-ip.com/SS/Suse/YaST/newbug-yast2fontsizesTooSmall421kde3-168.p…
Clearly sw_single (and other y2 apps) post-13.1 (except in KF5) is using
smaller fonts than those used in the y2 control center and in the rest of DE
UI, as if both the non-KF5 DE's font settings and QT's font setting in
Trolltech.conf are being disregarded.
Is there something that can be installed or removed to bring up font sizes to
match the rest of the DE and y2cc in KDE3 and TDE without loading the
installation with QT5 and/or KF5, or even with QT5 and/or KF5? Or, is this a
bug that's already been filed, or one that needs filing?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
In celebration for our 25th Scrum sprint[1], we have published a new
sprint report. Enjoy it at
https://lizards.opensuse.org/?p=11983
Cheers.
[1] Yes, we publish one for every sprint. Still, it's always a
celebration ;)
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hello,
I have adjusted the image with installer using new storage stack [1];
now it can generate the software proposal without dependency conflicts
if you select the minimal X11 pattern.
For now, I set the image build to fail if package missing - which will
happen rather soon due to "renames" with library version changes, I
assume. However, image which cannot select packages properly is still
more useful for current testing than no image at all (feel free to
disagree here).
Jiri
[1] http://download.opensuse.org/repositories/YaST:/storage-ng/images/iso/
imag openSUSE-TW-NewStorage-DVD-x86_64 Build22.1 or newer
--
Regards,
Jiri Srain
Project Manager
---------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.com
Lihovarska 1060/12 tel: +420 284 084 659
190 00 Praha 9 fax: +420 284 084 001
Czech Republic http://www.suse.com
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
