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

project board #843

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from
Draft

project board #843

wants to merge 10 commits into from

Conversation

MichaelMure
Copy link
Collaborator

No description provided.

@smoyer64
Copy link
Collaborator

smoyer64 commented Aug 15, 2022

I started looking this over yesterday but didn't finish. This morning, I realized that the "research" I'd promised which looked at how the GitHub and GitLab APIs represented Kanban is STILL on the computer at home.

The essence is:

Board <-- 1:n --> Columns <-- 1:n --> Bug (issue)

There shouldn't be a lot of operations changing columns on a board once they've been set up, but there will be a ton of adding and moving bugs around the columns, so caching should really help there. I had also looked at Github Projects and that's a whole different data structure (I'm assuming out-of-scope WRT Kanban).

In any case, Board looks like I'd expect. My only suggestion is that Board might want an open/closed status like bug.

@MichaelMure
Copy link
Collaborator Author

I had also looked at Github Projects and that's a whole different data structure (I'm assuming out-of-scope WRT Kanban).

Isn't that just a board with some form of transition rules?

My only suggestion is that Board might want an open/closed status like bug.

You mean that the board itself should support being "closed" ?

@smoyer64
Copy link
Collaborator

Projects can be cross-repository, so I think it's structurally similar to a board but how would the importer handle this? I also got the impression that it was possible to add cards to columns that weren't issues but it's been a few months and I'd have to look again. I'd be happy to be proven wrong too!

And yes, at least on GitHub you can mark boards as closed. I can take a look at the JSON I saved when I get back to my other computer on Monday. Better yet, I can attach the JSON to this repository for reference.

@MichaelMure
Copy link
Collaborator Author

Projects can be cross-repository, so I think it's structurally similar to a board but how would the importer handle this?

Import multiple remote repo within the same local git repo?

@MichaelMure MichaelMure added this to the 0.9.0 milestone Feb 1, 2023
@github-actions github-actions bot added the lifecycle/stale Inactive for 90d or more label Jul 23, 2024
@sudoforge sudoforge modified the milestones: 0.9.0, 0.8.1 Aug 2, 2024
@sudoforge sudoforge added lifecycle/frozen Avoids automatic lifecycle changes area/project Relates to projects kind/feature Relates to a new feature and removed lifecycle/stale Inactive for 90d or more labels Aug 2, 2024
@sudoforge sudoforge removed this from the 0.8.1 milestone Aug 2, 2024
Also rework of entity generic interfaces, in a way that allows to handle low level or cache entities the same way (ReadOnly), and another ReadWrite interface that also allow to mutate the entity. This should fix some long long standing issue around that, and notably fix the resolvers.

This is the first time an entity really load another one, which is what required that fix. Hopefully this opens the way for Identities to use the dag framework.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/project Relates to projects kind/feature Relates to a new feature lifecycle/frozen Avoids automatic lifecycle changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants