On Monday 14 January 2013 17:37:28 Aaron J. Seigo wrote:
I'll add only one semi-new point:
* active, healthy communication between components teams. no more developing
in caves. no more not talking to each other. broad, inter-component
coordination.
Development plans and progress should
On Saturday 12 January 2013 17:56:14 Kevin Ottens wrote:
[*] Historical note no one will probably care about
actually, i care :) i rather suspected this was the case, given the number
of developers i've heard this same kind of story from. the reason for
moving to packages varies, but
On Monday 14 January 2013 11:16:43 Martin Gräßlin wrote:
On Saturday 12 January 2013 17:56:14 Kevin Ottens wrote:
[*] Historical note no one will probably care about
actually, i care :) i rather suspected this was the case, given the
number
of developers i've heard this same kind
ok, so finally my answers ... i deliberately waited until the discussion was
done give my own answers as it's really hard to facilitate a discussion and
participate at the same time. (well, i did poke my thoughts into the thread a
few times .. :)
On Thursday, January 10, 2013 22:05:28 Aaron J.
On Saturday, January 12, 2013 20:01:46 Alex Fiestas wrote:
On Saturday 12 January 2013 18:45:07 Aaron J. Seigo wrote:
we have 3 repositories which probably should target 4.11:
* kscreen (playground/base/)
* libkscreen (playground/libs/)
* kio_mtp (playground/base/)
they have a few
In data sabato 12 gennaio 2013 08:36:52, Martin Gräßlin ha scritto:
yes, but you cannot install it into a different directory AFAIK. It
overwrites your stable installation.
A few of the openSUSE community are working on live images based on current
master (using the same repository). I plan on
On Saturday 12 January 2013 08:36:52 Martin Gräßlin wrote:
OpenSUSE has KDE:Unstable:SC which is made up of (regularly) updated
snapshots of current git master.
yes, but you cannot install it into a different directory AFAIK. It
overwrites your stable installation.
Hi Martin,
This is
On Friday, January 11, 2013 21:13:58 Mark wrote:
Why don't we use one of the sprints for this?
i'd rather use in-person meetings for things that are difficult to do
otherwise.
testing really should not require being in person, and issues of design and
things like large refactorings are
On Friday 11 January 2013 20:37:58 Aaron J. Seigo wrote:
On Friday, January 11, 2013 18:37:44 Alex Fiestas wrote:
If we want to discuss this, we should start another thread for not going
off topic.
imho it's completely on topic.
Very well then
We talked about quality, reviews and process
On Friday 11 January 2013 13:08:03 Martin Gräßlin wrote:
My personal highlight is the menu in windeco, but that is so hidden, that I
don't expect users will find it.
From my perspective, it's not really a problem. It allows to have the feature
maturing through the power users involvement first.
On Saturday, January 12, 2013 14:08:44 Alex Fiestas wrote:
-Master
-Integration
this is what we are doing now in plasma-mobile. it has taken a bit to get used
to (mostly for me doing the integration branch; we were already using branches
heavily). i think it is working pretty well. i blogged
On Friday 11 January 2013 17:26:39 Marco Martin wrote:
On Friday 11 January 2013, Marco Martin wrote:
On Thursday 10 January 2013, Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development cycle
very fresh in mind, it is a reasonble time to
On Friday 11 January 2013 22:58:49 Martin Gräßlin wrote:
Back in the days of early 4.x I did rebuild almost every day. To me it's a
sign that our software got better, I don't have the need to rebuild just to
get the latest bug fix and most components are so feature complete that I
don't need
On Saturday, January 12, 2013 03:35:22 Christoph Feck wrote:
On Thursday 10 January 2013 22:05:28 Aaron J. Seigo wrote:
what, if anything, would you like to be done differently in 4.11?
We should honestly ask ourself, if we still take user feedback
seriously. If there is no maintainer for
This is my opinion now (no longer what I remember from the sprint).
On Saturday 12 January 2013 15:54:39 Aaron J. Seigo wrote:
On Saturday, January 12, 2013 14:08:44 Alex Fiestas wrote:
-Master
-Integration
this is what we are doing now in plasma-mobile. it has taken a bit to get
used to
On Saturday, January 12, 2013 17:01:40 Alex Fiestas wrote:
This is my opinion now (no longer what I remember from the sprint).
On Saturday 12 January 2013 15:54:39 Aaron J. Seigo wrote:
On Saturday, January 12, 2013 14:08:44 Alex Fiestas wrote:
-Master
-Integration
this is what we
On Saturday, January 12, 2013 16:00:10 Kevin Ottens wrote:
As already pointed out, this should be a set of people not a single one.
a bus number greater than 1 is important, but i also think the realities of
doing this job limits the number of people who can, will and even should be
doing it.
On Saturday 12 January 2013, Aaron J. Seigo wrote:
* when branches are merged into master (because they've passed whatever
testing set out as required) i send an email to the list noting what has
been merged into master and what is still being merged into integration
as we don't have force
On Saturday 12 January 2013, Marco Martin wrote:
yep, it works well on plasma-mobile (and yeah, needs *one* person,first
weeks of it we tried it done by more than one person and uuuh, nope ;))
wonder how much scales for something as big as the kde-workspace repo...
coulb be person a
On Saturday 12 January 2013 17:36:01 Aaron J. Seigo wrote:
On Saturday, January 12, 2013 16:00:10 Kevin Ottens wrote:
As already pointed out, this should be a set of people not a single one.
a bus number greater than 1 is important, but i also think the realities of
doing this job limits the
On Saturday, January 12, 2013 17:38:03 Marco Martin wrote:
wonder how much scales for something as big as the kde-workspace repo...
my experience with plasma-mobile seems to indicate that it is easily done by
one person. i wouldn't want to see one person doing all of kdelibs, kde-
runtime,
On Saturday 12 January 2013, Kevin Ottens wrote:
actually, i care :) i rather suspected this was the case, given the
number of developers i've heard this same kind of story from. the reason
for moving to packages varies, but fewer KDE devs run master than
probably ever before. it seems a
On Saturday 12 January 2013 17:57:37 Aaron J. Seigo wrote:
On Saturday, January 12, 2013 17:38:03 Marco Martin wrote:
wonder how much scales for something as big as the kde-workspace repo...
my experience with plasma-mobile seems to indicate that it is easily done by
one person. i wouldn't
On Saturday, January 12, 2013 18:14:21 Marco Martin wrote:
On Saturday 12 January 2013, Kevin Ottens wrote:
actually, i care :) i rather suspected this was the case, given the
number of developers i've heard this same kind of story from. the reason
for moving to packages varies, but
On Saturday, January 12, 2013 18:29:22 Alex Fiestas wrote:
In the recent past, we have had people giving ship it in reviewboard to
code that was not maintained by them and what is worst modifications that
broke (or still breaks) stuff, we should prevent this from happening.
we already
On Saturday 12 January 2013 18:45:07 Aaron J. Seigo wrote:
if they are targetted for 4.11 (or some future release even?) we'll need to
figure out how to deal with these separate repos. do they end up merged into
kde-workspace? do we put them as child repos of kde-workspace and rely on
On Saturday 12 January 2013 18:54:23 Aaron J. Seigo wrote:
so i'd like to see *more* reviewboard input rather than less.
it would be totally awesome if more people would do reviews outside their
normal teritory. E.g. me doing more reviews of Plasma stuff, but also Plasma
people doing more
On Saturday 12 January 2013 18:54:23 Aaron J. Seigo wrote:
On Saturday, January 12, 2013 18:29:22 Alex Fiestas wrote:
In the recent past, we have had people giving ship it in reviewboard to
code that was not maintained by them and what is worst modifications that
broke (or still breaks)
On Saturday 12 January 2013 19:13:29 Martin Gräßlin wrote:
On Saturday 12 January 2013 18:45:07 Aaron J. Seigo wrote:
if they are targetted for 4.11 (or some future release even?) we'll need
to
figure out how to deal with these separate repos. do they end up merged
into kde-workspace? do
On Saturday 12 January 2013 18:45:07 Aaron J. Seigo wrote:
we have 3 repositories which probably should target 4.11:
* kscreen (playground/base/)
* libkscreen (playground/libs/)
* kio_mtp (playground/base/)
they have a few things in common:
* they are all worked on by Alex F. :)
*
On Thursday 10 January 2013 22:05:28 Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development cycle
very fresh in mind, it is a reasonble time to reflect on how it went. this
thread can be a place for us to do so, if we so wish. and i hope we do so
On Thursday 10 January 2013, Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development cycle
very fresh in mind, it is a reasonble time to reflect on how it went. this
thread can be a place for us to do so, if we so wish. and i hope we do so
that we can
2013/1/10 Aaron J. Seigo ase...@kde.org:
hello.
Hi
we're nearly at the point of releasing 4.10. with this development cycle very
fresh in mind, it is a reasonble time to reflect on how it went. this thread
can be a place for us to do so, if we so wish. and i hope we do so that we can
improve
On Friday 11 January 2013, Marco Martin wrote:
On Thursday 10 January 2013, Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development cycle
very fresh in mind, it is a reasonble time to reflect on how it went.
this thread can be a place for us to
On Fri, Jan 11, 2013 at 9:56 PM, Marco Martin notm...@gmail.com wrote:
On Friday 11 January 2013, Marco Martin wrote:
On Thursday 10 January 2013, Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development
cycle
very fresh in mind, it is a
On Friday 11 January 2013 17:26:39 Marco Martin wrote:
On Friday 11 January 2013, Marco Martin wrote:
On Thursday 10 January 2013, Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development cycle
very fresh in mind, it is a reasonble time to
If we want to discuss this, we should start another thread for not going off
topic.
In the workspace sprint we had some ideas about this.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Saturday, January 12, 2013 02:04:13 Jekyll Wu wrote:
If there is such an (plasma) master available, I think he/she should
probably better spend time on development, instead of on poking others.
that's a lovely idea, but who knows who needs to be poked when but someone who
knows the
On Friday, January 11, 2013 17:53:34 Martin Gräßlin wrote:
I think it's needed and I think nobody in our inner development circle can
be part of it. We are all blind :-)
i've already said this in another email, but this is only half true.
we need people outside our inner circle looking at
On Friday, January 11, 2013 18:37:44 Alex Fiestas wrote:
If we want to discuss this, we should start another thread for not going off
topic.
imho it's completely on topic.
In the workspace sprint we had some ideas about this.
please share them :)
--
Aaron J. Seigo
signature.asc
On Friday, January 11, 2013 22:11:49 Vishesh Handa wrote:
I think this is too big for one person.
certainly one person can not do it *all*. however, as i think 4.10 has shown
rather dramatically, unless there is at least one person who is specifically
given this responsibility, nobody does
On Fri, Jan 11, 2013 at 8:43 PM, Aaron J. Seigo ase...@kde.org wrote:
On Friday, January 11, 2013 22:11:49 Vishesh Handa wrote:
I think this is too big for one person.
certainly one person can not do it *all*. however, as i think 4.10 has shown
rather dramatically, unless there is at least
On Friday 11 January 2013 17:26:39，Marco Martin :
On Friday 11 January 2013, Marco Martin wrote:
On Thursday 10 January 2013, Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development cycle
very fresh in mind, it is a reasonble time to reflect
On Friday 11 January 2013 20:37:37 Aaron J. Seigo wrote:
On Friday, January 11, 2013 17:53:34 Martin Gräßlin wrote:
I think it's needed and I think nobody in our inner development circle can
be part of it. We are all blind :-)
i've already said this in another email, but this is only half
On Friday 11 January 2013 15:20:42 Weng Xuetian wrote:
On Friday 11 January 2013 17:26:39，Marco Martin :
On Friday 11 January 2013, Marco Martin wrote:
On Thursday 10 January 2013, Aaron J. Seigo wrote:
hello.
we're nearly at the point of releasing 4.10. with this development
In data venerdì 11 gennaio 2013 22:58:49, Martin Gräßlin ha scritto:
Granted, not everyone is using Kubuntu, but I do think that other distros
could do similar (not looking into a particular direction, but there's a
Geeko on my desk)
OpenSUSE has KDE:Unstable:SC which is made up of
On Thursday 10 January 2013 22:05:28 Aaron J. Seigo wrote:
what, if anything, would you like to be done differently in 4.11?
We should honestly ask ourself, if we still take user feedback
seriously. If there is no maintainer for a particular piece of code,
simply admitting it can cause less
On Saturday 12 January 2013 00:52:36 Luca Beltrame wrote:
In data venerdì 11 gennaio 2013 22:58:49, Martin Gräßlin ha scritto:
Granted, not everyone is using Kubuntu, but I do think that other distros
could do similar (not looking into a particular direction, but there's a
Geeko on my desk)
48 matches
Mail list logo
