Page MenuHomePhabricator

Create new labs project for development & testing of WMDE technical wishlist features/extensions
Closed, DeclinedPublic

Assigned To
None
Authored By
gabriel-wmde
Jun 6 2018, 1:05 PM
Referenced Files
None
Tokens
"Meh!" token, awarded by MichaelSchoenitzer_WMDE."Like" token, awarded by Addshore."Love" token, awarded by WMDE-Fisch.

Description

Project Name: wmde_tech_wishes

Purpose: WMDE extension testing

Wikitech username of requestor: Gabriel Birke (gbirke)

Brief description: Testing and development of new features from the "Technical Wishlist" of the German community (implemented by software engineers at WMDE). At the moment, for testing the AdvancedSearch extension, we need one web instance for MediaWiki, a DB instance and one instance for Elasticsearch.

How soon are you hoping this can be fulfilled: in the next 1-3 weeks?

Event Timeline

chasemp changed the task status from Open to Stalled.Jun 12 2018, 8:40 PM
chasemp subscribed.

We decided to mark this as stalled for our next meeting as we need to get input from team members who were not present. Nothing bad here just a very busy few weeks.

Vvjjkkii renamed this task from Create new labs project for development & testing of WMDE technical wishlist features/extensions to qjbaaaaaaa.Jul 1 2018, 1:05 AM
Vvjjkkii changed the task status from Stalled to Open.
Vvjjkkii triaged this task as High priority.
Vvjjkkii updated the task description. (Show Details)
Vvjjkkii removed a subscriber: Aklapper.
CommunityTechBot renamed this task from qjbaaaaaaa to Create new labs project for development & testing of WMDE technical wishlist features/extensions.Jul 2 2018, 3:16 PM
CommunityTechBot changed the task status from Open to Stalled.
CommunityTechBot raised the priority of this task from High to Needs Triage.
CommunityTechBot updated the task description. (Show Details)
CommunityTechBot added a subscriber: Aklapper.

We have been trying to discourage creation of new projects oriented around a team rather than a project/product. The three main problems that we have seen in the past with team ownership/scope for a Cloud VPS project are:

  • team gets disbanded/reorganized but its project needs to live on due to hosting of important VMs
  • difficulty establishing who is the primary point of contact for a given VM when trying to reclaim quota or fix a broken instance
  • tendency to close membership/participation to only team members rather than inviting participation by other volunteers

There are things that can be done to mitigate these problems. We have been working with the Reading Web team recently on some compensating controls for their legacy group project. That being said, the easiest thing to do is to create more targeted projects (for example advancedsearch) that are scoped to a product/project rather than a team. This can become a burden in other ways if a common group of developers is active on a large number of such projects, so we are willing to be flexible if good cause can be shown for project consolidation.

@gabriel-wmde, what are your thoughts about creating an 'advancedsearch' project instead of a generic 'wmde_tech_wishes' one? Does your team have a lot of other projects you are expecting to work on in parallel that would make it especially burdensome to maintain additional Cloud VPS projects for each of them?

Is this project still wanted? The task is stalled without activity since July.

Unfortunately closing this report as no further information has been provided.

@gabriel-wmde / @WMDE-Fisch: After you have provided the information asked for and if this is still wanted, please set the status of this report back to "Open" via the Add Action...Change Status dropdown. Thanks!