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

Merging projects #12

Open
stuartpb opened this issue Jan 21, 2018 · 2 comments
Open

Merging projects #12

stuartpb opened this issue Jan 21, 2018 · 2 comments
Labels
model / schema Shortcomings of the project definition structure quiddity What a thing is

Comments

@stuartpb
Copy link
Member

I just had an insight that the "Universal Domain Dashboard" project would make more sense as a feature of Parked Project, so I'm thinking I might merge it into that.

How should that project's file change in the event of a merge? I'm thinking the "name", "concept", and "formerly" fields should stay as-is, but everything else should get replaced with "merged", with the UUID of the project it was functionally merged into as the value.

There's also the question of what should happen when a project spins off an idea or splits into two (#11), as that is essentially the reverse of this, and it may make sense in some scenarios for the representations to mirror each other

This also ties into #1 (on stages outside of 0/1/2/3) and #4 (on cross-linking projects - there in text, here in data).

@stuartpb stuartpb added model / schema Shortcomings of the project definition structure quiddity What a thing is labels Jan 21, 2018
@stuartpb
Copy link
Member Author

stuartpb commented Sep 18, 2018

I think there should be two things: the UUID of the project it was merged into, and a summary of the nature of the merge (ie. for Blotpass into NilPass, it'd be "NilPass has a feature to display a hashblot for a site the way Blotpass was going to"). I guess that'd be the "Remarks" field.

The real driver for this, as I should have remembered from whenever I wrote "Look to the Use Cases", is how these project's'd be presented on https://unusual.studio/projects (which I don't think I'd templated when I wrote this): I'm thinking they'd appear within an expando on the item for the project they were merged into, labeled something like "Merged projects", in between the top line (with the project status / faint UUID) and the rest of the card (or maybe just beneath everything).

I'm also thinking they'd keep their logo, I mean, why not? Keep anything that's still around from the old project - only remove URLs if they're dead, or if they just redirect to the root URL of the project they've been merged into.

I guess they'd also keep their dex, but it's only relevant as a "historical" dex, used to gauge interest in ranking multiple projects that may have been merged into a project.

@stuartpb
Copy link
Member Author

I guess a big reason this is on my mind is because not only is NilPass eating Blotpass, but Lean Notes just acquired the scope of like half my collected writings, even though most of them were never assigned Unusual Studio UUIDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
model / schema Shortcomings of the project definition structure quiddity What a thing is
Projects
None yet
Development

No branches or pull requests

1 participant