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

Widget Alignment and Documentation #97

Open
kltm opened this issue Oct 30, 2024 · 1 comment
Open

Widget Alignment and Documentation #97

kltm opened this issue Oct 30, 2024 · 1 comment
Assignees
Labels

Comments

@kltm
Copy link
Member

kltm commented Oct 30, 2024

Project link

https://github.com/orgs/geneontology/projects/223

Project description

The purpose of this project is to:

  • align the pathways widget version in use across the GO (i.e. noctua, amigo, alliance)
  • make sure that fixes and rollout can be done by any developer
  • move noctua to a versioned pathway widget
  • fully document the process from the POV of 1) an end user and 2) GO developers.

We would like to do this for the pathway widget (first focus) and ribbon.

Scope/Deliverables

  • Bring all GO-authored web components into a uniform development and release process
  • Deploy the most recent version of the Pathway Widget to all internal instances: AmiGO, Noctua (others?)
  • Document the functioning and installation of the widget for 'external users'
  • Set up a communication system to announce modifications (GH repo 'GO technical announcements')
  • Get a list of all known users of the widget and register them to 'GO technical announcements'

Motivations

  • Curators
    • Data will look more uniform across various implementations
  • Data consumers
    • Internal and external uses of the Pathway widget will be able to use the same version
    • New users will have clear documentation
    • Users will be notified of any changes in widget version
  • Optimizing use of internal resources
  • Current grant aim
  • Positioning for next grant
    • Solid Pathway widget that can be used to disseminate GO-CAMs

Coordination (with other resources)

  • List all impacted groups
    • UniProt, Alliance, FlyBase, PomBase. Others?
  • Get a formal approval from groups before starting the project

Tasks

TBD

Dependencies

TBD

Cost/Resources

TBD

Strengths/Opportunities

TBD

Weaknesses/Threats

TBD

Risks/Mitigations

TBD

Fail state/Withdrawal

TBD

Technical specs

TBD (template: https://docs.google.com/document/d/111UqtS3G0aJZpAijZYI3Da0t94OQpGePlPJsqZE4Tio/edit)

Personnel

PI: Chris; PO: Pascale; TL: Patrick; Other: Tremayne, Seth

Other comments

N/A

@kltm kltm added Needs LA approval Needs final approval from the Lead Architect Needs PM approval Needs final approval from the Project Manager Needs tech doc Needs PI Needs PO Needs TL labels Oct 30, 2024
@kltm kltm moved this from Hopper to Resourcing (waiting for capacity) in Project Metadata Overview Oct 30, 2024
@pgaudet

This comment was marked as duplicate.

@kltm kltm moved this from Resourcing (waiting for capacity) to Active in Project Metadata Overview Nov 12, 2024
@kltm kltm added Ready and removed Needs LA approval Needs final approval from the Lead Architect Needs PM approval Needs final approval from the Project Manager Needs tech doc Needs PI Needs PO Needs TL labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Active
Development

No branches or pull requests

2 participants