4:12 a.m.
I'd like to propose we use a Taiga kanban board to track the state of our
articles and the publishing schedule.
Having a board will have multiple benefits, including:
- Quick overview of the current state and the publishing schedule
- Writing comments to the articles — things to remember when editing, etc.
- Ability to move some of our activities from the meeting to the board,
such as +1's on the pitches, assigning edits and images, or even scheduling
in some cases — that could give us more time in the meeting for other
discussions that need to happen real-time
- A board will be also more intuitive and accessible to newcomers
What do you think? Do we wanna give this a try? To give people a better
idea I've created an example board [1] in the teams.fp.o Taiga.
Cheers!
Adam
[1] https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
--
Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat
4:39 a.m.
On Wed, 29 May 2019 at 11:13, Adam Samalik <asamalik(a)redhat.com> wrote:
I'd like to propose we use a Taiga kanban board to track the state of our
articles and the publishing schedule.
Having a board will have multiple benefits, including:
- Quick overview of the current state and the publishing schedule
- Writing comments to the articles — things to remember when editing, etc.
- Ability to move some of our activities from the meeting to the board,
such as +1's on the pitches, assigning edits and images, or even scheduling
in some cases — that could give us more time in the meeting for other
discussions that need to happen real-time
- A board will be also more intuitive and accessible to newcomers
What do you think? Do we wanna give this a try? To give people a better
idea I've created an example board [1] in the teams.fp.o Taiga.
I like the idea :-) +1 for me
>
> Cheers!
> Adam
>
> [1] https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
>
> --
>
> Adam Šamalík
> ---------------------------
> Senior Software Engineer
> Red Hat
> _______________________________________________
> Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
> To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraprojec...
5:38 a.m.
On Wed, May 29, 2019 at 7:12 PM Adam Samalik <asamalik(a)redhat.com> wrote:
I'd like to propose we use a Taiga kanban board to track the
state of our
articles and the publishing schedule.
Having a board will have multiple benefits, including:
- Quick overview of the current state and the publishing schedule
- Writing comments to the articles — things to remember when editing, etc.
- Ability to move some of our activities from the meeting to the board,
such as +1's on the pitches, assigning edits and images, or even scheduling
in some cases — that could give us more time in the meeting for other
discussions that need to happen real-time
- A board will be also more intuitive and accessible to newcomers
What do you think? Do we wanna give this a try? To give people a better
idea I've created an example board [1] in the teams.fp.o Taiga.
Wordpress has most of this stuff already (or we did at some point with some
of the plugins), but we have never really used it to any extent, and it
also is kind of hard to keep track of it from the birds-eye view that taiga
will give us.
A quick google search suggests that there really arent any plugins or
anything to integrate between wordpress and taiga, so when something
changes state (i.e. a pitch to a draft), we will have to manually change it
in both places, right?
cheers,
ryanlerch
Cheers!
Adam
[1]
https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
--
Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat
_______________________________________________
Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraprojec...
6:48 a.m.
On Wed, 29 May 2019 at 12:38, Ryan Lerch <rlerch(a)redhat.com> wrote:
On Wed, May 29, 2019 at 7:12 PM Adam Samalik <asamalik(a)redhat.com> wrote:
> I'd like to propose we use a Taiga kanban board to track the state of our
> articles and the publishing schedule.
>
> Having a board will have multiple benefits, including:
> - Quick overview of the current state and the publishing schedule
> - Writing comments to the articles — things to remember when editing, etc.
> - Ability to move some of our activities from the meeting to the board,
> such as +1's on the pitches, assigning edits and images, or even scheduling
> in some cases — that could give us more time in the meeting for other
> discussions that need to happen real-time
> - A board will be also more intuitive and accessible to newcomers
>
> What do you think? Do we wanna give this a try? To give people a better
> idea I've created an example board [1] in the teams.fp.o Taiga.
>
Wordpress has most of this stuff already (or we did at some point with some
of the plugins), but we have never really used it to any extent, and it
also is kind of hard to keep track of it from the birds-eye view that taiga
will give us.
A quick google search suggests that there really arent any plugins or
anything to integrate between wordpress and taiga, so when something
changes state (i.e. a pitch to a draft), we will have to manually change it
in both places, right?
My understanding was that we would move the state management of
articles in taiga. So I am not sure if still need all the current
categories in wordpress ? Otherwise I think the weekly meeting would
be a good place to maintain the board so IMO we would really only move
cards in taiga during the meeting.
>
> cheers,
> ryanlerch
>
>
> >
> > Cheers!
> > Adam
> >
> > [1]
> > https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
> >
> > --
> >
> > Adam Šamalík
> > ---------------------------
> > Senior Software Engineer
> > Red Hat
> > _______________________________________________
> > Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
> > To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraprojec...
> >
> _______________________________________________
> Fedora Magazine mailing list -- magazine(a)lists.fedoraproject.org
> To unsubscribe send an email to magazine-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraprojec...
2:34 p.m.
On Wed, May 29, 2019 at 7:48 AM Clement Verna <cverna(a)fedoraproject.org> wrote:
On Wed, 29 May 2019 at 12:38, Ryan Lerch <rlerch(a)redhat.com>
wrote:
> On Wed, May 29, 2019 at 7:12 PM Adam Samalik <asamalik(a)redhat.com> wrote:
>
> > I'd like to propose we use a Taiga kanban board to track the state of our
> > articles and the publishing schedule.
> >
> > Having a board will have multiple benefits, including:
> > - Quick overview of the current state and the publishing schedule
> > - Writing comments to the articles — things to remember when editing, etc.
> > - Ability to move some of our activities from the meeting to the board,
> > such as +1's on the pitches, assigning edits and images, or even
scheduling
> > in some cases — that could give us more time in the meeting for other
> > discussions that need to happen real-time
> > - A board will be also more intuitive and accessible to newcomers
> >
> > What do you think? Do we wanna give this a try? To give people a better
> > idea I've created an example board [1] in the teams.fp.o Taiga.
> >
>
> Wordpress has most of this stuff already (or we did at some point with some
> of the plugins), but we have never really used it to any extent, and it
> also is kind of hard to keep track of it from the birds-eye view that taiga
> will give us.
>
> A quick google search suggests that there really arent any plugins or
> anything to integrate between wordpress and taiga, so when something
> changes state (i.e. a pitch to a draft), we will have to manually change it
> in both places, right?
My understanding was that we would move the state management of
articles in taiga. So I am not sure if still need all the current
categories in wordpress ? Otherwise I think the weekly meeting would
be a good place to maintain the board so IMO we would really only move
cards in taiga during the meeting.
That would let us remove a couple 'status' values, yes. And that might
simplify some issues with writers not being able to access their
articles once they're in Pending Review. We might just have the
default status values in that case and maybe simplify the ACLs.
I'm game for this. It would be great if someone can write up a *page*
on the WP proposing how the workflow will work.
Paul
3:08 a.m.
So should we give this a try this week? I'll get everything in place before
the meeting!
On Wed, May 29, 2019 at 9:35 PM Paul Frields <stickster(a)gmail.com> wrote:
On Wed, May 29, 2019 at 7:48 AM Clement Verna
<cverna(a)fedoraproject.org>
wrote:
> On Wed, 29 May 2019 at 12:38, Ryan Lerch <rlerch(a)redhat.com> wrote:
> > On Wed, May 29, 2019 at 7:12 PM Adam Samalik <asamalik(a)redhat.com>
wrote:
> >
> > > I'd like to propose we use a Taiga kanban board to track the state
of our
> > > articles and the publishing schedule.
> > >
> > > Having a board will have multiple benefits, including:
> > > - Quick overview of the current state and the publishing schedule
> > > - Writing comments to the articles — things to remember when
editing, etc.
> > > - Ability to move some of our activities from the meeting to the
board,
> > > such as +1's on the pitches, assigning edits and images, or even
scheduling
> > > in some cases — that could give us more time in the meeting for other
> > > discussions that need to happen real-time
> > > - A board will be also more intuitive and accessible to newcomers
> > >
> > > What do you think? Do we wanna give this a try? To give people a
better
> > > idea I've created an example board [1] in the teams.fp.o Taiga.
> > >
> >
> > Wordpress has most of this stuff already (or we did at some point with
some
> > of the plugins), but we have never really used it to any extent, and it
> > also is kind of hard to keep track of it from the birds-eye view that
taiga
> > will give us.
> >
> > A quick google search suggests that there really arent any plugins or
> > anything to integrate between wordpress and taiga, so when something
> > changes state (i.e. a pitch to a draft), we will have to manually
change it
> > in both places, right?
>
> My understanding was that we would move the state management of
> articles in taiga. So I am not sure if still need all the current
> categories in wordpress ? Otherwise I think the weekly meeting would
> be a good place to maintain the board so IMO we would really only move
> cards in taiga during the meeting.
That would let us remove a couple 'status' values, yes. And that might
simplify some issues with writers not being able to access their
articles once they're in Pending Review. We might just have the
default status values in that case and maybe simplify the ACLs.
I'm game for this. It would be great if someone can write up a *page*
on the WP proposing how the workflow will work.
Paul
--
Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat
11:09 a.m.
I mentioned to Adam there's also a Kanban plugin (maybe more than one)
for WP. No problem using Taiga for this, but I wonder if the plugin is
worth investigating if it offers some way to conveniently link to
article content (drafts, etc.).
Paul
On Mon, Jun 3, 2019 at 4:08 AM Adam Samalik <asamalik(a)redhat.com> wrote:
>
> So should we give this a try this week? I'll get everything in place before the
meeting!
>
> On Wed, May 29, 2019 at 9:35 PM Paul Frields <stickster(a)gmail.com> wrote:
>>
>> On Wed, May 29, 2019 at 7:48 AM Clement Verna <cverna(a)fedoraproject.org>
wrote:
>> > On Wed, 29 May 2019 at 12:38, Ryan Lerch <rlerch(a)redhat.com> wrote:
>> > > On Wed, May 29, 2019 at 7:12 PM Adam Samalik
<asamalik(a)redhat.com> wrote:
>> > >
>> > > > I'd like to propose we use a Taiga kanban board to track the
state of our
>> > > > articles and the publishing schedule.
>> > > >
>> > > > Having a board will have multiple benefits, including:
>> > > > - Quick overview of the current state and the publishing schedule
>> > > > - Writing comments to the articles — things to remember when
editing, etc.
>> > > > - Ability to move some of our activities from the meeting to the
board,
>> > > > such as +1's on the pitches, assigning edits and images, or
even scheduling
>> > > > in some cases — that could give us more time in the meeting for
other
>> > > > discussions that need to happen real-time
>> > > > - A board will be also more intuitive and accessible to newcomers
>> > > >
>> > > > What do you think? Do we wanna give this a try? To give people a
better
>> > > > idea I've created an example board [1] in the teams.fp.o
Taiga.
>> > > >
>> > >
>> > > Wordpress has most of this stuff already (or we did at some point with
some
>> > > of the plugins), but we have never really used it to any extent, and
it
>> > > also is kind of hard to keep track of it from the birds-eye view that
taiga
>> > > will give us.
>> > >
>> > > A quick google search suggests that there really arent any plugins or
>> > > anything to integrate between wordpress and taiga, so when something
>> > > changes state (i.e. a pitch to a draft), we will have to manually
change it
>> > > in both places, right?
>> >
>> > My understanding was that we would move the state management of
>> > articles in taiga. So I am not sure if still need all the current
>> > categories in wordpress ? Otherwise I think the weekly meeting would
>> > be a good place to maintain the board so IMO we would really only move
>> > cards in taiga during the meeting.
>>
>> That would let us remove a couple 'status' values, yes. And that might
>> simplify some issues with writers not being able to access their
>> articles once they're in Pending Review. We might just have the
>> default status values in that case and maybe simplify the ACLs.
>>
>> I'm game for this. It would be great if someone can write up a *page*
>> on the WP proposing how the workflow will work.
>>
>> Paul
>
>
>
> --
>
> Adam Šamalík
> ---------------------------
> Senior Software Engineer
> Red Hat
11:15 a.m.
Yeah I think that's definitely worth looking into!
My main motivation behind having a board is to have a quick overview of
what's going on. One part of it is the board itself, and the other part is
that we could only see the content that's "active" without deleting things
from Wordpress — maybe articles that take time to write, etc. (or maybe we
should delete more things?) And comments, so we remember what we talked
about in the past regarding each article.
So if there are better ways to do this than the Taiga board, I'm definitely
up to try it!
On Mon, Jun 3, 2019 at 6:10 PM Paul Frields <stickster(a)gmail.com> wrote:
I mentioned to Adam there's also a Kanban plugin (maybe more than
one)
for WP. No problem using Taiga for this, but I wonder if the plugin is
worth investigating if it offers some way to conveniently link to
article content (drafts, etc.).
Paul
On Mon, Jun 3, 2019 at 4:08 AM Adam Samalik <asamalik(a)redhat.com> wrote:
>
> So should we give this a try this week? I'll get everything in place
before the meeting!
>
> On Wed, May 29, 2019 at 9:35 PM Paul Frields <stickster(a)gmail.com>
wrote:
>>
>> On Wed, May 29, 2019 at 7:48 AM Clement Verna <cverna(a)fedoraproject.org>
wrote:
>> > On Wed, 29 May 2019 at 12:38, Ryan Lerch <rlerch(a)redhat.com> wrote:
>> > > On Wed, May 29, 2019 at 7:12 PM Adam Samalik
<asamalik(a)redhat.com>
wrote:
>> > >
>> > > > I'd like to propose we use a Taiga kanban board to track the
state of our
>> > > > articles and the publishing schedule.
>> > > >
>> > > > Having a board will have multiple benefits, including:
>> > > > - Quick overview of the current state and the publishing
schedule
>> > > > - Writing comments to the articles — things to remember when
editing, etc.
>> > > > - Ability to move some of our activities from the meeting to the
board,
>> > > > such as +1's on the pitches, assigning edits and images, or
even
scheduling
>> > > > in some cases — that could give us more time in the meeting for
other
>> > > > discussions that need to happen real-time
>> > > > - A board will be also more intuitive and accessible to
newcomers
>> > > >
>> > > > What do you think? Do we wanna give this a try? To give people a
better
>> > > > idea I've created an example board [1] in the teams.fp.o
Taiga.
>> > > >
>> > >
>> > > Wordpress has most of this stuff already (or we did at some point
with some
>> > > of the plugins), but we have never really used it to any extent,
and it
>> > > also is kind of hard to keep track of it from the birds-eye view
that taiga
>> > > will give us.
>> > >
>> > > A quick google search suggests that there really arent any plugins
or
>> > > anything to integrate between wordpress and taiga, so when something
>> > > changes state (i.e. a pitch to a draft), we will have to manually
change it
>> > > in both places, right?
>> >
>> > My understanding was that we would move the state management of
>> > articles in taiga. So I am not sure if still need all the current
>> > categories in wordpress ? Otherwise I think the weekly meeting would
>> > be a good place to maintain the board so IMO we would really only move
>> > cards in taiga during the meeting.
>>
>> That would let us remove a couple 'status' values, yes. And that might
>> simplify some issues with writers not being able to access their
>> articles once they're in Pending Review. We might just have the
>> default status values in that case and maybe simplify the ACLs.
>>
>> I'm game for this. It would be great if someone can write up a *page*
>> on the WP proposing how the workflow will work.
>>
>> Paul
>
>
>
> --
>
> Adam Šamalík
> ---------------------------
> Senior Software Engineer
> Red Hat
--
Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat
1789
days inactive
1794
days old
magazine@lists.fedoraproject.org
7 comments
4 participants
participants (4)
-
Adam Samalik -
Clement Verna -
Paul Frields -
Ryan Lerch