[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [remus-dev] [Remus] - Confirmation of SourceCode Contribution
|
> When do you plan to make a nightly build of your RCP app,
> so that I could make tests in the real environment ?
In the next 2 weeks.
> Bugs regarding the framework to Eclipse Bugzilla;
> Bugs regarding the sourceforge components to Jira ! Is that right ?
Absolutely.
Cheerz
Tom
Von: Andreas Deinlein [mailto:dev.deasw@xxxxxxxxxxxxxx]
Gesendet: Dienstag, 28. September 2010 19:18
An: Tom Seidel
Cc: remus-dev@xxxxxxxxxxx
Betreff: Re: [Remus] - Confirmation of SourceCode Contribution
2010/9/28 Tom Seidel <tom.seidel@xxxxxxxxxxxxxxxxxx>
Hi Andreas,
Damn, youve got long vacations ;)
Yes, that's true. The vacations were only a smaller part of it !
For the committer agreement, can you ask the emo team (emo@xxxxxxxxxxx) how
to proceed with the issue, that you want to register as individual
committer, Im pretty sure that this is possible, but I dont know the
details. Although you dont have so much time for working on the project Id
prefer you as a committer, not a contributor. As a contributor you also have
to do the whole paperwork (the agreements) but you dont have any
write-access to the repository, that means you have to attach patches to a
bug, which is not very comfortable, IMHO. Everything becomes easier if
youre a committer, and it is not relevant (at least for me) how much time
you work on different issues.
For the architecture. Youre observation is correct, Ive splitted the
sources:
- The framework to build applications for information units
- A collection of information units and connectors
The reason for that is an organizational one: The information units and
connectors tend to use a lot of third-party-bundles which can change very
often (especially for connectors) e.g. the twitter api changes every 2
month. If we host this connectors at eclipse.org referencing or updating a
third-party-bundle requires the whole review-process of the Eclipse IP Team.
Additionally these bundles are typically not made to be consumed as base for
another application. Another thing is that we dont get the icons approved,
but I love these icons and think theyre very important for a good
user-acceptance (there are not good free icons available). I think this
separation is also good to separate the user-base. The eclipse.org code is
used for other developers which want to build applications based on that
framework, The other sources, hosted at sourceforge are for the non-techis
which want to use the built product. My hope is to attract developers inside
the Eclipse community to get the underlying components (like the
synchronization) more stable.
Ive updated all information types and connectors at sourceforge; they are
all referencing now the org.eclipse.remus bundles, so you can already test
and If you find bugs (I remember that you had issues with the
synchronization) you can open a bug at bugs.eclipse.org and attach a patch.
Bugs regarding the framework to Eclipse Bugzilla; Bugs regarding the
sourceforge components to Jira ! Is that right ?
Cheerz
Tom
PS: Ive posted this message at the remus-dev mailing list. Id suggest,
that you register at this list
(https://dev.eclipse.org/mailman/listinfo/remus-dev) and use this as primary
communication channel to keep the communication transparent.
Von: Andreas Deinlein [mailto:dev.deasw@xxxxxxxxxxxxxx]
Gesendet: Montag, 27. September 2010 20:31
An: Tom Seidel
Betreff: Re: [Remus] - Confirmation of SourceCode Contribution
Hi Tom,
sorry for my late answer - I was on vacation !
Congratulations that you have committed the first code to Eclipse.
i could confirm the statements below, except the copyright owner. I have
done this contributions in my spare time, independent of Siemens. I would
say i am the copright owner.
You mean that I have to write something different then "Remus Software" in
the copyright owner ! I have done this on sourceforge !
By the way, I still did not have the comitter agreement from Siemens. And i
must admit, that I do not have enough time at the moment to really help you
with the project, because of my current job situation ! Nevertheless, i am
still very interested in Remus and i am still using it. Maybe I could act as
"Contributor" for a while ! When you have a first version based on eclipse,
I am looking forward to test the new version.
I had a first look at the Eclipse archive ! Is your plan, that the eclipse
bundles provide only a framework, whereas extensions (e.g. connectors) and
your RCP application is still located on sourceforge ?
Best regards
Andreas Deinlein
2010/8/26 Tom Seidel <tom.seidel@xxxxxxxxxxxxxxxxxx>
Hi Andreas,
Good news: We made progress to commit the initial version of Remus. The last
step is that you confirm that the contributed code you've written in the
rating bundle is authored 100% by your own. The Eclipse IP Team needs a
confirmation of the following:
-------------------
1. Andreas authored 100% of the content contributed to the Remus project
2. Andreas had the rights to contribute the content
3. The content was contributed under the EPL
4. The copyright owner is Siemens
Assuming all four above are confirmed, you will need to modify the copyright
holder information on the following files (including any others that Andreas
may have contributed to):
RatingOverviewDialog.java
RatingOutline.java
RatingActivator.java
-------------------
Can you give me please feedback regarding this issue? - I've added Sharon
from the Eclipse IP Team as CC.
Regards
Tom Seidel, Dipl.-Ing.
Independent Eclipse-Developer
mail tom.seidel@xxxxxxxxxxxxxxxxxx
web http://www.remus-software.org
blog http://www.richclient2.eu
twitter http://www.twitter.com/tmseidel