From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 184] new mailing lists proposal for libre-soc.org
Date: Sun, 07 Jun 2020 00:57:20 +0000
Message-ID: <bug-184-13-t5GXsrSq8W@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-184-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=184
--- Comment #19 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #18)
> (In reply to Cole Poirier from comment #17)
> > Since we have completed the domain move, and we now have pitch meetings with
> > potential investors coming up, I think it is essential that we set up the
> > Libre-SOC-Org mailing list.
>
> they're done several weeks ago: i don't believe anyone realises that they're
> there:
>
> http://lists.libre-soc.org/mailman/listinfo
You're right, I saw the emails in april, but didn't realize then that this was
complete. Thanks so much Alain! I think this discussion now falls under the
scope of bug #366.
> > In addition to this, I'd like to suggest that we have a short weekly meeting
> > (~30 min) to discuss organizational matters, which should be recorded and
> > made available somehow. I found the OPF virtual coffee call to be very good
> > for adding some more connection to our highly distributed team. I think the
> > purpose of these meeting should be to discuss and layout proposals, for
> > further discussion on, and subject to unanimous approval by the
> > Libre-SOC-Org mailing list.
> >
> > I'm writing this here because it's directly related to mailing lists. If you
> > find my idea of the video organizational chats to be worthy of further
> > discussion, then I think this will merit the creation of a new bug report.
>
> yes go for it, i like it.
Done. Bug #367 <https://bugs.libre-soc.org/show_bug.cgi?id=367>
> > I think it's also a good idea to add a new category of bug report to the
> > thee existing "Libre-SOC Website", "Libre-SOC First SOC", and "TODO IIT
> > Madras 180nm Foundry", perhaps "Systemes Libres Organization", such that
> > technical bugs are not mixed with non-technical bugs.
>
> separate bugreport for that, too :)
Done. bug #366 <https://bugs.libre-soc.org/show_bug.cgi?id=366>
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
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@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 [this message]
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
[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
2020-04-07 15:07 ` bugzilla-daemon
2020-04-07 15:09 ` 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=bug-184-13-t5GXsrSq8W@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--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