Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11669 (closed)

Opened 7 years ago

Closed 7 years ago

Revive OmeroPyGatewayProcess

Reported by: jamoore Owned by: hflynn
Priority: major Milestone: 5.0.0-rc1
Component: Documentation Version: 4.4.9
Keywords: n.a. Cc: python-team@…, aknab
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description now redirects to plone but I don't think the content from the wiki page itself was transferred. I've attached the content from the wiki here.

See #4772 for background (content which became the wiki page)

Attachments (1)

OmeroPyGatewayProcess.txt (2.7 KB) - added by jamoore 7 years ago.
contents of wiki page of the same name exported via trac-admin wiki export

Download all attachments as: .zip

Change History (6)

Changed 7 years ago by jamoore

contents of wiki page of the same name exported via trac-admin wiki export

comment:1 Changed 7 years ago by hflynn

Having looked at this, I'm not sure where to put it. It kind of reads like development team practices but I take it to be OMERO-specific so do we want it in a new 'contributing developers' section in the public docs, or would it more properly belong in ome-internal?

comment:2 Changed 7 years ago by spli

Does this need a separate dev process from the main workflow? Is it sufficient to ensure PRs are reviewed by the right people?

comment:3 Changed 7 years ago by wmoore

Most of that document is pre-github and Kanban approach so is mostly out of date.
The rest can probably be summarised:

  • Keep Blitz Gateway commits separate from other commits.
  • cc Chris, Carlos (and Andreas) on all PRs with changes to Blitz Gateway or webgateway.
  • Keep track of Blitz Gateway API changes somewhere (not decided yet).

Other stuff (code style etc) is not restricted to Blitz Gateway.

comment:4 Changed 7 years ago by hflynn

  • Status changed from new to accepted

I will add the points Will has commented that are still relevant to the contributing developer doc team-workflow.txt

comment:5 Changed 7 years ago by hflynn

  • Resolution set to fixed
  • Status changed from accepted to closed

Remaining points identified by Will have been added to the new team-workflow.txt file in
Closing ticket as fixed.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.193035 sec.)

We're Hiring!