From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 366] Create new buzilla product "Systemes Libres Organization"
Date: Sun, 07 Jun 2020 22:39:59 +0000
Message-ID: <bug-366-13-26xRxb5pvr@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-366-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=366
--- Comment #3 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Cole Poirier from comment #2)
> (In reply to Luke Kenneth Casson Leighton from comment #1)
> > i like this idea: it does however have implications that systemes-libre
> > (the Company) is the same as "Libre-SOC the .org", which is not the case.
> > i have no problem with using libre-soc as an interim home for SL.
>
> I see your point. Is this the place to clarify the relationship between the
> two entities? I think that this kind of clarification that needs to be
> handled in an organized and publicly documented manner, which is why I was
> recommending we use the libre-soc-org mailing list. Once this is clarified,
> perhaps it is actually a systemes-libres-org mailing list that is needed?
Since there hasn't been any discussion of this yet, but I need a place to share
the pitch that I'm working on to get technical and 'polish' feedback, I would
like to create a page for collaborative editing of the pitch deck on the wiki.
Titled "Systemes Libres Amazon Alexa IOT Pitch 10-JUN-2020". I think before I
do so however I need input/permission on whether this is allowed/the right
approach from Yehowshua, Luke, or Jacob, because I don't understand the exact
nature of the relationship between Libre-SOC and Systemes Libre.
--
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: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 0:50 [libre-riscv-dev] [Bug 366] New: " bugzilla-daemon
2020-06-07 0:55 ` [libre-riscv-dev] [Bug 366] " bugzilla-daemon
2020-06-07 1:03 ` bugzilla-daemon
2020-06-07 22:39 ` bugzilla-daemon [this message]
2020-06-07 22:45 ` 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-366-13-26xRxb5pvr@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