You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Andrew Palumbo (JIRA)" <ji...@apache.org> on 2014/06/24 00:30:26 UTC
[jira] [Comment Edited] (MAHOUT-1587) Update website to reflect
move to GitHub
[ https://issues.apache.org/jira/browse/MAHOUT-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041398#comment-14041398 ]
Andrew Palumbo edited comment on MAHOUT-1587 at 6/23/14 10:28 PM:
------------------------------------------------------------------
Ok thanks- yeah I saw some of the conversation on squashing commits on the dev list. When I get a chance, I'll make a couple trivial commits to my branch and then make sure that their squashed by following the directions step by step. I just closed a site-related JIRA issue that i can add to the changelog. (unless this is frowned upon)
I think that it might make sense to eventually split the "Handling GitHub PRs" page. For one thing its under the "For Committers" section in the "Developers" dropdown.
Also we should probably mention things like including the JIRA Issue in the title and whatever else needs to be done to link back to JIRA. (Edit: I see now thats at the bottom of the page- in the committers section- I think it would be good to have that in a place where contributors see it easily)
I don't think that its a big priority right now. I'll look at what needs to come out of the other pages re: creating patches and maybe we could move that all over to a "Creating GitHub PRs" page under the "Contributions" section of the "Developers" dropdown.
was (Author: andrew_palumbo):
Ok thanks- yeah I saw some of the conversation on squashing commits on the dev list. When I get a chance, I'll make a couple trivial commits to my branch and then make sure that their squashed by following the directions step by step. I just closed a site-related JIRA issue that i can add to the changelog. (unless this is frowned upon)
I think that it might make sense to eventually split the "Handling GitHub PRs" page. For one thing its under the "For Committers" section in the "Developers" dropdown.
Also we should probably mention things like including the JIRA Issue in the title and whatever else needs to be done to link back to JIRA.
I don't think that its a big priority right now. I'll look at what needs to come out of the other pages re: creating patches and maybe we could move that all over to a "Creating GitHub PRs" page under the "Contributions" section of the "Developers" dropdown.
> Update website to reflect move to GitHub
> -----------------------------------------
>
> Key: MAHOUT-1587
> URL: https://issues.apache.org/jira/browse/MAHOUT-1587
> Project: Mahout
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 1.0
> Reporter: Andrew Palumbo
> Fix For: 1.0
>
>
> The following pages have directions for either checking out code from SVN, patching with SVN or have direct links to files in the old SVN repo:
> http://mahout.apache.org/developers/developer-resources.html
> http://mahout.apache.org/developers/version-control.html
> http://mahout.apache.org/developers/issue-tracker.html
> http://mahout.apache.org/developers/how-to-contribute.html
> http://mahout.apache.org/users/basics/creating-vectors-from-text.html
> http://mahout.apache.org/users/classification/bayesian.html
> http://mahout.apache.org/users/classification/twenty-newsgroups.html
> http://mahout.apache.org/users/clustering/k-means-clustering.html
> http://mahout.apache.org/users/clustering/fuzzy-k-means.html
> http://mahout.apache.org/users/clustering/canopy-clustering.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)