From: Andrea Bernardini <andrebask@gmail.com>
To: kawa@sourceware.org
Subject: Re: proposal: move Kawa web-site to kawa-lang.org
Date: Sun, 13 Nov 2016 12:03:00 -0000 [thread overview]
Message-ID: <CAPFJfsuZ3wSW8Cc916CsQMiFaWYWkOD2t50q_B9TBBzcZAeRsQ@mail.gmail.com> (raw)
In-Reply-To: <CAPFJfsuX_EQPN_-nbdsd=j_a_azOWp0sVA1yCVvp6GDujpLXBA@mail.gmail.com>
And having just read you other email, GitLab offers exactly the same
functionality https://pages.gitlab.io/
On 13 November 2016 at 11:53, Andrea Bernardini <andrebask@gmail.com> wrote:
> Hi Per,
> Changing the kawa-lang.org seems sensible. Another easy way to host a
> static site is the github Pages service. I used that when proposing
> changes to the Kawa website
> (https://andrebask.github.io/kawa-website/).
>
> Cheers,
> Andrea
>
> On 13 November 2016 at 02:11, Per Bothner <per@bothner.com> wrote:
>> Currently the URL http://kawa-lang.org redirects to
>> https://www.gnu.org/software/kawa/ . I'm thinking maybe we should
>> do it the other way round, and have kawa-lang.org be the official Kawa URL.
>> The main reason is better branding, plus a shorter URl for people to
>> remember/type.
>>
>> The easiest and cheapest in the short term would be to host kawa-lang.org
>> on the same hosting site where I host bothner.com - which is DreamHost.
>> Of course that means it is still dependent on me, though it is possible
>> for me to create other maintainer accounts. If there is some reason
>> to move it (for example Kawa gets a corporate sponsor) it should be
>> easy to move - it's just some static web pages.
>>
>> If we do this, I'm thinking of doing it right after the move to git, and
>> have it be part of the kawa 2.3 changes.
>>
>> That means the only service remaining at GNU/FSF would be the
>> download (ftp) site. I see no major reason to move that,
>> though it would be easy to set up ftp.kawa-lang.org hosted using DreamHost.
>>
>> The mailing list(s) can stay on sourceware.org for now.
>> --
>> --Per Bothner
>> per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2016-11-13 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 2:11 Per Bothner
2016-11-13 11:54 ` Andrea Bernardini
2016-11-13 12:03 ` Andrea Bernardini [this message]
2016-11-13 15:15 ` Per Bothner
2016-11-14 0:47 ` Per Bothner
2016-11-14 21:44 ` Andrea Bernardini
2016-11-13 17:54 ` David Pirotte
2016-11-13 18:21 ` Per Bothner
2016-11-15 20:38 ` David Pirotte
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=CAPFJfsuZ3wSW8Cc916CsQMiFaWYWkOD2t50q_B9TBBzcZAeRsQ@mail.gmail.com \
--to=andrebask@gmail.com \
--cc=kawa@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).