Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] publish crowdsupply update ourselves
@ 2020-06-05  1:37 Jacob Lifshay
  2020-06-05  1:43 ` Yehowshua
  2020-06-05  1:54 ` Luke Kenneth Casson Leighton
  0 siblings, 2 replies; 4+ messages in thread
From: Jacob Lifshay @ 2020-06-05  1:37 UTC (permalink / raw)
  To: Libre-RISCV General Development

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?

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [libre-riscv-dev] publish crowdsupply update ourselves
  2020-06-05  1:37 [libre-riscv-dev] publish crowdsupply update ourselves Jacob Lifshay
@ 2020-06-05  1:43 ` Yehowshua
  2020-06-05  1:54 ` Luke Kenneth Casson Leighton
  1 sibling, 0 replies; 4+ messages in thread
From: Yehowshua @ 2020-06-05  1:43 UTC (permalink / raw)
  To: Libre-RISCV General Development

Lets wait for crowd supply.

No rush right now. MHO

Yehowshua

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [libre-riscv-dev] publish crowdsupply update ourselves
  2020-06-05  1:37 [libre-riscv-dev] publish crowdsupply update ourselves Jacob Lifshay
  2020-06-05  1:43 ` Yehowshua
@ 2020-06-05  1:54 ` Luke Kenneth Casson Leighton
  2020-06-05  2:06   ` Jacob Lifshay
  1 sibling, 1 reply; 4+ messages in thread
From: Luke Kenneth Casson Leighton @ 2020-06-05  1:54 UTC (permalink / raw)
  To: Libre-RISCV General Development

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.

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.

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [libre-riscv-dev] publish crowdsupply update ourselves
  2020-06-05  1:54 ` Luke Kenneth Casson Leighton
@ 2020-06-05  2:06   ` Jacob Lifshay
  0 siblings, 0 replies; 4+ messages in thread
From: Jacob Lifshay @ 2020-06-05  2:06 UTC (permalink / raw)
  To: Libre-RISCV General Development

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-05  1:37 [libre-riscv-dev] publish crowdsupply update ourselves Jacob Lifshay
2020-06-05  1:43 ` Yehowshua
2020-06-05  1:54 ` Luke Kenneth Casson Leighton
2020-06-05  2:06   ` Jacob Lifshay

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