Hello Bjorn,
(1) A request as already been sent to the webmaster for
removing the CVS code. It should be taken care of shortly (if not
already).
(2) Good reading, thanks. I will do my best to
be a good citizen within the community.
But I
have one question about commiter rights vs contributors.
In
these graphs...
...it
says that "commiters" can write code to CVS and "contributors" must attach their
code in bugzilla for a commiter to review.
Since
I am a commiter on the Babel project, why must I comply with what appears to be
reserved for "contributors"? Is it that there is a different flow
for commiter's initial contributions not illustrated there?
The
rest of my reading also suggest that as a commiter, I was OK to put my code in
(except I was missing an about.html file). This document further
illustrate my understanding:
I am
by no mean trying to be difficult by asking for clarifications. I just
want to make sure I understand fully what is involved in being a commiter (vs a
contributor). Your help is appreciated.
Thank
you,
Pascal
E.
Pascal,
Please (1) remove the code from CVS until it is approved
and (2) familiarize yourself with the rules of being a committer: http://www.eclipse.org/projects/dev_process/index-quick.php
-
Bjorn
Pascal Essiembre wrote:
Oups, no I was not aware. By contributed I meant
that I have put my code in CVS.
Sorry for not being fully aware of all processes involved
into being an Eclipse commiter. This is a new experience to
me. I have just filled in the IP Policy (Contribution
Questionnaire). Please let me know if I am missing anything
else.
Thank you,
Pascal E.
Pascal,
Can
you explain a little more about what you mean by you “…have contributed …
code…”?
I
assume that you’re aware that new code needs to go through the IP review
process? Since Babel is incubating, it gets to use the parallel IP process.
I
have contributed my code in progress for the RessourceBundle
Editor.
Rather than being a
straight port of the SourceForge project coming
from...
... the code
actually comes from a rewrite of it that was already in progress (it was
agreed
in an early
conference call I would commit the rewrite work and not the stable one
found
As such it is not
nearly as stable or complete yet as the one on SourceForge.
One can
refer to the original SourceForge "ResourceBundle Editor" plugin to
get
a better feel for it until this one gets
fixed/completed.
It is heavily being
worked on and far from being "clean" code yet. It was
put in CVS at
this early stage so people can see it in action and monitor
progress.
Once as mature as
its SourceForge equivalent, I will make sure to let everyone
know.
_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev