From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] publish crowdsupply update ourselves
Date: Thu, 4 Jun 2020 19:06:40 -0700
Message-ID: <CAC2bXD4d-SBnAMkz-phOGSjutg+7U4ruJGfGqayihVb8DFvHyw@mail.gmail.com> (raw)
In-Reply-To: <CAPweEDyxMqZuxXs_H_YzirB3RY6St8orZ-xrx4+_W+8PNLBSvg@mail.gmail.com>
On Thu, Jun 4, 2020, 18:54 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> On Friday, June 5, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > since crowdsupply is taking such a long time (about 3mo, I think), I
> think
> > we should just publish the last update ourselves, otherwise it will be
> waay
> > out of date by the time it's finally published.
> >
> > We should probably also set up an announcements mailing list such that we
> > can just email everyone on it, and, since we control it, we won't have to
> > wait for crowdsupply or someone else.
> >
> > What do the rest of you think?
>
>
> they reach far more people, with a much greater impact.
>
> it is a very exclusive platform.
>
> to build the same mailing list with the same reach would require us to hire
> and create a marketing and PR team.
>
Ok, yeah, that's pretty impractical.
>
> even large well established innovative companies do not do that.
>
> what do they do?
>
> use a crowdfunding platform.
>
> i feel it is worth continuing to be patient with them, given the longterm
> support they've shown for so many years.
>
Yeah, ok. though we should at least send them another reminder email.
Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
prev parent reply index
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:37 Jacob Lifshay
2020-06-05 1:43 ` Yehowshua
2020-06-05 1:54 ` Luke Kenneth Casson Leighton
2020-06-05 2:06 ` Jacob Lifshay [this message]
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=CAC2bXD4d-SBnAMkz-phOGSjutg+7U4ruJGfGqayihVb8DFvHyw@mail.gmail.com \
--to=programmerjake@gmail.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git