well. Who would be interested to discuss this? We have it on the agenda
for the upcoming Goals sprint end of April, but it might be worth
extending this discussion if there is broader interest.
--
Cornelius Schumacher
.
Matija suggests to add the year once as the year of file creation, but
not change it afterwards.
--
Cornelius Schumacher
ed, what we consider to be
acceptable and what not.
--
Cornelius Schumacher
at's something we probably should clarify in a trademark
policy.
--
Cornelius Schumacher
be to formulate our trademark policy
so we have a clear base to operate from for now and the future. We should look
at the trademark policies of other projects and use them as inspiration and
maybe something like a template.
--
Cornelius Schumacher
examples for REUSE compatible license usage should best
> be put on a separate wiki page for better readability.
Great, makes sense to me.
--
Cornelius Schumacher
examples for license headers which don't use the
full text of the headers but only the SPDX identifiers as specified by REUSE.
This is the more concise version and I think the one we would like to settle
on longer term. So it would be good to have explicit examples which show how
this will look like. That could be a later step, though.
--
Cornelius Schumacher
domain that CC0 doesn't solve?
--
Cornelius Schumacher
?
I'm happy to do that. I'm generating this kind of data for inqlude.org
already, so extending it for the use in OIN won't be too difficult.
--
Cornelius Schumacher
On Freitag, 24. August 2018 00:23:29 CEST Valorie Zimmerman wrote:
> >> On Monday, 20 August 2018 10:58:05 CEST Cornelius Schumacher wrote:
> >> > I don't think that anybody has a problem with having a healthy
> >> > ecosystem of
> >> > compani
der such
situations as well.
It would be good if we can have a rational debate about how we make best use
of paid work in KDE. I have the feeling that some emotions are in the way of
actually discussing the real questions. Let's put them aside for now and talk
actual business.
--
Cornelius Schumacher
his websites, please feel free to reach
> to us through sysadmin ticket.
I see an issue with inqlude.org. I'll open a ticket.
--
Cornelius Schumacher
to be
able to do so.
I'm most excited about all the fresh contributors joining the community.
Students who come through the summer of code, projects like the amazing
WikiToLearn, or new people wherever they come from. KDE is an amazing
community.
--
Cornelius Schumacher
g this out. I think this is a valuable and important step.
Will you update http://wiki.kde.org as well to reflect what you decided about
the structure?
--
Cornelius Schumacher
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
at insights
> I'm thanking Ingo for! I like the direction.
Thank you for writing this up. It expresses pretty much exactly what I'm
thinking as well. I like the direction very much.
--
Cornelius Schumacher
___
kde-community mailing li
thread we should not focus on criteria who
and what to keep out, but we should focus on what drives us forward.
--
Cornelius Schumacher
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
es me with a perspective to give
me control and freedom of my own computing needs, and leave being the uber of
mobile big data cloud containers to somebody else.
--
Cornelius Schumacher
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
convincing anybody, but about expressing the common
driver which already is there. I do think it's motivating, but I also think
there are many other motivations and concrete reasons which bring people to
KDE. In the end I feel they are compatible with a vision statement as Ingo
expre
n through the distribution outreach program. This would be
really wonderful.
In essence I think this is about better communication between KDE and
distributions, so that we can productively work on what needs to be fixed,
avoid misunderstandings, and keep a common
Akonadi stops filling up my hard disk and memory
> and... etc. etc. Promised!)
Now I am amazed...
--
Cornelius Schumacher
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
on't have the intention or time to dig deeper into the community.
With this separation in mind the structure makes more sense. That said, there
certainly are many areas where it still can be improved.
--
Cornelius Schumacher
___
kde-communi
ow to get things
done best and do what is needed for that. This will be much more helpful than
trying to nail down a documented rule.
--
Cornelius Schumacher
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
to put the KDE desktop in the center in addition to the KDE
frameworks. It's Plasma and the application which are our base and where we
are coming from. It's this whole set which gives us the integration points we
can use to expand to cloud, to devices, to other services. The desk
f we find good
answers to these questions, a whole new world opens to us.
Because in the end it's about people, giving our software to users, and enable
them to make use of all the wonderful things we can provide.
> Hope this helpful and I'm genuinely happy to be a part
ny complicated psychological twist will just make it, well,
complicated. So I think "donate" is the superior term here.
--
Cornelius Schumacher
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
term (although I kind of like Kevin's suggestion of
"product assets"). We could for example say "source code and all other data,
which is released as part of the project's product".
--
Cornelius Schumacher
___
kde-commun
anifesto discussion.
I guess the reason why I'm perceiving this as excluding non-KDE hosted
infrastructure is that I read "KDE contributor accounts must have r/w access"
as "I must be able to log in with identity.kde.org". That's obviously not
possible with many services hosted by other parties.
--
Cornelius Schumacher
___
kde-community mailing list
kde-community@kde.org
https://mail.kde.org/mailman/listinfo/kde-community
people were there. So it's not that we know nothing.
That doesn't mean that the communication around it can't be improved. From our
point of view, I would just take it from where we are and get involved.
--
Cornelius Schumacher
28 matches
Mail list logo