[go: up one dir, main page]

Page MenuHomePhabricator

Clarify RelEng support for WMF Community Resources Team on software-related grant applications
Open, Needs TriagePublic

Description

The now defunct Developer-Advocacy team provided input on technology/software related grant requests: The WMF Community Resources Team has reached out to @Aklapper on a per-application basis.
@Aklapper moved from Developer-Advocacy to Release-Engineering-Team.

Older links:

Previous program, to be discontinued: https://meta.wikimedia.org/wiki/Grants:Project/Rapid/Browse_applications
Current program: https://meta.wikimedia.org/wiki/Grants:Programs/Wikimedia_Community_Fund
Note that as of 2022, the Grants concept is in the process of being reworked.

Non-public notes: https://docs.google.com/document/d/1cU589cNoxcpTNAqL4SWkUEPTAOgGp6DjznlS9p5pDsQ/edit#

Event Timeline

Aklapper created this task.

To use for Community Resources and Technical Engagement as a base template on a per-case basis: https://docs.google.com/document/d/12wQqwv28TBrA8Vw65q309aQe5nHEfbeMujXhN4r0KQ0/edit

Aklapper added a subscriber: Bmueller.

@Bmueller: I think we would still welcome more clarification when it comes to criteria for [not] funding projects repeatedly/continuously? Or did I miss something in meetings about this?

Unassigning myself as I have not received a reply to the previous comment yet

@Aklapper this is now a task for July-Sept, as discussed during quarterly planning. Apologies for the delay in following up here on the ticket. Melinda will be the assignee of this ticket.

Aklapper added a subscriber: TBurmeister.

@TBurmeister: Hi, tasks must have at least one active team project tag or codebase project tag so a task can be found in a related bucket (task search result, workboard, etc). Thus I'm re-adding Developer-Advocacy as this task is about Developer-Advocacy (and nothing else applies).

Current status:

Currently, proposals are still under "Rapid Funds" on a per-case basis; we use a non-public template at https://docs.google.com/document/d/12wQqwv28TBrA8Vw65q309aQe5nHEfbeMujXhN4r0KQ0/edit (covering aspects like getting input from another reviewer on completion vs money, if the result will be a Minimum Viable Product and thus if priorities are clear, thinking about potential unintended side effects, consideration of potential edge cases, what is covered and what not, etc) to request feedback from Developer-Advocacy on software related grant proposals.

Since September 2022, https://meta.wikimedia.org/wiki/Grants:Programs/Wikimedia_Research_%26_Technology_Fund outlines software related funds.
As of today, this says "Coming soon". Thus this is not really actionable yet when it comes to potential topics / questions that applicants should cover in their proposal.

this is now a task for July-Sept, as discussed during quarterly planning.

For the records, apart from 1 meeting to discuss things a bit, this task never happened as part of some quarterly "planning" in WMF.

Since Technical Engagement no longer exists as a team / department, marking this as Declined.

Aklapper renamed this task from Clarify Technical Engagement support for WMF Community Resources Team on software-related grant applications to Clarify RelEng support for WMF Community Resources Team on software-related grant applications.Oct 9 2023, 11:08 AM
Aklapper reopened this task as Open.
Aklapper raised the priority of this task from Low to Needs Triage.
Aklapper updated the task description. (Show Details)
Aklapper removed subscribers: TBurmeister, Bmueller.