There are two aspects here:
- First, we (Benoît Langlois, Pierre Gaufillet, Raphaël Faudou and myself) started to think about the content of a Top Level Project proposal for Polarsys and how to split the TLP in several sub-projects that contain leaf projects. We just need a bit more formalization before we can send this information to the list. I hope that we will send it to the liste for comment by the end of this week.
- Second, I understand that the request from Jorge is only about the "test" infrastructure that is under use by the OPEES members. I don't know wht is the best way to address this point: the projects being handled on this alpha infrastructure will need to go through the formal Polarsys creation process before they move to the official Polarsys process. As such, the split of the projects in sub components will be addressed during this project proposal phase.
I suggest we discuss thi topic during the Polarsys telco on Wednesday at 17:00 (Paris time).
Hope this helps.
Regards,
Gaël Blondelle
Le 22/06/12 17:03, Wayne Beaton a écrit :
The structure of Bugzilla naturally follows the project layout.
Top-level projects are represented as as Bugzilla classification.
Projects are represented as Bugzilla products
Functional areas within a project are represented as Bugzilla components
I think this will serve your needs.
We need to start defining one or more top-level projects for Polarsys. I can help with this. Top-level projects define categories of projects. Perhaps we might go with something along the lines of "Tools", "Runtimes", etc. Or maybe TopCased is a top-level project with subprojects defining independent bits of the technology. I don't have answers to these questions. I can help you build the charter [1], but you will have to sort out the overall organization (with my help).
Who can take the lead on defining the overall project structure?
Wayne
[1] http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.1.php
On 06/22/2012 08:21 AM, Rodríguez Vázquez, Jorge Juan wrote:Hello again, Denis and all.
Let me try to explain it, as I’ve been clearly unclear the first time:
Polarsys, brainchild of the OPEES project, will be a repository of software tools, all of them having certain features. There are a number of tools which are currently being upload such as Papyrus, Moskitt4Me, Topcased, etc.
We at OPEES think that each tool should have some identification within Bugzilla: If I want to report a bug in Topcased, I go to the page https://polarsys.org/bugs/enter_bug.cgi , I choose “Topcased” from the available options, and then I go on.
However, there are quite a few tools to be uploaded to Polarsys. The list includes those that I am aware of, but I expect new tools to join the repository soon. Some partners have already contacted me because they want to report bugs (or test Bugzilla) for their tools, including ArCon, BIT and others.
Alternatively, Mr. Roy the webmaster may have a different idea on how to do this without creating a lot of new lines in the Bugzilla screen.
When I told you about the “right column”, I was referring to the layout of the page: The left column is made of hyperlinks which do not accept spaces (“TestProduct”), while the right column includes descriptions and allow spaces in the full name of the tool (“This is a test product”). The names I gave were for the “right column”, but the spaces and special characters should be edited to create the links.
I’m attaching two screenshots, one of the current layout of the screen, and the other with all the tools that I think should be included.
Regards,
Jorge J. Rodríguez Vázquez
Researcher
Technological Innovation
Centers of Excellence
c/Anabel Segura, 7
28108 Alcobendas, Madrid
Spain
T +34 914 807 929
jjrodriguezv@xxxxxxxx
www.indracompany.com
![indra]()
De: polarsys-infra-bounces@xxxxxxxxxxx [mailto:polarsys-infra-bounces@xxxxxxxxxxx] En nombre de Denis Roy
Enviado el: jueves, 21 de junio de 2012 20:49
Para: polarsys-infra@xxxxxxxxxxx
Asunto: Re: [polarsys-infra] new products for Bugzilla
Jorge,
Apologies for the delay in responding.
Bugzilla uses a Product->Component model, and at Eclipse the Product typically identifies the Project.
Are all the items below Polarsys Projects? If so, I need to create at least one "component" under each project. This could be as simple as "Core" or it could actually be two or three components to allow better bug classification.
Please confirm how you wish to structure the list below.
Also, in your email you state "but I give you the full names for the right column"; however, I do not see a right column.
Again, please confirm.
Thanks,
Denis
On 06/18/2012 03:41 AM, Rodríguez Vázquez, Jorge Juan wrote:
To the attention of the webmaster in charge of the Bugzilla instance of the Polarsys infrastructure.
I'm writing you in representation of the OPEES Project.
It is the idea of Polarsys that users should be able to upload bugs regarding any of the projects (or"components") uploaded to Polarsys. However, when I currently go to the list of projects https://polarsys.org/bugs/enter_bug.cgi , a number of components are missing.
I'd like you, as a webmaster, to create these new products with the following names, at your convenience.
AADL co-modeler
Acceleo
ArCon
ATL
BIT
EGF
EMF
FRAMA-C
GeneAuto
GeneAuto UI
GMF
Kermeta
ModMap
SMP2
UNISIM
I expect that the space'll be removed in the left column, but I give you the full names for the right column.
I'd appreciate if you keep me informed about progress in this activity.
Thank you for your time,
Regards,
Jorge J. Rodríguez Vázquez
Researcher
Technological Innovation
Centers of Excellence
c/Anabel Segura, 7
28108 Alcobendas, Madrid
Spain
T +34 914 807 929
jjrodriguezv@xxxxxxxx
www.indracompany.com
![indra]()
Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, contiene información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. Si no es vd. el destinatario indicado, queda notificado que la lectura, utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. En el caso de haber recibido este correo electrónico por error, se ruega notificar inmediatamente esta circunstancia mediante reenvío a la dirección electrónica del remitente.
Evite imprimir este mensaje si no es estrictamente necesario.
This email and any file attached to it (when applicable) contain(s) confidential information that is exclusively addressed to its recipient(s). If you are not the indicated recipient, you are informed that reading, using, disseminating and/or copying it without authorisation is forbidden in accordance with the legislation in effect. If you have received this email by mistake, please immediately notify the sender of the situation by resending it to their email address.
Avoid printing this message if it is not absolutely necessary.
_______________________________________________ polarsys-infra mailing list polarsys-infra@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/polarsys-infra
_______________________________________________ polarsys-infra mailing list polarsys-infra@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/polarsys-infra
