Hi Guang,
I think it's a great idea
I looked at this last year as well, and how easy it was, and am hosting
it at https://github.com/xcat-org. I have been mirroring the code there
on daily basis. The only problem is that, you have the limit of 1G per
repository and the xcat-dep is not possible to mirror on github (which
you have pointed out on your cons section), although everything else
looks good. So from when I last tried mirroring xcat-dep, I got the
following errors, and I got the same errors today
remote: warning: File nbkernel/kernel-2.6.18-164.el5.src.rpm is 71.93
MB; this is larger than GitHub's recommended maximum file size of 50 MB
remote: error: GH001: Large files detected.
remote: error: Trace: 511451e5f43fe87506983574f48462c8
remote: error: See http://git.io/iEPt8g for more information.
remote: error: File
nbroot/xCAT-nbroot-oss-x86_64-2.0-snap201003091331.src.rpm is 126.87 MB;
this exceeds GitHub's file size limit of 100 MB
To g...@github.com:xcat-org/xcat-dep.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'g...@github.com:xcat-org/xcat-dep.git'
No refs in common and none specified; doing nothing.
which indicates file sizes could still be an issue, it would be
interesting to find out how you was able to do this in your repo
An alternative to github.com is gitlab.com, where they don't have the
limitation, and also has all of the same features as github with a Wiki,
Issues, merge requests etc... This doesn't have any limitation on repo
sizes, and will therefore give you extra flexibility. I have been
experimenting, and mirroring to my private gitlab implementation
https://gitlab.arif-ali.co.uk/groups/xcat, where you will be able to see
how this works.
I like the idea of github or gitlab, primarily due to the fact it will
allow more visibility as well it will be easier for people to contribute
with the pull/merge requests, and it having the ability to do that with
a click of a button
regards,
Arif Ali
Technical Director
OCF plc
Tel: +44 (0)114 257 2200
Mob: +44 (0)7970 148 122
Fax: +44 (0)114 257 0022
Web: www.ocf.co.uk <http://www.ocf.co.uk>
Blog: blog.ocf.co.uk <http://blog.ocf.co.uk>
Twitter: @ocfplc <http://twitter.com/#%21/ocfplc>
OCF plc is a company registered in England and Wales. Registered number
4132533, VAT number GB 780 6803 14. Registered office address: OCF plc,
5 Rotunda Business Centre, Thorncliffe Park, Chapeltown, Sheffield, S35
2PG.
This message is private and confidential. If you have received this
message in error, please notify us and remove it from your system.
On 07/01/15 09:57, Guang Cheng Li wrote:
HI xCAT users,
In year 2014, we have been experiencing the network access problems to
sourceforge quite a bit, even when there is no network access
problems, the network speed is also very slow, it dramatically slows
down our development and testing progress, and also make us wondering
about the stability of sourceforge in the future, so the xCAT
development team spent some time to investigate the feasibility of
migrating xCAT from sourceforge to github. Here are the findings:
1. Code repositories
It is easy to mirror the sourceforge code repositories to github using
the git CLI. The example of mirroring xcat-core from sourceforge to
github:
git clone --bare --mirror
ssh://l...@git.code.sf.net/p/xcat/xcat-core github-mirror-xcat-core
cd github-mirror-xcat-core
git remote add github g...@github.com:xcat2/xcat-core.git
git config remote.github.mirror true
git push github
See https://github.com/xcat2
2. Wiki pages
Both sourceforge and github uses markdown syntax, migrating the wiki
pages from sourceforge to github is not that difficult, we could
simply get the markdown files through sourceforge APIs and then use
git CLI to push the markdown files to github. However, there are still
some markdown syntax differences we need to deal with, like github
markdown does not support transclude and TOC. You could take a look at
https://github.com/xcat2/xcat-core/wiki to get some feeling about how
does it look like
3. Bug tracking
Github has its own bug tracking system, we could write some simple
scripts to copy the existing sourceforge bugs to github, see
https://github.com/xcat2/xcat-core/issues for more details.
4. Binaries hosting
github supports binary host but does not support Yum online repository
hosting, it means we will not be able to use the online yum repository
to update xCAT. An alternative is to put the RPMs into a github code
repository, the user could use git clone and git pull to keep the RPMs
up to date locally(yum seems not be able to fetch RPMs from github
code repo), then points the yum repository to the local git repo. See
https://github.com/xcat2/xcat-core/releases and
https://github.com/xcat2/xcat-core-bin and
https://github.com/xcat2/xcat-dep-bin
5. Mailing list
Github does not support mailing list, we could keep the mailing list
on sourceforge.
Migrating to github has pros and cons:
Pros:
1) the network access speed to github seems to be much better than
sourceforge
2) the github is more popular
3) github uses code repository to manage the wiki pages, it makes
things easier for local editings and global editings
4) github has REST-APIs everywhere
Cons:
1) github does not have mailing list
2) github does not support hosting online yum repositories
3) github limits the repository size to be 1GB and file size to be 100MB
4) github wiki does not support transclude and TOC, printing xCAT docs
will be a little bit more difficult
5) emails notification for the code,wiki,bugs updates needs more
complex configuration
Any comment, suggestion, concern or objection for moving xCAT from
sourceforge to github will be appreciated.
-------------------------------------------------------------------------
Li,Guang Cheng (李光成)
IBM China System Technology Laboratory
Email: ligua...@cn.ibm.com
Address: Building 28, ZhongGuanCun Software Park,
No.8, Dong Bei Wang West Road, Haidian District Beijing
100193, PRC
北京市海淀区东北旺西路8号中关村软件园28号楼
邮编: 100193
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
