[prev in list] [next in list] [prev in thread] [next in thread]
List: subclipse-dev
Subject: Re: [Subclipse-dev] Submitting Subclipse as project to Eclipse.org
From: "Johan Compagner" <jcompagner () gmail ! com>
Date: 2006-06-30 20:54:54
Message-ID: 2e1ce7cd0606301354h20cdbe80m9b3764050a54c331 () mail ! gmail ! com
[Download RAW message or body]
you got my approval to change the license to what is needed for eclipse for
the code i sent in.
I can contribute stuff if needed or wanted. But the current way (sending
patches) is fine by me.
johan
On 6/30/06, Mark Phippard <markp@softlanding.com> wrote:
>
> I have had a lot of off-line conversations with Brock and a few others
> about submitting a proposal to Eclipse to create an SVN Team Provider
> based on Subclipse. At the time, I was not sure if I was going to be able
> to devote the time required to create the proposal and lead the effort and
> no one else has come forward to do so. Things have changed for the better
> for me, so I can now safely do this and would like to.
>
> I think one of the strengths of Subclipse is our community and the diverse
> group of individuals that have made contributions. Subclipse is not the
> result of the effort of one person or one company. I would like to
> continue this tradition as we begin this process and do everything out in
> the open. When I have the proposal to a good enough stage to call it a
> rough draft I will commit it into our repository and post the URL and
> checkout information to this list. That way it will be easier to work on
> this proposal in a collaborative manner.
>
> In the meantime it would be useful to know who would like to participate
> in this project and be listed in the proposal? Myself, and some of my
> coworkers that have contributed behind the scenes will be listed. Brock
> has agreed to be listed. What about others? Martin, Eugene, Johan,
> others? This would be a good time for all with interest to come forward.
>
> Another issue is going to be the license. We will need to get approval
> from everyone that has contributed code to have their code re-licensed
> under the EPL. The EPL is virtually identical to the CPL license we use
> for Subclipse, and is very similar in intent to the Apache license we use
> in svnClientAdapter. So I am not anticipating any difficulties in this
> area. If you have contributed code to this project, it would be helpful
> if you send an email to the list stating your
> approval/disapproval/concerns about this. The mailing list can then serve
> as a record of your intent.
>
> Aside from all of this, I will also be interested in your comments about
> this. I know a lot of people will be in favor of it, but if you have
> concerns, please share them. Subclipse has become very stable and I think
> the list of things we need or would like to do has become small and
> manageable enough that this is the right time to do this. I did not want
> to do this before we got past the 1.0 stage because I did not want to
> divert that process. We have now given our users a stable and
> feature-rich release, and are close to releasing a second major release
> aimed at Eclipse 3.2. So this is probably a point in time where we can
> afford to spend refactoring package and class names and dealing with
> license issues.
>
> Thanks
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>
[Attachment #3 (text/html)]
you got my approval to change the license to what is needed for eclipse for the code \
i sent in.<br><br>I can contribute stuff if needed or wanted. But the current way \
(sending patches) is fine by me.<br><br><br>johan<br><br> <br><div><span \
class="gmail_quote">On 6/30/06, <b class="gmail_sendername">Mark Phippard</b> <<a \
href="mailto:markp@softlanding.com">markp@softlanding.com</a>> \
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I have had a lot of \
off-line conversations with Brock and a few others<br>about submitting a proposal to \
Eclipse to create an SVN Team Provider<br>based on Subclipse. At the time, \
I was not sure if I was going to be able <br>to devote the time required to create \
the proposal and lead the effort and<br>no one else has come forward to do \
so. Things have changed for the better<br>for me, so I can now safely do \
this and would like to.<br><br> I think one of the strengths of Subclipse is our \
community and the diverse<br>group of individuals that have made \
contributions. Subclipse is not the<br>result of the effort of one person \
or one company. I would like to <br>continue this tradition as we begin \
this process and do everything out in<br>the open. When I have the \
proposal to a good enough stage to call it a<br>rough draft I will commit it into our \
repository and post the URL and <br>checkout information to this \
list. That way it will be easier to work on<br>this proposal in a \
collaborative manner.<br><br>In the meantime it would be useful to know who would \
like to participate<br>in this project and be listed in the \
proposal? Myself, and some of my <br>coworkers that have contributed \
behind the scenes will be listed. Brock<br>has agreed to be \
listed. What about others? Martin, Eugene, \
Johan,<br>others? This would be a good time for all with interest to come \
forward. <br><br>Another issue is going to be the license. We will need to \
get approval<br>from everyone that has contributed code to have their code \
re-licensed<br>under the EPL. The EPL is virtually identical to the CPL \
license we use <br>for Subclipse, and is very similar in intent to the Apache license \
we use<br>in svnClientAdapter. So I am not anticipating any difficulties \
in this<br>area. If you have contributed code to this project, it would be \
helpful <br>if you send an email to the list stating \
your<br>approval/disapproval/concerns about this. The mailing list can \
then serve<br>as a record of your intent.<br><br>Aside from all of this, I will also \
be interested in your comments about <br>this. I know a lot of people will \
be in favor of it, but if you have<br>concerns, please share \
them. Subclipse has become very stable and I think<br>the list of things \
we need or would like to do has become small and <br>manageable enough that this is \
the right time to do this. I did not want<br>to do this before we got past \
the 1.0 stage because I did not want to<br>divert that process. We have \
now given our users a stable and<br>feature-rich release, and are close to releasing \
a second major release <br>aimed at Eclipse 3.2. So this is probably a \
point in time where we can<br>afford to spend refactoring package and class names and \
dealing with<br>license \
issues.<br><br>Thanks<br><br>Mark<br><br><br>---------------------------------------------------------------------
<br>To unsubscribe, e-mail: <a \
href="mailto:dev-unsubscribe@subclipse.tigris.org">dev-unsubscribe@subclipse.tigris.org</a><br>For \
additional commands, e-mail: <a \
href="mailto:dev-help@subclipse.tigris.org">dev-help@subclipse.tigris.org \
</a><br><br></blockquote></div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic