Hi,
while waiting for some tests to finish, I drew this up: http://www.karan.org/stuff/c5-release-plan.jpeg
its no where near complete, at the moment it has perhaps half of all the things that need doing. But overall it should give people an idea on what happens. Now for the questions:
- Whats good way to publish something like this so it does not get in the way. For the people who need to keep it going, as well as for people looking for info.
- How might one factor in timetaken or things. One option is that we just dont do that for one release, then use the timings from that release for estimates on the next release - hopefully getting better and more accurate in a few cycles like that.
- does anyone know of a non-java based ( flash is fine ) mindmap renderer that could get its data from a db ( so more than 1 person can edit things and we could use the same data at other places as well )
Dear Karan.
while waiting for some tests to finish, I drew this up: http://www.karan.org/stuff/c5-release-plan.jpeg
Thanks for that. You're great :)
its no where near complete, at the moment it has perhaps half of all the things that need doing. But overall it should give people an idea on what happens. Now for the questions:
- Whats good way to publish something like this so it does not get in
the way. For the people who need to keep it going, as well as for people looking for info.
I was thinking about a build infrastructure category on the wiki holding that kind of documentation (as well as others, like build instructions/scripts ...)
Best Regards Marcus
Marcus Moeller napsal(a):
I was thinking about a build infrastructure category on the wiki holding that kind of documentation (as well as others, like build instructions/scripts ...)
Marcus, I think that build infrastructure category on the wiki is good place to start. - it can help the others to understand the whole rebuild process - one can use tips and scripts to create own rpm build infrastructure - users can share their knowledge on mock, plague, koji - ...
Thanks, David Hrbáč
On Fri, Sep 18, 2009 at 5:48 AM, Karanbir Singh mail-lists@karan.org wrote:
while waiting for some tests to finish, I drew this up: http://www.karan.org/stuff/c5-release-plan.jpeg
its no where near complete, at the moment it has perhaps half of all the things that need doing. But overall it should give people an idea on what happens. Now for the questions:
- Whats good way to publish something like this so it does not get in
the way. For the people who need to keep it going, as well as for people looking for info.
- does anyone know of a non-java based ( flash is fine ) mindmap
renderer that could get its data from a db ( so more than 1 person can edit things and we could use the same data at other places as well )
I haven't seen any multi-user mindmap apps. So I think the best alternative would be the wiki. But that isn't graphical of course, then again it is already running and is multi-user.
- How might one factor in timetaken or things. One option is that we
just dont do that for one release, then use the timings from that release for estimates on the next release - hopefully getting better and more accurate in a few cycles like that.
I see no problem in just releasing all the steps to the public, even without timestampts or estimates. We can add those after this release.
Regards, Tim
On 09/18/2009 04:42 PM, Tim Verhoeven wrote:
I haven't seen any multi-user mindmap apps. So I think the best alternative would be the wiki. But that isn't graphical of course, then again it is already running and is multi-user.
Its way too hard and time consuming ( for me, maybe i am dim ) to do these kind of things on the wiki :/
perhaps just a jpeg export and embedd into a page somewhere.
on the other hand, a git repo somewhere with the xml's that go into the mindmap. For now, I am inclined to take the lazy route and solve individual issues as they come up.
I see no problem in just releasing all the steps to the public, even without timestampts or estimates. We can add those after this release.
thats interesting... I was actually hoping to programatically update something like this so people know what thread was at what stage at any given time.
On Fri, Sep 18, 2009 at 5:47 PM, Karanbir Singh mail-lists@karan.org wrote:
On 09/18/2009 04:42 PM, Tim Verhoeven wrote:
I haven't seen any multi-user mindmap apps. So I think the best alternative would be the wiki. But that isn't graphical of course, then again it is already running and is multi-user.
Its way too hard and time consuming ( for me, maybe i am dim ) to do these kind of things on the wiki :/
perhaps just a jpeg export and embedd into a page somewhere.
on the other hand, a git repo somewhere with the xml's that go into the mindmap. For now, I am inclined to take the lazy route and solve individual issues as they come up.
I see no problem in just releasing all the steps to the public, even without timestampts or estimates. We can add those after this release.
thats interesting... I was actually hoping to programatically update something like this so people know what thread was at what stage at any given time.
Isn't trac capable of this timeline and project management stuff ? I've seen it a couple of times but never done/used it myself.
Regards, Tim
Karanbir Singh wrote:
Hi,
while waiting for some tests to finish, I drew this up: http://www.karan.org/stuff/c5-release-plan.jpeg
its no where near complete, at the moment it has perhaps half of all the things that need doing. But overall it should give people an idea on what happens. Now for the questions:
- Whats good way to publish something like this so it does not get in
the way. For the people who need to keep it going, as well as for people looking for info.
- How might one factor in timetaken or things. One option is that we
just dont do that for one release, then use the timings from that release for estimates on the next release - hopefully getting better and more accurate in a few cycles like that.
Last time I asked, some years ago, I think someone@redhat.com suggested mrproject.
That was about the timeframe mentioned here: http://dag.wieers.com/rpm/packages/mrproject/ According to this http://wiki.linuxquestions.org/wiki/MrProject it vanished into gnome office, then got dropped. Does gnome have anything to replace it?
I once attended a project management course. The little I remember now boils down to, at least in the planning stage, a small committee is good. 4-6 people. A small group will give better results one person.
Write down the necessary steps, Argue about them until you agree the list is "more or less done."
Decide what order tasks need to be completed. Some can be in parallel - eg much package building. Augue over that until the order seems right.
Argue about how long they will take to do. When done, add a fudge factor.
Publish the lot as "best guestimate." I think you need some software such as planner (I think KDE has something too), and ideally it allows remote, shared access for updating, but if not appoint a secretary and deputy secretary and be sure both can get to the important files. Heck, let tout le monde have read access to the files, argue when/if needed if the "right" person is not available to update the master copy.
Probably, some tasks can be spun off into their own projects.
John Summerfield wrote:
Karanbir Singh wrote:
Hi,
while waiting for some tests to finish, I drew this up: http://www.karan.org/stuff/c5-release-plan.jpeg
Last time I asked, some years ago, I think someone@redhat.com suggested mrproject.
That was about the timeframe mentioned here: http://dag.wieers.com/rpm/packages/mrproject/ According to this http://wiki.linuxquestions.org/wiki/MrProject it vanished into gnome office, then got dropped. Does gnome have anything to replace it?
Here is another list http://www.linuxlinks.com/article/200904102027568/ProjectManagement.html
Am Dienstag, den 22.09.2009, 03:40 +0200 schrieb John Summerfield:
Karanbir Singh wrote:
Hi,
while waiting for some tests to finish, I drew this up: http://www.karan.org/stuff/c5-release-plan.jpeg
its no where near complete, at the moment it has perhaps half of all the things that need doing. But overall it should give people an idea on what happens. Now for the questions:
- Whats good way to publish something like this so it does not get in
the way. For the people who need to keep it going, as well as for people looking for info.
- How might one factor in timetaken or things. One option is that we
just dont do that for one release, then use the timings from that release for estimates on the next release - hopefully getting better and more accurate in a few cycles like that.
Last time I asked, some years ago, I think someone@redhat.com suggested mrproject.
That was about the timeframe mentioned here: http://dag.wieers.com/rpm/packages/mrproject/ According to this http://wiki.linuxquestions.org/wiki/MrProject it vanished into gnome office, then got dropped. Does gnome have anything to replace it?
financial.com AG
Munich head office/Hauptsitz München: Maria-Probst-Str. 19 | 80939 München | Germany Frankfurt branch office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt | Germany Management board/Vorstand: Dr. Steffen Boehnert (CEO/Vorsitzender) | Dr. Alexis Eisenhofer | Dr. Yann Samson | Matthias Wiederwach Supervisory board/Aufsichtsrat: Dr. Dr. Ernst zur Linden (chairman/Vorsitzender) Register court/Handelsregister: Munich – HRB 128 972 | Sales tax ID number/St.Nr.: DE205 370 553
On 09/22/2009 02:40 AM, John Summerfield wrote:
I once attended a project management course. The little I remember now boils down to, at least in the planning stage, a small committee is good. 4-6 people. A small group will give better results one person.
Not sure what any of that hasto do with the original email :)
I'm looking for optiions for publishing the state of a task as it works its way through different milestones. It needs to be : - clear - exact - automateable - visual
And if its something that needs me to go poking around in things - I'm not going to use it, or I will forget about it etc. Hence the requirement for the automateable.
The search is still on for something that is open source and while I dont mind something that is purely web based, I'd prefer something that didnt need an interweb's connection.
- KB
Karanbir Singh wrote:
On 09/22/2009 02:40 AM, John Summerfield wrote:
I once attended a project management course. The little I remember now boils down to, at least in the planning stage, a small committee is good. 4-6 people. A small group will give better results one person.
Not sure what any of that hasto do with the original email :)
I'm looking for optiions for publishing the state of a task as it works its way through different milestones. It needs to be :
- clear
- exact
- automateable
- visual
And if its something that needs me to go poking around in things - I'm not going to use it, or I will forget about it etc. Hence the requirement for the automateable.
There's no possibility that you will escape data entry. If you kept reading, you would see I suggested actual products, and that Christoph identified that mrproject, while renamed, isn't dead and lives on in the Gnome project.
It's up to you to assess it, the program's description suggests it does what you say you want.
The search is still on for something that is open source and while I dont mind something that is purely web based, I'd prefer something that didnt need an interweb's connection.
- KB
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On 09/22/2009 01:48 PM, John Summerfield wrote:
There's no possibility that you will escape data entry.
:(
I have about 40% of the work done to make the process 'measureable'. I guess what would be ideal is if the test / run scripts can do some of the data points as a part of their routine.
- KB
Karanbir Singh wrote:
On 09/22/2009 02:40 AM, John Summerfield wrote:
I once attended a project management course. The little I remember now boils down to, at least in the planning stage, a small committee is good. 4-6 people. A small group will give better results one person.
Not sure what any of that hasto do with the original email :)
I'm looking for optiions for publishing the state of a task as it works its way through different milestones. It needs to be :
- clear
- exact
- automateable
- visual
And if its something that needs me to go poking around in things - I'm not going to use it, or I will forget about it etc. Hence the requirement for the automateable.
The search is still on for something that is open source and while I dont mind something that is purely web based, I'd prefer something that didnt need an interweb's connection.
The output side is probably going to involve graphviz. Maybe you could use one of the manual layout tools like dotty for the process with some tokens for the status/times so you could substitute real values to render periodically.
-
Christoph Maser -
David Hrbáč -
John Summerfield -
Karanbir Singh -
Les Mikesell -
Marcus Moeller -
Tim Verhoeven