| Mit freundlichen Grüßen / Kind regards
Markus Hilger Infrastructure Architect GTS / High Performance Computing Services |
| | ||
| Phone: +49-7034-274-0859 | Mobile: +49-173-2105582 E-mail: markus.hil...@de.ibm.com Website: obihoernchen.net Find me on: | Nahmitzer Damm 12 Berlin, 12277 Germany | |
Geschäftsführung: Baerbel Altmann, Frank Hammer, Thorsten Moehring
Sitz der Gesellschaft: Ehningen
Registergericht: Amtsgericht Stuttgart, HRB 17122
----- Original message -----
From: Guang Cheng Li <ligua...@cn.ibm.com>
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Cc:
Subject: Re: [xcat-user] Toward a post-sourceforge future....
Date: Thu, Jul 23, 2015 5:25 AM
We discussed this topic in the xCAT development team meeting today, here are the consensus from the team, if you have any further comments, please let us know.
1. Code repository: We will migrate the xCAT code repository from sourceforge to github after xCAT 2.10 release, which is planned for July 31. After the migration, we will remove all the code write permissions from sourceforge to avoid anyone continue changing code on sourceforge.
2. Documentation: The xcat-docs.readthedocs.org is a better option, it could hook with the github.com to automatically fetch the xcat-doc code changes and convert the restructedtext files to html and host these html files on readthedocs, just in case the readthedocs have problem in the future, the user could download the xcat-doc code and convert them to html files and browse locally, or we could host the html files on xcat.org. In the next one or two months, we will move the documentation from sourceforge to readthedocs, during this time frame, the users could still use the sourceforge doc as the master copy.
3. Packages download and online yum/zypper/apt repositories will be on xcat.org, we need to see if there is any performance or capacity problem with xcat.org on hosting the files, if there is performance/capacity problem, we could consider falling back to sourceforge(hope this will not happen).
4. Bug system and user forum: we will try to use the github issue system as the bug system and user forum, we do see that the github issue system could be deeply customized, if this turns out to be a problem, we could consider hosting some bug system or user forum on xcat.org, but if we need to host this on xcat.org, the user authentication needs to be handled carefully.
5. xCAT home page: the xCAT homepage will be xcat.org, on this homepage, it will have links to github and readthedocs.
-------------------------------------------------------------------------
Li,Guang Cheng (李光成)
IBM China System Technology Laboratory
Tel: 86-10-82453499
Tie-Line: 9053499
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号楼
邮编: 100193Jarrod Johnson ---2015/07/22 21:46:19---So this is my take on how things are/should proceed. First, as soon as possible the primary git repo
From: Jarrod Johnson <jjohns...@lenovo.com>
To: "xCAT Users Mailing list (xcat-user@lists.sourceforge.net)" <xcat-user@lists.sourceforge.net>
Date: 2015/07/22 21:46
Subject: [xcat-user] Toward a post-sourceforge future....
So this is my take on how things are/should proceed.
First, as soon as possible the primary git repositories will shift to github. This has already happened for confluent. I think this is a pretty unambiguous move. It aligns with a good community contribution, and in the (hopefully unlikely) event of github 'pulling a sourceforge' or 'pulling a code.google.com', it's not too terrible for developers to pack up and move.
As to the rest, I think there's some debate:
-Default landing:
-I think it should be xcat.org and not a redirect to anywhere else (i.e. not cause people to end up bookmarking a url that could change).
-Documentation: I've heard/said three different options:
-github wiki
-readthedocs.org
-self-hosted on xcat.org (doc source in restructured text or asciidoc, probably using https://github.com/gollum/gollum to serve it up)
I personally am leaning toward xcat.org. This is the most portable without disrupting user access. At sourceforge we were subjected to having to migrate at the whim of sourceforge's will to support, and now we face an increasingly urgent need to migrate away. For github and readthedocs.org, the same applies: we may be forced to do migrations in a manner disruptive to people.
-Package Downloads:
- I think having xcat.org present a more straightforward filesystem would be ideal. It's hard for users to sync the file release area today, and I'd like to change that. There has been concern about the scale of our downloads and whether what we currently have in xcat.org is up to the task (sourceforge does have a pretty decent CDN going on).
- An additional approach would be to get things into copr/ppa/opensuse build service, though at least xCAT-genesis-base may be a difficult thing to get to build in at least some of those services.
-Discussion:
-Self hosted mailing list/forum software. I have no experience on this front yet, though I think this clearly falls into the category of things you don't want to change drastically at the behest of hosting provider/having to move hosting providers. For example, sourceforge's outage broke our ability to discuss.
-Issue reporting/tracking
-Use github. It's there, it's free. It's probably in the category of things the users can follow if we move.
-Self-hosted redmine instance. I find github a bit less fully featured on issue tracking than I would like. If people feel like issue tracking is one of those things that should seamlessly persist across a hypothetical hosting change, this would be the way to do it.
Thoughts?
Also, do people think that Lenovo should host a Lenovo oriented site additionally packaging this content? Obviously it would still be able to be used in the same way that, but it may include some content that isn't afraid to be tied to a vendor (potentially: warranty status reporting, bundled firmware/config utilities that aren't cross-vendor or are not open source, documentation that more specifically addresses using Lenovo equipment without branching for the myriad of possibilities). It wouldn't have an independent git repository, but it might have distinct sets of packages (built on a cadence for Lenovo Cluster releases), documentation, etc.------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
