Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Community Growth and User Adoption Plans #13

Closed
10 tasks
brooklynrob opened this issue Oct 25, 2019 · 4 comments
Closed
10 tasks

Build Community Growth and User Adoption Plans #13

brooklynrob opened this issue Oct 25, 2019 · 4 comments
Assignees

Comments

@brooklynrob
Copy link
Member

For each program and/or its component projects

  • Create/Refine plan for how to build the basis of contributors into the project and/or projects

    • What skill sets are needed?
    • What overall level of commitment (FTEs) are needed to deliver on the roadmap?
    • What support is required/requested from
      • FINOS Staff?
      • FINOS Board?
  • (For programs w/ project in "active" status or approaching activation) create user adoption and product marketing plan to drive usage and consumption

    • What support is required/requested from
      • FINOS Staff?
      • FINOS Board?
  • DAV
  • DEG
  • DT
  • FDC3
  • FDX
  • FO
  • Hadouken
  • Plexus
  • Symphony
  • Voice
@brooklynrob
Copy link
Member Author

@mcleo-d Any update here, especially in regards to our two 2020 focus projects, Perspective (CC @neilslinger) and Plexus (@paulwhitby @lspiro-Tick42)?

@mcleo-d
Copy link
Member

mcleo-d commented Feb 14, 2020

Hi @brooklynrob

  • Perspective is waiting for @neilslinger to okay an Issue / PR being raised by @mindthegab that will activate the project. @neilslinger's been away from JPMC, so I'm still waiting for the Go-no-Go as we don't want to alert the Perspective team to an unexpected PR arriving into the project.
  • The following epic has been created in the Plexus-Interop repo and assigned to @paulwhitby that sets out project activation criteria - Activating the FINOS Plexus-Interop Project plexus-interop#147. @paulwhitby's on annual leave next week, so @mcleo-d will work with @udalmik on the first parse of the project to highlight growth stories.
  • There's an open question around the Plexus API project that's been contributed into the Plexus program by @lspiro-Tick42 and whether that's in scope for this round of activation. I'm currently focused on Plexus Interop with @paulwhitby until that question is answered.

@mcleo-d
Copy link
Member

mcleo-d commented Feb 14, 2020

Hi @brooklynrob

Just to update, @mcleo-d and @mikhail are meeting on Monday 17th February at 11am UK to have a first parse at the Plexus activation criteria.

The output will be stories that fill activation gaps that will roll into discussions with @paulwhitby the following week. 👍

James.

@brooklynrob brooklynrob added the panpmc Items from when Pan PMC was meeting & operating label May 13, 2020
@mcleo-d mcleo-d removed the panpmc Items from when Pan PMC was meeting & operating label Feb 2, 2021
@maoo
Copy link
Member

maoo commented Sep 8, 2021

This issue refers to FINOS Programs, which is an entity that doesn't exist anymore. Closing issue.

@maoo maoo closed this as completed Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants