music creation spin - git repo created and commit logs ?

[Development discussions related to Fedora]

Hi, I requested git hosting for the music-list under:
http://git.fedorahosted.org/git/?p=music-creation.git;a=summary

This is now set up, and having learnt the absolute basics of git, I have
committed progress so far on the Fedora only packages spin, which at
this stage is dubbed "Music Creation Lite".

Since this is not going to be built automatically by Fedora
infrastructure to generate test iso images, we need to build images
independently and post them somewhere. I am happy to place CD sized
images on my web space.

One thing this begs is are people happy to test these images on real
hardware ?

This implies that you trust that the iso I built was generated from the
spin - kickstart that lives in git, and that I don't have any untoward
code on my build = daily use machine, that could taint the build. Is
there something better that we could do ?

By the way, when the git repo was requested I set the commit diffs to be
emailed to musc(a)lists.fedoraproject.org. This doesn't work at the moment
because the git user (my @ fedoraproject address) is not a member of the
music list, and hence the mails get rejected.

1. Would people be happy to have such git commit logs coming into this
list ?
2. A better plan for keeping people informed of changes ?

Best regards,
David

ps. Orcan: holy-cow: you have a lot of packages; I get stumped trying to
keep up with about 10 packages. I hope there are some music / computer
lovers out there who are willing to become co-maintainer of at least
some of Orcan's packages ;-)

[Orcan Ogetbil]

On Sun, Aug 15, 2010 at 4:13 AM, David Timms wrote:
>  By the way, when the git repo was requested I set the commit diffs to
> be
>  emailed to musc(a)lists.fedoraproject.org. This doesn't work at the moment
>  because the git user (my @ fedoraproject address) is not a member of the
>  music list, and hence the mails get rejected.
>
>  1. Would people be happy to have such git commit logs coming into this
>  list ?
>  2. A better plan for keeping people informed of changes ?
>  
Depends on the commit load. If there will be a lot of commits, a
separate mailing list may be needed.

But anyway, why do we need git diffs sent us by email? Those who are
curious can track stuff via the gitweb.

>  ps. Orcan: holy-cow: you have a lot of packages; I get stumped trying to
>  keep up with about 10 packages. I hope there are some music / computer
>  lovers out there who are willing to become co-maintainer of at least
>  some of Orcan's packages ;-) 
Well, many of those packages have dead or almost dead upstreams and
they require little to no maintenance. Some are retired packages.
pkgdb keeps showing the retired packages in your list. Also I am a
comaintainer, not the primary maintainer, of many of these packages.
Unfortunately, some primary maintainers are no longer active, and I
became the effective maintainer of certain ones.

After discounting all of these, I actively maintain about 30 packages,
which is still a lot, hence I started retiring those that I do not
really use. Sadly, there is still a lot of other stuff that needs to
be packaged, but I don't have time or room to handle them.

Don't hesitate to comaintain and to break things up. That's how I
learned stuff :)

Orcan

[Christopher Antila]

Hi:

Thanks again for getting the ball rolling for us, David.  This git
repository will be a big step forward in allowing more people to try and
contribute to the remix.

I'm willing to test whatever you build, in whatever spare time I have,
but having you build the remix yourself is obviously not a secure,
sustainable, long-term solution.  Eventually, we'll find a solution for
this.

As for the git commits, I guess we should do as Orcan says: send them to
music@ until we get enough changes to create a separate list just for them.

As for the menus, again we'll do as Orcan says: use a structure like the
multimedia-menus package.  This will be important for the remix to be
effective.


Christopher.

On 08/15/2010 04:13 AM, David Timms wrote:
>  Hi, I requested git hosting for the music-list under:
>  http://git.fedorahosted.org/git/?p=music-creation.git;a=summary
>  
>  This is now set up, and having learnt the absolute basics of git, I have
>  committed progress so far on the Fedora only packages spin, which at
>  this stage is dubbed "Music Creation Lite".
>  
>  Since this is not going to be built automatically by Fedora
>  infrastructure to generate test iso images, we need to build images
>  independently and post them somewhere. I am happy to place CD sized
>  images on my web space.
>  
>  One thing this begs is are people happy to test these images on real
>  hardware ?
>  
>  This implies that you trust that the iso I built was generated from the
>  spin - kickstart that lives in git, and that I don't have any untoward
>  code on my build = daily use machine, that could taint the build. Is
>  there something better that we could do ?
>  
>  By the way, when the git repo was requested I set the commit diffs to be
>  emailed to musc(a)lists.fedoraproject.org. This doesn't work at the moment
>  because the git user (my @ fedoraproject address) is not a member of the
>  music list, and hence the mails get rejected.
>  
>  1. Would people be happy to have such git commit logs coming into this
>  list ?
>  2. A better plan for keeping people informed of changes ?
>  
>  Best regards,
>  David
>  
>  ps. Orcan: holy-cow: you have a lot of packages; I get stumped trying to
>  keep up with about 10 packages. I hope there are some music / computer
>  lovers out there who are willing to become co-maintainer of at least
>  some of Orcan's packages ;-)
>  _______________________________________________
>  music mailing list
>  music(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/music