On Thursday, December 19, 2013 21:58:36 Martin Graesslin wrote:
A standard which is used, is better than a not-used proprietary format. No
matter what language it is. In the end it's about being machine readable and
any machine readable language can be converted into another. Don't like
XML?
Le jeudi 19 décembre 2013 20:50:43 Nicolás Alvarez a écrit :
2013/12/19 Aurélien Gâteau agat...@kde.org:
On Thu, 19 Dec 2013 12:13:08 +0200, Giorgos Tsiapaliokas wrote:
I definitely like the idea but I don't like xml/rdf. Why don't we just
use json?
Because DOAP is an existing format,
Le vendredi 20 décembre 2013 14:15:33 Aurélien Gâteau a écrit :
Mandatory files for a framework:
# README
Formatted in Markdown. Contains a high level overview of the framework and
links to:
- mailing list
- IRC channel
- git repo
- bugtracker
- reviewboard
# INSTALL
Formatted
On Friday 20 December 2013 Aurélien Gâteau wrote:
Are we all OK with this short-term plan?
I'm very much in favor with anything which gets us moving forward.
Bikeshedding about the format is not one of these things.
It would be great, if the fields needed for Inqlude would be available in a
On 20/12/13 19:39, Aurélien Gâteau wrote:
I created $framework.yaml file for all frameworks, and updated kf5dot to make
use of it (hackish for now). You can find updated dependency diagrams at:
http://agateau.com/tmp/kf5
I created placeholders for the missing README.md and
On Wednesday 18 December 2013 21:35:33 Christophe Giboudeaux wrote:
On Wednesday 18 December 2013 19:50:58 Alex Merry wrote:
On 18/12/13 17:54, Aurélien Gâteau wrote:
We need to have at least a COPYING file in there, with the full content
of
the license.
I believe this was already
On Thu, Dec 19, 2013 at 9:15 PM, Martin Graesslin mgraess...@kde.org wrote:
On Wednesday 18 December 2013 21:35:33 Christophe Giboudeaux wrote:
On Wednesday 18 December 2013 19:50:58 Alex Merry wrote:
On 18/12/13 17:54, Aurélien Gâteau wrote:
We need to have at least a COPYING file in
On Thursday 19 December 2013 21:22:36 you wrote:
On Thu, Dec 19, 2013 at 9:15 PM, Martin Graesslin mgraess...@kde.org
wrote:
On Wednesday 18 December 2013 21:35:33 Christophe Giboudeaux wrote:
On Wednesday 18 December 2013 19:50:58 Alex Merry wrote:
On 18/12/13 17:54, Aurélien Gâteau
On 19 December 2013 08:47, Cornelius Schumacher schumac...@kde.org wrote:
On Wednesday 18 December 2013 Aurélien Gâteau wrote:
The information in the DOAP file can also be used to generate manifest
files for Inqlude (http://inqlude.org/)
For this to work we need at least the following data
On 19 December 2013 08:47, Cornelius Schumacher schumac...@kde.org wrote:
On Wednesday 18 December 2013 Aurélien Gâteau wrote:
The information in the DOAP file can also be used to generate manifest
files for Inqlude (http://inqlude.org/)
For this to work we need at least the following data
I definitely like the idea but I don't like xml/rdf. Why don't we just use
json?
Qt is already using json and the
On Thu, 19 Dec 2013 12:13:08 +0200, Giorgos Tsiapaliokas wrote:
I definitely like the idea but I don't like xml/rdf. Why don't we
just
use json?
Because DOAP is an existing format, so it avoids reinventing the wheel.
If we decide we want to reinvent the wheel, then let's use YAML rather
On Wed, 18 Dec 2013 21:35:33 +0100, Christophe Giboudeaux wrote:
On Wednesday 18 December 2013 19:50:58 Alex Merry wrote:
On 18/12/13 17:54, Aurélien Gâteau wrote:
We need to have at least a COPYING file in there, with the full
content of
the license.
I believe this was already done before
On Wed, Dec 18, 2013 at 09:35:33PM +0100, Christophe Giboudeaux wrote:
./tier1/kjs/src/kjs/context.h: *No copyright* UNKNOWN
This is a single line: #include ExecState.h
I don't think this is copyrightable?
./tier1/kjs/src/kjs/dtoa.cpp: UNKNOWN
On Thu, 19 Dec 2013 17:18:37 +0100, Cornelius Schumacher wrote:
On Thursday 19 December 2013 14:58:36 Aurélien Gâteau wrote:
* list of licenses
Project/license
Can this be a list?
Just checked: you can have multiple license elements in the Project
element, see:
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
On Thursday 19 December 2013 14:35:29 Aurélien Gâteau wrote:
On Thu, 19 Dec 2013 12:13:08 +0200, Giorgos Tsiapaliokas wrote:
I definitely like the idea but I don't like xml/rdf. Why don't we
just
use json?
Because DOAP is an existing format, so it avoids reinventing the wheel.
Reminder:
2013/12/19 Aurélien Gâteau agat...@kde.org:
On Thu, 19 Dec 2013 12:13:08 +0200, Giorgos Tsiapaliokas wrote:
I definitely like the idea but I don't like xml/rdf. Why don't we just
use json?
Because DOAP is an existing format, so it avoids reinventing the wheel.
Everyone please keep in mind
Hi,
I'd like to gather opinions regarding the split task Ensure all the necessary
files are in place in each framework (README, license, apidox, etc. etc.),
especially defining the etc. etc. part :)
## Intro
I think the information we want to provide for each framework is to define the
On 18/12/13 17:54, Aurélien Gâteau wrote:
We need to have at least a COPYING file in there, with the full content of
the
license.
I believe this was already done before the split.
Then there is the README file. Historically we haven't been very good at
keeping them up to date, have a
On Wednesday 18 December 2013 19:50:58 Alex Merry wrote:
On 18/12/13 17:54, Aurélien Gâteau wrote:
We need to have at least a COPYING file in there, with the full content of
the license.
I believe this was already done before the split.
I added COPYING files in each frameworks which have
On Wednesday 18 December 2013 Aurélien Gâteau wrote:
The information in the DOAP file can also be used to generate manifest
files for Inqlude (http://inqlude.org/)
For this to work we need at least the following data in the DOAP file:
* machine-readable name as identifier (all lower-case, no
22 matches
Mail list logo
