Hi Richard,
I think both your possibilities work, and with the current state
of art, I would agree with Kate, Jilayne and Gary.
On the other hand it seems to me that exactly how to mark source
code is perhaps a bit out of the scope of SPDX (I might be wrong
though).
A project that is based
On petek, 06. september 2019 05:35:48 CEST, J Lovejoy wrote:
I really wouldn’t conflate attribution and copyright notices -
that seems to lead to a lot of unnecessarily confusion and other
energy
FWIW - this reminded me that there are some licenses that
require a specific acknowledgment (I’m
Hi all,
recently I’ve been thinking about how to store¹ additional notices that are
required by some licenses on the SPDX license list. Specifically reference
to the origin of the work, and notice of modification of original work.
I’m sure people on this list are very well aware of the
Die 1. 06. 19 et hora 00:58 Dave Marr scripsit:
> +1
>
> SPDX is only pragmatically useful to me if it generally reflects
> the licenses I’m likely to encounter when vetting community
> software.
I agree.
Although the question still remains what constitutes a popular
license – does a non-FOSS
Die 18. 01. 19 et hora 18:30 Gary O'Neall scripsit:
> Let me know if you see any issues with the proposal. We can
> always tune up the project idea over the next couple of weeks.
I can see no issues (at least after only my first coffee) and it
looks really cool to me :)
cheers,
Matija
--
On petek, 19. oktober 2018 08:08:09 CEST qiwihui wrote:
> Short Identifier: SATA
In any case, should we decide to adopt this license, I would
suggest we use a different short ID, as it could cause confusion
with the widely known SATA/Serial ATA:
https://en.wikipedia.org/wiki/Serial_ATA
On petek, 19. oktober 2018 08:08:09 CEST qiwihui wrote:
> The basic idea is, whenever using a project using SATA license,
> people shall star/like/+1 that project and thank the author.
…this brings up so many questions in me.
Would I really not be allowed to use the software, if I don’t +1
it?
First of all, I apologise for the long delay. I got distracted by
illness, work etc.
I see this discussion has progressed a bit since then. I’ll try to
weave the new parts of the thread into my old draft.
Dne četrtek, 09. avgust 2018 ob 15:43:15 CEST je James Bottomley
napisal(a):
> Sure ...
Dne četrtek, 09. avgust 2018 ob 02:46:21 CEST je James Bottomley
napisal(a):
> Most of the alternative formulations go for wordier versions, but I
> think brevity is better.
I have pondered on this for longer than I thought I would, but don’t
have a proposal I would be happy with yet.
Would
Hi James,
if there is interest, I volunteer to help with this one.
cheers,
Matija
--
gsm:+386 41 849 552
www:http://matija.suklje.name
xmpp: matija.suk...@gabbler.org
sip:matija_suk...@ippi.fr
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
Dne četrtek, 02. avgust 2018 ob 15:25:51 CEST je Kate Stewart
napisal(a):
> I think if we socialize it with the kernel community in advance, and
> then send a pull request to change the locations in the kernel and
> reference the change to the REUSE.software to implement this, we
> shouldn't
Hi all,
I’m currently battling figuring out how to integrate SPDX through
REUSE.software and am at a stage of severe head-scratching¹. I am CC’ing Jonas
(FSFE, REUSE), in case he is not actively following this list.
While I am referring to REUSE.software² here, the situation is near identical
12 matches
Mail list logo
