Re: [ubuntu-studio-devel] LiveFS ubuntustudio/yakkety/amd64 failed to build on 20160820

[Kaj Ailomaa]

On Tue, Aug 23, 2016, at 07:57 PM, Ross Gammon wrote:
> On 08/20/2016 10:50 AM, Ross Gammon wrote:
> > On 08/20/2016 10:23 AM, CD Image wrote:
> >> The following information may help to resolve the situation:
> >>
> >> The following packages have unmet dependencies:
> >>  gnupg1 : Breaks: gnupg (< 1.4.20-6+exp1) but 1.4.20-6ubuntu1 is to be 
> >> installed
> >>  kactivitymanagerd : Breaks: kactivities (< 5.20~) but 5.18.0-0ubuntu1 is 
> >> to be installed
> > There appear to be a few library transitions going on. I triggered the
> > rebuild after checking the last error (libwebkitgtk-1.0-0) seemed to be
> > OK in launchpad. As I can't be on IRC much today, I will check the
> > situation periodically over the weekend. As Len says, we really need the
> > Live Image building for Beta 1 testing this coming week.
> >
> >
> The gnupg issue seems to be solved according to the last buildlog
> failure. But the other still exists.
> 
> kactivitymanagerd is not co-installable with kactivities. However,
> kactvities requires plasma-framework, which requires libkf5activities5,
> which requires kactivitymanagerd!
> 
> It seem that krita is our package that pulls in this mess.
> 
> I am about to test that theory in a VM (currently downloading a vanilla
> Ubuntu ISO). Then I will submit a bug. We should drop krita from the
> seeds temporarily, to try and get a successful CD built.
> 

Yes, sakrecoer was able to find out about as much from talking with
Kubuntu devs (who I assumed were handling that package, but actually
not).

It seems krita is dropped from Debian, and hasn't been updated since
December.  According to the info I reveived is the package needs to be
updated (the source is calligra, and maintained by pkg-kde).

So, yes, we need to drop it. Question is - who is up for updating the
Debian package, and the syncing it?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Please help testing ardour5 for yakkety

[Kaj Ailomaa]

On Tue, Aug 23, 2016, at 07:21 AM, Kaj Ailomaa wrote:
> On Tue, Aug 23, 2016, at 06:48 AM, Ross Gammon wrote:
> > On 08/22/2016 06:28 PM, Kaj Ailomaa wrote:
> > > A new ardour has appeared in unstable, so now would be good to do a
> > > sync-request. I'm unable to do it atm. But, will check back tomorrow.
> > >
> > Someone beat me to it :-)
> > 
> > 
> 
> Well, wasn't me :).
> 
> As soon as it's in I'll revert the change in the seeds and the meta.
> 

That was fast (already in the archive). I already updated the seeds.
Building the new meta right now, which I will be uploading soon.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Please help testing ardour5 for yakkety

[Kaj Ailomaa]

On Tue, Aug 23, 2016, at 06:48 AM, Ross Gammon wrote:
> On 08/22/2016 06:28 PM, Kaj Ailomaa wrote:
> > A new ardour has appeared in unstable, so now would be good to do a
> > sync-request. I'm unable to do it atm. But, will check back tomorrow.
> >
> Someone beat me to it :-)
> 
> 

Well, wasn't me :).

As soon as it's in I'll revert the change in the seeds and the meta.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Please help testing ardour5 for yakkety

[Kaj Ailomaa]

A new ardour has appeared in unstable, so now would be good to do a
sync-request. I'm unable to do it atm. But, will check back tomorrow.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] support for wine-rt out-of-box?

[Kaj Ailomaa]

On Sat, Aug 20, 2016, at 04:45 PM, Len Ovens wrote:
> On Sat, 20 Aug 2016, Set Hallstrom wrote:
> 
> > I'm not 100% sure, but i think wine isn't distributed because of the
> > license. However, your idea of creating good instruction on how to set
> 
> The main reason we have not included wine is a lib problem. I do not know 
> where things are at now, but in the past wine has been a 32bit
> application 
> that required a whole set of 32bit libraries. This makes it not work for
> a 
> 64bit ISO (wine has to be installed after the ISO install). Wine did used 

I'm not entirely sure this is correct. The 32bit libs can co-exists
quite nicely with the 64bit ones.

We don't include wine itself, because we have not included it as a part
of our workflows.
As for wine-rt. I have never tried it, but I'm assuming it is a package
that doesn't exist in the archive.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] support for wine-rt out-of-box?

[Kaj Ailomaa]

On Sat, Aug 20, 2016, at 11:54 AM, Set Hallstrom wrote:
> Hi Hank!
> 
> On 2016-08-19 08:47, Hank Stanglow wrote:
> > Hello, I am a Web Developer, Artist, Musician, and long time user of
> > Ubuntu Studio. You guys do a great job! This distribution gives me the
> > best out-of-box experience for Web Development and I find the Art and
> > Publishing tools perfectly adequate for my needs. 
> 
> Thank you for reaching out with your input in such an uplifting tone!
> 
> > Music and Video? Not
> > so much, but this a problem for all Linux distributions. In fact, after
> > seven years of fumbling with the JACK/ALSA/Pulse nightmare I've given up
> > using native tools and now use WINE exclusively for audio work. Even KX
> > Studio has more problems than I care to deal with and the only thing I
> > take from its repos is wine-rt. If I were to make ONE suggestion for
> > Ubuntu Studio it would be to have a super stable, low-latency WINE-rt
> > environment for audio users (or good instructions on how to set one up).
> 
> I agree that the state of Linux in terms of Music is tougher than
> mainstream OS. Since i mainly record hardware electronics, it isn't much
> of an issue for me personally. But lately I've grown pretty fond of
> qtractor for ITB (In The Box) production with midi controlled Software
> synthesizers. I have yet to finish a song to prove my point, but while
> it is a little wilder than i remember ITB production from other OS'es,
> it actually works :) For video editing i always have to point towards
> blender's VSE which has become pretty awesome if one has got the time to
> get familiar with its GUI.
> 
> I'm not 100% sure, but i think wine isn't distributed because of the
> license. However, your idea of creating good instruction on how to set
> it up is an excellent one. In fact, we really need help with
> documentation. If you have any spare time to share, you are welcome to
> join the ubuntustudio-documentation team. Maybe pass by our IRC channel
> sometime on freenode #ubuntustudio-devel and say hi?:)
> 

Wine is fully free. We have distributed it before. But, I've never tried
wine-rt myself and it doesn't exist in Debian repos, and hence neither
in Ubuntu repos. Someone would need to package it. If that happens, we
can include it.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Petri-foo

[Kaj Ailomaa]

On Sat, Aug 20, 2016, at 11:24 AM, br...@linuxsynths.com wrote:
>   
> 
> Ok, I logged into Launchpad and am ready to post the bug. Here is
> what the terminal gave me: 
> 
> /usr/share/apport/apport-gtk:16:
> PyGIWarning: Wnck was imported without specifying a version first. Use
> gi.require_version('Wnck', '3.0') before import to ensure that the right
> version gets loaded.
>  from gi.repository import GLib, Wnck, GdkX11, Gdk
> 
> 
> Should I confirm this as an actual bug? 
> 
> brian 
> 

Someone else needs to confirm the bug. You simply report it with the
terminal tool 'ubuntu-bug', by running the command in the terminal:

ubuntu-bug petri-foo

Then, someone else needs to try the steps you describe in the bug report
and see if that also happens on their machine. If so, then that person
may confirm the bug. 

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Please help testing ardour5 for yakkety

[Kaj Ailomaa]

On Sat, Aug 20, 2016, at 11:10 AM, Ross Gammon wrote:
> On 08/19/2016 09:15 AM, Kaj Ailomaa wrote:
> > Actually, not all of the packages are published on the PPA yet, but for
> > yakkety it's just a matter of minutes. xenial should follow within an
> > hour, with any luck.
> >
> > And, to be clear, you need to add the PPA no matter how you decide to
> > test. So, at the end, always do
> >
> > sudo add-apt-repository ppa:ubuntustudio-dev/dev-testing
> > sudo apt-get update && sudo apt-get dist-upgrade
> >
> Thanks for looking after this Kaj. It's been a busy week for me.
> 
> It took me a while to get my Yakkety VM up-to-date. Ardour 5 (ppa
> version) installs fine for me. I ran the Manual Test Case
> (http://packages.qa.ubuntu.com/qatracker/milestones/361/builds/117793/testcases/1672/results)
> for Ardour, and had no problems until the end when I was fiddling with
> Jack to get some sound, and the VM crashed. Probably just the VM's fault
> (and because I didn't set up "High" latency first). I will try again
> over the weekend with real hardware.
> 
> Do you plan to produce a new version for sponsorship in Debian (I saw
> your commit)? Or I could help take care of that?

I've never done that before, so if you would like to take care of it,
that would be great. As soon as it's in Debian we should do a
request-sync for it, and then update the meta again.

Apparently ardour 5.1 is soon to be released with some bug fixes, which
would be good to do a request-sync for as well. But, I'm not sure about
the schedule, so could be it's worth waiting for that first. That might
mean we need to update the Debian package ourselves, if we are in a
hurry (depending on when the maintainer is able to do it). Len might
know more about when ardour 5.1 is released.

> 
> By the way. I subscribed you (and the sponsors team) to my packaging of
> the new package list version (blueprint) of the -meta package (but
> forgot to ping you):
> 
> https://bugs.launchpad.net/ubuntustudio-meta/+bug/1608275
> 
> I will re-base this on top of your recent "drop Ardour" version, but it
> would be nice to get this in before the final beta. Or would you prefer
> to wait until after the "restore Ardour" event?
> 
> Cheers,
> 
> Ross
> 

I think that bug would be more appropriate if you needed a sponsor
outside of the team. As long as I'm able to do uploads, you just need to
ping me when an update to the meta is needed. The meta package is always
built by the uploader directly, which makes the procedure quite simple.

I will be able to do uploads after FF without much problems (uploads
will only be for bug fixes). It is only when we hit Final Freeze when
things get troublesome.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Petri-foo

[Kaj Ailomaa]

On Sat, Aug 20, 2016, at 11:04 AM, br...@linuxsynths.com wrote:
>   
> 
> Hi everyone, 
> 
> I have the latest version (Xenial) of Petri-foo
> installed on my 32-bit laptop with Ubuntu Studio (15.10 recently updated
> to 16.04). Unfortunately I can't get it running, I get a core dumped
> message. 
> 
> Anyone able to help with this? 
> 
> Thanks in advance.. 
> 
> brian
> 
>   

Please report a bug. Get a launchpad account at http://launchpad.net and
then, from the terminal, do:

ubuntu-bug petri-foo

Someone will need to confirm the bug by trying it on their own machine.
If the bug is confirmed, it is clearly a bug in the package and needs to
be fixed.

So, that's the general procedure. But, it's quite ok to write to us
about it as well.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] 16.10 Beta 1 Freeze

[Kaj Ailomaa]

On Sat, Aug 20, 2016, at 10:53 AM, Set Hallstrom wrote:
> tisdagen den 16:e augusti 2016 kl. 22:55:37 CEST, Set Hallstrom 
>  skrev:
> > 
> > Ok, thanks guys! I'll let the release team know we are in.
> > Regarding the theme changes, if i understood Kaj correctly on IRC today,
> > we have until UI freeze on September 8th to land them...
> > 
> > Yours,
> 
> I reached out and i've been asked who is holding it from our side. I 
> assumed Ross would, but the question made me realise he hasn't answered
> yet 
> and might be too busy, in which case i guess i could do it, unless there 
> are some permissions needed that i don't behold. I'm reading up on the 
> process anyway..
> 
> At the moment, this page says Kaj is the contact for it:
> 
> https://wiki.ubuntu.com/YakketyYak/Beta1
> 
> is that correct or copypasta?
> 
> Yours,
> 
> 

Just change that page and put you and Ross on it instead of me - I'm not
the contact. Make those links to your LP pages as well.
I have made an announcement on the -release list about Ross being our
testing lead and also on -devel about you being project lead, but could
be someone missed or forgot that. Sooner or later they will remember who
is who.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Please help testing ardour5 for yakkety

[Kaj Ailomaa]

Actually, not all of the packages are published on the PPA yet, but for
yakkety it's just a matter of minutes. xenial should follow within an
hour, with any luck.

And, to be clear, you need to add the PPA no matter how you decide to
test. So, at the end, always do

sudo add-apt-repository ppa:ubuntustudio-dev/dev-testing
sudo apt-get update && sudo apt-get dist-upgrade

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Please help testing ardour5 for yakkety

[Kaj Ailomaa]

# Help testing

ardour was recently updated to v5. The package was updated just before
Debian Import Freeze, and had at least one problem - which now is fixed,
but not yet uploaded. There may be other problems. So, I'm asking for
help with testing ardour and making sure we don't release a half
finished package for yakkety.

# Installing the latest ardour

Currently, you may only find the latest package in one of our testing
PPAs. To add the PPA, do:

sudo add-apt-repository ppa:ubuntustudio-dev/dev-testing

You may test on either yakkety, or xenial (xenial package is currently
building, but may fail). In both cases, just add the PPA,  do a system
upgrade, and start testing ardour.

If xenial fails, and you don't have yakkety, here are some options:

* Install Ubuntu Studio from a mini iso (will not add RT settings - use
ubuntustudio-controls for that)
  * 64bit
  
http://archive.ubuntu.com/ubuntu/dists/yakkety/main/installer-amd64/current/images/netboot/mini.iso
  * 32bit
  
http://archive.ubuntu.com/ubuntu/dists/yakkety/main/installer-i386/current/images/netboot/mini.iso
* Do a full upgrade from xenial to yakkety with the command 'sudo
do-release-upgrade -d', then add the PPA and install/upgrade ardour
* In xenial, change xenial to yakkety in /etc/apt/sources.list, add the
PPA, then install ardour (will mess up your system somewhat - so don't
do this if you plan on using it further, but should be ok for testing
ardour)

# Running ardour

If all else fails, run it from the terminal with the command 'ardour5'

# Reporting bugs

To report a bug, get yourself a launchpad account, if you haven't
already. Then, from your system, run the command:
 
ubuntu-bug ardour

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ardour5 bug probably causing build failure - WAS:Re: Ardour 5 just landed in debian

[Kaj Ailomaa]

On Wed, Aug 17, 2016, at 10:45 PM, Kaj Ailomaa wrote:
>  > Just checked the error log, and it seems ardour5 is what is causing the
> > build failure. I will remove it from our meta and do a bug report for
> > it. Once the bug is fixed, it can be readded.
> > 
> > This could be the cause. We had a talk about it on IRC as well.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834488
> > 
> > I will try and see if I can commit a fix to Debian source today, and ask
> > for an upload (both in Debian, and Ubuntu). Won't have much time the
> > rest of the week for this though.
> > 
> 
> Was only able to report a bug and upload a new meta. Will try to find
> some time tomorrow again.
> 

I've pushed the tiny change needed to fix the bug to the Debian git repo
for ardour. There may be other issues though (since the package is still
so young), so I think it would be wise to test it before the Beta 1.
Otherwise, we risc releasing a half finished package.

I've uploaded the ardour source to:
  ppa:ubuntustudio-dev/dev-testing

Will take a while to build. Will do a new post asking for testers once
it's ready.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ardour5 bug probably causing build failure - WAS:Re: Ardour 5 just landed in debian

[Kaj Ailomaa]

 > Just checked the error log, and it seems ardour5 is what is causing the
> build failure. I will remove it from our meta and do a bug report for
> it. Once the bug is fixed, it can be readded.
> 
> This could be the cause. We had a talk about it on IRC as well.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834488
> 
> I will try and see if I can commit a fix to Debian source today, and ask
> for an upload (both in Debian, and Ubuntu). Won't have much time the
> rest of the week for this though.
> 

Was only able to report a bug and upload a new meta. Will try to find
some time tomorrow again.

https://bugs.launchpad.net/ubuntu/+source/ardour/+bug/1614224

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Ardour5 bug probably causing build failure - WAS:Re: Ardour 5 just landed in debian

[Kaj Ailomaa]

On Wed, Aug 17, 2016, at 07:26 AM, Ross Gammon wrote:
> Just checked, and Ardour 5 is in yakkety.
> 
> On 08/16/2016 05:43 PM, Set Hallstrom wrote:
> > Hi,
> >
> > Len just announced on IRC that Ardour 5 landed in debian
> > https://packages.qa.debian.org/a/ardour.html
> >
> > Do i read this correctly:
> > https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting_a_new_package_for_Ubuntu
> >
> > if i think it will be synced automatically, since FF and DIF is tomorrow?
> >
> > Do we have time to include it in 16.10?
> >
> > Yours,
> >

Just checked the error log, and it seems ardour5 is what is causing the
build failure. I will remove it from our meta and do a bug report for
it. Once the bug is fixed, it can be readded.

This could be the cause. We had a talk about it on IRC as well.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834488

I will try and see if I can commit a fix to Debian source today, and ask
for an upload (both in Debian, and Ubuntu). Won't have much time the
rest of the week for this though.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] 16.10 Beta 1 Freeze

[Kaj Ailomaa]

On Tue, Aug 16, 2016, at 09:07 PM, Kaj Ailomaa wrote:
> On Tue, Aug 16, 2016, at 08:37 PM, Len Ovens wrote:
> > On Tue, 16 Aug 2016, Len Ovens wrote:
> > 
> > > On Tue, 16 Aug 2016, Set Hallstrom wrote:
> > >
> > >> Hi all,
> > >> 
> > >> Do we want to participate in Beta 1 Freeze next week?
> > >> Beta 1 Freeze (Monday), and Beta 1 release on Thursday...
> > >> 
> > >> https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
> > >
> > > It seems all our seeds changes are in, so I would say yes. This assumes 
> > > you 
> > > can still make the theme changes after such a freeze.
> > 
> > Of course, it would be nice if the ISO was building ... bug 1
> > 
> > --
> > Len Ovens
> > www.ovenwerks.net
> > 
> 
> I know there have been some changes in our seeds done by infinity. If
> so, I'm hoping he will also fix whatever the problem is with the build.

I mean of course that if his changes caused the build failure, he will
probably fix it.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] 16.10 Beta 1 Freeze

[Kaj Ailomaa]

On Tue, Aug 16, 2016, at 08:37 PM, Len Ovens wrote:
> On Tue, 16 Aug 2016, Len Ovens wrote:
> 
> > On Tue, 16 Aug 2016, Set Hallstrom wrote:
> >
> >> Hi all,
> >> 
> >> Do we want to participate in Beta 1 Freeze next week?
> >> Beta 1 Freeze (Monday), and Beta 1 release on Thursday...
> >> 
> >> https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
> >
> > It seems all our seeds changes are in, so I would say yes. This assumes you 
> > can still make the theme changes after such a freeze.
> 
> Of course, it would be nice if the ISO was building ... bug 1
> 
> --
> Len Ovens
> www.ovenwerks.net
> 

I know there have been some changes in our seeds done by infinity. If
so, I'm hoping he will also fix whatever the problem is with the build.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] 16.10 Beta 1 Freeze

[Kaj Ailomaa]

On Tue, Aug 16, 2016, at 08:29 PM, Set Hallstrom wrote:
> Hi all,
> 
> Do we want to participate in Beta 1 Freeze next week?
> Beta 1 Freeze (Monday), and Beta 1 release on Thursday...
> 
> https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
> 
> Yours,
> -- 
> Set Hallstrom aka sakrecoer
> 
> -- 

It's a good time to do a first evaluation of the state of the distro. It
is just after Debian import freeze, and an excellent chance to test the
Debian imported packages so there is time to catch and fix any obvious
bugs. So, yes from me.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Feature tour (was: Seventh try )

[Kaj Ailomaa]

On Thu, Jul 28, 2016, at 02:33 PM, Set Hallstrom wrote:
> On 2016-06-23 02:00, Jóhann Örn Geirdal wrote:
> > Seventh try ;)  Hi here is only a base I will ad to it some more but
> > what do you think about this?
> > http://geirdal.is/index.php/studio-0
> 
> I made a few shots that could work well as complementary pictures to the
> more abstracto-figurative pictures Geirdal made for the categories.
> 
> I realize they might not be perfect, but maybe you like the idea?
> 
> I tried to make one for each category, but i think they all end up
> having a lot of "audio focus" maybe it is a good thing? You tell me. One
> sure thing is that the "graphic workflow" one, needs a different
> on-screen content :D (too "cute, wtf, kindergarten")
> 
> http://sakrecoer.com/ubuntustudio/featuretour__1.jpg
> http://sakrecoer.com/ubuntustudio/featuretour__2.jpg
> http://sakrecoer.com/ubuntustudio/featuretour__3.jpg
> 
> The more i look at Geirdal pictures, the better i like these:
> 
> http://geirdal.is/images/studio/audio_x.png
> http://geirdal.is/images/studio/graphic_03.png
> http://geirdal.is/images/studio/video_x.png
> 
> If they are used without the pictograms, like they were intended: as
> backgrounds for text and screenshots, i think they are perfect! They
> refer to analogue times with very contemporary elements. I think it
> emulates what we are quite well: /linux for creative humans/ a digital
> product made by analogue robots ;) And they are quiet and noisy at the
> same time, which i find to be a really poetic contrast.
> 
> I think this one is really beautyfull but it should be used without the
> logos for the general "about" text in the feature tour (:
> http://geirdal.is/images/studio/studio_07.png
> 
> It is risky, but i also find it very cool, fresh and inspiring. 90's
> fractal with a millennial twist! This afternoon i will try put together
> what i mean in a collage.
> 
> I'm convinced that, properly framed on the page, using geirdals pictures
> could make the sexiest feature tour, ever :)
> 
> Yours,
> 
> -- 
> Set Hallstrom aka sakrecoer
> 

The only thing I would like to remind of is of the "big picgture", which
should be about information. It's easy to become a bit obsessed about
the details of a design, but the importance is still around what the
whole thing informs.

And, what is the information? That is the question that needs to be
answered - not only with graphics, but with  the whole thing.

The current feature tour is old, and should be buried. It should be
replaced by something that does the same thing, but better. Better
information. Better graphics, but most importantly - better information.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Yakkety Alpha 2 (for opt-in flavors)

[Kaj Ailomaa]

On Mon, Jul 25, 2016, at 02:55 PM, Ralf Mardorf wrote:
> 
> Make it transparent, easy to understand and I will help.
> 

I was referring to helping Ubuntu Studio by becoming a developer. The
information is what it is, until someone by their own initiative
improves it.  And, the only way to do so is to learn how it is done.
And, to learn that, you may need to consult other developers - either
Ubuntu Studio devs,  or devs who do work for other flavors.  I can share
what I know, which is that - what I know. And, if I don't know something
I will refer you to someone who I believe knows what I don't know.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Add and remove packages

[Kaj Ailomaa]

On Mon, Jul 25, 2016, at 02:52 PM, Ralf Mardorf wrote:
> I tried to do this since years, but didn't find any explanation on how
> to do this.
> 


Did you ever ask for advice on how to dit?

The meta is built with the help the tool *germinate*. There's a config
file in the source (update.cfg - which needs to be updated for each new
release, and hasn't been yet, but I will fix that on next upload). In
the config file you will find the url for some seed files.
Some of the seeds are the same for all official Ubuntu flavor desktop
metas, some are specific for the flavor. So, in order for us to make
changes the packages audio, video, graphics, etc, we do that in our
seeds - not in the meta itself.
Once the seeds have been changed, the meta is updated.

If you want to create your own custom meta, you can clone our seeds, and
the add your own bzr branch for it in launchpad. Then, also create your
PPA to which you will upload your own custom meta. In the config for the
meta, change the url so it points to your own seed files. Usually, we
only change the codename, but I'm sure you can work out the logic for
the renaming.

Finally, to create the new meta package (once you have changed the
config), you run the update script:

fakeroot debian/rules clean
./update
dput  

If you need more info, let me know. This is quite a sparse explanation,
but I'm guessing you will make sense of it. If not, just let me know.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Yakkety Alpha 2 (for opt-in flavors)

[Kaj Ailomaa]

On Mon, Jul 25, 2016, at 02:48 PM, Ralf Mardorf wrote:
> On Mon, 25 Jul 2016 14:26:55 +0200, Kaj Ailomaa wrote:
> >Get the latest seeds. Make the changes as specified in the wiki
> >(additions, replacements or removals).
> 
> Do you consider
> https://wiki.ubuntu.com/UbuntuStudio/UbuntuStudioPackageMaintenance a
> helpful Wiki?
> 
> Are you kidding?
> 
> If I search for those keywords, one after the other ("additions,
> replacements or removals"), nothing is show.
> 
> Is there another hidden Wiki?
> 

If you were sakrecoer, who that post was meant for, you would know which
page I'm talking about.

Again, if you would like to help, please start from the right end.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Add and remove packages

[Kaj Ailomaa]

On Mon, Jul 25, 2016, at 02:36 PM, Ralf Mardorf wrote:
> On Mon, 25 Jul 2016 13:57:32 +0200, Set Hallstrom wrote:
> >i can't find docs on how to remove or add apps to a package, for
> >example add drumgizmo to ubuntustudio-audio...
> 
> Just edit the "control" file. With an editor add a package to or remove
> it from the "Depends" or "Recommends" list. The "control" file is in
> the "debian" folder.
> 
> Assumed the package should contain the binary, then you need to add
> everything, "Depends", "Recommends", "Description" etc. to the
> "control" file, also you need to add the "Build-Depends". After that
> edit the "rules" file.
> 
> Editing the "rules" could be as easy as ./configure but also very
> tricky.
> 
> I guess you already know this and you've got problems with the tricky
> kind of "rules".
> 
> The problem is that already Debian, but even more Ubuntu follows an
> opposite of the KISS principle. In addition to make it idiotic
> complicated, they also don't provide good documentations. There are
> good reasons that I'm an Arch Linux user, the KISS principle + good
> documentations in English + good documentation in my native language
> and _everybody_ _easily_ could edit Arch Wikis.
> 
> You would be surprised how complicated building a snap is, compared to
> a deb. However, consider to become familiar with both, building debs
> and snaps.
> 
> Regards,
> Ralf
> 


Please don't advice on our packagin Ralf, unless you actually know how
it works :).

Each package has its own logic, and when it comes to metas, it is not as
simple as editing the meta package itself.

If you would like to help out with this in the future, you are free to
do so. Just let us know in that case.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Yakkety Alpha 2 (for opt-in flavors)

[Kaj Ailomaa]

On Mon, Jul 25, 2016, at 11:54 AM, Set Hallstrom wrote:
> On 2016-07-24 23:17, Len Ovens wrote:
> 
> > Ya, I haven't seen anything about packages actually being added
> > removed... maybe it has been done and I missed it. I just meant that if
> > the actual changes to our packages have not been made there is nothing
> > to test.
> 
> Ok, thanks for clarifying, Len. No i haven't seen anything either. In
> fact no one has assigned themselves to a work item.
> https://blueprints.launchpad.net/ubuntu/+spec/ubuntustudio-y-development
> I guess i should have been more alert and pushy...
> 
> I'd love to do a few but someone has to teach me.
> 

Get the latest seeds. Make the changes as specified in the wiki
(additions, replacements or removals).  Either do one bzr commit per
change, or for the whole thing at once by referring to the planned
changes.
The upside with doing one commit per change is that you can throughly
document the reason for that change in the commit log itself, removing
the need to consult any other source. But, I leave that up to the
commiter.

Once the seeds are updated, anyone can just ping me and I can update the
meta package - which is the only package of ours that is not really in a
bzr branch (it's the same with all meta packages, usually).

Once both the seeds and the meta are updated, our next ISO will contain
the changes.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] 16.04.1 RC Testing

[Kaj Ailomaa]

On Tue, Jul 19, 2016, at 11:28 AM, Set Hallstrom wrote:
> Thank you Kaj! Sorry, i got confused with the alpha2 date next week. But
> i've found the schedule for dot releases now [1]
> Although it doesn't announce for when .2 is planned. Is there another
> wiki page for these schedules?
> 
> Indeed, Ross will be away. I can write the release notes.. Although i
> don't find any previous dot release notes for ubuntustudio to base on.
 
There are no previous dot release notes AFAIK. IMO, we can add to the
same release notes. Just add a new header at the bottom for the dot
release for any important changes

> Is it better to edit the Xenial release note page [2], or should it be a
> separate one? I did find a "change summary" for the 14.04.x releases
> [3], maybe a link to the upcoming 16.04.1 change summary and an
> announcement on the website is enough?
> 
> [1] https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule
> [2] https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/UbuntuStudio
> [3] https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/ChangeSummary/14.04.4
> 
> -- 
> Set Hallstrom aka sakrecoer
> 
> -- 
> ubuntu-studio-devel mailing list
> ubuntu-studio-devel@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] 16.04.1 RC Testing

[Kaj Ailomaa]

Let me just remind everyone that 16.04.1 is to be tested before release
on thrusday. If I remember correctly, Ross would is not able to
participate for this one.

ISOs and test cases can be found here
http://iso.qa.ubuntu.com/qatracker/milestones/363/builds.

If you want to help out, make sure to get yourself a launchpad account,
login, and then follow instructions on the link above for testing and
reporting results. Also, please report any bugs you find.

There may be rebuilds, so we may need to redo tests a few times until
Thursday, but consider each ISO a release candidate from now on.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Apologies

[Kaj Ailomaa]

On Thu, Jul 14, 2016, at 10:23 AM, Set Hallstrom wrote:
> Hi all,
> 
> First of all: i am very sorry things went so sour in that discussion. I
> feel i owe everyone an apology: I apologize for letting my own feelings
> take the lead. Kaj, Jimmy and the group as a hole.
> 

I also apologize for the language and attitude that was used on my part.

> Who wants to work with a grumpy extremist with static ways? Not me.
> 
> Many of the blames i formulated were probably aimed at myself: i
> understand this project is not the place to push my freesoftware
> philosophy agenda in 7 steps, to Set us free, hackers, to Set us free. I
> understand i need to leave discussions open for solutions in an
> inclusive way for the benefit of the team and the users, over the
> benefit of my personal integrity. I realize i tend to be triggered by
> the idea of using mainstream media, and i will work on that. While i
> admit still being in the midst of a thought process, for now i can say
> this: i do understand it is up to the community in its entirety; users
> and devels a-like to decide how, when, why and what tools we use. Not up
> to my personal beliefs to determine what is appropriate or not for our
> project. This is our project, not mine.
> 
> I understand i came across as an extremist/purist/grumpycat, but i
> assure you i am not. I am just a pingnu perfectly comfortable with the
> compromises Ubuntu does in order to enable the community to welcome
> users of all levels of computer literacy. If i wasn't comfortable with
> this, i wouldn't be here to begin with. TBH with you and myself, i'm
> still working on understanding what made me allow myself to be stubborn
> and exclusive, and while at the moment i might not be in the brightest
> most secure position in my life away from keyboard, i will work hard to
> address it and to make sure i do not get the community mixed up with my
> moods again.
> 
> I reached out fairly soon the to community council to ask for help but
> they haven't responded yet. In all sincerity, i'm glad they didn't get
> back ASAP, because it let me marinate in my mess for a moment giving me
> time to get back down and reflect upon my own behavior. But i look
> forward to develop contact with them because i think they have
> experiences, tools and ideas we may benefit from. I do not plan to bail
> on you, unless that would be the desire/best-interest of the group and i
> hope you will give me the chance to show you that i can learn from my
> mistakes.
> 
> Hopefully, from here we will be able to move forward to release yet
> another great version of Ubuntu Studio in happy collaboration, without
> leaving any mess under the rugg...
> 
> Yours sincerly,
> 

Thanks for this! 

I at least don't see any reason why the project should not be able to
continue and improve with such an open minded attitude. And, surely, we
are all human and we all make mistakes from time to time.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio policy - Was: Would Ubuntu Studio Team be Interested in Partnering with New England Conservatory?

[Kaj Ailomaa]

On Sun, Jul 10, 2016, at 01:14 PM, Set Hallstrom wrote:
> On 2016-07-10 12:42, Kaj Ailomaa wrote:
> 
> >
> > So, let me say this one last thing about the discussion whether we
> > should or should not use Google Hangouts.
> >
> 
> This has _nothing_ to do with google hangouts. This is about an inactive
> member, spreading confusion to a 3rd part, insulting a fellow
> team-member for the 3rd and last time, and as you can read bellow, using
> team resources to push a freelance IT-consultation agenda for free as in
> beer.
> 

I truly hope no one takes any at all influence from these ludicrous
claims.

And, I would encourage others to share their opinions about this subject
- if not on list, then at least directly to Set, because this has really
gotten way out of hand and I don't feel like I have anything
constructive to add to this "subject" myself.

Though I'm sure I'm partly guilty to it, the wording in some posts here
are not suitable for this list (much of it is in direct violation of
Ubuntu mail list policy, in fact), so we should really think about where
we want to go from here as far as team communication goes.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Would Ubuntu Studio Team be Interested in Partnering with New England Conservatory?

[Kaj Ailomaa]

On Sun, Jul 10, 2016, at 12:13 PM, Set Hallstrom wrote:
> On 2016-07-10 11:48, Kaj Ailomaa wrote:
> > It would evidently exclude one person - the project lead, who is not
> > ready to be flexible enough to meet the needs of the rest of the team.
> 
> I'm affraid it is not up to you to decide. And i find it ironcial that
> you of all past project leads invoke flexibility.
> 
> But sure, set up a vote: Who is the villain that should be fired? Good
> Ubuntu Studio spirit my friend.

Not sure what you are talking about here. So, I will not comment on
this.

Also, though I can agree that I'm overly harsh with my words (as I so
often am), I would still rather focus on the issue at hand. Which is
about Google Hangouts.

So, let me say this one last thing about the discussion whether we
should or should not use Google Hangouts.

1. Ubuntu Studio does not have a policy for/against Google services.
Historically we have used them plenty. So, historically it is something
we use. This means, though it is not in writing we actually do have a
policy for using Google services.
2. It is your personal opinion that we should not use Google Hangouts.
If you prefer not to use them, start a discussion about it, and see who
is for/against. Since, in fact, it is no one who chooses that but the
community.
3. If the community prefers to use Google Hangouts, it would be highly
counterproductive if you did not, particularly if you are a involved in
the work being discussed. And, you already knew coming to Ubuntu Studio
that we are not a political movement against non-free services (where
Google Hangouts can hardly be deemed as a threat against free and open
communication, rather the opposite). So, logic dictates that you should
use the services if the community wishes it.

Jimmy knew this, out of experience. So, naturally, he would suggest
using something like Google Hangouts for live communication.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Would Ubuntu Studio Team be Interested in Partnering with New England Conservatory?

[Kaj Ailomaa]

On Sun, Jul 10, 2016, at 11:34 AM, Set Hallstrom wrote:
> On 2016-07-10 11:10, Kaj Ailomaa wrote:
> > Just want to mention a couple of things.
> > 
> > The way this communication was handled here has led to that Jimmy left
> > our team, which is a bad thing (Jimmy, me and Len are the oldest active
> > members of this community, currently).
> > 
> > Jimmy takes an initiative, but instead of being encouraged he is stopped
> > by something clearly unimportant in this particular situation.
> 
> Ok, he took an initiative, and formulated it as an initiative on behalf
> of the group. It was a miscommunication, ok, we get that now.
> 
> Why not just correct the shot instead of tacitly call a fellow team-mate
> narrowminded contraproductive.

Perhaps your own words describe it best. Or, if I rewrite it to
"narrowmindedly counterproductive".

At least, it is clear that you are very stubborn and not ready to back
one inch from your original position - which in itself is not the Ubuntu
Studio position, but your own personal position. You don't actually
promote discussion. Just that you are prepared to fire more words at it,
if someone is ready to listen to them - since you clearly are not ready
to reevaluate your role in this project and what the project is actually
about.

> 
> > 
> > Using Google Hangouts for live communication would in no way mean Ubuntu
> > Studio is promoting Google - just that a few people would be using a
> > very simple solution for live communication. If Set feels other tools
> > would be better, and simple enough to set up, he can always work out the
> > solution and present it as an alternative, once he has done so.
> 
> No, it was jimmy's initiative. If HE wants to help with video HE should
> set up a sollution for video conference. Using hangouts or skype would
> exclude major part of the team from taking part.

It would evidently exclude one person - the project lead, who is not
ready to be flexible enough to meet the needs of the rest of the team.

> 
> And like i said MANY times, i don't care what jimmy does in his
> freetime. However, being a member of the team, if jimmy writes "we" to a
> 3rd part in the context of this list then he has to assume to be read as
> taking an initiative on behlaf of the group. This is basic
> communciation. Had that mail of his been sent off-list directly to Devin
> nothing of this would have been necessary. There was already clear signs
> of confusion in the discussion regarding what the team could do for NEC
> or not, i felt Jimmy's freelance shot had the potential to build uppon
> that confusion and corrected that.
> 
> Believe it or not, i have regards concerning Jimmy. I do enjoy him as a
> person. But this drama number has severely affected me personaly and the
> way i perceive him. Trying to look back i wonder what he has done, but i
> sure know it is the 3rd time he calls me out for being a conservative
> freesoftware extremist. And Last time someone slammed the door on me
> over a simple disagreement, i was a teenager.
> 
> > 
> > Our work is to promote Ubuntu Studio, which in itself is not 100% free
> > software, so having zero tolerance to non-free software in combination
> > with Ubuntu Studio is hypocrisy. It is not up to us who uses free
> > software, and we couldn't provide a 100% free software solution anyway
> > already because of the kernel. If someone wants to use a completely free
> > solution Ubuntu Studio is not the right choice - neither for the user or
> > the developer. It's just an impossibility.
> > That said, we do promote free software. And we do that through Ubuntu
> > Studio, which is where the focus should be. Using non free services in
> > order to reach as many people as possible is unfortunate, but it is also
> > the best way to do that in this moment. Not using those services will
> > just add barriers where there already are too many barriers, in order
> > for people to discover the free software world.
> > 
> > We are not crusading against Google, Facebook, or any other such
> > services. We are not *against* non-free software, in fact. But, we are
> > *for* free software. It's a big difference.
> 
> Exactly, we are FOR free software. That means we should first look for
> freesoftware alternatives. If you come with a plan, than make it happen.
> 

There was already a good plan. But, there was only one person in the
team who was against it, and it was you.

> Now i understand Jimmy did NOT speak on behalf of the group. Why is
> that? Maybe he hasn't felt like a member for a long time? I don't know,
> i can just speculate. His departue sure is a loss, and i wish things
> would have worked

Re: [ubuntu-studio-devel] Would Ubuntu Studio Team be Interested in Partnering with New England Conservatory?

[Kaj Ailomaa]

On Sun, Jul 10, 2016, at 11:10 AM, Kaj Ailomaa wrote:
> Just want to mention a couple of things.
> 
> The way this communication was handled here has led to that Jimmy left
> our team, which is a bad thing (Jimmy, me and Len are the oldest active
> members of this community, currently).
> 

..though I'm sure Jimmy has probably pondered about quitting before (I
can't really speak for Jimmy), and I should not put the entire blame on
this discussion.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Would Ubuntu Studio Team be Interested in Partnering with New England Conservatory?

[Kaj Ailomaa]

Just want to mention a couple of things.

The way this communication was handled here has led to that Jimmy left
our team, which is a bad thing (Jimmy, me and Len are the oldest active
members of this community, currently).

Jimmy takes an initiative, but instead of being encouraged he is stopped
by something clearly unimportant in this particular situation.

Using Google Hangouts for live communication would in no way mean Ubuntu
Studio is promoting Google - just that a few people would be using a
very simple solution for live communication. If Set feels other tools
would be better, and simple enough to set up, he can always work out the
solution and present it as an alternative, once he has done so.

Our work is to promote Ubuntu Studio, which in itself is not 100% free
software, so having zero tolerance to non-free software in combination
with Ubuntu Studio is hypocrisy. It is not up to us who uses free
software, and we couldn't provide a 100% free software solution anyway
already because of the kernel. If someone wants to use a completely free
solution Ubuntu Studio is not the right choice - neither for the user or
the developer. It's just an impossibility.
That said, we do promote free software. And we do that through Ubuntu
Studio, which is where the focus should be. Using non free services in
order to reach as many people as possible is unfortunate, but it is also
the best way to do that in this moment. Not using those services will
just add barriers where there already are too many barriers, in order
for people to discover the free software world.

We are not crusading against Google, Facebook, or any other such
services. We are not *against* non-free software, in fact. But, we are
*for* free software. It's a big difference.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Leaving the community

[Kaj Ailomaa]

On Sat, Jul 9, 2016, at 04:56 PM, Jimmy Sjölund wrote:
> Hi,
> 
> as most of you already know I've been having a hard time to put in much
> time in the project. It's more or less some hit'n'run the last years. In
> that aspect and others which I will not dwell upon I've decided to leave
> the community. It's been fun and educational. I've met great people both
> in real life and online!
> 
> Other than that, take care! And you know where to find me if you want to
> stay in touch.
> 
> Cheers
> Jimmy

It's been great to have you, Jimmy! You've always been a positive force
for this project!

See you around :)

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Backports

[Kaj Ailomaa]

On Fri, May 27, 2016, at 12:16 PM, Set Sakrecoer wrote:
> I read zequence was talking on IRC about finding a good way to warn our 
> users of the consequences of backports, since it appears backports are 
> able to break things for people having a project in the making. Hence 
> please also consider this email as an invitation to discuss how we 
> communicate this change to our user base.
> 
> Yours,
> -- 
> Set aka ~sakrecoer
> 

Yes, I'm planning on adding a one-time popup information for
ubuntustudio-controls to be run at login, but that will only be helping
those who already have it installed (which all Ubuntu Studio users will
have, unless they uninstalled it).

Since Ubuntu users aren't used to backports for their multimedia
applications, it's important that they know the risks, and that they can
deselect backports.

We should spread this information quite soon on our web site and social
channels, as well as the user mail list.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] package proposals - publishing

[Kaj Ailomaa]

On Fri, May 6, 2016, at 04:02 PM, Len Ovens wrote:
> On Fri, 6 May 2016, Kaj Ailomaa wrote:
> 
> > For now, publishing seems the best fit, though in fact there is no
> > correct meta for it yet.
> 
> Now that you bring it up... it seems that there was a sense that:
> 
> Publishing - means the distribution of finished product, which might be 
> video,audio,graphic or book or whatever.
> 
> Writing - means writing... making books, or other written works.
> 
> When the pubishing metea was first envisioned, it was thought to be
> making 
> books. But this is because most of us at the time were audio-centric. 
> (also because we had very few of us too)
> 
> As most of these would end up in "Office", perhaps rather than trying to 
> massage the menu to split these things out of office, we could just
> change 
> the name of the Office sub menu to something that indicates more writing 
> tools are included as we have with "Graphics". Perhaps "Office and
> Writing 
> tools" or something. Also Give it one of our own style icons.
> 

The metas currently do correlate with the menu, but it's just
coincidence at this point. The menu should use freedesktop
categorization, while the metas are more workflow focused in some way.
Writing is a workflow, but the tool types used are for Office or
Publishing (publishing is a subcategory for both graphics and office).

So, the name of the meta doesn't have to correlate with names in the
meta. ubuntustudio-writing would not add a menu item called "writing",
but I kind of like your suggestions renaming the Office category could
be renamed to Office and Writing, so worth looking into IMO.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] package proposals - publishing

[Kaj Ailomaa]

On Fri, May 6, 2016, at 09:45 AM, Jimmy Sjölund wrote:
> In terms of writing software (and this is just out of curiosity) why
> plume over manuskript? and either way I personally like the idea. There
> are other applications besides Plume Creator and Manuskript but from my
> tests Plume Creator was then and still seems to be the most mature and
> already in the Debian repos. The two main developers are in contact
> though so perhaps there might be some collaboration in the future.
> Plume Creator is being rewritten for a new version but as there are only
> a few developers it might take some time. It would be great to include
> the new version of course, but the current stable version has been used
> to write several books by different authors.
> 
> /Jimmy


I added it as a suggestion to the publishing meta.

I remember now more clearly the arguments for a "writing" meta.
"writing" is not a freedesktop category - applications inside that
workflow would end up under "Office", but it is absolutely a digital art
form nowadays and could perhaps be granted its own meta, which would be
separate from the other metas audio, graphics and video. I'm working on
something for that right now, and will present it later.

For now, publishing seems the best fit, though in fact there is no
correct meta for it yet.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] package proposals - publishing

[Kaj Ailomaa]

On Thu, May 5, 2016, at 11:11 PM, Jimmy Sjölund wrote:
> On Thu, May 5, 2016 at 22:39, autumna <'autu...@gmail.com'> wrote:
> I added 2 more software packages to the wiki page under "graphics" for
> the publishing related workflows.
> 
> (add) calibre: Calibre is a book managing software, but it also happens
> to have a well designed epub editor. To my knowledge there currently
> isn't any software available on ubuntu studio to make or edit ebooks.
> 
> I've only done a quick glance on the homepage and didn't get a feel for
> what the features are. Is it a writing software as well as publishing and
> converting to ebook format, or is it just the publishing part? We
> discussed before 15.10 about adding a writing software and where to put
> it. I was looking into a couple of candidates where my suggestion was
> Plume Creator. It was too late to include them and I had too little time
> to contribute to 16.04 and the writing stuff was left on hold.
> (add) pdf-shuffler: There is currently no way to rearrange an existing
> pdf, or merge two pdfs without importing the whole thing into
> libreoffice or graphics software which can mess up formatting. Useful
> when you are asked to glue the application form and your portfolio into
> one file.
> I've only done this in terminal but understand it would be helpful for
> many users. I get to do it for my GF as well as the process to do it in a
> Mac is really really bad...
> 
> 

We are still using the publishing meta, and there have been no plans to
remove it, so I've adjusted the two recent proposals to be incuded in
the publishing meta, which is where they belong
https://wiki.ubuntu.com/UbuntuStudio/PackageSelection/yakkety.

Publishing is a standardized freedesktop sub category of graphics, so it
makes total sense to have it, as is, in the menu too. Though our metas
don't necessarily need to reflect on freedesktop categories, it is
actually what they are doing currently (photography is also a sub
category of graphics).

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Backports for Ubuntu Studio Xenial

[Kaj Ailomaa]

On Tue, May 3, 2016, at 06:33 PM, Len Ovens wrote:
> On Tue, 3 May 2016, Ross Gammon wrote:
> 
> > On 05/03/2016 08:01 AM, Kaj Ailomaa wrote:
> >> We could in fact do a round of backports for trusty, as it is still what
> >> many people uses.
> >>
> >
> > I will add the table. We could try and backport all the way to Trusty
> > from Yakkety via Xenial. But this gets harder if the dependencies have
> > changed too much (or not even available).
> >
> > We could start on Trusty from Xenial right away of the version is still
> > the same as Yakkety. Trusty users are probably more in need at the
> > moment than the early Xenial adopters :-)
> 
> My advice is against that. It is true there is not anything I know for X, 
> but anyone staying with T is probably doing so because they wish to
> finish 
> a project with the version of SW that is there. (for example ardour 2 has 
> a set of bugs that affect the sound of things mixed there, A3/4 will be 
> able to use those sessions, but they will sound different and may need 
> remixing) EQ10Q in X is not compatable with T (I tried :) but EQ10Q from
> W 
> is ok. X is using a different version of GCC (5 not 4) and applications 
> that use plugins have to use the same version for both application and 
> plugin. (this is why EQ10Q beta 5.1 will work in T but 2.0 will not BTW)
> 
> The only two packages That may be worth doing are jackd and calf plugins 
> (provided calf can be done with GCC4), qjackctl is not compatable with
> lib 
> versions in T. However, anyone who does audio with Jack has already 
> figured out the right workaround for jack and knows to avoid calf reverb.
> 
> Maybe things are different in graphics or video though.

Backports is not for fixing bugs. That should be done as SRUs. If
there's a calf bug that can blow speakers, please at least let us know
what the bug is so someone can prepare a patch and do a SRU.

Backports are something the user can choose. But, our users are not used
to them. So, I could imagine us adding small info thing for
-default-settings which lets the user know that backports are coming,
and let them have the ability to deselect backports, if they do not wish
to have them. Also, how to undo updates, if they were done by mistakes.
We probably need to educate our users a bit on this.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Backports for Ubuntu Studio Xenial

[Kaj Ailomaa]

On Mon, May 2, 2016, at 10:23 PM, Kaj Ailomaa wrote:

> Every now and then there may an important release that could be
> important to backport in advance, but otherwise it may be hard to do
> quality control on packages in the dev release if we have no
> confirmation if they have been tested at all.
> 

..of course, the backporter(s) need to do testing either way, and I
suppose the test cases are useful for this.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Backports for Ubuntu Studio Xenial

[Kaj Ailomaa]

On Mon, May 2, 2016, at 10:04 PM, Ross Gammon wrote:
> Hi All,
> 
> I am hoping to maintain backports to Xenial for the 10 packages we
> decided were important enough to have in the "Mandatory" testsuite on
> the the Package Tracker.
> 
> They are listed here:
> https://wiki.ubuntu.com/UbuntuStudio/BackportsList
> 
> I am not adverse to adding other packages to the backport list as long
> as we don't go crazy, and they are not difficult to backport.
> 
> The backporting instructions (linked on that page) are a little out of
> date, so if you would like to help out then let me know. I will
> prioritise updating the instructions.
> 
> Regards,
> 
> Ross
> 

I would also like to participate in this, if not backport request, then
at least testing when the time comes. Was thinking of when would be the
good time to do those, and at least every 6 months is a good time to do
the whole list - when the next release is out.

Every now and then there may an important release that could be
important to backport in advance, but otherwise it may be hard to do
quality control on packages in the dev release if we have no
confirmation if they have been tested at all.

What kind of schedule did you have in mind?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] default screen recorder WAS:Re: Package Selection for Yakketi Yak

[Kaj Ailomaa]

On Mon, Apr 25, 2016, at 07:53 PM, lukefro...@hushmail.com wrote:
> If Recordmydesktop is dropped it should be replaced. I have issues with
> it but
> still use it, as the alternative is to take the time to set up a video
> camera aligned
> with the screen. 
> 

vokoscreen is the proposed alternative. Any opinions about that?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] libgsl0ldbl, pd-l2ork

[Kaj Ailomaa]

On Mon, Apr 25, 2016, at 12:00 AM, Gerhard Lang wrote:
> Compilation of pd-l2ork-x86_64-20160227.deb from git works out of the 
> box, but installation gives erros: missing libgsl0ldbl. Tried to install 
> libgsl0ldbl_1.16+dfsg-4_amd64.deb faild by incompatibility with libgsl2. 
> Any suggestions?
> Cudos for your great work, I cherish ubuntustudio since 7.04
> Best regards
> Gerhard
> 

I've had problems with pd-l2ork installations myself, and it is mainly
because of bad packaging. Probably the package is only installable on
certain Ubuntu releases. You should inform the packagers about this
problem, and specifically let them know on which release you are unable
to install it, and hopefully they can fix it soon.

That's unless you are willing to find the fix by looking at the
problematic dependencies, and see if you can use installable
dependencies (like libgsl2) just as well, and then rebuild the package
with the fixes to the packaging.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] 16.04 Release Candidate Testing - for release Thursday 21st

[Kaj Ailomaa]

On Wed, Apr 20, 2016, at 10:41 PM, Thomas Pfundt wrote:

>however I noticed that some of the titles in the slideshow that
> are displayed while installing received line breaks, because apparently
> the text is too long to be displayed in one line. The problem with this
> is that the field in which these titles are placed is too small to
> display two lines with appropriate spacing, so the lines are
> overlapping, making the titles extremely awkward to read. I also have to
> mention that this happened while installing in the German language,
> which is my native language, but I could imagine this happening with
> other languages as well, if words tend to be a little longer. When
> installing in English, I did not not encounter anything like this.
> 

I've tried English, Italian, German, French and Swedish so far, very
quickly. But, I can't spot a problem. Where exactly does this happen and
which language?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] 16.04 Release Candidate Testing - for release Thursday 21st

[Kaj Ailomaa]

On Thu, Apr 21, 2016, at 02:30 PM, Thomas Pfundt wrote:
> Hi Len,
> 
> thanks for your reply.
> 
> > Thankyou for testing in other languages. I have not noticed this on my 
> > system, but that is because I can only read english.
> 
> Well, as far as languages go, I could only test Italian and maybe French
> in terms of spelling, but I guess it would just generally be safe to
> make sure that the texts fit the content boxes even if they become a
> little longer than the English version. It's a bit unfortunate that you
> have to fully start an installation in order to check this


You could get the source code, and try different languages there
directly.
You need bazaar and zenity, so first:

sudo apt-get install bzr zenity

Then, get the source code and try the slideshow in Italian:

bzr branch lp:ubuqity-slideshow-ubuntu
cd ubiquity-slideshow-ubuntu
./test-slideshow.sh ubuntustudio it

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Announcing new project leader for Ubuntu Studio

[Kaj Ailomaa]

As 16.04 Xenial Xerus is just about to be released, my duties as project
lead have to come to an end and it is time to announce the new project
leader for Ubuntu Studio - Set Hallström (a.k.a sakrecoer) - who some of
you might remember was the only candidate during our first ever election
process earlier this year - but a very good one at that!

During the last 6 months I'm happy to have seen the the team of
contributors grow (something I was almost giving up hope for in the
past). And, we've already succeeded in doing some new and fantastic
things the recent months. So, good sign for the future!

cfhowlett took the initiative for the community wallpaper competition,
something we had wanted to do for years, it seems - and it was a great
success.
Len is as always a great resource on the technical side of things -
following up bugs and fixing them, as well as contributing to some of
the user interface side of things (he is the author of ubuntustudio-menu
and has had an important influence on many of our packages over the
years). Ross is getting more and more adept in packaging, and also helps
fix many bugs. Ross has also been very competent in advancing our
testing routines (something that many have contributed to during this
cycle by writing test cases) and taking care of our milestone releases
as our testing lead and release manager. Jimmy has had less time lately,
but is always around the corner, and helping out here and there. We had
a guy who helped us out intensely during winter, (was it Noklam)? He had
some computer problems, but perhaps he will show up again at a later
date? krytarik has become more involved lately, and has helped clean up
some of our packages, as well as fixing some bugs! flocculant is as
always a great support and a fountain of knowledge, particularly when it
comes to testing, and many of us have him to thank for our knowledge.
knome has been essential to us in many ways. He is the author of our
current website theme, and is also the author of the next one we will be
using. But, he is also a supportive source in other areas - as are many
of the Xubuntu developers, who we have come to know over the years, such
as Unit193! Just a few days ago, autumna appeared and quickly became
included in the development of the website and documentation for Ubuntu
Studio. And, of course, sakrecoer, our new project lead, who has put a
lot of effort in learning what is needed in order to carry on the
maintenance and development of this fine distro.
Apart from the mentioned, there are so many who contribute - other
Ubuntu developers (and there are many), users at this mail list and
other forums, Canonical employees (who were instrumental in helping to
make linux-lowlatency available to users - and of course the original
author of the kernel, Alessio Bogani), micahg who was a great support
when we still needed sponsors for our packages, madeinkobaia who did the
artwork for us at around 14.04, and also many people who have just not
been active in the later months or years - the list is long and I will
forget to name everyone, and for that I'm sorry (but this is not an
Oscars speech anyway, so I hope you will forgive me).
But, yes, it is quite a thriving community after all!

I will not be disappearing after Thursday, by any means. Packages still
need to be uploaded, and I will always be available to answer any
questions on both the mail list as well as on IRC. There are a few
things I would like to help with still, like the next website theming
and content organization, and I absolutely am going to make a few video
tutorials, something that really needs to happen now.
But, I will be spending a lot less time on overall development, and
after three years as project lead, it's kind of nice not having the
responsibility anymore. I'm probably not the best people person either
at all times, so I see a lot of benefits when someone like Set takes
over!

With that, I hand the torch (which is burning quite bright at the
moment) over to Set, which he will carry until the next election, and
wish the team good luck in the future with all the fun that flavor
development offers!

/Kaj Ailomaa - musician and author of Oscar speeches

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] One week until xenial final relase "RecordMyDesktop"

[Kaj Ailomaa]

On Sat, Apr 16, 2016, at 11:29 AM, Grant Frank Burton wrote:
> RecordMyDesktop works but not very good. It looks a clunker, takes a long
> time to process the video and the quality is not very good.
> 
> Kazam is a much better program but when I installed it, I don't get
> to
> option to remove it, I only can install it again. I can take it out with
> a
> terminal but not from the software center window.

I would agree that we should probably use another program for desktop
recording. I may have suggestions there too, but we don't do any changes
in our application selection this late in the game, unless there's a
critical bug, so this will have to wait until the next development cycle
(which is quite soon).

If you are unable to install applications with Software, please report a
bug about that. The package name is gnome-software, so in a terminal,
you do:

ubuntu-bug gnome-software

Thanks for putting some attention on this

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] ubuntu-bug and system logs WAS:Re: One week until xenial final relase, please help testing

[Kaj Ailomaa]

On Fri, Apr 15, 2016, at 07:33 PM, Ralf Mardorf wrote:
> On Fri, 15 Apr 2016 19:23:18 +0200, Kaj Ailomaa wrote:
> >On Fri, Apr 15, 2016, at 07:20 PM, Ralf Mardorf wrote:
> >> There are still issues regarding log files. Assumed somebody doesn't
> >> use DHCP, but e.g. PPPoE, the password could be provided in plain
> >> text by a log file and even if you don't dial up, be careful when
> >> filing a bug against a MUA.
> >>   
> >
> >To be a little bit ironical, but yet correct.
> >
> >Please, file a bug.
> 
> No hard feelings!
> 
> It's simply reality that there are situations, when not "cleaning" log
> files could be dangerous. While an Ardour related log file unlikely is
> critical, nobody knows what amount of systemd log file is transmitted.
> Do you give that log files the shirt off your back?
> 

The motive and the goal behind ubuntu-bug is to make bug reporting
easier for the bug fixer, which is a perspective hard to understand
unless you are the bug fixer.
The bug fixer does not need to know your passwords or your credit card
information to fix the bug - just what caused the bug, and under which
circumstances- which package, which release, which kernel, which system,
basically.
So, if any unintentional and sensitive information does appear -  that
is a problem, and as was stated before, launchpad already takes care of
a deal of that, but if you find any more problems, please do tell.

Why systemd, specifically?

As trivia:
I remember when I attended the Debian Conference in Switzerland last,
and Lennart told us how pretty much everyone would be using systemd
pretty soon. Some laughed at the way he said it, perhaps, or for some
other reason. But, the truth is - both Debian and Ubuntu started using
systemd after that. And, probably for good reason. 
Me, personally - I don't care so much which init system we use, because
I wouldn't be able to tell you why one is better than the other. But, if
there are concerns, or errors, or bugs, those should always be brought
up and dealt with.

Hard feeling?
This is not the place for that type of discussion. This is a public mail
list for Ubuntu Studio development, where we do our best to develop the
best free OS for multimedia production in the world.
For Ubuntu Studio to be free, it needs special scrutiny. It is important
that we do things right. And everyone should feel welcome in helping to
achieve that. It is we, here, who make that happen. No one else. It's up
to us. Like it or not - you are one of us Ralf, even though you choose
to have a more distant position.

No, I'm not going to start looking for every single bit that is wrong in
this myriad of bits. That is simply not very practical. Instead, I'm
going to urge anyone who did experience a bit that was wrong to report a
bug for it, so that the right people can become aware of it. And, the
best option I know right now is ubuntu-bug.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] One week until xenial final relase, please help testing

[Kaj Ailomaa]

On Fri, Apr 15, 2016, at 07:20 PM, Ralf Mardorf wrote:
> There are still issues regarding log files. Assumed somebody doesn't
> use DHCP, but e.g. PPPoE, the password could be provided in plain text
> by a log file and even if you don't dial up, be careful when filing a
> bug against a MUA.
> 

To be a little bit ironical, but yet correct.

Please, file a bug.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] One week until xenial final relase, please help testing

[Kaj Ailomaa]

On Fri, Apr 15, 2016, at 05:21 PM, Ralf Mardorf wrote:
> IMHO nobody should use 'ubuntu-bug ardour' as suggested by Kaj, but
> using a browser and logging in and reporting bugs is a good idea, in
> addition post links to the list.
> 

Let's just make it clear that this is Ralfs personal opinion, and he is
not a Ubuntu Studio developer.

We, the Ubuntu Studio developers would like you to report the bug using
ubuntu-bug.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] One week until xenial final relase, please help testing

[Kaj Ailomaa]

On Fri, Apr 15, 2016, at 05:33 PM, Kaj Ailomaa wrote:
> On Fri, Apr 15, 2016, at 05:21 PM, Ralf Mardorf wrote:
> > IMHO nobody should use 'ubuntu-bug ardour' as suggested by Kaj, but
> > using a browser and logging in and reporting bugs is a good idea, in
> > addition post links to the list.
> > 
> 
> Let's just make it clear that this is Ralfs personal opinion, and he is
> not a Ubuntu Studio developer.
> 
> We, the Ubuntu Studio developers would like you to report the bug using
> ubuntu-bug.
> 


..and also, do not post links to bugs here at the mail list unless you
have a good reason to. There's a reason launchpad exists.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] One week until xenial final relase, please help testing

[Kaj Ailomaa]

On Fri, Apr 15, 2016, at 03:23 PM, Grant Frank Burton wrote:
> Greetings all
> 
> I downloaded xenial  and installed it
> 
> Was looking pretty good till I got to Ardour  Lot of things wrong.
> 
> Is anyone working on this?
> 

None of us are specifically working on any application, but if you have
found any specific bugs, please do report them.

Get a launchpad account at http://launchpad.net, then in a terminal do:
ubuntu-bug ardour

If there are any severe bugs, we should fix them ASAP, but first - a bug
report.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] One week until xenial final relase, please help testing

[Kaj Ailomaa]

On Wed, Apr 13, 2016, at 05:39 PM, Thomas Pfundt wrote:
> Hello Kaj,
> 
> I just read your mail on the 16.04 release testing. I started fully
> using Ubuntu Studio at the end of last year (been a vanilla Ubuntu user
> next to Windows for around two years before).
> 
> First of all, I would like to personally thank you and the others for
> your work on this great system. I'm so happy with how well it works,
> audio performance is much better than with Windows and everything is so
> configurable and responsive, it's really cool!
> 
> Anyway, I thought I'd join the development channel and see if I was able
> to help out in some way, since 16.04 is kind of an important release for
> me and I plan on using this system for a while now. Unfortunately, I've
> been rather busy with the job and also at home lately, so I haven't had
> very much time.
> 
> I want to download and test the new release right now, but I have got
> two main questions about that:
> 
> Will it be fine to test the live system (or: fully installed on a USB
> drive)? I'm asking because I can't reinstall my current system at the
> moment and I don't have a spare hard drive at hand, or would that not be
> sufficient for testing?
> 

Like Jimmy said, doing a virtual installation is fine (something like
Virtualbox). But, for live processing (both audio and video), you will
need to use actual hardware. And for that, booting the live ISO works,
all though there's an extra dimension to everything once you install and
have user settings for stuff.
So, I guess you have those two options 1) use something like Virtualbox
for an actual installation 2) boot the live ISO on a real machine to
test applications that require more processing power.

> And: How do I report bugs, should I encounter any? Is it enough to
> submit an automatic report as soon as an error window shows up or do I
> have to manually file some kind of bug report (I have never done this
> before).
> 


In short, get yourself a launchpad account at http://launchpad.net, and
when you find a bug, use a terminal. Input the command(replace
 with the name of the package you want to report against):

ubuntu-bug 

Knowing which package to report against can be difficult. This section
deals a bit with that -
https://wiki.ubuntu.com/UbuntuStudio/Testing/ISOTesting#If_you_find_bugs.
But,  that page is mainly purposed for how to do the final smoke test of
the ISO for each milestone -  when we report our results at
http://iso.qa.ubunty.com. So, just skip any notions about that, for now,
and focus on the bug reporting part - if you find any.

Thanks for showing interest, and hope to see you around more in the
future. Testing is a good way to get involved in the development
process, which is something that anyone can participate in.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] One week until xenial final relase, please help testing

[Kaj Ailomaa]

Just a reminder to everyone that we only have one week until release, so
please help testing the ISO. As always - if you find bugs, please report
them!

You can find the latest ISOs at
http://cdimage.ubuntu.com/ubuntustudio/dvd/current/

ubiquity (the installer) is still missing a few of our updates, but
otherwise, not much will change before release.

There will probably be no specific release candidate until closer to
release, so no need to use http//iso.qa.ubuntu.com to report test
results, unless you really want to. We will however do our smoke testing
and report results there during the one day or so before release.

This is just a short reminder, so no specific instructions here for
those who are new. Let us know if you want to help, and we'll help you
on your way.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Missing applications: Audacious & Shotwell

[Kaj Ailomaa]

On Sat, Apr 2, 2016, at 05:46 PM, Ross Gammon wrote:
> Hi All,
> 
> Prompted by a comment by Len on IRC (about Audacious), I did a quick
> check for obvious packages that might have dropped of our DVD without a
> conscious action.
> 
> When producing the Package QA Tracker, I prioritised the Test Cases
> based on what was in our menu at the time.
> 
> The only one that seems to have dropped off is Audacious:
> https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1565040
> 
> And then when checking the bugs for Len's Synaptic bug, I discovered a
> bug related to Shotwell:
> https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1189250
> 
> Is there any reason why I shouldn't add these to to our seeds? I don't
> want to randomly add packages without thinking about it first.

I think all DEs have a media player that comes with the DE. So, I don't
see why audacious absolutely needs to be included.
Is Shotwell intresting for graphics?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ubuntustudio-screensaver

[Kaj Ailomaa]

On Fri, Apr 1, 2016, at 03:03 PM, Set Hallstrom wrote:
> On 2016-04-01 13:24, Kaj Ailomaa wrote:
> > We aren't seeding ubuntustudio-screensaver, which means it's not
> > installed in Ubuntu Studio. I haven't looked at the package at all, but
> > I'm pretty sure it's one screensaver with some form of Ubuntu Studio
> > motive.
> 
> I'm not sure i understand this, in 14.04 there are quite a few
> screen-savers available... As far as i want to remember, i found the
> usual "screensaver" entry in settings when i tested the beta for 16.04
> and they seemed to work...?
> 

Those are not in the package ubuntustudio-screensaver. We aren't
supplying the package ubuntustudio-screensaver.
Whatever screensavers you have there are installed from another package.

If something is not seeded, it means no one has it in their seeds. And,
as I already explained - we do not include it in our installation.

You are assuming things without actually knowing any facts. Please check
the package for yourself, and how it is used.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ubuntustudio-screensaver

[Kaj Ailomaa]

On Fri, Apr 1, 2016, at 11:57 AM, Set Hallstrom wrote:
> On 2016-03-31 22:24, Kaj Ailomaa wrote:
> > On Thu, Mar 31, 2016, at 08:17 PM, Ross Gammon wrote:
> >> Hi All,
> >>
> >> Whilst looking at something else I came across the
> >> ubuntustudio-screensaver package. It has not been touched for a long
> >> time, and is no longer seeded.
> >>
> >> Knowing that screensavers are not the "in thing" any more (most screens
> >> just go blank these days), I decided to install it to see what it looked
> >> like.
> >>
> >> It pulls in gnome-screensaver, but nothing else visible seems to happen
> >> and there is no settings utility appearing in the menu.
> >>
> >> Running "gnome-screensaver --debug" prints some warning about no
> >> .session being registered or something. Not wanting to spend any more
> >> time on it, I thought I would ask here:
> >> 1. Is there some setup step I am missing?
> >> 2. Does the package need work, or the X-defaults need something set up,
> >> to help any users installing it?
> >> 3. Should we just remove it from the archive?
> >>
> >> Cheers,
> >>
> >> Ross
> >>
> > 
> > We should probably drop that package, as well as ubuntustudio-sounds.
> > They are pretty much abandoned. Might as well do it now, before this
> > release.
> > 
> 
> This emails comes as strange to me; when i installed the dev
> environment, i noticed a considerably higher amount of screen-savers
> than in the LTS, much of which are pretty awesome!
> 
> Now i don't get me wrong, i'm in favor of dropping whatever is
> superfluous and broken. But i for one would be sad not to have any
> screen-saver at all, specifically a diaporama of my photo-library. :)
> 
> 

We aren't seeding ubuntustudio-screensaver, which means it's not
installed in Ubuntu Studio. I haven't looked at the package at all, but
I'm pretty sure it's one screensaver with some form of Ubuntu Studio
motive.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ubuntustudio-screensaver

[Kaj Ailomaa]

On Thu, Mar 31, 2016, at 08:17 PM, Ross Gammon wrote:
> Hi All,
> 
> Whilst looking at something else I came across the
> ubuntustudio-screensaver package. It has not been touched for a long
> time, and is no longer seeded.
> 
> Knowing that screensavers are not the "in thing" any more (most screens
> just go blank these days), I decided to install it to see what it looked
> like.
> 
> It pulls in gnome-screensaver, but nothing else visible seems to happen
> and there is no settings utility appearing in the menu.
> 
> Running "gnome-screensaver --debug" prints some warning about no
> .session being registered or something. Not wanting to spend any more
> time on it, I thought I would ask here:
> 1. Is there some setup step I am missing?
> 2. Does the package need work, or the X-defaults need something set up,
> to help any users installing it?
> 3. Should we just remove it from the archive?
> 
> Cheers,
> 
> Ross
> 

We should probably drop that package, as well as ubuntustudio-sounds.
They are pretty much abandoned. Might as well do it now, before this
release.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] New developer in the team - krytarik

[Kaj Ailomaa]

krytarik has been helping out with development recently, and I invited
him to become a dev team member, since he seems to know his way around
packaging, and he accepted. So, please welcome krytarik to the team of
developers!

https://launchpad.net/~krytarik

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] DVD authoring software

[Kaj Ailomaa]

On Sat, Mar 12, 2016, at 12:25 AM, Set Hallstrom wrote:
> > On 2016-03-11 22:55, Len Ovens wrote:
> >> Basically the same info there. devede looks like the the best choice at
> >> this point. (best as in at least it seems includable)
> >> 
> >> Comments?
> 
> 
> I installed both devede and bombono-dvd
> 
> sudo apt-get install devede
> gave me a boring but very functional and faithfully working DVD burner.
> Basic edition is there, i can chose colors, position and fonts for text,
> png (only png) for background after a little fiddling, i made that DVD
> my own. Although
> 
> sudo apt-get install bombono-dvd
> gave me a good looking piece of software, i get the impression i might
> do more, but at some point, my computer freezes to the point where not
> even ctrl+alt+F2 will do. (Obviously, my computer being, well,
> /my computer/, all i'm saying here is my _personal_ experience was
> frustrating.)
> 
> So, I vote for devede.
> 

devede looks good to me. I'll replace dvdstyler with devede as we seem
to lean on that choice. We can still change it, if there is a strong
opinion for that.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] ubuntustudio.org email addresses for team members

[Kaj Ailomaa]

I would like to set up some new email addresses for new team members.

sacrecoer
retail-0 (Ross)
cfhowlett

Am I missing someone?

I will also send emails directly to all parties asking which username
they would like, and where the @ubuntustudio.org email should point to
(it's a redirect), and then create a ticket at rt.ubuntu.com to ask
Canonical admins to set this up.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Xenial - Beta 1 ISO Testing

[Kaj Ailomaa]

On Thu, Feb 25, 2016, at 04:55 PM, Ross Gammon wrote:
> On 02/25/2016 01:20 PM, Kaj Ailomaa wrote:
> > the most important part this time was application testing.
> 
> Parole popped up on the tracker at one point as having a crash. 
> Launchpad reports other crashes as well - we should look at that one
> first?
> 

I don't usually regard media players as our field of expertise, even if
they are absolutely needed. And, I figure there are people interested in
fixing those. But, I think that's up to you.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Xenial - Beta 1 ISO Testing

[Kaj Ailomaa]

Beta 1 will not be representative of the final release of Ubuntu Studio,
however, the most important part this time was application testing.

Even after release of Beta 1, please do help with application testing,
and report any bugs you may find, because that will help us be able to
fix those before the Final Release.

I don't think we will be rebuilding the ISOs anymore before release,
which is nigh. At this point, we need to test the current builds, and
once the obligatory tests are completed, the ISOs need to be marked
ready for release.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Xenial - Beta 1 ISO Testing

[Kaj Ailomaa]

Found a couple of bugs concerning our desktop:

- no CoF in the whisker menu button (even after -default-settings was
updated)
- additional ubuntu vanilla indicators in the top panel

Please do some testing now to find any more bugs, and also do some
application testing.
To follow discussions about what is happening with other flavors, which
may affect us, drop into the IRC channel #ubuntu-release.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] last minute uploads

[Kaj Ailomaa]

On Wed, Feb 24, 2016, at 05:50 PM, set wrote:
> On 2016-02-24 12:29, Kaj Ailomaa wrote:
> > Just uploaded ubuntustudio-default-settings, fixing our whiskers icon
> > and ubuntustudio-look with the new wallpapers.
> 
> So, this was the last day we can make changes to the ubuntustudio-look?
> I've been feeling a bit confused since last week regarding the FF, the
> different tests and deadlines, and not having the time to bring my
> questions up i've gotten a bit deeper in my confusion.
> 

No, not at all. We can make changes all the way up until final release.
Feature Freeze means no added functionality to Ubuntu as a whole. So,
applications should not add new functionality, but you may still be
working on the UI for them. And, that's why UI freeze happens somewhat
later. Things like desktop look is a part of that too. And we are not at
UI freeze yet.
I simply wanted to upload latest changes so that people get the chance
to try it out for the Beta 1 release, since probably many will be
testing it.

Also, much of our stuff is only in our ISO. Therefore, we won't have
much problem with uploading our packages up until Final Freeze. After
that, I really need to poke someone in order to get an upload through,
and I would only do that to fix something critical.

> However, in the task of thinkiering about the tightening up of the
> desktop-look, i stumbled upon these icons that match our workflow icons
> very well: http://snwh.org/moka/icons
> They have a launchpad, and the license they use seems to be ok for our
> use. Although i'm sure they would like to be informed, and of course,
> the team needs to wight in on wether or not they are
> suitable/good-looking enough... But the question i mean to ask is: Would
> it still be possible to include this icon-set, given we get some time to
> discuss it? Or should that be for next release?
> 

I do think we should consider all options now as far as the look goes.

> > 
> > I won't have time to finish enough of -controls to get it up also, so
> > that will have to wait until after Beta 1. Is there anything else that
> > needs to be done before the Beta tomorrow? The archive may be frozen any
> > second now, in fact.
> > 
> 
> That would be the final beta right? Ross linked to this excellent page
> of the wiki you wrote zequence:
> https://wiki.ubuntu.com/UbuntuStudio/Testing/ISOTesting
> 

I should have something finished by next week. I don't have more time
than that do work on it, anyway. I really just want to add something
more to it, making it more useful. Unfortunately, I will have to do that
after Feature Freeze (which is in effect). Would have been better to get
that stuff in well before, but this is how it is.

btw, just before a release, such as the Beta1, uploads have to be
stopped so that no one accidentally breaks everyones ISO. That is not a
part of Feature Freeze, when I was talking about archive freeze before.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] last minute uploads

[Kaj Ailomaa]

On Wed, Feb 24, 2016, at 03:31 PM, Ralf Mardorf wrote:
> On Wed, 24 Feb 2016 12:29:19 +0100, Kaj Ailomaa wrote:
> >Is there anything else that needs to be done before the Beta tomorrow?
> >The archive may be frozen any second now, in fact.
> 
> Hi,
> 
> you could do inexperienced Linux users a favour by providing a version
> of JACK2 that can be used with Ardour. I suspect that many users will
> download up-to-date pre-build Ardour versions from upstream instead of
> using packages from their distros. It's even questionable if the
> version of Ardour provided by Ubuntu will work. Some audio cards can
> not be used with ALSA [1], they require using JACK, but when using
> JACK2 it requires a build from git to work with Ardour [2]. IMO there
> are too many pitfalls for newbies to build and maintain JACK from git
> on their own.
> 
> Regards,
> Ralf
> 

If you want to help Ralf, grab an ISO, find a bug, and report it. And
help fix it, if you can. 

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Xenial - Beta 1 ISO Testing

[Kaj Ailomaa]

I requested a rebuild of the ISO, after recently added packages. There
will probably be more rebuilds before the Beta 1 will be released. Our
testing at this point is mostly about finding problems.
Tomorrow it'll become clear which version of the ISO will be the one
released, and we test that to ensure it is ready for release.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] last minute uploads

[Kaj Ailomaa]

Just uploaded ubuntustudio-default-settings, fixing our whiskers icon
and ubuntustudio-look with the new wallpapers.

I won't have time to finish enough of -controls to get it up also, so
that will have to wait until after Beta 1. Is there anything else that
needs to be done before the Beta tomorrow? The archive may be frozen any
second now, in fact.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Wallpaper question...

[Kaj Ailomaa]

On Wed, Feb 24, 2016, at 10:02 AM, CFH wrote:
> Kaj, Ross, Art Team, others
> 
> I appreciate the urgency to submit the package.  Are we getting a new
> default paper?  If assigning one from the existing pool?

No, I think we should work on a new one. I've submitted a very simple
one as an example of where we could go. And, we should focus on a
unified design for 16.04, where the wallpaper is one part of it. Doesn't
need to be very advanced, but it needs to look good and feel right for
us.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ART TEAM ALERT! 16.04 Wallpaper Contest has been decided.

[Kaj Ailomaa]

On Sat, Feb 20, 2016, at 06:36 PM, Kaj Ailomaa wrote:
> On Sat, Feb 20, 2016, at 06:28 PM, Ross Gammon wrote:
> > Hi All,
> > 
> > On 02/16/2016 01:49 PM, C. F. Howlett wrote:
> > > ART TEAM NOTE: Hotwheel, by Lui Li Hua was in the top 3 throughout this
> > > election cycle and was #1 in the final tally.  Absent objections or
> > > suggestions, I assign Hotwheel as the default wallpaper for the 16.04
> > > release.  As we are trying to beat feature freeze, please advise post
> > > haste if this is unacceptable.
> > > 
> > > I will send out public notice of these results on 02/18/16.
> > 
> > Up until this point, I had been working on packaging the highest 16
> > voters with CF Howlett. I have pushed that work to launchpad:
> > $ bzr branch lp:ubuntustudio-look
> > 
> > This was mainly to work out how it worked (and practise for me).
> > 
> > But at some point, I will remove Hotwheel due to the questions about
> > it's source, and Kaj's creations that he would rather not include.
> >
> 
> Well, I only didn't want to use it as a default wallpaper. So, I'm still
> for keeping it. There is not evidence that there would be something not
> right with it. I just felt that I didn't want to use it as basis for a
> default wallpaper, is all.
> 

I just had a look at the package (ubuntustudio-look) you have prepared,
Ross. Thanks for fixing the links too.

I think I was confused about which of my wallpapers were in the
competition, and looking at the two that are included in the package, I
have no problem with those, so I guess the selection is set and the
package ready for upload. So, I'll get that done today.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Application Testing for Ubuntu Studio Xenial 16.04

[Kaj Ailomaa]

On Tue, Feb 23, 2016, at 05:11 PM, Ross Gammon wrote:
> On 02/23/2016 04:55 PM, Kaj Ailomaa wrote:
> > On Tue, Feb 23, 2016, at 04:42 PM, lukefro...@hushmail.com wrote:
> >> Kdenlive is STILL version 15.08, which is a buggy mess as well as being
> >> old. if that gets to release, anyone wanting to do a complex video in
> >> Xenial will need to install from PPA or source. Version 15.08 is OK for
> >> simple stuff but gets things like compositing transitions that move on
> >> their own and crashes.
> >>
> > 
> > Ross, did you contact anyone about this yet?
> > 
> 
> Yes - the Kubuntu people are working on it:
> https://bugs.launchpad.net/bugs/1546803
> 

Thanks, Ross. Looks like it will happen sooner or later then, before
release.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Xenial - Beta 1 ISO Testing

[Kaj Ailomaa]

On Tue, Feb 23, 2016, at 07:37 AM, Ross Gammon wrote:
> Hi All,
> 
> On Thursday 25th February the 1st Beta (Beta 1) of Ubuntu Studio (and
> other flavours) will be released. So please help by occasionally testing
> an ISO image from today and especially on the 25th.
> 
> The more testing, the more bugs we can identify and try to fix.
> 
> *Short instructions on how to test:*
> 
> 1. Get a launchpad account, if you haven't, at http://launchpad.net
> 2. Head to http://iso.qa.ubuntu.com, and login
> 3. Go to http://iso.qa.ubuntu.com/qatracker/milestones/357/builds/ and
> follow the links for Ubuntu Studio to the test cases.
> 4. Make sure your to do a checksum on your ISO before you report bugs.
> 5. If you find bugs, check at the bottom of the test case page if the
> bug was already reported, then make sure to include it in your test
> results. If no one had reported the bug, in a terminal, do: ubuntu-bug
> 
> 6. Even if all tests are completed, but the build is not yet marked
> *ready*, you may still help testing and submitting bug reports.
> 
> *Long instructions:*
> 
> For those new to ISO testing, please refer to:
> 
> https://wiki.ubuntu.com/UbuntuStudio/Testing/ISOTesting
> 
> For even more extensive information, please check out:
> 
> https://wiki.ubuntu.com/Testing/ISO
> 
> Cheers,
> 
> Ross

This is a very important testing period, in deed, so we should all make
use of this time to find problems. As Ross already has pointed out,
after Debian Import Freeze, we stop getting new packages from Debian.
And, after Feature Freeze, changes to Ubuntu are generally only bug
fixes, so for those reasons, now is a perfect time to do quality
assurance testing.

Also, we are still lacking a few things. We should get wallpaper
packages ready for upload. Tomorrow I'll be uploading whatever is still
missing, such as a new version of ubuntustudio-controls, which I'm
working on. Those are not critical for our tests, but would be nice to
have there for all to try out.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ART TEAM ALERT! 16.04 Wallpaper Contest has been decided.

[Kaj Ailomaa]

On Sat, Feb 20, 2016, at 06:28 PM, Ross Gammon wrote:
> Hi All,
> 
> On 02/16/2016 01:49 PM, C. F. Howlett wrote:
> > ART TEAM NOTE: Hotwheel, by Lui Li Hua was in the top 3 throughout this
> > election cycle and was #1 in the final tally.  Absent objections or
> > suggestions, I assign Hotwheel as the default wallpaper for the 16.04
> > release.  As we are trying to beat feature freeze, please advise post
> > haste if this is unacceptable.
> > 
> > I will send out public notice of these results on 02/18/16.
> 
> Up until this point, I had been working on packaging the highest 16
> voters with CF Howlett. I have pushed that work to launchpad:
> $ bzr branch lp:ubuntustudio-look
> 
> This was mainly to work out how it worked (and practise for me).
> 
> But at some point, I will remove Hotwheel due to the questions about
> it's source, and Kaj's creations that he would rather not include.
>

Well, I only didn't want to use it as a default wallpaper. So, I'm still
for keeping it. There is not evidence that there would be something not
right with it. I just felt that I didn't want to use it as basis for a
default wallpaper, is all.

> We of course need to add the new themed one (that will be the default)
> when it is ready.
> 
> Should we ship the remainder? Or is it better to create a separate
> competition wallpaper package that can be "suggested" when
> ubuntustudio-wallpapers is installed?
> 

That sounds good to me. ubuntustudio-wallpapers-extra, or something like
that?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Default Wallpaper Design, WAS: Re: ubuntu-studio-devel Digest, Vol 106, Issue 15

[Kaj Ailomaa]

On Fri, Feb 19, 2016, at 03:47 PM, Ralf Mardorf wrote:
> On Fri, 19 Feb 2016 14:02:04 +0100, Kaj Ailomaa wrote:
> >On Thu, Feb 18, 2016, at 07:25 PM, Ralf Mardorf wrote:
> >> IOW instead of
> >> 
> >>"Blue -violet -orange" consider to use
> >> "pastel blue - pastel violet - pastel red"  
> >
> >Would you be interesting in providing us with an example of these
> >colors, so we can see for ourselves?
> 
> Hi,
> 
> screenshot and for experimenting with colours, opacity and contrast by
> layers, also a Gimp file attached.
> 
> Regards,
> Ralf
> -- 

Thanks Ralf. Very clear colors. But, the look of it is a bit too soft
for me using pastel colors. It's an interesting proposal, but I have
trouble finding the right path from this junction - where to go with the
pastel colors, that is.

I did a mockup for the wallpaper, as I've said before. After sleeping on
it for a day or so, I would like to make it available. It's a very
classic design, for me. The one I did for 13.10 has much resemblance to
the technique with colors and shades (though I used a single color and a
pattern for 1310). Using this design I feel it could benefit from a bit
more complexity, so I'm not satisfied, but I still feel it could work
somehow as a basis for a unified design. See for yourselves.

I've put my mockup in the branch ubuntustudio-artwork. Get it with:

bzr branch lp:ubuntustudio-artwork

Then, you'll find the mockups in the dir:

ubuntustudio-artwork/16.04/unified-design-1604/mockups/

I'll also put Ralfs stuff in there in a moment.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Default Wallpaper Design, WAS: Re: ubuntu-studio-devel Digest, Vol 106, Issue 15

[Kaj Ailomaa]

On Thu, Feb 18, 2016, at 07:25 PM, Ralf Mardorf wrote:
> If you consider "red" as too aggressiv and perhaps too dominating, then
> replacing it by "orange" breaks your idea of "video is a mix of audio
> and graphics".
> 
> You could solve it by not replacing "red" by "orange", but instead by
> giving the colours a pastel shade.
> 
> IOW instead of
> 
>"Blue -violet -orange" consider to use
> "pastel blue - pastel violet - pastel red"

Would you be interesting in providing us with an example of these
colors, so we can see for ourselves?

I'm not an expert in colors, so much of my reasoning is not perfect.
When I use the three colors, the blue is changed during the process when
mixing it with other components of the full image. At least when using
it as a background component.
I have found a mix of the three colors I've mentioned to look good, and
that is of course the most important thing. Using the colors for our
three categories would then give some symbolism, even if they are not
fully logical according to either the color cycle, or how we perceive
colors.

> so the viewer is able to follow the idea of "video is a mix of audio
> and graphics". The "pastel blue" isn't the Ubuntu Studio logo default
> colour, but that doesn't matter and anyway wouldn't make sense, since
> Ubuntu Studio isn't = audio, audio is just the most likely most
> important domain of Ubuntu Studio, which is good represented by a
> different shade of blue.
> 
> You not necessarily need to follow the idea [1] "video is a mix of audio
> and graphics", but if you do so, it needs to "add up", you also could
> mix "blue" with another colour, but then the result needs to be
> plausible for at least one, additive mixing of colours or for
> subtractive mixing of colours.
> 
> [1] Actually video not necessarily is a mix of audio and video, keyword
> "silent movie", OTOH the idea to mix colours for the design is a
> good idea, makes sense, but it's not absolutely correct, video and
> audio always are two separated things, even while film comes with
> analog optical sound,
> 
> https://en.wikipedia.org/wiki/Sony_Dynamic_Digital_Sound#/media/File:35mm_film_audio_macro.jpg
> we usually often can't mix optical impressions with audio
> impressions, especially for digital television that often isn't
> lip-sync :D.
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Kdenlive [Was: Manual Test Cases]

[Kaj Ailomaa]

On Thu, Feb 18, 2016, at 12:24 AM, Ross Gammon wrote:
> The package set needs to be updated to match the packages we are
> interested in now (it looks very old). At the Community Council checkup
> meeting in IRC, I was encouraged to become a member. So after the 16.04
> release I might begin working towards that :-)
> 

That would be great, I think. You should have no problem becoming a
member, and I'm sure you can get upload rights to the package set as
well in time. I haven't followed your packaging work very closely, but I
believe what is needed is simply understanding of the Debian policy and
a bit of packaging experience, in a way that your work is persistent and
reliable. Our packages serve as a soft start, in a way. I will gladly
make myself more informed and support you if you apply for upload
rights.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Default Wallpaper Design, WAS: Re: ubuntu-studio-devel Digest, Vol 106, Issue 15

[Kaj Ailomaa]

On Wed, Feb 17, 2016, at 08:44 PM, Kaj Ailomaa wrote:
> On Wed, Feb 17, 2016, at 08:39 PM, Kaj Ailomaa wrote:
> > 
> > I have an idea, which I do think we should be able to get done. It's
> > pretty simple, and symbolic. It should not be hard to make it look good.
> > 
> > These are some possible elements of the image that we could develop
> > together:
> > 
> > * Incorporate the CoF somehow
> > * A fairly dark and neutral background color.
> > * Three fuzzy lights, like stage lights, each one representing a main
> > category (blue for audio, but the exact colors for graphics and video
> > need to be reevaluated).
> > * Visual elements from the kind of digital tools we provide, like
> > sequencer graphics (not a real sequencer, but a simple design), 3D model
> > fundamentals, a photograph, that sort of thing
> 
> The visual elements could be in a single color, using the category
> colors for each. That way, three fuzzy lights may be superfluous, and
> the image would be even more focused.
> 

# Did a mockup, but not going to show you yet

I took some time to play around. I found that using three colors for the
background works pretty well. It sits right, both visually and
symbolically. So, I really feel like doing something with the three
colors as basis is the way to go. I don't have a mockup worthy to show
you, but just want to spill my thoughts on that, in case someone wants
to pick this up and do some stuff with it.

# About the colors

The colors that feel the most right to me are:

* blue for audio (our standard blue, used for our CoF)
* orange for graphics
* purple for video

The logic behind the colors:
Purple is a mix between red and blue, just as video is a mix of audio
and graphics. Orange is not red, but close enough. Pure red may be too
aggressive. On top of that, both orange and purple are used a lot of
Ubuntu vanilla, so there's that too.

If having the colors side by side, purple seems the best fit to have in
the middle, considering the relationship between the colors. I would put
blue to the left (which from a western POW is the start of a page).

We are already using those colors in ubuntustudio-menu, but that doesn't
mean we can't change them, if we want. I would like to revisit the exact
hue of those though.

# Schedule

I'm not going to work too intensively on this myself during the next
week, at least. But, I will revisit as soon as I'm able.
We should have a final candidate of the default wallpaper ready about 1
month before release (final beta), but we can always make last minute
changes, if we really need to.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ubuntu-studio-devel Digest, Vol 106, Issue 15

[Kaj Ailomaa]

On Wed, Feb 17, 2016, at 08:39 PM, Kaj Ailomaa wrote:
> 
> I have an idea, which I do think we should be able to get done. It's
> pretty simple, and symbolic. It should not be hard to make it look good.
> 
> These are some possible elements of the image that we could develop
> together:
> 
> * Incorporate the CoF somehow
> * A fairly dark and neutral background color.
> * Three fuzzy lights, like stage lights, each one representing a main
> category (blue for audio, but the exact colors for graphics and video
> need to be reevaluated).
> * Visual elements from the kind of digital tools we provide, like
> sequencer graphics (not a real sequencer, but a simple design), 3D model
> fundamentals, a photograph, that sort of thing

The visual elements could be in a single color, using the category
colors for each. That way, three fuzzy lights may be superfluous, and
the image would be even more focused.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ubuntu-studio-devel Digest, Vol 106, Issue 15

[Kaj Ailomaa]

On Wed, Feb 17, 2016, at 01:48 PM, Jimmy Sjölund wrote:
> 
> 
> On 17 February 2016 13:11:28 +01:00, C. F. Howlett
>  wrote:
> 
> > Perhaps it would an opportune moment for our very own team to supply a
> > new design?? It *has* been awhile and this will an LTS ...
> > 
> > Absolutely. That was a previous goal for 16.04, but I'm hesitant if there 
> > is enough time left to pull it off. Rather than to create something quick 
> > that might not "hold its standard" until the next LTS.
> 

I have an idea, which I do think we should be able to get done. It's
pretty simple, and symbolic. It should not be hard to make it look good.

These are some possible elements of the image that we could develop
together:

* Incorporate the CoF somehow
* A fairly dark and neutral background color.
* Three fuzzy lights, like stage lights, each one representing a main
category (blue for audio, but the exact colors for graphics and video
need to be reevaluated).
* Visual elements from the kind of digital tools we provide, like
sequencer graphics (not a real sequencer, but a simple design), 3D model
fundamentals, a photograph, that sort of thing

We then use the material to create the wallpaper, artwork for our
website, social channels and for our merchandise.

Everyone could contribute with specific elements to the whole. Someone
should be responsible for putting it all together, with feedback from
others (I could do initial work for this, but then someone more suitable
should finish it).

Does this seem sensible? Would this work?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Default Wallpaper, WAS:Re: ART TEAM ALERT! 16.04 Wallpaper Contest has been decided.

[Kaj Ailomaa]

On Tue, Feb 16, 2016, at 03:58 PM, Kaj Ailomaa wrote:
> On Tue, Feb 16, 2016, at 03:54 PM, Kaj Ailomaa wrote:
> 
> > I already sent an email to the guy, but realized we have other concerns
> > too. For 14.04, the wallpaper was not just a wallpaper. It was a theme
> > used for all our social channels. If we want to continue to have a
> > generic theme, which we use for everything, I'm not sure a flame will do
> > it. The flame could be a variant of it, but not the "it".
> 
> This is my initial opinion, by the way. If flames were to be used as a
> generic theme, I believe they would need to be stylized somehow. It's
> still a bit weird for a generic theming, I think.
> 

I got word from lihualiu, the author of the proposed default wallpaper.
Unfortunately he is not interested in further work, but supplied me with
the original project file, which is a photoshop project. The flame is
found on the internet, but I haven't asked from where exactly. So, all
in all, I'm a little reluctant to use this as the default wallpaper
right now.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Default Wallpaper, WAS:Re: ART TEAM ALERT! 16.04 Wallpaper Contest has been decided.

[Kaj Ailomaa]

On Tue, Feb 16, 2016, at 02:56 PM, Kaj Ailomaa wrote:
> I like HotWheel. I'm slightly bothered by the CoF not being in the
> middle of the image. I'm sure the artist wanted to make up for the
> flames on the left side, but it gives it a slightly skewed impression to
> me. Also, it's a bit upward from the centre. All in all, it feels
> strange to me.
> 
> But, if we would prefer this one, we could work together with the artist
> to find the perfect default wallpaper for us. Besides working with the
> symmetry, another thing I would try is change the coloring. A blue flame
> would probably be the best fit for us, even if the original is "cooler"
> as an image. I any case, I would like to add something blue to it. There
> are a lot of things you could try to make the wallpaper a better fit for
> us as a default.
> I'll contact the artist to see if he would be interested in working more
> on it.
> 

I already sent an email to the guy, but realized we have other concerns
too. For 14.04, the wallpaper was not just a wallpaper. It was a theme
used for all our social channels. If we want to continue to have a
generic theme, which we use for everything, I'm not sure a flame will do
it. The flame could be a variant of it, but not the "it".
Zak would have wanted to do a general theme, I'm sure. It's not totally
needed, but it feels a lot more solid. I will need to consider this a
bit, and if anyone has any ideas on generic theme concepts, please let
me know. I would like to pursue it anyway.

I might not be much more involved in artwork for the rest of this week
though, so don't expect a lot of activity from me right away. I'm
currently working on adding planned features to ubuntustudio-controls,
so I will be busy with that. But, I will come back to this later!

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Scripts to help users troubleshooting

[Kaj Ailomaa]

On Sun, Feb 7, 2016, at 06:10 PM, Ralf Mardorf wrote:
> Hi,
> 
> perhaps Ubuntu Studio should include a few scripts, that could be used
> by inexperienced users, to provide troubleshooting information, if they
> wish to send a request for help.
> 

Thanks Ralf.

I'm going to work on something like that for ubuntustudio-controls, with
some session start checking to notify the user if sometbing is off. So,
I'll have a look at this before I do that.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Destktop/Window Manager

[Kaj Ailomaa]

On Fri, Jan 29, 2016, at 12:00 AM, Daniel M Gessel wrote:
> Created launch pad account.
> 
> I’m sure this is a total Newbie question, but is there a 25 word reason
> for not using compiz/Unity? It feels pretty solid, though I’d like to
> have more flexibility controlling the environment with my touch tablet. 
> 
> 

Ubuntu Studio is not specific to a desktop environment, and there are
plans (but no concrete work) on making Ubuntu Studio desktop agnostic,
making it possible to choose your favorite DE during installation of
Ubuntu Studio (when having an internet connection).

XFCE was chosen when Gnome went Gnome3, and Unity was young, and those
were different times. A lot of people had the idea that both those DEs
were moving away from the desktop, which apparently was not true, but
there is some controversy around both those DEs, and well, IMO there
isn't a clear candidate for a default DE, if we were to choose one
today.
But, since we already do have a default DE, it would require some work
on changing it - nothing impossible, but still, work that someone would
need to do.

And I would like to add this word of advice if you want to become a
contributor:

If you have the support of the community here, you can just go ahead and
do any kind of development as you please.
Each developer is free to do the things they are willing to do, unless
having made some sort of a commitment - like say being a project lead,
or some other kind of lead - where you will be responsible for certain
things and at least need to make sure they are working and functional,
but beyond that - since we are all volunteers, no one can order anyone
else to do anything - which is why it can be hard to make something
happen, unless you are willing to do some work yourself.

So, if you really feel like switching DEs is a good idea, keep the topic
going, and see who would like to work on that. I would rather make
Ubuntu Studio desktop agnostic instead, and improve how one can make any
Ubuntu flavor quickly suitable for audio production specifically, since
the other areas don't suffer as much from generic system settings.

On that note, when someone installs ubuntustudio-audio, or
ubuntustudio-audio-core, we should probably let -controls notify the
user that adding RT privilege might be a good idea, if that hasn't been
added already. So, that is actually one huge little detail to improve
the life of any DE user who wants to make music on their Ubuntu.

/Kaj (Current Project Lead)

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Congrats to Set, our next project lead

[Kaj Ailomaa]

Since we only have one candidate so far, and the window for announcing
your candidacy is closed as of today, Set automatically becomes next
project lead. So, congratulations!

I will continue as lead until Xenial is released, but will now help Set
in the transitioning and will also stick around for as long as is needed
with technical assistance.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] New to Ubuntu Studio!

[Kaj Ailomaa]

On Mon, Jan 25, 2016, at 05:11 PM, Daniel M Gessel wrote:
> Thanks for the info - it’s going to take me some time to get up to speed
> on joining all the online communities and things on the tech side.
> Getting older, I guess. ;)
> 
> If these kinds of directions have already been pursued, forgive me, but
> is there aversion to getting companies involved? I know the head of
> marketing at Universal Audio and might be able to find out their level of
> interest in Linux (I’m pretty sure they don’t ship any products right now
> - drivers are windows and Mac).
> 
> Thanks again - Dan
> -- 

As an organization, it is doubtful that Ubuntu Studio could have any
affiliation with a company which would involve money. However, there's
nothing that prevents collaboration between any entity as long as it
means the product is free and open source software.

I think it would be great to get some feedback from that kind of
companies about Ubuntu Studio though.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Wallpaper contest + [PR]

[Kaj Ailomaa]

On Wed, Jan 20, 2016, at 12:41 AM, set wrote:
> Re, wallpap-PR :)
> I created a draft here:
> https://ubuntustudio.org/wp-admin/post.php?post=1206=edit
> 
> I think it was fairly urgent given the time frame for the competition
> Please confirm i can post it, or i will do it! :D I added the repo as a
> link to the legacy-wallpapers in the showcase. I figure we need to
> motivate people to join the sources.
> 
> You're doing a great jobb cfhowlett
> Looking forward to read y'all!
> 
> -- 
> Set Sakrecoer
> 

Thanks Set. I was just about to do this myself, since cfhowlett can't
properly.
I'll also send the passwords to all parties, so that you can publish
this on the different social networks.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] [PR] Twitter account access

[Kaj Ailomaa]

I've sent passwords for all sites where there is an Ubuntu Studio
account in encrypted files to Set, Jimmy and Set, since you are the only
active people in PR at the moment.

cfhowlett can decide if he wants to make use of them at all. Probably
best if cfhowlett just focuses on content mostly and lets Set or Jimmy
announce stuff on the different sites, considering his internet
limitations.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Art Team: Ubuntustudio Design Assets questions

[Kaj Ailomaa]

The current-standard repo is updated -
lp:~ubuntustudio-art/ubuntustudio-artwork/current-standard

I had forgotten what the defect in the CoF was, and noticed earlier that
it was actually present in the CoF I had provided, which makes the ones
cfhowlett provided correct (somehow, my eye is telling me none of the
CoFs look perfect). So, I put the correct ones in the repo, and also
supplied a black version of the wordmark (just changed the color in
inkscape).

The current-standard branch now includes the same stuff as the wiki page
https://wiki.ubuntu.com/UbuntuStudio/Artwork/UserShowcase.

current-standard is not complete. I advice to wait until we can discuss
with Zak what should belong there (he might have more material than us),
before going forward with that. Also, creating an art standard page on
our web site will have to wait.
But, surely this amount of material is enough for creating wallpapers.

I'll announce the competition tomorrow, since cfhowlett is not able to
do so from his whereabouts.

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Art Team: Ubuntustudio Design Assets questions

[Kaj Ailomaa]

I've done some cleaning up of our artwork branch, and set up a new
routine for us when dealing with artwork material.
There are now three branches as you can see here
https://code.launchpad.net/ubuntustudio-artwork

Before I explain a bit more, I want to clarify one thing about the LP
urls.

lp:ubuntustudio-artwork is not the url to the repo in itself. Each
launchpad project has a lp: available, and you can point
that to any repo you like. This setting can be adjusted at the project
main page http://launchpad.net/ubuntustudio-artwork.
In this case lp:ubuntustudio-artwork points to the actual url
lp:~ubuntustudio-art/ubuntustudio-artwork/trunk.

So, what I have done now is:
* renamed lp:~ubuntustudio-art/ubuntustudio-artwork/trunk and called it
lp:~ubuntustudio-art/ubuntustudio-artwork/15.10. 
* Created a new branch with the url
lp:~ubuntustudio-art/ubuntustudio-artwork/trunk, which will serve as
trunk until the release of 16.04
* Created a third branch with the url
lp:~ubuntustudio-art/ubuntustudio-artwork/current-standard

The 'current-standard' repo should only contain standard materials that
we are absolutely clear about using right now. If you want to check out
the current standard, pull the branch with:
  bzr branch lp:~ubuntustudio-art/ubuntustudio-artwork/current-standard

All new artwork that we do for 16.04 should be added to the trunk
branch, so if you want to add new artwork, remove or rename the old
folder you pulled, and then pull the trunk branch for the first time,
like you did before with:
  bzr branch lp:ubuntustudio-artwork (lp:ubuntustudio-artwork is
  interchangeable with lp:~ubuntustudio-art/ubuntustudio-artwork/trunk)

We are missing some stuff in the current standards branch. I will add
whatever I know for sure we are using right now. Beyond that, it is a
matter of discussion and really more of problem for the art lead rather
than me, but I will try to fill in while Zak is not available. Hopefully
there's more material at hand by the end of this week.

Hope this clears things up a bit :)

/Kaj

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Wallpaper Contest site and design resources: comments invited

[Kaj Ailomaa]

On Tue, Jan 5, 2016, at 03:10 PM, C. F. Howlett wrote:
> Ubuntustudio Artwork User Showcase 
> 
> 
> I've set up a page to showcase User Created Content.  The first project 
> on this page will be the 16.04 wallpaper contest.  Please take a look 
> and point out the things I can enhance.  Thank you.
> -- 


Really nice work.

The text logos don't seem right though. Zak updated those by removing
some space in between letters and making the "studio" part a bit fatter.
The ones you have there are the old, original version.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] [LAU] Nama 1.204 is now in Debian unstable (fwd)

[Kaj Ailomaa]

On Wed, Dec 30, 2015, at 08:44 PM, Len Ovens wrote:
> 
> > -- Forwarded message --
> > Date: Wed, 30 Dec 2015 09:21:20 -1000
> > From: Joel Roth 
> > To: linux-audio-u...@lists.linuxaudio.org
> > Subject: [LAU] Nama 1.204 is now in Debian unstable
> >
> > Thanks to the Debian Perl Team, we now have a recent Nama in
> > Debian.
> 
> ...
> 
> How can we get this into the ubuntu repos? What kind of bug report? We
> have version 1.078-2 right now, so this would be an upgrade request.
> 
> Bug #1530199
> 
> This DAW is a great CLI based application and when paired with midish is 
> quite complete. I do not know if this is something we should ship as it
> is 
> CLI, but having in our installer as an option would make sense. It seems 
> to be the favourite DAW for people who have sight issues.

Unless there is some kind of problem it should be automatically synced -
assuming it is free software (and thus ends up in the universe repo).

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Voting System, WAS:Re: Next project lead

[Kaj Ailomaa]

Ok, let me give you an update on how condercet works. It's pretty simple
once you figure it out. It all comes to ranking, and how often a choice
is ranked higher than other choices, no matter if a choice is ever
ranked first.

Here's an example of an election with three candidates and seven voters.
Each line is a vote, where the voter ranks the three choices.

cand 1, cand 3, cand 2
cand 1, cand 3, cand 2
cand 1, cand 3, cand 2
cand 2, cand 3, cand 1
cand 2, cand 3, cand 1
cand 2, cand 3, cand 1
cand 3, cand 1, cand 2

So, who is the winner?
The answer is candidate 3.

While both cand 1 and cand 2 are ranked higher than cand 3 in three
votes each, cand 3 is ranked higher than the other two in four different
votes - when comparing per candidate.
Match between cand 1 and cand 3, cand 1 wins the first three votes, but
loses the last four.
Match between cand 2 and cand 3, cand 2 wins votes 4-6, but loses the
other four.
So, cand 3 wins.

In the case with three candidates, at least one vote needs to rank a
candidate first in order for that candidate to win, but with more
candidates, one who was never ranked first in a vote may win.

I'm using the default system when using http://civs.cs.cornell.edu/. If
anyone wants try it out, just head to that site and start a test poll.

Pretty simple, huh?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Voting System, WAS:Re: Next project lead

[Kaj Ailomaa]

On Tue, Dec 29, 2015, at 01:19 PM, Kaj Ailomaa wrote:
> The problem with this method becomes apparent when 30% vote on A, 30% on
> B and 30% on C, while all of them believe that if they're favorite does
> not win, they all would prefer D as the second choice. But, no one voted
> for D at all.
> With the condercet method, in this case, D could win.
> 

tbh, I still haven't actually looked at the specific, which is why I say
"could" (and I'm sure there are variants of it, not just one system).
The only thing I'm concerned about is that the system is fair and
represents the true wishes of the community. And my gut feeling said
this is a good choice for a system.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Voting System, WAS:Re: Next project lead

[Kaj Ailomaa]

On Mon, Dec 28, 2015, at 11:06 PM, Jimmy Sjölund wrote:
> On Mon, Dec 28, 2015 at 11:57 AM, Kaj Ailomaa <zeque...@mousike.me>
> wrote:
> 
> >
> > The common voting system is when each voter has one vote, and can put it
> > on one candidate. The one who gets the most votes, wins (don't know the
> > proper term for this system). This is simple and accurate if there are
> > only two candidates. This is what Xubuntu used for their last vote, with
> > only two nominees.
> >
> 
> I was thinking in line of majority vote, where everyone in a team get one
> vote. With the exception that if there is a draw the current Project Lead
> would get the casting vote.
> 

The problem with this method becomes apparent when 30% vote on A, 30% on
B and 30% on C, while all of them believe that if they're favorite does
not win, they all would prefer D as the second choice. But, no one voted
for D at all.
With the condercet method, in this case, D could win.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Voting System, WAS:Re: Next project lead

[Kaj Ailomaa]

I will confirm the date for the vote next week, if no one objects by
then, and announce it.

...but, we still need a method for the vote. I'm making some proposals
here based on what other Debian/Ubuntu communities use.

# VOTING SYSTEM (information and proposal)

The common voting system is when each voter has one vote, and can put it
on one candidate. The one who gets the most votes, wins (don't know the
proper term for this system). This is simple and accurate if there are
only two candidates. This is what Xubuntu used for their last vote, with
only two nominees.

Debian, among others (Ubuntu community council), uses
https://en.wikipedia.org/wiki/Condorcet_method for their project lead
vote. This works best with three candidates or more. IMO, this method
will slightly favor candidates who are less controversial, and perhaps
also reflects the community's wishes more accurately.

If there are more than three candidates, one may want to divide the vote
into two rounds, where two or three finalists remain in the second
round. But, this to me seems interesting only with a very big pool of
candidates.

Since I have very little experience in this sort of thing, I don't have
very strong opinions myself. I do think it's good to have an accurate
system which suits our organization. And, so, I'm proposing this, based
on how many candidates we have:

1 candidate - no vote, the sole candidate becomes project lead
2 candidates - simple majority vote (everyone has one vote, the winner
requires above 50% of votes)
3 or more candidates - condorcet method (vote for three candidates, by
ranking them 1, 2, 3 )

# WHERE TO VOTE

Xubuntu did their vote openly on the mailing list, but as said, only two
candidates.
Ubuntu community council uses this http://civs.cs.cornell.edu/, which is
based on the condorcet method.

I propose we use http://civs.cs.cornell.edu/, no matter the number of
candidates. Using the condorcet method with two candidates is the same
as a simple 50% majority vote, so technically there will be no
difference.

# WHO VOTES

I've proposed this before, and have seen no objections so far, but
adding it here again as a proposal:

Anyone who is in a moderated Ubuntu Studio launchpad team is allowed to
vote, which is evidence of somehow having been actively involved in
Ubuntu Studio development (one who is not part of such a team yet is
noklam, who was highly active for a little while a couple of weeks ago.
If he appears again before the vote, I will gladly add him to the
contributor team).

All the teams can be seen here
https://wiki.ubuntu.com/UbuntuStudio/TeamStructure.

# CONCLUSION

I know these are busy times for a lot of folks, but I'm sure there is
little controversy with these proposals. So, if no one objects before
next Monday, I will announce the vote with all relevant information.

Jan 25th: Nominee Window closes
Feb 1st: Vote begins, and is open for one full week

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Next project lead

[Kaj Ailomaa]

On Fri, Dec 25, 2015, at 12:38 PM, set wrote:
> On 2015-11-19 10:00, Kaj Ailomaa wrote:
> > Oh, and the link to the interesting part of the page -
> > https://wiki.ubuntu.com/UbuntuStudio/ProjectLeadVote#Announcing_your_candidacy
> > 
> > Here's the template that candidates should use when announcing their
> > candidacy -
> > https://wiki.ubuntu.com/UbuntuStudio/ProjectLeadCandidateTemplate.
> > 
> 
> So, here is my Candidacy Wiki page.
> 
> https://wiki.ubuntu.com/UbuntuStudio/ProjectLeadVote2016/Sakrecoer
> 

Thanks, Set.

So, that's one! :)

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Next project lead

[Kaj Ailomaa]

Btw, let's discuss when we have the vote, and when we close the window
for new candidates.

I think it's important that we have a chance to review candidates a few
days before a vote, so my suggestion is one week before the vote we
don't accept new candidates.

How about we have the vote the first week of february?

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Wallpaper contest

[Kaj Ailomaa]

On Mon, Dec 21, 2015, at 11:08 AM, C. F. Howlett wrote:
> Yeah about that:
> 
> I have looked at the art work produced for the other derivatives, and I 
> admit to a great deal of envy for ubuntukylin's design and prodigious 
> output.
> 
> I am unconvinced that we are fully obligated to comply with Canonical 
> Design requirements sole exception being logo use.  As it happens, I 
> have the *official* ubuntustudio logos released by Ubuntu Design.  I 
> would like to upload them to the bzr site, but I have yet to figure out 
> the method.
> 

I'm not sure about the logo, if you are referring to the Circle of
Friends. We have our own design, for sure, though it is derived from
Ubuntu.
Also, the name Ubuntu Studio I think is a trademark of Canonical. At
least the "Ubuntu" part is.
In some way, all of what we do is derived from the same base: Ubuntu. I
would say, as long as we don't do anything stupid, I'm sure we'll be
fine.

Before making any changes to the branch, make sure you have got the
latest changes first with the command:
  bzr pull :parent

To add anything to the bzr branch, add the files to the folder like you
normally would. Then, from the command line add all new files with
(don't forget the punctation mark):
  bzr add .

To commit your changes, do (add your own description):
  bzr commit -m "describe your change here"

Then, upload:
  bzr push :parent

> As regards the photography rules, I suggest that as a dedicated OS for 
> *art creation*, we have a wide discretion and latitude. I am not 
> suggesting a photographic free-for-all, but I submit that imposing 
> restraining rules on creative output is somewhat contradictory.
> 
> So: questions.  Do we / should we have a wiki page?  We have had a 
> community art page in the past, but it seems to be defunct.  Should we 
> resurrect it?
> 

Feel free to create a new page or change an existing one if that makes
sense. Use the root https://wiki.ubuntu.com/UbuntuStudio/Artwork, i.e.
something like UbuntuStudio/Artwork/UserContributed. Put a link to the
art sidebar so everyone can find it easily.

As it so happens, there is a page exactly like that, but you may want to
start a new one, or reorganize the existing one. You can find it here:
https://wiki.ubuntu.com/UbuntuStudio/Artwork/UserContributed

These pages are not among the sidebar links
https://wiki.ubuntu.com/CategoryUbuntuStudioArtwork.

Also, there may be more artwork related pages here, if you want to take
a look: https://wiki.ubuntu.com/UbuntuStudio/SubPages

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Boot partition and old kernel images - are we alone with this problem?

[Kaj Ailomaa]

I'm sure some of you have noticed that if you have a small boot
partition (UEFI installs, generally), old kernel images are not being
autoremoved, and when you do your third or whatever update you get a
message that there's not enough room for the update.

I haven't actually used a vanilla Ubuntu system enough to know if this
is a problem there as well. We have our own kernel, so could be -generic
gets autoremoved, but not -lowlatency. In either case, this sure needs
to be fixed for the next LTS, and needs to be a priority for this cycle.

If anyone has any good information on the problem, please let us know.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Introduction to feature definition (for all you newcomers, and memory refresh for the rest)

[Kaj Ailomaa]

All contributors who don't know what this is, please ready through this,
as it is crucial for how we organize our development. 

# Introduction to feature definitiion

## What is feature definition?

Typically, at the beginning of a development cycel (6 months), some sort
of plan is laid out on what is to be done. For each area of development,
the features are specified on a wiki page.  Like this one (though not
complete):
https://wiki.ubuntu.com/UbuntuStudio/FeatureDefinitions/MultimediaApplicationCategorization

Then, one or many blueprints may be created at launchpad which has a
list of tasks that team members can take on themselves to do and mark
ready once they are done with them. In this case, there are three
different blueprints for "MultimediaApplicationCategorization", and this
is one of them -
https://blueprints.launchpad.net/ubuntustudio/+spec/fdc-audio.

The blueprint is typically drafted during the feature definition period.
Once feature definition is over, and no one objects about any new
features, we start working on implementation. Where many people are
involved in doing the same form of tasks, blueprints become handy as to
make sure not two people are doing the same thing, but for a lot of
other things a feature definition on a wiki page may be quite enough.

## When do we do it?

Feature definition is what Ubuntu flavor devs usually do during the
first month of a development cycle(November -> December), which would
have been November in this case. I was a little busy with other things,
and since we seem to have more activity now compared to then, it may be
just as good we begin feature definition now (though, much is already
defined, as you will see later).

## Feature Definition Freeze

After this date features can not be added without consent from a lead of
some sort.
It is has fact a specific date that Canonical follows for any features
added for Ubuntu. We are less strict with this date, but it is a
reasonable date which allows for enough time to complete implentations
and testing of new features. The date is different for each cycle, but
is about one month after development begins. For this cycle it was 26th
of November. You may see all of the dates here -
https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule

Since we obviously are not on schedule, we will not be freezing any
features yet.

## Where can I see all of the feature definitions and blueprints?

*Feature Definitions*

Here are all of our feature definitions:
https://wiki.ubuntu.com/UbuntuStudio/FeatureDefinitions/
They appear there, if a page has the root
UbuntuStudio/FeatureDefinitions/

*Blueprints*

Links at the wiki: https://wiki.ubuntu.com/UbuntuStudio/Blueprints
Main topic blueprint at launchpad:
https://blueprints.launchpad.net/ubuntustudio/+spec/ubuntustudio-topic-x

## If I have an idea and would like to make something out of it

If you have an idea you would like to develop, start by discussing it on
the mail list. If you aren't breaking something else, or in any other
way affecting the harmony of the whole system, there is no reason for
anybody to object what you want to do.
Whether you are alone in being interested in that specific feature, or
not, you'd start by making a feature definitions page at the wiki.

## Conclusion

The whole system with feature definitions and blueprints is very useful
for a large group of developers who cooperate on may areas. Since we are
very small, the use of blueprints is less important in many cases.
Feature definitions however are crucial, and developers should not
deviate from those unless discussing with someone first.

And if you have any at all questions, please do ask.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Introduction to feature definition (for all you newcomers, and memory refresh for the rest)

[Kaj Ailomaa]

Btw, since we most certainly do not make use of all of our blueprints,
and many of them are not really specified for a single release (like
some of our applications), I will be doing some reorganization. I'd like
to make things as simple as possible now.

Once I'm done with that, I'd like us to do a bit of feature definition,
so that we are all on the same page once some heavy changes may be
implemented later in the cycle. So, give me a few days (I'm thinking
Monday the latest), before we can start with that.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel