Le 06/12/2015 22:16, Rick Timmis a écrit :
Hi Olivier
My day to day job is as a product development manager. So running
sprints is a core part of my job.
Happy to do this for this task.
Nice!
Luigi, suggests focusing on Techbase.
It is important to focus on one Product at a time, the first step is
to generate a backlog, largely in the manner that you described in
your opening email Olivier.
I also agree with what Luigi says, because I think Techbase is the
easiest part as there is no so much discussion and reforming to do, but
just organize the existent.
Thanks
Rick
On 06/12/15 18:45, Olivier Churlaud wrote:
Hi,
I however would need help...
I've never organized nor taken part of a sprint... So I would be glad
to get some pieces of advice to do it.
@Valorie: I heared that you'd been here for some time and that you're
one of the community manager (?). Maybe you are the good person to
help me on this?
Anyone with some experience in this is welcome to give me some hints
about where to begin, what should be thought of and so on.
Cheers
Olivier
Le 05/12/2015 22:45, Valorie Zimmerman a écrit :
On Wed, Dec 2, 2015 at 3:10 PM, Olivier Churlaud
<oliv...@churlaud.com> wrote:
Hi,
I'm coming here with this observation: the wiki are quite a mess.
And very
often KDE4 and KF5 things are mixed.
That everyone do it at their scale is impossible. That's why I have a
proposition. (I've thought about it for a while)
It would be easier to do this like in a sprint, in team.
1) Define what structure the wiki should have: What is techbase?
What is
Community? Are the manuals in Userbase or on doc? and so on
2) then take each page and order => Archive KDE4 | Mess | KF5 | To
remove
3) Do a list of what is missing and what should be tidied.
4) Write to the corresponding teams so that they take care of it.
5) Remove what should be
What I mean in 2) is: for example there are N pages about how to
configure
Git. We take the good one, put the other in a namespace "To remove"
What I mean in 4) is: for example in
https://community.kde.org/Sonnet, it's
very old, and not much documented (sorry if some of you are reading
this, I
pick it randomly), so we can put a mail on the ML and tell them
'well we saw
that...'
Basically this is my vision of what could be done.
Since I don't always know what is old what is still usable and so
on, people
with this knowledge would be required.
I think we should plan it very carefully, to have a battle plan,
and then
go.
What do you think?
Would people be interested to give a hand?
How and when do we begin?
Cheers
Olivier
Sounds good to me! And I certainly would be willing to help, whether
remotely or at a physical sprint.
Valorie
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
