From: Cole Poirier <colepoirier@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Cc: "libre-riscv-dev@lists.libre-riscv.org"
<libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
Date: Sun, 22 Mar 2020 17:01:07 -0700
Message-ID: <F2F6597B-70C7-4B79-BA2F-B897A848484C@getmailspring.com> (raw)
In-Reply-To: <bug-184-13-ZvOgwzSRqn@http.bugs.libre-riscv.org/>
On Mar 21 2020, at 4:24 pm, bugzilla-daemon@libre-riscv.org wrote:
> http://bugs.libre-riscv.org/show_bug.cgi?id=184
> --- Comment #6 from vklr@vkten.in <vklr@vkten.in> ---
> (In reply to Jacob Lifshay from comment #4)
>> (In reply to Luke Kenneth Casson Leighton from comment #0)
>> > These should be *new* lists on libre-soc.org (retire libre-riscv-dev)
>> >
>> > 1) Libre-SOC-Dev, for hardware and software development (productive)
>> > discussion
>> > 2) Libre-SOC-Org, for discussion about related to the organization
>> > itself, such as funding, investing, finances, domain change, website
>> > design, members, ethics, business, administration, you get my point
>> > 3) Libre-SOC-Misc, for everything else (the non serious stuff that I
>> > can safely ignore unlike the first two which should have important
>> > stuff only)
>> > 4) Bugtracker separate list, readonly announce only, and replyto
>> set to
>> > bugzilla ready for when/if incoming bugzilla is ever set up
>>
>> I think the above proposal is a good idea. When we finally shut-down
>> libre-riscv-dev, I think we should send out a single notification
>> email to
>> everyone who's subscribed even if they have mail delivery turned off. We
>> should also announce our name & domain change on crowdsupply.
>>
>> Is everyone ok with the above plan?
>
> I am also fine with it.
I endorse this plan.
Cole
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-184-13@http.bugs.libre-riscv.org/>
2020-03-20 18:54 ` bugzilla-daemon
2020-03-21 15:47 ` bugzilla-daemon
2020-03-21 23:24 ` bugzilla-daemon
2020-03-23 0:01 ` Cole Poirier [this message]
2020-04-07 15:07 ` bugzilla-daemon
2020-04-07 15:09 ` bugzilla-daemon
[not found] <bug-184-13@https.bugs.libre-soc.org/>
2020-04-08 19:21 ` bugzilla-daemon
2020-04-09 11:20 ` bugzilla-daemon
2020-04-09 18:56 ` bugzilla-daemon
2020-04-09 19:36 ` bugzilla-daemon
2020-04-09 20:14 ` bugzilla-daemon
2020-04-09 20:28 ` bugzilla-daemon
2020-04-10 18:27 ` bugzilla-daemon
2020-05-20 5:58 ` bugzilla-daemon
2020-06-07 0:29 ` bugzilla-daemon
2020-06-07 0:31 ` bugzilla-daemon
2020-06-07 0:57 ` bugzilla-daemon
2020-06-10 13:53 ` bugzilla-daemon
2020-06-10 21:25 ` bugzilla-daemon
2020-06-14 18:57 ` bugzilla-daemon
2020-06-14 23:16 ` bugzilla-daemon
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=F2F6597B-70C7-4B79-BA2F-B897A848484C@getmailspring.com \
--to=colepoirier@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