Status of Ivy Roundup migration to GitHub?

[Andre-John Mas]

Hi,

Just curious to know what the timelines are for migrating Ivy Roundup to GitHub, given the EOL for code.google.com?

Thanks

Andre

[Archie Cobbs]

No timeline set yet but we should set one. Other logistical aspects...

• The repository URL will need to change, so we should announce a date for the switchover and give plenty of warning
• Does github have an equivalent URL-space for direct downloads?
• Updating utility scripts that perform svn operations to use git instead

Other thoughts?

-AC

--
You received this message because you are subscribed to the Google Groups "ivyroundup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ivyroundup+...@googlegroups.com.
To post to this group, send email to ivyro...@googlegroups.com.
Visit this group at http://groups.google.com/group/ivyroundup.
For more options, visit https://groups.google.com/d/optout.

--

Archie L. Cobbs

[André-John Mas]

- For the URL-space, possibly this should answer that:

  http://stackoverflow.com/questions/6978954/add-binary-distribution-to-githubs-download-link

- We would probably need to check the repository to see if there are any hard references to current repository

- Possible transitions stages:

    - beta version on GitHub, to isolate any issues, while announcing beta current site

      - do we put current svn in a 'hold' state, to avoid parallel changes?

      - would include migration & updating of docs

    - final, with current site being updated with redirects to new location

- Additionally, encourage changes to submitted via pull-requests, as part of an adapted process?

[Martin Weber]

Am Montag, 30. März 2015, 08:52:54 schrieb Archie Cobbs:
> No timeline set yet but we should set one. Other logistical aspects...

...
> - Does github have an equivalent URL-space for direct downloads?

YES. I use it as a p2 composite update site like here:
<https://raw.githubusercontent.com/15knots/cmake4eclipse/master/releng/comp-update/>

> - Updating utility scripts that perform svn operations to use git instead
>
> Other thoughts?

SVN keyword expansion like $Rev and $Id. Git does no keyword expansion,
however, one can use a commit hook to do something similar to expand $Rev.
But that will give you the SHA-hash of the commit which is much longer than
the svn revision.

Martin

--
Cd wrttn wtht vwls s mch trsr.

[Martin Weber]

Am Montag, 30. März 2015, 11:41:57 schrieb André-John Mas:
> - For the URL-space, possibly this should answer that:

...

> - final, with current site being updated with redirects to new location

You mean a HTTP redirect? Not quite sure how to make that working on
googlecode.

[André-John Mas]

For now I am just thinking of something low tech, such as a paragraph on top of key pages pointing to their new home.

André-John

Sent from my phone. Envoyé depuis mon téléphone.

[Archie Cobbs]

On Mon, Mar 30, 2015 at 1:13 PM, Martin Weber <fifteen...@gmail.com> wrote:

SVN keyword expansion like $Rev and $Id. Git does no keyword expansion,
however, one can use a commit hook to do something similar to expand $Rev.
But that will give you the SHA-hash of the commit which is much longer than
the svn revision.

The current SVN keyword expansion does really not add much value. So I suggest we just remove it in the transition.

-AC

--

Archie L. Cobbs

[André-John Mas]

Hi,

Just following up this. Could we start with a preliminary export now and then

start preparing the changes, via pull-requests?

Although I could click on the 'export' myself, it may be better for Archie to

do it, since that would make sense as the main owner of the new repository.

After having exported the project, the new location can point back to the old

location, in the site description, until we ready to treat the new site as

official.

For all the references to code.google.com, you could run this (tweaking as appropriate):

find . -type f -name "*.xml" -exec sed -i.bak "s/code\.google\.com\/p\/ivyroundup\/source\/browse\/trunk/github.org\/archiecobbs\/ivy-roundup/g" {} \;

There will still be references to code.google.com left afterwards, but from my running

of this command, I see they are only references to other projects.

Regards

Andre

On Mar 30, 2015, at 11:41 , André-John Mas <andrej...@gmail.com> wrote:

- For the URL-space, possibly this should answer that:

  http://stackoverflow.com/questions/6978954/add-binary-distribution-to-githubs-download-link

- We would probably need to check the repository to see if there are any hard references to current repository

- Possible transitions stages:

    - beta version on GitHub, to isolate any issues, while announcing beta current site

      - do we put current svn in a 'hold' state, to avoid parallel changes?

      - would include migration & updating of docs

    - final, with current site being updated with redirects to new location

- Additionally, encourage changes to submitted via pull-requests, as part of a new proces?

On Mar 30, 2015, at 09:52 , Archie Cobbs <arc...@dellroad.org> wrote:

[Archie Cobbs]

OK, I've got a preview of Ivy RoundUp running on github. Please check it out and let me know if you see any issues.

Summary of changes:

• Update scripts to use git(1) instead of svn(1)
• Update URLs to point at github instead of googlecode
  
• Remove all use of $Id$ tags
• Update wiki pages for new workflow, etc.
  
• Use htmlpreview.github.io for HTML repository viewer
  
• Generate HTML files from XML files manually during repo build
  

One problem I foresee is that raw.githubusercontent.com does not provide directory listings (example). This may mean ivy is unable to auto-detect revisions...?

-Archie

On Sun, Mar 29, 2015 at 6:38 PM, Andre-John Mas <andrej...@gmail.com> wrote:

--

You received this message because you are subscribed to the Google Groups "ivyroundup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ivyroundup+...@googlegroups.com.
To post to this group, send email to ivyro...@googlegroups.com.
Visit this group at http://groups.google.com/group/ivyroundup.
For more options, visit https://groups.google.com/d/optout.

--

Archie L. Cobbs

[André-John Mas]

What is the URL of the GitHub project?

[André-John Mas]

Never mind, found it: https://github.com/archiecobbs/ivyroundup

For the issue you see, maybe the solution there is to generate an

index file, suitably formatted, as part of the ant script? 

[Archie Cobbs]

On Mon, Apr 20, 2015 at 2:32 PM, André-John Mas <andrej...@gmail.com> wrote:

For the issue you see, maybe the solution there is to generate an

index file, suitably formatted, as part of the ant script? 

We could do that, but it would only work if ant/ivy already knows how to look for and read such a file.

With a quick look I don't see any documentation to this effect regarding the URL resolver (on which the packager resolver is based).

[André-John Mas]

Another solution could be to push pages to http://archiecobb.github.io/ivyroundup/ ,

with an index.html file, though that may end up being convoluted, since from what

I understand, that is supported by a repository with your user name.

[15 knots]

How did you import that?
With the googlecode exporter, the wiki content would be in the wiki branch

[Archie Cobbs]

I used the googlecode exporter. I've ported 3 projects so far. In all cases the porting of issues has failed or only worked partially.

As for the wiki, I do it myself manually using their .wiki -> .md converter (from https://code.google.com/p/support-tools/). In github, wiki files live in their own separate git repo, not on a branch of the main repo.

-Archie