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

Flag a crop for edit or merging #1046

Open
CloCkWeRX opened this issue Sep 23, 2016 · 3 comments
Open

Flag a crop for edit or merging #1046

CloCkWeRX opened this issue Sep 23, 2016 · 3 comments

Comments

@CloCkWeRX
Copy link
Collaborator

We've got:

both with content. As a non crop wrangler, there's nothing I can do to fix this - can't flag a problem or recommend a merge.

Though we can add alternative names, there's no current facility to mark one crop as an alias of or superceded by another either; nor to move content.

I think marking it as superceded is the better option, as that way we don't have to migrate blog post links, plantings, photos, etc.

@pozorvlak
Copy link
Member

Agreed that this would be a good feature to have in general. I'd suggest
the following subtasks:

  • allow users to mark crops as needing crop-wrangler attention, with a
    comment as to why;
  • allow crop wranglers to mark crops as superseded;
  • write code to merge crops (migrate blog posts, etc - we need to think
    about an "undo" feature here);
  • run a one-off "merge all superseded crops" task;
  • replace the "mark superseded" button with "merge".

In this specific case, "habanero pepper" has no plantings and one post; we
could edit the post to refer to "habanero" and then delete "habanero
pepper". Does that sound OK?

Also, @CloCkWeRX, would you like to be made a crop wrangler?

On 23 September 2016 at 02:07, CloCkWeRX notifications@github.com wrote:

We've got:

both with content. As a non crop wrangler, there's nothing I can do to fix
this - can't flag a problem or recommend a merge.

Though we can add alternative names, there's no current facility to mark
one crop as an alias of or superceded by another either; nor to move
content.

I think marking it as superceded is the better option, as that way we
don't have to migrate blog post links, plantings, photos, etc.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1046, or mute the thread
https://github.com/notifications/unsubscribe-auth/AANyx-Uo7faovKysnpcUuXnfWF-uyNZIks5qsyZZgaJpZM4KEg5R
.

@CloCkWeRX
Copy link
Collaborator Author

Also, @CloCkWeRX, would you like to be made a crop wrangler?

Yeah, why not :)

@maco
Copy link
Member

maco commented Oct 11, 2016

  • write code to merge crops (migrate blog posts, etc - we need to think
    about an "undo" feature here);

that sounds like having superceding blog post versions

On Sat, Sep 24, 2016 at 12:34 AM CloCkWeRX notifications@github.com wrote:

Also, @CloCkWeRX, would you like to be made a crop wrangler?

Yeah, why not :)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1046 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYfcFnfIjbU634HRtXD5xUvFhTLpHurks5qtKhGgaJpZM4KEg5R
.

@Br3nda Br3nda added this to Backlog in Growstuff Apr 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Growstuff
  
Backlog
Development

No branches or pull requests

5 participants