search

DPascalBernard / maven-alfresco-archetypes

Automatically exported from code.google.com/p/maven-alfresco-archetypes
0 stars 0 forks source link

Move project to github #189

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
To gain visibility, we might want to move the SDK to Github.

Maurizio already did this 7 months ago by:

    mkdir mas
    cd mas && svn2git -v -m http://maven-alfresco-archetypes.googlecode.com/svn
    git push -u origin master
    Run "git push origin <branch_name>" for each branch; use "git branch" for the full list
    Run "git push origin <tag_name>" for each tag; use "git tag" for the full list

We should look into this for the 2.x version of the SDK

Original issue reported on code.google.com by colum...@gmail.com on 10 Jun 2014 at 12:51

GoogleCodeExporter commented 8 years ago 
Just my thoughts on this:

1) This needs to happen (accepting pull requests will make the whole process of 
contributions easier)

2) We should take over the alfresco-sdk repository 
(https://github.com/Alfresco/alfresco-sdk), it's currently being used for the 
examples I made durring the hackathon, and they really don't belong in a 
repository called "Alfresco SDK" unless they're part of the SDK, which they are 
not at the moment. 

I talked to Richard Esplin about it on IRC the other day, and he has access to 
the repositories and can help make the changes, if you don't have access to the 
Alfresco github accounts.

If we are not going to merge the examples in (see issue #190), we should at 
least rename the current "alfresco-sdk" to "alfresco-sdk-examples" and put the 
SDK where it belongs.

Original comment by o...@magenta-aps.dk on 13 Jun 2014 at 8:57

GoogleCodeExporter commented 8 years ago 
To simplify the issue migration, we could use these Python scripts - 
https://github.com/arthur-debert/google-code-issues-migrator

Original comment by maurizio...@alfresco.com on 3 Jul 2014 at 12:23