From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Subject: [ANNOUNCE] Git wiki & repo.or.cz migration, donations and volunteers pledge
Date: Thu, 14 Jan 2010 00:29:08 +0100 [thread overview]
Message-ID: <20100113232908.GA3299@machine.or.cz> (raw)
Hello!
I would like to notify you that unfortunately, Czech UPC terminated the
sponsorship of the hardware and connectivity hosting the Git Wiki and
repo.or.cz (after generously donating it for several years).
We have just secured at least provisional hosting at the Charles University,
Prague and CESNET - the connectivity should be equally good as at UPC,
even better on university backbones over the world. However, I will have
to buy new rack server for the hosting service from my own pocket and this is
where I have to ask for your help - I can't afford to sponsor the full price
of the server, and reasonably powerful rack hardware ain't cheap (repo.or.cz
_is_ quite a workload!).
Thus, I would like to ask you for donations for the new hardware - the full
cost is $1400 (CZK 24000); we would like to gather more in order to be able to
buy a RAID0 pair disk and more RAM. Any extra money would all go to
the server-related costs, most likely hardware upgrades in the future.
I apologize for abusing the vger public forum for this, I hope the readers
not using repo.or.cz and the wiki will not mind.
On a related note, unfortunately I can't spend nearly as much time on
the wiki and repo.or.cz maintenance and enhancements as it would deserve.
Thus, I'm seeking for volunteers to help with both day-to-day maintenance
and development. You will be richly credited and ethernal glory in the Git
community awaits you, plus it will surely make a great CV bullet-point! :)
I'm sure really cool things could be done by developers with fresh ideas,
especially after the hardware upgrade.
*** You can donate and view the current pledge status at: ***
http://repo.or.cz/h/pledge.html
Thanks,
Petr "Pasky" Baudis
next reply other threads:[~2010-01-13 23:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 23:29 Petr Baudis [this message]
2010-01-14 1:24 ` [RFC] Git Wiki Move Petr Baudis
2010-01-14 10:28 ` J.H.
2010-01-14 10:35 ` Matthieu Moy
2010-01-14 18:56 ` J.H.
2010-01-15 23:18 ` J.H.
2010-01-15 23:21 ` Sverre Rabbelier
2010-01-15 23:50 ` Junio C Hamano
2010-01-16 0:05 ` J.H.
2010-01-16 0:02 ` J.H.
2010-01-16 0:08 ` Sverre Rabbelier
2010-01-16 0:12 ` Junio C Hamano
2010-01-16 0:28 ` J.H.
2010-01-16 0:44 ` Sverre Rabbelier
2010-01-16 1:18 ` J.H.
2010-01-16 10:17 ` Clemens Buchacher
2010-01-17 12:00 ` Matthieu Moy
2010-01-17 23:06 ` Johannes Schindelin
2010-01-18 0:43 ` J.H.
2010-01-18 9:53 ` Johannes Schindelin
2010-01-18 12:03 ` Johannes Schindelin
2010-01-18 18:47 ` J.H.
2010-01-18 20:46 ` Johannes Schindelin
2010-01-21 21:35 ` Petr Baudis
2010-01-22 0:21 ` Jakub Narebski
2010-01-22 0:31 ` Petr Baudis
2010-01-22 0:39 ` Johannes Schindelin
2010-01-14 10:43 ` Johannes Schindelin
2010-01-14 11:01 ` Johannes Schindelin
2010-01-14 18:52 ` J.H.
2010-01-14 10:48 ` Petr Baudis
2010-01-14 11:03 ` Johannes Schindelin
2010-02-12 11:38 ` Petr Baudis
2010-01-14 10:48 ` Wincent Colaiuta
2010-01-15 17:17 ` Joey Hess
2010-01-15 19:16 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100113232908.GA3299@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).