whether this is true or not.
Regardless, there are a LOT of licenses that don't have a specific
provision for moral rights. Most of them, really. Blue Oak isn't special.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender
: External Dependency?
Out of those, Venue and Choice of Law feel like they could be
consolidated. And we'll use "conflict resolution" if it's there, but if
it's not we won't miss it.
--
Josh Berkus
___
The opinions expressed in this email
to enforce it. It takes a whole project infrastructure, and a
lot more text.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
O
Pam,
Also, Kevin has a script to copy all the licenses to Github issues,
which could work for tagging them.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative
f descriptive tags. Could we do a two-part display on
the website to make sure that doesn't happen?
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official s
better licensing is not.
There is absolutely no reason to be gratuitously rude.
Daniel, please be aware that Bruce does not speak for the OSI Board or
any body of the OSI.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender
your company's mission. It just won't be open source.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open Source Initiative
-restricted licenses as well, as long as those permit
redistribution of source. While that's not necessarily a blocker to
approval, you might want to think through the implications.
6. It seems weird to call the first release of a new license &q
never been sure what it's actually used for.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open Source Initiative will be
oy any of the APL's patent claim
protections. And, if you were a downstream recipient of the code, how
would you know what license you were receiving it under?
Am I missing something here?
[1]: https://crates.io/crates/syn
--
Josh Berkus
___
The op
nt doesn't matter if they weren't successful.
We also regularly have licenses submitted that aren't written with legal
advice and are so poorly drafted that they would not be enforceable
anywhere at all. Do you really think that the OSI should approve these?
--
J
Reminder: if you are interested in this committee, the application
closes in 6 days.
On 6/26/23 15:25, Josh Berkus wrote:
Fellow licensing enthusiasts:
As some of you know, OSI currently has a legal intern reviewing all of
our data on approved licenses on our website and elsewhere. In some
On 6/26/23 16:07, Kevin P. Fleming wrote:
It appears that this form needs to have its permissions opened up to allow
people who are not members of the OSI group in Google Workspace to see it :-)
Thank you! Fixed, I think.
--
Josh Berkus
discussions.
Three to six committee members will be selected by the Board.
[1] Charter:
https://wiki.opensource.org/bin/Working-Groups-Incubator-Projects/License%20Consistency%20Working%20Group/
--
Josh Berkus
Board, OSI
___
The opinions expressed
cense expiration committee". Happy
to help with that.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open Source Initiative wi
lz4 # v14
recovery_init_sync_method = syncfs # v14
check_client_connection_interval = ... # v14
wal_compression = {lz4,zstd} # v15
If anyone has links to blogs or other things that discuss the
performance implications of the above settings that would be wonderful!
--
Josh Berkus
?
I've heard about new parallel stuff an JIT, but neither is that
applicable to my use-case.
--
Josh Berkus
s of LinShare and LinShare software Programs is mandatory notwhistanding any
other terms and conditions.
... this is the most burdensome example of an attribution notice I've
ever seen. Feels like it's a violation of 10, and possibly 6 or 8 as
well. Thoughts?
--
Josh Berkus
__
checked, flatpak was still broken. Will retest this week.
--
-- Josh Berkus
Kubernetes Community Architect
OSPO, OCTO
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org
Fedora
e main project, they just need to be open source somewhere, which
can just be a matter of creating their own public GH/GL repo.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Op
ur name). This works especially well if you
distribute your software via a version-control system that publishes
every modification as metadata (e.g., GitHub).
Yes ... a lot of folks simply have a NOTICES file that links to the
reflog, which after all has a full list of chang
Matt,
You're correct, I was being very dramatic. I've since talked to Otaylor, and
the only real problem is that the announcement of this change is misleading.
Fedora isn't "filtering" anything, you're adding Flathub packages in a place
they weren't available before. The announcement reads
Ben, FESCO:
Thank you for your decision to destroy Silverblue, the best thing Fedora has
done in the last 10 years.
The only thing that makes Silverblue useful -- indeed, superior -- as a desktop
is the ready availability of Flatpaks for any application the user could want.
Unlike
as 0BSD, but may
> still be used by some under its original submission name." or something like
> that.
Yes, and it should still be indexed as the FPL, in case someone wants to
look that up.
Which is ... kinda the situation we al
o the approval name.
Yeah, I'm OK with listing both names, but the idea that we'd remove the
original approval name, that some people are using, is a non-starter.
The current listing is 100% appropriate given the history of the
license, Rob's hyperbole and ill-considered metaphors
for whatever they wish.
Clever, Gil.
I was wondering about that as well. At best, the license would prevent
a corporation from appearing on the copyright of derivative versions.
--
Josh Berkus
___
The opinions expressed in this email are those o
ately, tacking the GDPR onto a license is just another "unrelated
conditions" license, and thus a clear violation of OSD5/6. We have OSD5
and 6 for good reasons.
--
Josh Berkus
___
The opinions expressed in this email are those of the
etty dead, and will soon shut down.
I suggest that you ask your question in Openstack, on the Magnum focus.
--
Josh Berkus
identify themselves, although
I'd like to include in that identifications that might be internet-based
rather than government-issued (e.g. "I'm 'onehacker' on Gitlab, you can
see my projects here").
--
Josh Berkus
___
The opinions
>
> Amazon’s preferred permissive license is Apache 2.0. In part because it
> doesn’t have this “dozens and dozens of pointless minor variants” problem.
For such a short license, BSD has an awful lot of variations.
Gotta be the bikeshed problem.
--
Jo
On 7/28/20 11:51 AM, Florian Weimer wrote:
>> This is just a rebranding of the Commons Clause. It is not
>> OSI-compliant, and cannot be made OSI-compliant.
> The web page says this:
I was looking at the n8n project, which is licensed under the Commons
Clause.
why open
source is superior to the shareware model, but that seems like
well-trodden ground.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statemen
On 5/13/20 11:08 AM, Tobie Langel wrote:
> Mark, LMK if you need help starting the process to get it OSI-certified.
I don't think we need anything else, we're already going over it on
license-review.
--
Josh Berkus
___
The opinions expres
question:
Is there significant use of MIT-0 in the field?
I would argue that, if there's nobody using it, we shouldn't approve it
as "technically OSS but not really needed". But if projects are using
it, then approve it as a "redundant&qu
catergory words we've
chosen work in that fasion.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open Source Initiative will be se
th attribution language
more similar to the GPLv3. Which would kinda make it the "acceptable
BSD 4-clause".
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. O
d him myself becase I think and OSI board member
should do that.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open Source Initiative
nal author, but we don't need his permission.
The license is public domain.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open
dn't have significant use anymore.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open Source Initiative will be sent from an opens
in the case of licenses in
> the badgeware category, though).
Yeah, and honestly having a license listed as "deprecated" is as
effective as actual removal for purposed of getting people to NOT draft
new licenses based on it.
--
Josh Berkus
___
fix
the badgeware clause, replacing it with a proper attribution clause.
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open
feedback it has received, and taken into account potential newly found
> projects where license is in use, can decide to remove the license from
> the list of approved licenses.
>
> - Removed licenses will be listed on a separate page on opensource.org
> <http://opensource.org>
o other license authors to write noncompliant
licenses. Deprecated licenses need to be removed in some reasonable
timeline, such as 6-12 months.
Unless you're saying that "several years" is the alternative if we don't
bother to try to track down any users/authors? If that's what you're
ctively prevents
downstream developers from ever removing the GUI from the program, or
from running it on an embedded system (thus violating OSD6 and/or OSD10).
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily t
Yeah, we used to apparently have the policy that "if nobody strenuously
objects, the license passes".
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiati
ended and nonreusable licenses".
--
Josh Berkus
___
The opinions expressed in this email are those of the sender and not
necessarily those of the Open Source Initiative. Official statements by the
Open Source Initiative will be sent from an opensource.org ema
e first part of #4 (or the
> details of #6).
oooh, nice summary. A very succinct way of putting the issue.
If you don't blog this, I'm gonna borrow it.
--
Josh Berkus
___
License-discuss mailing list
License-discuss@lists.opensource.org
http://lists.
here isn't an OSD-discuss list. This is it.
That's one reason why I would be thrilled to see OSI move to Discourse
or a similar platform; I think it would really help us separate
discussions better.
--
Josh Berkus
___
License-discuss mailing list
License-dis
(among other things) what it means
to be Open Source, up to, and including, revisions of the OSD (OSD 8/9,
I have my eyes on you). If you want a list where the OSD text is
immutable, then that's license-review.
--
Josh Berkus
___
License-d
On 3/11/20 1:09 PM, Russell McOrmond wrote:
> On Wed, Mar 11, 2020 at 9:42 AM Josh Berkus <mailto:j...@berkus.org>> wrote:
>
> Coraline showed *tremendous* patience with a list discussion not exactly
> marked by good faith or good manners on the part of at least
at is based on history. And since a lot of that
history happened in 1995-2004, it's ancient history to a lot of people.
So I'm gonna work on explaining why those clauses exist, and why they
are still relevant.
--
Josh Berkus
___
License-discuss mailin
On 3/11/20 11:36 AM, Pamela Chestek wrote:
>
> On 3/11/2020 1:42 PM, Josh Berkus wrote:
>> On 3/11/20 6:56 AM, Russell Nelson wrote:
>>>> I still say we should use the Vaccine License as a case example of an
>>>> unpassable license on our website.
>>&
various clauses of the OSD exist, and not just
do "we're experienced and we know what we're doing". Examples of
unpassable licenses *with an explanation of why they are unpassable*
would help.
For the vaccine license, I think I'll write a blog post to s
ents. License-discuss is for thought experiments.
>
> There was also something similar submitted recently IIRC; the Vaccine License
> was it?
>
I still say we should use the Vaccine License as a case example of an
unpassable license on our website.
--
Josh Berkus
__
nity of a senior manager. If
nothing else, it reflects poorly on your employer.
--
Josh Berkus
___
License-discuss mailing list
License-discuss@lists.opensource.org
http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
ntly,
violations of the CoC.
--
Josh Berkus
___
License-discuss mailing list
License-discuss@lists.opensource.org
http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
m-scratch projects in
isolation, even though that's rarely the case. In fact, I'd say that
case is so exceptional that it's not worth talking about.
--
Josh Berkus
___
License-discuss mailing list
License-discuss@lists.opensource.org
http://lists.open
uct. Violating *that* is the way to
determine who is an outsider (or at least can no longer post to the list).
--
Josh Berkus
___
License-discuss mailing list
License-discuss@lists.opensource.org
http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
iginal or even original to this
list. In his absence, not one of the ideas he so "colorfully" expressed
will be lost. In the meantime, we're missing the input of so many people
who will not participate in OSI because of our tolerance for wholl
safe space" where only
people you agree with can speak, it's cheap and easy to create your own
mailing list, and I wish you the joy of it.
--
Josh Berkus
___
License-discuss mailing list
License-discuss@lists.opensource.org
http://l
Things may have changed in the interim, but I think that a broad user
survey would still find a strong audience for a "just works" distro in
Fedora.
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
___
dev mailing list
dev@lists.openshift.redhat.co
Things may have changed in the interim, but I think that a broad user
survey would still find a strong audience for a "just works" distro in
Fedora.
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
___
users mailing list
us
All,
I know it's kind of last-minute, but I have a pass available for
GopherCon, if anyone can easily make it there on their own (travel funds
not included).
PM me.
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
On 03/15/2018 12:45 PM, Charles Moulliard wrote:
> Hi,
>
> I played the scenario showed hereafter based on OpenShift doc [1] to
> install OSE in a Centos Atomic vm but ansible reports that it can't ssh
> to 192.168.99.50
Whose IP address is 192.168.99.50? The host? The VM?
--
Josh Berkus
I haven't had a chance to try installing to the minnowboards in a while
(3 months). In the meantime, something got fixed.
They now install and boot correctly. Yay!
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
quot;the hard way" doc for FAH/CAH, but I can't
commit to putting in the time it would require to write it, since I'm
not sure who the target user for it is. Someone who wants something
"production" is going to install Origin, no?
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
view it and make sure I'm on the right track. Once I
> put something together, I'll ask Jason and others to take a look at it.
I'll help with this. Find me on kube-docs on slack?
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
com/stefwalter/oci-kvm-hook/issues/5
>
> I propose moving it into our organization to raise its visibility and
> have it not be "owned" by one person in general.
>
> Any thoughts/objections? (Or other ways people do qemu-in-containers?)
Does Stef *want* it to be moved? It'
Folks,
An Atomic BOF session has been confirmed for RH Summit in May. I will
be organizing it since Sanja won't be at this year's Summit.
Who will be at RH Summit? I'd like 4-6 people to talk about various
Atomic projects before we take questions.
--
--
Josh Berkus
Kubernetes Community
Red
fedoraproject.org/calendar/meeting/6394/
Feh, there's supposed to be a different calendar item for this. I
apparently didn't remove the old one correctly.
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
On 01/04/2018 06:10 AM, Joe Brockmeier wrote:
> Did you ask about the number of hosts for this?
I did not.
Damn! That would have been a really good question.
--
--
Josh Berkus
Kubernetes Community
Red Hat OSAS
Atomic Team:
I've prepared some graphs and a report from our docker usage survey:
https://docs.google.com/document/d/1aC8uthOMrTLiYK3l5muUVKDnOO7Rich2JxJ0sd4LJ6o/edit?usp=sharing
We'll discuss this tommorrow at the Fedora Atomic meeting (12:30 EST).
--
--
Josh Berkus
Kubernetes Community
Red
On 12/18/2017 08:00 AM, jber...@redhat.com wrote:
> Dear all,
>
> You are kindly invited to the meeting:
>General Atomic Community Meeting on 2017-12-25 from 16:00:00 to 17:00:00
> UTC
Please ignore, we are obviously not having a meeting on Christmas.
--
--
Josh Be
Sinny, Dusty, Stephen:
There's going to be a delay on posting to the projectatomic.io blog.
We've moved to OpenShift Online Pro, but DNS propogation has been
delayed, and we're waiting for the switchover before we can push more stuff.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
to the 17.x.x series (Docker CE/EE)?
If you have opinions on this, can you fill out this survey?
http://www.projectatomic.io/blog/2017/11/docker-usage-survey/
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
On 11/22/2017 11:55 AM, Josh Berkus wrote:
> Agenda:
>
> * KubeCon Plans: talks, demos, sessions, salons, booth duty.
>
> * Telling a good developer story: How do our docker-alternative tools
> integrate?
>
> * CAH Update
>
And minutes from the meeting today:
htt
rc.freenode.net, #atomic
>
> Topics for the meeting should be decided on the atomic-devel@projectatomic.io
> mailing list ahead of the meeting.
>
>
> Source: https://apps.fedoraproject.org/calendar/meeting/6394/
>
>
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
On 11/10/2017 12:53 PM, Iván Chavero wrote:
> El vie, 10-11-2017 a las 11:34 -0800, Josh Berkus escribió:
>> On 11/09/2017 05:37 PM, Iván Chavero wrote:
>>>
>>> Hello, I want to use Atomic Host on a Cubietruck but i can't find
>>> any
>>> images for
objections to deleting any of these, please let me
know them by the end of the week. Thanks!
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
Minutes:
https://www.centos.org/minutes/2017/November/atomic.2017-11-13-16.05.html
Log:
https://www.centos.org/minutes/2017/November/atomic.2017-11-13-16.05.log.html
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
Atomicans,
We have an Atomic General community meeting scheduled for tommorrow,
1600 UTC/1100 EST, channel #atomic on irc.freenode.net.
We have two short things on the agenda:
* CentOS Atomic Host Update
* Improving atomic install --system
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
and i couldn't find any.
>
>
> Can somebody give me pointers on where to find the ARM images or guides
> on how to build them?
So the good news is that we'll have images and official support for
ARM64 with the release of Fedora 27.
The Cubie is 64-bit ... is it real ARM8?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
guarantee
that the same change will be made downstream in CentOS Atomic Host or
Red Hat Atomic Host.
Help us figure out what to do, fill out the survey.
https://goo.gl/forms/2C9qFOUEIfJaGkCp2
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
here:
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-08/fedora_atomic_wg.2017-11-08-16.30.html
full log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-11-08/fedora_atomic_wg.2017-11-08-16.30.log.html
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
cent image for testing. Maybe tag with ##devel? e.g.
docker.io/projectatomic/etcd:0.3devel
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
There is also a long discussion into clarity and improvements we need to
make on the Help File:
https://pagure.io/atomic-wg/issue/354
I've added that for the next meeting.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
f26
>
> Are you running docker with overlayfs? I don' think so
>
Then it's much simpler; you just need to grow the / volume using lvextend.
So:
lvextend -L6G /dev/mapper/atomicos-root
xfs_growfs /dev/mapper/atomicos-root
This is, BTW, why we're switching to "one big volume&
Folks:
As usual, Atomic General Community meeting will be this Monday, at 12:00
EDT / 1600 UTC.
This meeting will be run by Jason Brooks.
Please post replies with items that you have for the meeting.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
Minutes here:
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-25/atomic_wg.2017-10-25-17.02.html
Full log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-25/atomic_wg.2017-10-25-17.02.log.html
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
On 10/22/2017 10:11 AM, Filipus Klutiero wrote:
> I cannot find a list of SPI employees anywhere on spi-inc.org.
>
> A list indicating each employee's role and which would quantify each
> one's work would help determine if we should seek more, less or
> different staff.
>
SPI does not have any
and aren't on the
list of members, you should probably add yourself.
https://pagure.io/atomic-wg/issue/363
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
plementing/deploying that may become part of your project
Given the above requirements, does anyone in the wide Atomic community
have projects for which they could use a cluster, or part of a cluster?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
https://meetbot.fedoraproject.org/atomic/2017-10-16/atomic-community.2017-10-16-16.02.html
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
More topics? Bring them to the meeting.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
On 10/13/2017 03:09 AM, Fabian Keil wrote:
>> THE BOARD RESOLVES THAT
>>
>> 1. SPI agrees to be listed as a Supporting Organization of the "Public
>> Money, Public Code" compaign.
> How does SPI or SPI member projects or free software in general
> benefit from this?
>
I wanted to address this
So ...
For everyone else, care to share what talks you plan to submit?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
On 10/06/2017 05:19 AM, Tomas Tomecek wrote:
> Yes, I am. That's why I'm asking. If you don't submit one, I'll make
> sure our team does it.
I would love to help with a workshop led by your team.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
On 10/05/2017 05:14 PM, Josh Berkus wrote:
> Dusty, all:
>
> So I did an upgrade-and-rollback test today, and the results are kind of
> alarming: I can't rollback.
>
> Basically, on a minnowboard, with the current release, if you upgrade,
> you are forced to pave and
... but in the meantime we might want to
warn users in case they have hardware sufficiently similar to
minnowboards. Will put that in the blog announcement.
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
ifically, I'm interested to hear whether you are planning to do a
> workshop on building images.
*should* we do one? Are you interested in helping with one?
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
1 - 100 of 7833 matches
Mail list logo
