[Rmof-users] RMOF - new version?
Jesús Sánchez Cuadrado
jesusc at um.es
Fri Mar 30 04:45:57 EDT 2007
El Viernes, 30 de Marzo de 2007 10:15, Jim Steel escribió:
> Hi guys,
> I've been quickly scanning the changes to try and understand them. For
> the most part, the reorganisation into directories seems pretty good.
> I have a couple of questions though:
> - Has the core changed from EMOF to ECore? If so, is there a reason why?
There is no particular reason. In fact, my initial idea was to define a "duck
typed interface" in order to have two cores: emof and ecore. This is a TODO
task. I think that is not the same to parse an ecore file using the emof
meta-metamodel (for instance, what about the eAnnotations).
To develop the EMOF core your previous code should be enough, with some
> - Did the Editor get lost in the migration process?
Unfortunately, yes :-(
We need to adapt the editor code to the new structure. I think Antonio is in
charge of this issue (see a previous mail from him).
> On 3/28/07, Antonio S. de A. Terceiro <terceiro at dcc.ufba.br> wrote:
> > Jesús Sánchez Cuadrado escreveu isso aí:
> > > Great! We can start working with the code :-)
> > >
> > > One question about how to handle bugs and new features. I have found a
> > > bug in the serializer, so what should I do? Shall I create a new ticket
> > > in rmof.rubyforge.org and then try to fix it? I think this is the usual
> > > way, but it's my first time in a project with several people, so...
> > >
> > > If one of us come up with a new feature, what will be the procedure?
> > > Maybe sending a message to the list or a new ticket?
> > I think that the best thing to do is always to use the rubyforge tools,
> > for both bugs and features. If a new person says "hi, I want to help"
> > we'll have a place to point and say "nice, you could start fixing this
> > bugs or implementing those features". Besides, using the tools adds
> > some structure to the workflow and will provide us relevant
> > information about the project in the future.
> > Off course, discussing in the mailing list is by far much more practical
> > than using a web interface to tickets, but after the issue is
> > solved/discussed one could post on the ticket pointing to the mailing
> > list thread for reference.
> > It seems that one needs to be project admin to configure the monitoring
> > for the tickets, it would be nice if we can configure the mailing list
> > to monitor the tickets (i.e. everytime someone opens a ticket, the
> > mailing list is notified).
> > --
> > Antonio S. de A. Terceiro <terceiro at dcc.ufba.br>
> > GnuPG ID: E6F73C30
> > _______________________________________________
> > Rmof-users mailing list
> > Rmof-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rmof-users
> Rmof-users mailing list
> Rmof-users at rubyforge.org
More information about the Rmof-users