ct numbers.
I think it would be interesting to do both and see what the numbers say.
There certainly is a lot to be learned and to be improved here. For me
the most important step is to be more aware of energy consumption and to
try to get numbers at all. Any insight is welcome :-)
--
in/mailman/listinfo/energy-efficiency
[7]: https://webchat.kde.org/#/room/#energy-efficiency:kde.org
--
Cornelius Schumacher
orting 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 <schumac...@kde.org>
tps://wiki.kde.org/ (one
of the results of the sprint mentioned above ;-). Doesn't have to be set in
stone, but I do think this still gives a very good guide line.
--
Cornelius Schumacher <schumac...@kde.org>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
from the perspective of Inqlude and the
frameworks book.
Doing it together with PIM sounds good to me as well, although this probably
would result in a rather large sprint.
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing
issues, the review by the human
reviewer naturally focuses on more high-level questions.
--
Cornelius Schumacher schumac...@kde.org
, and make sure that we know why we
are not going with the flow, and why we are paying the price of a higher
barrier of entry and the additional effort of hosting our own infrastructure.
--
Cornelius Schumacher schumac...@kde.org
contributors and go with something like a gerrit-based solution, but if we
want to focus on new people there might be better solutions.
[1]: https://www.gnu.org/philosophy/network-services-arent-free-or-nonfree.html
--
Cornelius Schumacher schumac...@kde.org
there is no release yet, just a repository to grab the code from):
http://inqlude.org/unreleased.html.
Adding some frameworks there based on information from the yaml file would be
easy. At the moment all framework in the frameworks project are considered
stable by Inqlude.
--
Cornelius Schumacher schumac
for doing this. It's a significant improvement for the API
docs.
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
are part of the
release. So tarball names, version numbers in about dialogs, etc. would
continue to have the known version schema 4.xx or 5.xx depending on what
version of the platform/frameworks they are using. The release name would be a
pure promo thing.
Is this correct?
--
Cornelius
as introduction for people starting to use
the frameworks.
I would be happy to help with this effort and will sign up for the meeting
now.
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https
:-)
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
b211ae21d8f4414c025ac628dcbee009b05c9e36
Diff: https://git.reviewboard.kde.org/r/116538/diff/
Testing
---
Thanks,
Cornelius Schumacher
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
marked as submitted.
Review request for KDE Frameworks.
Repository: krunner
Description
---
Add configuration for ReviewBoard
Diffs
-
.reviewboardrc PRE-CREATION
Diff: https://git.reviewboard.kde.org/r/116540/diff/
Testing
---
Thanks,
Cornelius Schumacher
marked as submitted.
Review request for KDE Frameworks.
Repository: krunner
Description
---
Add README
Diffs
-
README.md PRE-CREATION
Diff: https://git.reviewboard.kde.org/r/116539/diff/
Testing
---
Thanks,
Cornelius Schumacher
to include the license (or the list of licenses) there.
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
files in there too..
Good point. So the assumption that all frameworks would have the same license
doesn't hold. We'll have to reflect that in the meta data then.
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde
want to use some more
welcoming page there in the future, though.
[1]:
https://community.kde.org/Frameworks/Epics/KF5.0_Release_Preparation/Necessary_Files
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks
, additional links, e.g. to tutorials or API
documentation need to be added, and each framework should have a nice home
page.
But for now it is a decent start. Thanks to all the people who put so much
effort into preparing the frameworks for their first release.
--
Cornelius Schumacher schumac
(kde-checkout-list.pl in
kde-dev-scripts, which might even be able to do the clones for you IIRC).
kde-checkout-list.pl --component=frameworks --clone
does indeed the trick. Thanks for the hint.
--
Cornelius Schumacher schumac...@kde.org
___
Kde
.
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
in a
structured format. I don't really care if it's XML, RDF, JSON, or whatever as
long as it can be extracted by software. So even some consistent way to
express it in a markdown README might be fine.
--
Cornelius Schumacher schumac...@kde.org
___
Kde
On Thursday 19 December 2013 14:58:36 Aurélien Gâteau wrote:
* list of licenses
Project/license
Can this be a list?
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https
knotifications krosskwindowsystem kcmutils
kcrash kdesukfileaudiopreview kidletime
kjobwidgetsknotifyconfig kservice kxmlgui
Cool. This is an impressive list.
--
Cornelius Schumacher schumac...@kde.org
to download page of release tarballs (optional)
* list of licenses
* list of authors (at least one person with a name and an email address)
* list of supported platforms
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde
On Monday 23 September 2013 11:43:58 Sebastian Kügler wrote:
On Monday, September 23, 2013 00:27:21 Cornelius Schumacher wrote:
On Thursday 19 September 2013 Sebastian Kügler wrote:
http://community.kde.org/Frameworks/Overview
I have put the data on Inqlude (see http://inqlude.org
library can stand on its own.
--
Cornelius Schumacher schumac...@kde.org
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
is only understandable, if you have inside knowledge, to 3rd parties as
documentation.
Techbase is supposed this organized documentation understandable by 3rd
parties, so only the stuff, which fits this should go there.
--
Cornelius Schumacher schumac...@kde.org
this
information. Maybe we need to just improve this or make it more accessible.
--
Cornelius Schumacher schumac...@kde.org
. The first we have in our hands, the second is
something where we need to team up with distributions.
--
Cornelius Schumacher schumac...@kde.org
,
translations, packaging, beta testing and all the other things which need to
happen around a release.
--
Cornelius Schumacher schumac...@kde.org
in KDE.
--
Cornelius Schumacher schumac...@kde.org
to achieve.
The same for releasing. We need branches for that, so that master can continue
to get feature development, while a branch is hardened for release.
--
Cornelius Schumacher schumac...@kde.org
takers for augmenting the examples with step-by-step
instructions from the real world?
--
Cornelius Schumacher schumac...@kde.org
On Thursday 09 June 2011 David Jarvie wrote:
In order to get good testing coverage, there should normally only be one
integration branch per git module. Otherwise, testing coverage will be
split between the competing integration branches.
Right.
--
Cornelius Schumacher schumac...@kde.org
pull --rebase, when pulling as this
doesn't create merge commits with local changes, which can clutter up the
history.
--
Cornelius Schumacher schumac...@kde.org
it to be a reasonable
fit for as many people as possible. Obviously we'll have to see how well it
works and adapt it, if necessary, but it should be a good start.
--
Cornelius Schumacher schumac...@kde.org
it to be a reasonable
fit for as many people as possible. Obviously we'll have to see how well it
works and adapt it, if necessary, but it should be a good start.
--
Cornelius Schumacher schumac...@kde.org
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
to the upcoming face-to-face
meetings, but we should also have a wider discussion, as this is affecting
many more people than those who will have the opportunity to be at these
meetings.
--
Cornelius Schumacher schumac...@kde.org
apps, isn't it sometimes
because KDE libraries rock?
Exactly. So if these rocking libraries are part of Qt and so available to
every single Qt developer, they can easily become part of KDE as well.
Something which is quite a barrier today.
--
Cornelius Schumacher schumac...@kde.org
41 matches
Mail list logo
