Hi, I would kindly ask you to place an entry in the issue tracker before you start working on something (even if it's not a bug): http://code.google.com/p/moose-technology/issues/list Also, when you add an issue, please make sure to tag it at least with the Component that is affected by it. If you want to work on it, also assign it to yourself. This has the benefit of communicating your intention around and synchronize with the rest of us. If you want to be up to date with the changes in the issue tracker, you can subscribe to the RSS feed: http://code.google.com/feeds/p/moose-technology/issueupdates/basic

On 3 déc. 2009, at 08:57, Tudor Girba wrote: > Hi, > > I would kindly ask you to place an entry in the issue tracker before you start working on something (even if it's not a bug): > http://code.google.com/p/moose-technology/issues/list > > Also, when you add an issue, please make sure to tag it at least with the Component that is affected by it. If you want to work on it, also assign it to yourself. > > This has the benefit of communicating your intention around and synchronize with the rest of us. If you want to be up to date with the changes in the issue tracker, you can subscribe to the RSS feed: > http://code.google.com/feeds/p/moose-technology/issueupdates/basic I was not sure I felt 100% comfortable with that. There are already many things in the bug tracker, some do not feel like bug. For example: 41 Started › [MOOSE] port SCG algorithms to SqMoose simon.denier Todo Feb 2009 Sep 22 4.1 Algos Medium The wiki pages do not work for this task too, unless someone is willing to do some wiki-gardening. So I spent some time this morning to play with google code, see if we could have two tabs of issues, one for defects and enhancements, one for project and long-term goals. We cant. So I spent some more time configuring the issues page, tweaking a few things which annoyed me. From now on: 1) when you create an issue as a developer, the issue is no longer automatically assigned to you. It is created as 'New' without an owner. If you want/start to tackle an issue, first edit it: - mark it as started - put your name as owner so that we know you are working on that I added the column 'Reporter' to see who reported the issue. I also spent some times this morning 'unregistering' myself from issue I cant deal with right now. It means there are lots of 'new' issues now if anyone is willing to take them. I suggest you do the same if you dont want we come after you about issue XXX :) 2) I change a bit the type of issues. In particular, I remove Todo and Task which were fuzzy and add Engineering and Project (I also updated the current issues to mirror that). Basically, Engineering is for any activities related to maintenance, refactoring the source code, enhancing its quality, applying lint rules, conforming to regularities, etc. There is lots to do in this area and unfortunately, no reward. Project is in particular for what Doru suggests, that is long-term projects you undertake, or even more small tasks which are somehow autonomous from the code base. The wizard if a good example of that. Type-Engineering = (Re)engineering the code base to enhance its quality Type-Defect = Report of a software defect Type-Enhancement = Request for enhancement Type-Project = Long-term project or autonomous task Type-Review = Request for a code review Type-Other = Some other kind of issue So next time you enter an issue, *please* take a bit of time to think about the type. I hope it will help us to get a better picture of what is going on in the Moose dev, and where things should be going. -- Simon _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi, I see one problem with the Type-Project: How do you know when you should close it?

For example, now you have a CAnalyzer project, but that is already around. So, CAnalyzer is rather better as a Component tag. Cheers, Doru On 3 Dec 2009, at 15:18, Tudor Girba wrote: > Nice job, Simon. > > Doru > > > On 3 Dec 2009, at 15:11, Simon Denier wrote: > >> >> On 3 déc. 2009, at 08:57, Tudor Girba wrote: >> >>> Hi, >>> >>> I would kindly ask you to place an entry in the issue tracker >>> before you start working on something (even if it's not a bug): >>> http://code.google.com/p/moose-technology/issues/list >>> >>> Also, when you add an issue, please make sure to tag it at >>> least with the Component that is affected by it. If you want >>> to work on it, also assign it to yourself. >>> >>> This has the benefit of communicating your intention around >>> and synchronize with the rest of us. If you want to be up to >>> date with the changes in the issue tracker, you can subscribe >>> to the RSS feed: >>> http://code.google.com/feeds/p/moose-technology/issueupdates/basic >> >> >> >> I was not sure I felt 100% comfortable with that. There are >> already many things in the bug tracker, some do not feel like >> bug. >> For example: 41 Started › [MOOSE] port SCG algorithms to >> SqMoose simon.denier Todo Feb 2009 Sep 22 4.1 Algos Medium >> >> The wiki pages do not work for this task too, unless someone is >> willing to do some wiki-gardening. >> >> >> So I spent some time this morning to play with google code, see >> if we could have two tabs of issues, one for defects and >> enhancements, one for project and long-term goals. We cant. >> >> So I spent some more time configuring the issues page, tweaking >> a few things which annoyed me. >> >> >> From now on: >> >> 1) when you create an issue as a developer, the issue is no >> longer automatically assigned to you. It is created as 'New' >> without an owner. >> If you want/start to tackle an issue, first edit it: >> - mark it as started >> - put your name as owner so that we know you are working on that >> >> I added the column 'Reporter' to see who reported the issue. I >> also spent some times this morning 'unregistering' myself from >> issue I cant deal with right now. It means there are lots of >> 'new' issues now if anyone is willing to take them. I suggest >> you do the same if you dont want we come after you about issue >> XXX :) >> >> >> 2) I change a bit the type of issues. In particular, I remove >> Todo and Task which were fuzzy and add Engineering and Project >> (I also updated the current issues to mirror that). >> >> Basically, Engineering is for any activities related to >> maintenance, refactoring the source code, enhancing its >> quality, applying lint rules, conforming to regularities, etc. >> There is lots to do in this area and unfortunately, no reward. >> >> Project is in particular for what Doru suggests, that is long- >> term projects you undertake, or even more small tasks which are >> somehow autonomous from the code base. The wizard if a good >> example of that. >> >> Type-Engineering = (Re)engineering the code base to enhance its >> quality Type-Defect = Report of a software defect Type- >> Enhancement = Request for enhancement Type-Project = Long-term >> project or autonomous task Type-Review = Request for a code >> review Type-Other = Some other kind of issue >> >> So next time you enter an issue, *please* take a bit of time to >> think about the type. >> >> >> I hope it will help us to get a better picture of what is going >> on in the Moose dev, and where things should be going. >> >> >> -- >> Simon >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > www.tudorgirba.com > > "Every now and then stop and ask yourself if the war you're > fighting is the right one." > > > -- www.tudorgirba.com "We cannot reach the flow of things unless we let go." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev