Skip to content

Commit

Permalink
Merge pull request #1944 from w3c/egekorkan-patch-1
Browse files Browse the repository at this point in the history
More concrete project management proposal
  • Loading branch information
egekorkan authored Dec 20, 2023
2 parents 10e1ad7 + 93d6982 commit 0b3fd6b
Show file tree
Hide file tree
Showing 3 changed files with 20 additions and 1 deletion.
1 change: 1 addition & 0 deletions proposals/project-management/kanbanidea.drawio
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
<mxfile host="Electron" modified="2023-12-20T12:32:07.355Z" agent="5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/20.8.16 Chrome/106.0.5249.199 Electron/21.4.0 Safari/537.36" etag="Buduf-B1hDF8zdfwfapI" version="20.8.16" type="device"><diagram id="wFE0QG_FPsp0jaGvCLVb" name="Page-1">7Vxdc+I2FP01PDLjDwzkkY8km+lmJy3pbNuXjrC1WMW2WFksZH99JVsCGwvHhro4oIcEfCXLku45Vz7WNR17Em4fCVj5z9iDQccyvG3HnnYsyzR6A/bBLW+pZWDZqWFBkCcq7Q0z9BPKM4V1jTwY5ypSjAOKVnmji6MIujRnA4TgTb7aNxzkr7oCC1gwzFwQFK1fkUf91Dp0jL39E0QLX17ZNERJCGRlYYh94OFNxmTfd+wJwZim38LtBAZ88uS8pOc9HCnddYzAiFY54W8nnL2uX7ak+xf65bfleDr7c9AVrfwAwVoMWHSWvskZiDcoDEDEjsbfcERnooT1f+z6KPA+gze85j2IKXCX8mjsY4J+svogYEUmM7BiQoWDrWGuxoyfKaoRGLM6L3JYh6ZnwKFl7KyfQUyFwcVBAFYxmif945YQkAWKxphSHAqTHM0DCoIJDjBh9gjvRvcAQhRwqL5AErJqrA+W8QzIEhI5/nQEZp8drzCKaAIwZ9xxpszyAxKKGHpGAVpErIDiVTp0dznGxOOt7DsP0p6mk0PwcocwPrfxElLXF8Ueinnl5zUD/iypKgqKIJAeZR2B24xJgOIR4hBS8saqyNK+AKhg6FAcbvZwH0gM+xmo93rCCATFFrum9yhkXwQQk0M8/4eT1DICMIdBetrvUYxZXz0JPEDX8WFJv2PZprEbbymkrcxoBQXUaC7O+fsI8GkYSCRl8GwqXD8XsBvHK+CiaLGDoaNEThmX8vixDGmapS1LW4ERCi4VSaemTg5+6Uwd0oUxSAaDGAfcJ4lNVmMuGxmOZU2VMC2NRu9jV2CVxZFDrJpDFVZNqzZW2aGA61HoPsUxC5uWwTrZD7ij5oR9W9BkxKmFOT/KIbD/fc0jfoK17kb0ccSqRJjhLdhXOGwJHRp4C8ebjhNk8oZNY7VVNesIrlmObJENOW00fyFmLlyc2dKhSXPi4AC40GdLLCT5ZbeUsHYpYTc+opADnR9v2E3GnoXqwJldpMw9/V55JE5ZgdeRBz1RDIgrSHyn5GWOCBUCBHD9NYGPvJ/ToaDEVwlFdcg+HsbqxHErH8bl1Gep0VNQY1g/itdghqWZcQYzepoZDTDDbAc1bE2NM6jhaGo0sWhclhoTQNn1jS77mwIKkilarfgdbkEbqMpLAdPXsqAtssAw+n3DqI7q+pJ2eADrqjJh9+SokYjf0xH/jIg/0BH/WFj76DKhD0Lur2ge8w9H0+QMmgw1TRqgSUs0w52mRjVqzCPgk8kn+r27+aP3/OXp1xEYd+2bfNJUwHxVunwQ0bB7CGtocpxDjpu8v2qcHPbFFbUlFPUEMIXGlSj6CSjCUVFTq2uU3m3caVXdFlVtjkfmvVX9lqi2qrb7J6rqRjff8tqhr9eAM7SDaZTS+UrXgHeZcnd9GnugeXIOT0zNkwZ40g6RnSfKUBPlHKKUJ2NponzIbbopvyflXXpg/584B2Yr6FbRmFottFQtnKKDyyHr9C6mFgqpz0owmj0x9H3u8wwznPDdZOM1yc0VCnmHUDZFNB+igECUy6YqQeEh1ELkefz0XMavoYQZWFMc70F71LMHpkoOLPdVb5D3lcxuz/jqTuEqu350qegap+Cagi90Wnrr09LPwuRhWrozKIKy0bz0CaBwwbHAE9CTJ2hfME2ajdkkqvLVVeXlONdJKa1ZEA9y1d/BbknYanuyulY0FRWN2sc3ub9+EhvqbSJeVNGMjsb0fAmbxBhH2TuSUrBY5c9TdXy/XNLhfxnfz806bDbeX0vWYbb7jiCiurTh9SEbBNLv/P0v9RuK6rBwk4+PT2FcLoC2fA2RfLuWrZUW863S2nuTj56bJ1k7NmmuJhPyg7PMvslXFP+HpezCLOMEeiF4we7a46IoUhTXVUZ6K6g1yqjeVtApykhnjukF5QSZpNeWqmuLXUq/Vsqkq0nXbzHhrHqEs2/ypfrmCdcSyXQt71W2mHA1Vzi7fP9XE+7UFe6D5sdZ5e9gaVV0Vaqo9RlyskOZNKx0OzRMkXVjSXKOk3PXzn1Zf6kSkk5Ik2OH+x+GTcoyP69r3/8L</diagram></mxfile>
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -16,11 +16,29 @@ The main question is "How do we organize the work?".
- Jan Romann: Splitting issues definitely helps. We should limit the workload of an issue in the beginning or use checkboxes per small item and open a "spinoff" issue.
- Kazuyuki Ashimura: We should think of what we have been doing so far.

## Proposal
## Proposals

**Preliminary goal from meetings:**

- An MVP is one place to look at the list of "work" to do in a short period. We can make sure to limit the load of a person per 1-2 week timeframe and thus prioritize certain issues/topics.
- A prioritization should happen and should be aligned with use cases and requirements, i.e. how do we choose the small list of work to do

### Proposal from Ege Korkan

- Create three tables in a GitHub project: Extraction, Sorting and Assigning
- Use the sorting table to categorize issues into topics we agree on via work item categories, i.e. `bindings`, `data mapping`, where each category is a column. The granularity of categories is to be discussed. The backlog of this table is uncategorized issues. This table is edited primarily outside of the calls, i.e. as issue or use case shows up.
- Use Assignment table to track who is most suited for the issue and whether that is being worked on. Based on people's availabilities, move issues to "in progress". The backlog of this table is categorized issues. This table is edited primarily during calls.
- Use extraction table for dealing with use cases. After a process (to be defined) there should be concrete issues created. The backlog of this table is use cases, the product is uncategorized issues for the sorting table. They can be categorized already in this stage and moved to the correct column in the sorting table.

This proposal is illustrated in the figure below:

![kanbanidea](./kanbanidea.drawio.png)

Here we see that no issue that is not categorized is in the assignment table, i.e. issues 1, 2 and 3.
Also, we see that a person can get assigned to issue since they are the best fit (more expertise, more motivation etc.) but is not necessarily doing it right now.
Since Person2 has less availability, they are working only on Issue 10 while having Issue 7 and 9 assigned to them.
Person1 has more time and is working Issue 5 and 6, while having assigned Issue 4 as well.

## Procedure

Concrete procedure text will come here.
Expand Down

0 comments on commit 0b3fd6b

Please sign in to comment.