Glad to hear people like the new workflow!
On Wed, Sep 25, 2019 at 4:30 PM Gregory Lee Bartholomew <
gregory.lee.bartholomew(a)gmail.com> wrote:
I agree, this new system looks great.
I may have found one small bug though -- I received an email notice from
the
system about Adam's comment this morning, but I never received an email
notice
about Paul's follow-up comment on the same thread. If I hadn't gone
through the
web interface, I wouldn't have known that Paul commented.
I think I know what happened.
The ideas was submitted by myself as part of the transition to the new
workflow. Normally it would be you submitting your own idea, and in that
case you'd get all notifications from the ticket. But because it was me,
you're not getting everything, just mentions. I've mentioned you directly,
but Paul has only replied to the ticket.
So in the future this won't happen as people will submit their proposals
themselves.
FYI,
gb
On Wed, 2019-09-25 at 09:52 -0400, Paul Frields wrote:
> This is great work, Adam. This morning's meeting went really well also --
> the new workflow makes it easier, I think, to move things through the
> process. Well done!
>
> On Wed, Sep 25, 2019 at 6:48 AM Adam Samalik <asamalik(a)redhat.com>
wrote:
>
> > Hi everyone!
> >
> > I just want to confirm that all the things regarding the new workflow
we've
> > discussed [1] are now in place!
> >
> > The documentation [2] describes the whole process, including how to
propose
> > ideas [3] and tracking articles from a spec all the way to being
published
> > [4]. I've also refreshed the contributor-oriented pages in the docs as
> > well.
> >
> > == Next actions ==
> >
> > 1/ Review proposals — See the article proposals [3] and put your
comments
> > in there. The goals is to clarify what the proposal means and to write
an
> > article spec [5].
> > 2/ Review articles that are ready — If you contribute as an editor,
see the
> > "Review" column on the board [4] and decide if the article is ready
to
go
> > [6].
> > 3/ Write articles — There are many topics you can write about yourself
in
> > the "Article Spec" column on the board [4]. Go ahead and write
something!
> > [7]
> >
> > Let's have some fun!
> >
> > Cheers,
> > Adam
> >
> >
> > Reference:
> > [1] New workflow proposal:
https://pagure.io/fedora-magazine/issue/2
> > [2] Documentation:
> >
https://docs.fedoraproject.org/en-US/fedora-magazine/workflow/
> > [3] Article proposals:
https://pagure.io/fedora-magazine-proposals/issues
> > [4] Tracking article states:
> >
https://teams.fedoraproject.org/project/asamalik-fedora-magazine/kanban
> >
> > Next actions:
> > [5] Workflow - Clarification:
> >
> >
https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-clarification/
> > [6] Workflow - Review:
> >
https://docs.fedoraproject.org/en-US/fedora-magazine/workflow-review/
> > [7] Workflow - Writing:
> >
https://docs.fedoraproject.org/en-US/fedora-magazine/writing-an-article/
> >
> > --
> >
> > 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://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > 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://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/magazine@lists.fedoraprojec...
--
Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat