imp-devhttp://dev.eclipse.org/mhonarc/lists/imp-dev/maillist.html
imp-deven-usFri, 28 Jun 2013 21:50:04 GMTFri, 28 Jun 2013 21:50:04 GMThttp://blogs.law.harvard.edu/tech/rssMHonArc RSS 2.0 RCFilewebmaster@eclipse.org (Webmaster)webmaster@eclipse.org (Webmaster)imp-devhttp://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpghttp://dev.eclipse.org/mhonarc/lists/imp-dev/maillist.html
Re: [imp-dev] [eclipse.org-members-committers] Reminder: Membership Meeting Tomorrow...and this one is importanthttp://dev.eclipse.org/mhonarc/lists/imp-dev/msg00498.html
Thanks Wayne. We have something to think about though. The process is being optimized!On Thursday, June 27, 2013, Wayne Beaton &lt;wayne@xxxxxxxxxxx&gt; wrote:&gt; With the social coding initiative, the Eclipse Foundation continues to act as the gate keeper for com...Thanks Wayne. We have something to think about though. The process is being optimized!

On Thursday, June 27, 2013, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:> With the social coding initiative, the Eclipse Foundation continues to act as the gate keeper for commit rights and all contributions will continue to be subject to the Eclipse Foundation's IP Due Diligence process.
>> HTH,>> Wayne>> On 06/22/2013 12:41 PM, Robert Fuhrer wrote:>> Well, as I recall, we also went to github to gain more control (read: a lighter-weight process) over source control repository commits/committers. I'm not sure whether the latest changes affect that. I.e., if eclipse.org still needs to retain control over who gets commit rights, and how community-supplied contributions are vetted, then moving to github still makes sense to me.
> On Jun 20, 2013, at 2:04 PM, Jurgen Vinju <jurgen@xxxxxxxxx> wrote:>> So we went to github to get social, and now eclipse goes there too. What does this mean for us?
> —> Sent from Mailbox for iPhone>> ---------- Forwarded message ----------> From: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
> Date: Thu, Jun 20, 2013 at 5:35 PM> Subject: [eclipse.org-members-committers] Reminder: Membership Meeting Tomorrow...and this one is important> To: "Eclipse Membership and Committer List" <eclipse.org-members-committers@xxxxxxxxxxx>
>> All,>> >> This week the Eclipse Foundation has announced two very significant changes. These are important to Eclipse, and are important to all of you who work on or consume Eclipse technology.
>> >> 1. The Eclipse Foundation has started using Contributor License Agreements.> blog: http://mmilinkov.wordpress.com/2013/06/17/eclipse-clas-are-live/
>>> 2. The Eclipse Foundation will start to allow its projects to host their day-to-day development on social coding sites such as GitHub and Bitbucket.> blog: http://mmilinkov.wordpress.com/2013/06/20/embracing-social-coding-at-eclipse/
> FAQ: http://www.eclipse.org/org/SocialCodingFAQ.php>> >> I will be spending a significant amount of time discussing these topics in our Membership call tomorrow at 11:30am Eastern, 8:30am Pacific, 17:30 CET (with apologies to our European members). Please join the call.
>> >> Here is the full agenda:>> --> Wayne Beaton> Director of Open Source Projects, The Eclipse Foundation> Learn about Eclipse Projects> </mail/u/0/s/?view=att&th=13f8395287f9dd68&attid=0.0.1.1&disp=emb&zw&atsh=1>

With the social coding initiative, the Eclipse Foundation continues
to act as the gate keeper for commit rights and all contributions
will continue to be subject to the Eclipse Foundation's IP Due
Diligence process.

HTH,

Wayne

On 06/22/2013 12:41 PM, Robert Fuhrer
wrote:

Well, as I recall, we also went to github to gain more
control (read: a lighter-weight process) over source control
repository commits/committers. I'm not sure whether the latest
changes affect that. I.e., if eclipse.org still needs to
retain control over who gets commit rights, and how
community-supplied contributions are vetted, then moving to
github still makes sense to me.

I will be spending a significant
amount of time discussing these topics in our
Membership call tomorrow at 11:30am Eastern, 8:30am
Pacific, 17:30 CET (with apologies to our European
members). Please join the call.

Well, as I recall, we also went to github to gain more control (read: a lighter-weight process) over source control repository commits/committers. I'm not sure whether the latest changes affect that. I.e., if eclipse.org still needs to retain control over who gets commit rights, and how community-supplied contributions are vetted, then moving to github still makes sense to me.

I will be spending a significant amount of time discussing these topics in our Membership call tomorrow at 11:30am Eastern, 8:30am Pacific, 17:30 CET (with apologies to our European members). Please join the call.

]]>Sat, 22 Jun 2013 16:41:43 GMThttp://dev.eclipse.org/mhonarc/lists/imp-dev/msg00496.htmlrmfuhrer@xxxxxxx (Robert Fuhrer)[imp-dev] Fwd: [eclipse.org-members-committers] Reminder: Membership Meeting Tomorrow...and this one is importantâhttp://dev.eclipse.org/mhonarc/lists/imp-dev/msg00495.html
So we went to github to get social, and now eclipse goes there too. What does this mean for us?&#xC2;&#xE2;Sent from Mailbox for iPhone---------- Forwarded message ----------From: Mike Milinkovich &lt;mike.milinkovich@xxxxxxxxxxx&gt; Date: Thu, Jun 20, 2013 at 5:35 PMSubj...So we went to github to get social, and now eclipse goes there too. What does this mean for us?Â

I will be spending a significant amount of time discussing these topics in our Membership call tomorrow at 11:30am Eastern, 8:30am Pacific, 17:30 CET (with apologies to our European members). Please join the call.

When the IMP project is terminated, all project resources, including
the directories containing the SVN content, will be packaged up into
a tar.gz file that will be accessible from our archives server.
IMP's SVN server, web pages, downloads, etc. would be shut down with
the project. Nothing gets deleted.

In terms of trademarks, the project name, The "IDE Meta-Tooling
Platform"; the package and bundle names, org.eclipse.imp; and the
IMP acronym are trademarks of the Eclipse Foundation and must be
changed with the project's move from eclipse.org.

Thanks,

Wayne

On 06/06/2013 03:18 PM, Jurgen Vinju
wrote:

Hi Bob,

I think everything is there on github, but it
would be a good idea if you want to make a backup of the svn.
it's all still there in one folder now (moved_to_github). I
think you are the only one that can do that now, since I have
not access to ssh anymore.

Wayne: After official project termination, will the
source remain accessible on SVN? Will the web page
sources remain accessible? (Last I recall, they were
still in CVS, which I know was deprecated.) Failing
that, will the project web sources remain available on
the Web itself for a while?

My main concern would be making sure we don't lose
anything valuable in the transition.

I confess I haven't kept track of exactly what's in
github. Perhaps we need to do a pass over everything to
make sure nothing will be lost in the process.

Thanks. All the code has been moved. So far
we have had no reaction to the branding issue
in IPzilla. I guess its not so important. We
will gradually start renaming packages on
github to reflect we are not hosted on eclipse.org
anymore. Thanks for everything.

Bob, are you ready for a termination review
in July? I will be on holidays until the 17th
of July

I think everything is there on github, but it would be a good idea if you want to make a backup of the svn. it's all still there in one folder now (moved_to_github). I think you are the only one that can do that now, since I have not access to ssh anymore.

Wayne: After official project termination, will the source remain accessible on SVN? Will the web page sources remain accessible? (Last I recall, they were still in CVS, which I know was deprecated.) Failing that, will the project web sources remain available on the Web itself for a while?

My main concern would be making sure we don't lose anything valuable in the transition.

I confess I haven't kept track of exactly what's in github. Perhaps we need to do a pass over everything to make sure nothing will be lost in the process.

Thanks. All the code has been moved. So far we have had no reaction to the branding issue in IPzilla. I guess its not so important. We will gradually start renaming packages on github to reflect we are not hosted on eclipse.org anymore. Thanks for everything.

Bob, are you ready for a termination review in July? I will be on holidays until the 17th of July

Wayne: After official project termination, will the source remain accessible on SVN? Will the web page sources remain accessible? (Last I recall, they were still in CVS, which I know was deprecated.) Failing that, will the project web sources remain available on the Web itself for a while?

My main concern would be making sure we don't lose anything valuable in the transition.

I confess I haven't kept track of exactly what's in github. Perhaps we need to do a pass over everything to make sure nothing will be lost in the process.

Thanks. All the code has been moved. So far we have had no reaction to the branding issue in IPzilla. I guess its not so important. We will gradually start renaming packages on github to reflect we are not hosted on eclipse.org anymore. Thanks for everything.

Bob, are you ready for a termination review in July? I will be on holidays until the 17th of July

Thanks. All the code has been moved. So far we
have had no reaction to the branding issue in IPzilla. I guess
its not so important. We will gradually start renaming
packages on github to reflect we are not hosted on eclipse.org
anymore. Thanks for everything.

Bob, are you ready for a termination review in
July? I will be on holidays until the 17th of July

Thanks. All the code has been moved. So far we
have had no reaction to the branding issue in IPzilla. I guess
its not so important. We will gradually start renaming
packages on github to reflect we are not hosted on eclipse.org
anymore. Thanks for everything.

Bob, are you ready for a termination review in
July? I will be on holidays until the 17th of July

]]>Wed, 05 Jun 2013 18:36:55 GMThttp://dev.eclipse.org/mhonarc/lists/imp-dev/msg00490.htmlwayne@xxxxxxx (Wayne Beaton)Re: [imp-dev] what's the status of the IMP project?http://dev.eclipse.org/mhonarc/lists/imp-dev/msg00489.html
Where are you planning to host the p2 site? I am interested as I was using github to host the p2 site also, but workflow is somewhat tedious to upload the artifacts using the maven-scm-plugin, and similar problems with github api calls limits using com.git...Hi Tom,

We haven't given it much though yet, but since we have a workflow on our own servers for Rascal, we will probable clone the setup for IMP from that. We use a jenkins-maven-tycho-scp setup to publish a continuous unstable p2 site, and plain mvn-tycho-scp for the stable Rascal p2 site.

First things first though, we need the termination at Eclipse.org, a domain name, and a plan for the more quiet parts of IMP.

A new update site is in the planning for when the eclipse.org one goes offline.

Where are you planning to host the p2 site?

I am interested as I was using github to host the p2 site also, but workflow is somewhat tedious to upload the artifacts using the maven-scm-plugin, and similar problems with github api calls limits using com.github.github:site-maven-plugin

obviously for the workflow tooling, I am interested to have a reasonable short turn-around, and be able to push out new artifacts to the p2 site, and available in less than say.... 1 hour.. ;-)

However the benefit of using github is that we already have the user github account in eGit, so its trivial to "generate" a p2 repo from that. (its not so simple to use S3 etc)