> > The changes need to be documented in the source branches, not on wiki
> > pages.
> >
> > I think Len and smartboyhw know what this means.
> >
> > Of course. The suggestion of a table in a wiki page was only to keep track
> on who was working on what package instead of everyone mailing the list
On Tue, Aug 6, 2013 at 11:08 PM, Kaj Ailomaa wrote:
>
>
> On Tue, Aug 6, 2013, at 10:56 PM, Jimmy Sjölund wrote:
>
> > Wouldn't the "safest" way be to set up a table on a wikipage and we could
> > pick and mark the packages one starts working on? I haven't set up any
> > wikipage on the ubuntu s
On Tue, Aug 6, 2013, at 10:56 PM, Jimmy Sjölund wrote:
> Wouldn't the "safest" way be to set up a table on a wikipage and we could
> pick and mark the packages one starts working on? I haven't set up any
> wikipage on the ubuntu side yet but have created similar tables and
> reports
> on other
On Tue, Aug 6, 2013 at 5:06 PM, Len Ovens wrote:
>
> On Tue, August 6, 2013 7:52 am, Len Ovens wrote:
>
> > All of our packages have a debian/copyright file. This file should be
> > machine readable ( see:
> > http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ ) and
> > none of our
Dear Ubuntu Studio Developers and contributors,
Your task (as in Mission Impossible XD) is to:
1. Update the debian/copyright file of each source package dedicated
for Ubuntu Studio to the Debian machine-readable copyright file.
2. Update the debhelper version to 9. Detailed steps:
a. Update de
On Tue, August 6, 2013 7:52 am, Len Ovens wrote:
> All of our packages have a debian/copyright file. This file should be
> machine readable ( see:
> http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ ) and
> none of ours are.
Forgot to add. it would be a good idea to leave a messa
Are you looking for something to do to help? It has been brought to my
attention that almost all of our ubuntustudio packages are out of date
and/or not really as they should be in other ways.
All of our packages have a debian/copyright file. This file should be
machine readable ( see:
http://www.
