[jira] [Commented] (JDO-770) Switch from svn to git

[Andy Jefferson (JIRA)]

[ 
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

[Andy Jefferson (JIRA)]

[ 
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)