Fwd: Re: [FESCo] #540: F15Feature: Robotics Suite - https://fedoraproject.org/wiki/Features/RoboticsSuite
Hi Fedora robotics people.
Our Robotics Suite feature has been accepted. Thanks to everybody, in particular to Rich and Hedayat.
I will setup the Fawkes demo repository tomorrow to start the demo. We should have a meeting again and discuss the next steps. What about next Tuesday, Jan 18 at 14:00 UTC?
Rich, do you know the process of getting the comps group to start tagging packages for the group? Can someone contact the arts group for icons and other artwork that is required? I'll focus on the demo then.
Tim
-------- Original-Nachricht -------- Betreff: Re: [FESCo] #540: F15Feature: Robotics Suite - https://fedoraproject.org/wiki/Features/RoboticsSuite Datum: Wed, 12 Jan 2011 18:55:26 -0000 Von: FESCo trac@fedorahosted.org Antwort an: nobody@fedoraproject.org CC: fesco@lists.fedoraproject.org, tcallawa@redhat.com, limb@jcomserv.net, toshio@fedoraproject.org
#540: F15Feature: Robotics Suite - https://fedoraproject.org/wiki/Features/RoboticsSuite ---------------------+------------------------------------------------------ Reporter: rbergero | Owner: Type: zFeature | Status: new Priority: major | Resolution: Keywords: meeting | ---------------------+------------------------------------------------------ Comment (by kevin):
This feature was approved.
On Wed, Jan 12, 2011 at 2:37 PM, Tim Niemueller tim@niemueller.de wrote:
Hi Fedora robotics people.
Our Robotics Suite feature has been accepted. Thanks to everybody, in particular to Rich and Hedayat.
I will setup the Fawkes demo repository tomorrow to start the demo. We should have a meeting again and discuss the next steps. What about next Tuesday, Jan 18 at 14:00 UTC?
Rich, do you know the process of getting the comps group to start tagging packages for the group? Can someone contact the arts group for icons and other artwork that is required? I'll focus on the demo then.
Tim
I did find out the process for adding a comps group, I will compile a package list for the Robotics Suite comps group and commit it to our github project. Before we contact the art people, I think we should narrow down what we want done. So far I see that we need:
* Logo for the Robotics Suite * Banner for Robotics Suite to be used on our webpages * Icons for Player utilities and Stage (I'd like these, but they're not essential to the robotics suite effort)
Once we narrow this list down, I will file a ticket and follow through. If you keep your demo work on github, I will try to jump in and help you. The fedora-robotics-spin project is as good a place as any to get all of this done.
Rich
On 12.01.2011 21:11, Rich Mattes wrote:
On Wed, Jan 12, 2011 at 2:37 PM, Tim Niemuellertim@niemueller.de wrote:
Hi Fedora robotics people.
Our Robotics Suite feature has been accepted. Thanks to everybody, in particular to Rich and Hedayat.
I will setup the Fawkes demo repository tomorrow to start the demo. We should have a meeting again and discuss the next steps. What about next Tuesday, Jan 18 at 14:00 UTC?
Rich, do you know the process of getting the comps group to start tagging packages for the group? Can someone contact the arts group for icons and other artwork that is required? I'll focus on the demo then.
TimI did find out the process for adding a comps group, I will compile a package list for the Robotics Suite comps group and commit it to our github project. Before we contact the art people, I think we should narrow down what we want done. So far I see that we need:
- Logo for the Robotics Suite
- Banner for Robotics Suite to be used on our webpages
- Icons for Player utilities and Stage (I'd like these, but they're not
essential to the robotics suite effort)
I think we need icons for Anaconda and stuff.
Once we narrow this list down, I will file a ticket and follow through. If you keep your demo work on github, I will try to jump in and help you. The fedora-robotics-spin project is as good a place as any to get all of this done.
I'll setup a fawkesrobotics.org repository, makes things easier on my side. I have added your pubkeys earlier already so you will have full access there as well.
Tim
Hi all,
/*Tim Niemueller tim@niemueller.de*/ wrote on 01/12/2011 11:54:40 PM +0350:
On 12.01.2011 21:11, Rich Mattes wrote:
On Wed, Jan 12, 2011 at 2:37 PM, Tim Niemuellertim@niemueller.de wrote:
Hi Fedora robotics people.
Our Robotics Suite feature has been accepted. Thanks to everybody, in particular to Rich and Hedayat.
Happy to hear that :)
I will setup the Fawkes demo repository tomorrow to start the demo. We should have a meeting again and discuss the next steps. What about next Tuesday, Jan 18 at 14:00 UTC?
Looks good. If possible, I would prefer Monday (or even Sunday), but I think I can attend Tuesday too.
Rich, do you know the process of getting the comps group to start tagging packages for the group? Can someone contact the arts group for icons and other artwork that is required? I'll focus on the demo then.
TimI did find out the process for adding a comps group, I will compile a package list for the Robotics Suite comps group and commit it to our github project. Before we contact the art people, I think we should narrow down what we want done. So far I see that we need:
- Logo for the Robotics Suite
- Banner for Robotics Suite to be used on our webpages
- Icons for Player utilities and Stage (I'd like these, but they're not
essential to the robotics suite effort)
I think we need icons for Anaconda and stuff.
Yes, if we'd like to bring a special look we need that too :).
If the list is final, I can contact arts group.
About the comps group, apparently the only requirement was what Rich has already done: mailing to -devel list! We could probably go ahead and add it to rawhide's comps.xml and wait to see if anybody objects! :P BTW, which category we want to put our group in? Applications? Development? Or maybe a new category just for this? (Not far from the reality since there is already a "Content" category containing a single group (currently) named Books). And what is the group name? Robotics? :P (just to make sure!)
Once we narrow this list down, I will file a ticket and follow through. If you keep your demo work on github, I will try to jump in and help you. The fedora-robotics-spin project is as good a place as any to get all of this done.
I'll setup a fawkesrobotics.org repository, makes things easier on my side. I have added your pubkeys earlier already so you will have full access there as well.
Thanks, I'll try to help as much as I can too.
Thanks, Hedayat
Tim
On Thu, Jan 13, 2011 at 10:13 AM, Hedayat Vatankhah hedayatv@gmail.comwrote:
Hi all,
*Tim Niemueller tim@niemueller.de tim@niemueller.de* wrote on 01/12/2011 11:54:40 PM +0350:
On 12.01.2011 21:11, Rich Mattes wrote:
On Wed, Jan 12, 2011 at 2:37 PM, Tim Niemuellertim@niemueller.de tim@niemueller.de wrote:
Hi Fedora robotics people.
Our Robotics Suite feature has been accepted. Thanks to everybody, in particular to Rich and Hedayat.
Happy to hear that :)
I will setup the Fawkes demo repository tomorrow to start the demo. We should have a meeting again and discuss the next steps. What about next Tuesday, Jan 18 at 14:00 UTC?
Looks good. If possible, I would prefer Monday (or even Sunday), but I think I can attend Tuesday too.
I can do any of these times as well. 1400UTC is a good time for me.
Rich, do you know the process of getting the comps group to start tagging packages for the group? Can someone contact the arts group for icons and other artwork that is required? I'll focus on the demo then.
TimI did find out the process for adding a comps group, I will compile a package list for the Robotics Suite comps group and commit it to our github project. Before we contact the art people, I think we should narrow down what we want done. So far I see that we need:
- Logo for the Robotics Suite
- Banner for Robotics Suite to be used on our webpages
- Icons for Player utilities and Stage (I'd like these, but they're not
essential to the robotics suite effort)
I think we need icons for Anaconda and stuff.
Yes, if we'd like to bring a special look we need that too :).
If the list is final, I can contact arts group.
I can't think of anything else we'd need. I don't know that we'll need the anaconda stuff for the RoboticsSuite feature, but we will once we create the LiveDVD.
About the comps group, apparently the only requirement was what Rich has already done: mailing to -devel list! We could probably go ahead and add it to rawhide's comps.xml and wait to see if anybody objects! :P BTW, which category we want to put our group in? Applications? Development? Or maybe a new category just for this? (Not far from the reality since there is already a "Content" category containing a single group (currently) named Books). And what is the group name? Robotics? :P (just to make sure!)
I started on the comps group last night. I'm creating a whole new group called "Robotics Suite", once it's done you should be able to "yum groupinstall "Robotics Suite"" and end up with a complete robotics development environment. Once we nail down the package list, we submit the patch to comps.xml to the -devel list, and barring any qualms we commit it to the comps git.
Once we narrow this list down, I will file a ticket and follow through. If you keep your demo work on github, I will try to jump in and help you. The fedora-robotics-spin project is as good a place as any to get all of this done.
I'll setup a fawkesrobotics.org repository, makes things easier on my side. I have added your pubkeys earlier already so you will have full access there as well.
Thanks, I'll try to help as much as I can too.
Thanks, Hedayat
Tim
One last thing: I'm about ready to start shuffling our wiki pages around: putting http://fedoraproject.org/wiki/User:Rmattes/Robotics at fp.o/wiki/Robotics, and then moving the SIG page to wiki/SIGs/Robotics (right now SIGs/Robotics is a redirect to wiki/Robotics, and Robotics contains the SIG page.) We still need the Fawkes example, maybe I'll try to come up with one as it will give me an excuse to learn a little bit more about it :) Once we get a banner, we can put it at the top of that wiki page as well.
Rich
On 13.01.2011 20:10, Rich Mattes wrote:
I can do any of these times as well. 1400UTC is a good time for me.
Ok, let's go for 1400UTC as I cannot make it on Monday or Sunday.
I can't think of anything else we'd need. I don't know that we'll need the anaconda stuff for the RoboticsSuite feature, but we will once we create the LiveDVD.
Ok, if we contact them we should do it all in one go I think.
I started on the comps group last night. I'm creating a whole new group called "Robotics Suite", once it's done you should be able to "yum groupinstall "Robotics Suite"" and end up with a complete robotics development environment. Once we nail down the package list, we submit the patch to comps.xml to the -devel list, and barring any qualms we commit it to the comps git.
Excellent. I'd vote for the Robotics category if that is different from the group. What has to happen to have an appropriate package group (RPM spec tag)?
One last thing: I'm about ready to start shuffling our wiki pages around: putting http://fedoraproject.org/wiki/User:Rmattes/Robotics at fp.o/wiki/Robotics, and then moving the SIG page to wiki/SIGs/Robotics (right now SIGs/Robotics is a redirect to wiki/Robotics, and Robotics contains the SIG page.) We still need the Fawkes example, maybe I'll try to come up with one as it will give me an excuse to learn a little bit more about it :) Once we get a banner, we can put it at the top of that wiki page as well.
Go for it!
Tim
Hi,
/*Tim Niemueller tim@niemueller.de*/ wrote on 01/14/2011 12:25:27 AM +0350:
On 13.01.2011 20:10, Rich Mattes wrote:
I can do any of these times as well. 1400UTC is a good time for me.
Ok, let's go for 1400UTC as I cannot make it on Monday or Sunday.
I can't think of anything else we'd need. I don't know that we'll need the anaconda stuff for the RoboticsSuite feature, but we will once we create the LiveDVD.
Ok, if we contact them we should do it all in one go I think.
I started on the comps group last night. I'm creating a whole new group called "Robotics Suite", once it's done you should be able to "yum groupinstall "Robotics Suite"" and end up with a complete robotics development environment. Once we nail down the package list, we submit the patch to comps.xml to the -devel list, and barring any qualms we commit it to the comps git.
Excellent. I'd vote for the Robotics category if that is different from the group. What has to happen to have an appropriate package group (RPM spec tag)?
In anaconda package customization UI, the left column shows categories (Desktop Environment, Applications, Server ...) and the right column shows groups of the selected category. Package groups are organized in comps.xml itself, so there is no need to change anything in the packages themselves.
Thanks, Hedayat
One last thing: I'm about ready to start shuffling our wiki pages around: putting http://fedoraproject.org/wiki/User:Rmattes/Robotics at fp.o/wiki/Robotics, and then moving the SIG page to wiki/SIGs/Robotics (right now SIGs/Robotics is a redirect to wiki/Robotics, and Robotics contains the SIG page.) We still need the Fawkes example, maybe I'll try to come up with one as it will give me an excuse to learn a little bit more about it :) Once we get a banner, we can put it at the top of that wiki page as well.
Go for it!
Tim
On 13.01.2011 23:12, Hedayat Vatankhah wrote:
In anaconda package customization UI, the left column shows categories (Desktop Environment, Applications, Server ...) and the right column shows groups of the selected category. Package groups are organized in comps.xml itself, so there is no need to change anything in the packages themselves.
Ok, Rich, which category is the Robotics Suite in?
The package group was just mixed in, I want to propose a package group specific to robot software, we have quite a few packages to which this could apply.
Tim
On Thu, Jan 13, 2011 at 5:15 PM, Tim Niemueller tim@niemueller.de wrote:
On 13.01.2011 23:12, Hedayat Vatankhah wrote:
In anaconda package customization UI, the left column shows categories (Desktop Environment, Applications, Server ...) and the right column shows groups of the selected category. Package groups are organized in comps.xml itself, so there is no need to change anything in the packages themselves.
Ok, Rich, which category is the Robotics Suite in?
The package group was just mixed in, I want to propose a package group specific to robot software, we have quite a few packages to which this could apply.
Tim
I think we fit best in the Development category. I'm creating a new group inside of the development category for our packages, called Robotics Suite, which will contain the robotics related stuff. I'm just not sure whether or not it makes more sense to list the -devel packages or the base packages for our stuff (or both). For instance, should I include player-devel and/or player? mrpt-devel and/or mrpt? I'm leaning towards including devel packages instead of base ones, since tutorials will probably rely on them at some point.
Rich
On 13.01.2011 23:34, Rich Mattes wrote:
On Thu, Jan 13, 2011 at 5:15 PM, Tim Niemuellertim@niemueller.de wrote:
On 13.01.2011 23:12, Hedayat Vatankhah wrote:
In anaconda package customization UI, the left column shows categories (Desktop Environment, Applications, Server ...) and the right column shows groups of the selected category. Package groups are organized in comps.xml itself, so there is no need to change anything in the packages themselves.
Ok, Rich, which category is the Robotics Suite in?
The package group was just mixed in, I want to propose a package group specific to robot software, we have quite a few packages to which this could apply.
TimI think we fit best in the Development category. I'm creating a new group inside of the development category for our packages, called Robotics Suite, which will contain the robotics related stuff. I'm just not sure whether or not it makes more sense to list the -devel packages or the base packages for our stuff (or both). For instance, should I include player-devel and/or player? mrpt-devel and/or mrpt? I'm leaning towards including devel packages instead of base ones, since tutorials will probably rely on them at some point.
I agree with the category and I suggest to add both, base and devel packages.
Tim
On 01/13/2011 05:39 PM, Tim Niemueller wrote:
On 13.01.2011 23:34, Rich Mattes wrote:
On Thu, Jan 13, 2011 at 5:15 PM, Tim Niemuellertim@niemueller.de wrote:
On 13.01.2011 23:12, Hedayat Vatankhah wrote:
In anaconda package customization UI, the left column shows categories (Desktop Environment, Applications, Server ...) and the right column shows groups of the selected category. Package groups are organized in comps.xml itself, so there is no need to change anything in the packages themselves.
Ok, Rich, which category is the Robotics Suite in?
The package group was just mixed in, I want to propose a package group specific to robot software, we have quite a few packages to which this could apply.
TimI think we fit best in the Development category. I'm creating a new group inside of the development category for our packages, called Robotics Suite, which will contain the robotics related stuff. I'm just not sure whether or not it makes more sense to list the -devel packages or the base packages for our stuff (or both). For instance, should I include player-devel and/or player? mrpt-devel and/or mrpt? I'm leaning towards including devel packages instead of base ones, since tutorials will probably rely on them at some point.
I agree with the category and I suggest to add both, base and devel packages.
Tim
Please have a look at [1] and see if I missed anything. I've been using [2] as a guide on how to do things; the diff is against the f15-comps file.
I also went ahead and adjusted the wiki pages. fp.o/wiki/Robotics is now the showcase page, and fp.o/wiki/SIGs/Robotics now holds the old robotics sig page.
Rich
[1] http://rmattes.fedorapeople.org/comps-robotics.diff [2] http://fedoraproject.org/wiki/PackageMaintainers/CompsXml
/*Rich Mattes richmattes@gmail.com*/ wrote on 01/16/2011 3:23:49 AM +0350:
On 01/13/2011 05:39 PM, Tim Niemueller wrote:
On 13.01.2011 23:34, Rich Mattes wrote:
On Thu, Jan 13, 2011 at 5:15 PM, Tim Niemuellertim@niemueller.de wrote:
On 13.01.2011 23:12, Hedayat Vatankhah wrote:
In anaconda package customization UI, the left column shows categories (Desktop Environment, Applications, Server ...) and the right column shows groups of the selected category. Package groups are organized in comps.xml itself, so there is no need to change anything in the packages themselves.
Ok, Rich, which category is the Robotics Suite in?
The package group was just mixed in, I want to propose a package group specific to robot software, we have quite a few packages to which this could apply.
TimI think we fit best in the Development category. I'm creating a new group inside of the development category for our packages, called Robotics Suite, which will contain the robotics related stuff. I'm just not sure whether or not it makes more sense to list the -devel packages or the base packages for our stuff (or both). For instance, should I include player-devel and/or player? mrpt-devel and/or mrpt? I'm leaning towards including devel packages instead of base ones, since tutorials will probably rely on them at some point.
I agree with the category and I suggest to add both, base and devel packages.
Tim
Please have a look at [1] and see if I missed anything. I've been using [2] as a guide on how to do things; the diff is against the f15-comps file.
Thanks Rich, that looks fine. :)
I also went ahead and adjusted the wiki pages. fp.o/wiki/Robotics is now the showcase page, and fp.o/wiki/SIGs/Robotics now holds the old robotics sig page.
Great!
Good luck, Hedayat
Rich
[1] http://rmattes.fedorapeople.org/comps-robotics.diff [2] http://fedoraproject.org/wiki/PackageMaintainers/CompsXml _______________________________________________ robotics mailing list robotics@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/robotics
robotics@lists.fedoraproject.org
-
Hedayat Vatankhah -
Rich Mattes -
Tim Niemueller