Re: [Wikitech-l] Fiscal Year Q2 Engineering goals

[Pine W]

Hi Tilman,

After rereading that email from September, I'm still a little hazy on what
the plan is.

I see that "Starting in October, Flow will not be in active development".
But rollout of Flow will continue on an opt-in basis, I see.

I'm hazy on what is happening with regard to the ex-Flow team's focus on
helping with improvements  to structured workflows; are those workflows
with or without the involvement of Flow, and what are some examples of of
assistance to structured workflows (example: ENWP BASC?) where this team is
likely to try to improve workflows (hopefully done with local consensus)?

Is integration of other tools like Echo still planned for Flow, or has that
already happened?

I have experimented more with VE than Flow and would appreciate some
clarifications WRT what to expect from Flow as well as the other structured
collaboration goals.

Thanks,
Pine
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fiscal Year Q2 Engineering goals

[Tilman Bayer]

Hi Pine,

I can't speak for the team that is responsible for Flow. But perhaps you
overlooked that a plan for such an opt-in system was already included in
the September reprioritization announcement

which
some (present company excluded) had their drama-and-doom focused mindset
let them misinterpret as "Flow is getting killed".

On Sun, Nov 1, 2015 at 7:30 PM, Pine W  wrote:

> Thanks Toby.
>
> Some of the goals for Research and Design Research particularly interest
> me.
>
> Can you (or someone in Product and Engineering) clarify what is happening
> with Flow? I thought that development status had changed to maintenance
> only, but then I heard otherwise off-list, and now I see that there is a
> Flow-related goal to "Increase access to Flow by deploying and supporting
> an opt-in system for it". Deploying it sounds different than putting it
> into maintenace-only status. Having Flow be opt-in will probably please
> Flow's supporters, and  hopefully will be a nice incremental way to
> identify problems with it on a manageable scale, and to allow wikimarkup
> users to continue to use that more flexible option. Is the plan to continue
> an opt-in rollout and continue to allocate development resources for Flow
> beyond minimal maintenance support? Clarification would be appreciated.
>
> (Side note: there are ongoing discussions about Flow on Lila's talk page on
> Meta.)
>
> Thanks,
> Pine
> On Nov 1, 2015 7:01 PM, "Toby Negrin"  wrote:
>
> > Hi Everyone --
> >
> > A bit late but I wanted to let you know that the Engineering goals for
> the
> > 2d quarter (October to December) of this current Fiscal year are posted
> on
> > Mediawiki.org.
> >
> > https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals
> >
> > We'll be more timely in the future. Please reach out to the respective
> goal
> > owner identified in the wiki page for more information.
> >
> > -Toby
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Tilman Bayer
Senior Analyst
Wikimedia Foundation
IRC (Freenode): HaeB
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fiscal Year Q2 Engineering goals

[Pine W]

Thanks Toby.

Some of the goals for Research and Design Research particularly interest me.

Can you (or someone in Product and Engineering) clarify what is happening
with Flow? I thought that development status had changed to maintenance
only, but then I heard otherwise off-list, and now I see that there is a
Flow-related goal to "Increase access to Flow by deploying and supporting
an opt-in system for it". Deploying it sounds different than putting it
into maintenace-only status. Having Flow be opt-in will probably please
Flow's supporters, and  hopefully will be a nice incremental way to
identify problems with it on a manageable scale, and to allow wikimarkup
users to continue to use that more flexible option. Is the plan to continue
an opt-in rollout and continue to allocate development resources for Flow
beyond minimal maintenance support? Clarification would be appreciated.

(Side note: there are ongoing discussions about Flow on Lila's talk page on
Meta.)

Thanks,
Pine
On Nov 1, 2015 7:01 PM, "Toby Negrin"  wrote:

> Hi Everyone --
>
> A bit late but I wanted to let you know that the Engineering goals for the
> 2d quarter (October to December) of this current Fiscal year are posted on
> Mediawiki.org.
>
> https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals
>
> We'll be more timely in the future. Please reach out to the respective goal
> owner identified in the wiki page for more information.
>
> -Toby
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l