If I understand correctly, the tag is used to denote the component. In the case of Moose we have multiple of these sub-components and somehow they would need to be captured. Looking at the existing tracker, we have the categories as listed below.

Perhaps this would pollute too much the Pharo space?

Component-MooseCore�

Component-Famix � ��

Component-SmalltalkImporter

Component-RPackage �

Component-Mondrian � = Visualization engine

Component-Roassal � �= Visualization engine

Component-Glamour ��

Component-Glamour-Seaside

Component-Algos � ��

Component-Fame � � �

Component-Finder � � = Issue relates to program UI

Component-Install � �= Utility and installation scripts

Component-Docs � � � = Issue relates to end-user documentation

Component-MooseTools

Component-ExternalTools = External tools such as inFusion, srcML, VerveineJ

Component-Test � � �

Component-CAnalyzer �= FAMIX extension dedicated to C

Component-DSM � � ��

Component-SmallDude�

Component-XML � � � �= XMLParser and Pastell (XPath query facility)

Component-Spy � � � �= The Spy profiling framework

Component-Hapao � � �= The Hapao test coverage tool

Component-PetitParser

Component-AutoMoose�

Component-Arki � � �

Component-VerveineJ�

Component-VerveineCSharp

Component-EyeSee � �

Component-Metanool �

Component-GlamorousToolkit

Cheers,

Doru

On Fri, May 31, 2013 at 1:33 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:

We could create a tag for moose without problem I guess.

I will let the experts answer.

Stef

Hi,

Would it be possible and desired, to open the Pharo fogbugz infrastructure for other related projects?

Namely, I am thinking of Moose, in particular given that various issues are directly relevant for Pharo as well? For projects like Moose, this would imply less costs. The question is if something in this direction is even desired.

Cheers,

Doru

--

www.tudorgirba.com

"Every thing has its own flow"

--

www.tudorgirba.com

"Every thing has its own flow"