[Biojava-dev] Github available

[Michael Heuer]

Hello Spencer,

Is the biojava/biojava-legacy repo set up with the same permissions (not
sure if that is the right word to use) as biojava/biojava?  I ask because I
received an email from github with the subject





On Wed, Apr 3, 2013 at 3:05 PM, Spencer Bliven <sbliven at ucsd.edu> wrote:

> Everyone who requested git access on the spreadsheet should now have it. I
> recommend forking the repository to your own account if you're new to git.
> You can then accept your own pull requests into the main devel branch,
> after checking that the git history looks reasonable. While git is very
> flexible with rewriting history on local forks, once it gets pushed to the
> main repository it is much harder to undo any mistakes.
>
> Let me know if I missed anyone!
> -Spencer
>
>
> On Wed, Apr 3, 2013 at 12:14 PM, Andreas Prlic <andreas at sdsc.edu> wrote:
>
> > Thanks a lot, Spencer! This is a big step forward for the project!
> >
> > Andreas
> >
> >
> > On Wed, Apr 3, 2013 at 11:55 AM, Spencer Bliven <sbliven at ucsd.edu>
> wrote:
> >
> >> The source to biojava3 is available on github! See
> >> https://github.com/biojava/biojava. Sorry about the delays–it was more
> >> difficult than I expected. I am still working on the legacy source, and
> >> should have that repository converted soon.
> >>
> >> You can get a clone via the commandline:
> >>
> >>   git clone -b devel https://github.com/biojava/biojava.git
> >>
> >> Remember, *DON'T USE THE 'RELEASE' BRANCH*! Any commits there should be
> >>
> >> considered full biojava releases. To add new features, please create a
> new
> >> feature branch from  'devel', make your changes, and then merge back
> into
> >> 'devel'. Hopefully the branch names should make this clear. Note that
> >> there
> >> is no 'master' branch. This is deliberate, to avoid ambiguity. Make sure
> >> your tools are set up to use the right branch when cloning. I've set
> >> 'release' as the default branch so that new users will get stable code
> by
> >> default, so us developers need to make sure we're doing the right thing!
> >>
> >> I am actively working on updating the documentation on the wiki to
> reflect
> >> the new location. I could use some help on this if anyone has time to
> >> contribute. As a start, here's a page on using Git in Eclipse (
> >> http://biojava.org/wiki/BioJava3_eclipse), and here's documentation of
> >> the
> >> migration process (http://biojava.org/wiki/SVN_to_GIT_Migration).
> >>
> >> To check that your github account was properly linked, find an old
> commit
> >> and check that the author links to your github account. Old commits
> >> currently do not show up in your contribution activity, but I am hoping
> >> that it will appear after the github servers have time to index the new
> >> repo. I haven't added everyone as contributors yet, but will do so
> >> shortly.
> >>
> >> The git repository contains all the history after biojava moved from Ant
> >> to
> >> Maven (r7227). There was a major code rearrangement at this point that
> >> could not be automatically resolved by git-svn due to the early version
> of
> >> SVN the old repository used. Most branches were started before this
> point,
> >> so they were also not converted to git. The SVN server is still up in
> >> read-only mode in case we need to access the old history or migrate old
> >> branches. Please let me know if this is a concern for anyone.
> >>
> >> Thanks for your patience through the process!
> >>
> >> -Spencer
> >>
> >> _______________________________________________
> >> biojava-dev mailing list
> >> biojava-dev at lists.open-bio.org
> >> http://lists.open-bio.org/mailman/listinfo/biojava-dev
> >>
> >
> >
> >
> >
>
> _______________________________________________
> biojava-dev mailing list
> biojava-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/biojava-dev
>