Re: [cross-project-issues-dev] CVS access to Orbit

Hi Denis Thanks. CVS from PSFs works again. If we now have an anonymous CVS server for Orbit, can we please restore the anonymous CVS access for the other repositories too so that Helios, Indigo, Juno facilities work again for ordinary users? Regards Ed Willink On 14/01/2013 2

[cross-project-issues-dev] Project plan on Git repository

Hi, I think there may be an issue with the script http://www.eclipse.org/projects/project-plan.php. It does not manage to display the new project plan of EMF Compare (http://www.eclipse.org/projects/project-plan.php?projectid=modeling.emf.compare) despite the raw XML is correct. The file is

Re: [cross-project-issues-dev] Project plan on Git repository

Hi Mikaël, I tend to use the project-plan script with a planurl argument instead, it makes it easier to point to a specific project plan. Example: http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/koneki/project-info/project-plan-0.9.xml Doesn’t directly answer you

Re: [cross-project-issues-dev] Project plan on Git repository

Hi Benjamin, Same result with planurl: http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/emf/compare/project-info/plan-2_0.xml is working but http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/emf/compare/project-info/

Re: [cross-project-issues-dev] CVS access to Orbit

What other repositories? The only CVS repo I know of is Orbit. Denis On 01/15/2013 03:36 AM, Ed Willink wrote: Hi Denis Thanks. CVS from PSFs works again. If we now have an anonymous CVS server for Orbit, can we please restore the anonymous CVS access for the other repositories too so th

Re: [cross-project-issues-dev] CVS access to Orbit

Hi /cvsroot/modeling etc etc Regards Ed Willink On 15/01/2013 14:58, Denis Roy wrote: What other repositories? The only CVS repo I know of is Orbit. Denis On 01/15/2013 03:36 AM, Ed Willink wrote: Hi Denis Thanks. CVS from PSFs works again. If we now have an anonymous CVS

Re: [cross-project-issues-dev] CVS access to Orbit

While Denis is pealing himself off the ceiling, I'll chime in. Isn't this all in git now? I thought Orbit was the only thing officially left in CVS. :D On 13-01-15 10:08 AM, "Ed Willink" wrote: >Hi > >/cvsroot/modeling etc etc > > Regards > > Ed Willink > > >On 15/01/2013 14:58, Den

[cross-project-issues-dev] Help Name Kepler+1

It's that time of year again, time to name the next Eclipse release. The Eclipse Kepler releasewill happen on June 26, 2013, but after that, we'll need a new name for the following release (because calling the next release Kepler+1 gets awkwar

Re: [cross-project-issues-dev] CVS access to Orbit

Hi December 21st was the end of the world as far as committer CVS write access was concerned. However it was not the end of the world as far as user CVS read access was concerned. A variety of examples and documentation describe fetching code from CVS. It is not feasible to rewrite such te

Re: [cross-project-issues-dev] CVS access to Orbit

Hi Ed, I totally understand your point and frustration. However havnt we all been warned by Wayne in numerous emails that "CVS will be shutdown" at the 21st December 2012 for over one year now. CVS shutdown is not the same thing as "set to readonly". So I think if that was a concern it should

Re: [cross-project-issues-dev] CVS access to Orbit

We talked about this on the Arch Council call this month. There was misinformation that CVS would be read-only. That isn't the case. It's gone and we need to get used to that. The only issue is Orbit which hasn't been shutdown yet since it's a more complicated beast. That we still need read-only a

Re: [cross-project-issues-dev] CVS access to Orbit

Hi But how could authors of Helios documentation change their documentation to use GIT?!! Regards Ed Willink On 15/01/2013 16:26, Campo, Christian wrote: Hi Ed, I totally understand your point and frustration. However havnt we all been warned by Wayne in numerous emails that "

Re: [cross-project-issues-dev] CVS access to Orbit

Maybe the product documentation shouldn't be pointing to committer resources? On Tue, Jan 15, 2013 at 8:34 AM, Ed Willink wrote: > Hi > > But how could authors of Helios documentation change their documentation to > use GIT?!! > > Regards > > Ed Willink > > > On 15/01/2013 16:26, Camp

Re: [cross-project-issues-dev] CVS access to Orbit

Hi But the whole ethos of Eclipse is Open Source. We make our source available. We encouarge users to read and copy. Of course our documentation referred to CVS. I am really amazed that we allow one of our outstanding achievements to be destroyed for such a trivial reason. Regards

Re: [cross-project-issues-dev] CVS access to Orbit

The community hardship angle is getting rather overplayed. Ok, so the user sees a reference to CVS and it doesn't work. What are they going to do next? Go to project website, perhaps, where they see a notice that source is now in Git. If they don't end up on the website, maybe they ask a question o

Re: [cross-project-issues-dev] CVS access to Orbit

Hi Picking on no one in particular from a "Eclipse Corner CVS" search. http://waynebeaton.wordpress.com/2006/04/11/updating-eclipse-corner-articles/ "Eclipse Corner GIT" gives very little. Regards Ed Willink On 15/01/2013 16:58, Konstantin Komissarchik wrote: The community hards

Re: [cross-project-issues-dev] Project plan on Git repository

I am investigating. Wayne On 01/15/2013 08:32 AM, Mikaël Barbero wrote: Hi Benjamin, Same result with planurl:  http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/modeling/emf/compare/project-info

Re: [cross-project-issues-dev] CVS access to Orbit

That was 2006. I was young and foolish. The post has multiple flaws. For one, hooking up to that repository will bring in a whole host of crap that you don't want. This is something that I've always wanted to do better, but since nobody contributes to Eclipse Corner

Re: [cross-project-issues-dev] CVS access to Orbit

I hate breaking things -- I really do. The HTTP protocol is beautiful in that respect -- there are built-in provisions for redirecting old links to new ones. I could easily do something similar with pserver cvs, where the server would respond with a plaintext "CVS is replaced with Git" messa

Re: [cross-project-issues-dev] CVS access to Orbit

On 01/15/2013 02:22 PM, Denis Roy wrote: we've been doing it for 13 years! I'd like to point out that I'm a server guy, not an accountant :-D ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailm

Re: [cross-project-issues-dev] CVS access to Orbit

Hi You may have been young, but not foolish; just diligent and helpful. Unfortunately you now show up as a prominent contributor our ten years of broken CVS legacy. Go to http://wiki.eclipse.org/CVS_FAQ. No mention of GIT anywhere. Click on the link to

Re: [cross-project-issues-dev] CVS access to Orbit

On 01/15/2013 02:28 PM, Ed Willink wrote: Go to http://wiki.eclipse.org/CVS_FAQ. No mention of GIT anywhere. It is a wiki and you are a trusted member of our community... I see that Denis--also a trusted member of our community--has added

Re: [cross-project-issues-dev] CVS access to Orbit

On 01/15/2013 02:28 PM, Ed Willink wrote: Hi You may have been young, but not foolish; just diligent and helpful. Unfortunately you now show up as a prominent contributor our ten years of broken CVS legacy. Go to http://wiki.eclipse.org/CVS_FAQ. No mention of GIT anywhere. I've added a bubb

Re: [cross-project-issues-dev] Project plan on Git repository

This one was a noggin-scratcher. The document isn't where you think it is. When you migrated the website to git, you changed from /modeling/emf/compare to /emf/compare Try this URL: http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclips

Re: [cross-project-issues-dev] Project plan on Git repository

Thank you Wayne. It is now working very well with the right URL! I should have taken care about redirection. Mikael Le 15 janv. 2013 à 22:04, Wayne Beaton a écrit : > This one was a noggin-scratcher. > > The document isn't where you think it is. When you migrated the website to > git, you c