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
