[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783610#comment-16783610 ] Andy Jefferson commented on JDO-770: The GitHub commit messages now seem to go to *jdo-dev* mailing list, instead of to *jdo-commits* mailing list. Is this intentional? if so then suggest that somebody removes the *jdo-commits* list since it serves no further purpose. If not intentional then suggest that *jdo-commits* is used for commits. For reference Apache ISIS has an *isis-dev* and *isis-commits* and seem to have such messages split out. > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783083#comment-16783083 ] Andy Jefferson commented on JDO-770: Why is the website not on GitHub under a simple "website" directory? Then people can commit updates to the website from the same source code host (and then have to do the manual update of the website). Better still would be (to do the above and then) for someone to enquire at Apache if it is possible to do auto-publishing of a website from a GitHub directory, e.g by running a cron job on some Apache box to build and publish the website. I've been doing this for years with DataNucleus and it means I never have to faff about with publishing, just commit the docs updates into GitHub and they appear on the website overnight. Further to that, and in reply to the Wiki question, has anyone looked at that Wiki in years? It is totally out of date. Users, in general, don't contribute to Wikis; we abandoned the DataNucleus one a few years back, and just encouraged people to provide GitHub pull requests to the docs. One less thing to maintain that way. > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774578#comment-16774578 ] Craig L Russell commented on JDO-770: - No one has admin on github except for root@. The default branch is now master. I asked on slack #asf-infra channel and they were very responsive. The url is now fixed, thanks to root@. I still need to figure out why papajdo is the committer on db-jdo. That's an old github id that I haven't used in years. > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774476#comment-16774476 ] Craig L Russell commented on JDO-770: - in order to use this workspace as a known user you need to associate your apache id with your github id. default branch indeed should be master and i'm trying to get admin for everyone so we can make this change the wrong url is probably something we can change once we have admin on the workspace > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774404#comment-16774404 ] Andy Jefferson commented on JDO-770: Comments : * I don't seem to have commit access to this, and all (past) commits of mine aren't linked to my GitHub account (andyjefferson). * Default branch should be "master", for consistency with every other project * URL is wrong on [https://github.com/apache/db-jdo/tree/master] > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604599#comment-16604599 ] Craig L Russell commented on JDO-770: - Issue with git svn show-ignore is not a blocker. cp .svnignore .gitignore # solves the problem There is only one .svnignore file. > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597518#comment-16597518 ] Craig L Russell commented on JDO-770: - Small issue with .ignore handling. cd ~/temp-db-jdo/ [MacBook-Pro-9:~/temp-db-jdo] clr% git svn show-ignore config --get svn-remote.svn.fetch :refs/remotes/git-svn$: command returned error: 1 I'm not sure if this is an issue with the instructions or if there is no svn ignore rule in db/jdo. > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16552132#comment-16552132 ] Michael Bouschen commented on JDO-770: -- I added an description how to convert svn to git (svn2git.html) and an authors file to svn (see revision 1836454). > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16547069#comment-16547069 ] Michael Bouschen commented on JDO-770: -- Could you please try it again? Today I could successfully run the above command: % svn checkout http://svn.apache.org/repos/asf/db/jdo A jdo/tags A jdo/tags/2.3-ea A jdo/tags/2.3-ea/dist A jdo/tags/2.3-ea/dist/db A jdo/tags/2.3-ea/dist/db/jdo ... > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Assignee: Craig L Russell >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[
https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16544892#comment-16544892
]
Andy Jefferson commented on JDO-770:
The sooner this can be done the better for all. I just tried to get current
code using (from the website)
{{svn checkout [http://svn.apache.org/repos/asf/db/jdo]}}
and was met with
{{svn: E170013: Unable to connect to a repository at URL
'http://svn.apache.org/repos/asf/db/jdo'}}
{{svn: E120108: Error running context: The server unexpectedly closed the
connection.}}
Nice, so much for that idea.
> Switch from svn to git
> --
>
> Key: JDO-770
> URL: https://issues.apache.org/jira/browse/JDO-770
> Project: JDO
> Issue Type: Improvement
> Components: site and infrastructure
>Affects Versions: JDO 3.1
>Reporter: Michael Bouschen
>Assignee: Craig L Russell
>Priority: Major
> Fix For: JDO 3.2
>
>
> We should consider switching from svn to git. The reason to make jdo
> available via git is to remove a possible barrier to new contributors.
> There are several alternatives if we decide to offer git as an alternative to
> svn:
> * migrating all the code to git
> * creating a read-only git mirror
> * creating a read-write bridge.
> See [Git at Apache | https://git.apache.org/] for more details.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373140#comment-16373140 ] Michael Bouschen commented on JDO-770: -- >From the Minutes JDO con call January 25: A recent change made for the apache juneau project might be relevant. This project formerly used gitbox and now has a read-write mirror on github so they can close pull requests from github users. http://juneau.apache.org/#about.html https://cwiki.apache.org/confluence/display/JUNEAU/How-to+articles > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen >Priority: Major > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JDO-770) Switch from svn to git
[ https://issues.apache.org/jira/browse/JDO-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311770#comment-16311770 ] Craig L Russell commented on JDO-770: - Another question is whether there are any svn dependencies in the tooling around releases. > Switch from svn to git > -- > > Key: JDO-770 > URL: https://issues.apache.org/jira/browse/JDO-770 > Project: JDO > Issue Type: Improvement > Components: site and infrastructure >Affects Versions: JDO 3.1 >Reporter: Michael Bouschen > Fix For: JDO 3.2 > > > We should consider switching from svn to git. The reason to make jdo > available via git is to remove a possible barrier to new contributors. > There are several alternatives if we decide to offer git as an alternative to > svn: > * migrating all the code to git > * creating a read-only git mirror > * creating a read-write bridge. > See [Git at Apache | https://git.apache.org/] for more details. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
