Track Progress of Resolution 014: Budget 008: Critical Fixes - 2023-12-06 #547

Closed
opened 2024-01-08 14:18:43 +00:00 by p4u1 · 8 comments
Member

https://docs.coopcloud.tech/federation/resolutions/passed/014/

  • #535 Comment parsing and modifiers
  • #519 abra app new [<recipe>] [<version>]
  • #518 Abra fails silently if required image doesn't exist
  • #527 abra catalogue generate ignores the specified recipe
    • Waiting for Feedback
  • #509 abra app remove could wait until volume is not in use
  • #530 abra recipe fetch can only fetch a single recipe
  • #525 prevent abra app cp from applying file permissions.
  • #537 Fix the operators tutorial
    • No Progress yet
https://docs.coopcloud.tech/federation/resolutions/passed/014/ - #535 Comment parsing and modifiers - Done in https://git.coopcloud.tech/coop-cloud/abra/pulls/391 - Was implemented outside of the resolution - #519 `abra app new [<recipe>] [<version>]` - Done https://git.coopcloud.tech/coop-cloud/abra/pulls/400 - Took 1 hours to implement - #518 Abra fails silently if required image doesn't exist - Done in https://git.coopcloud.tech/coop-cloud/abra/pulls/395 - Took 1 hour to implement - #527 abra catalogue generate <recipe name> ignores the specified recipe - Waiting for Feedback - #509 abra app remove could wait until volume is not in use - Done https://git.coopcloud.tech/coop-cloud/abra/pulls/399 - Took 1 hour to implement - #530 abra recipe fetch can only fetch a single recipe - Done https://git.coopcloud.tech/coop-cloud/abra/pulls/401 - Took 2 hours to implement - #525 prevent abra app cp from applying file permissions. - Done in https://git.coopcloud.tech/coop-cloud/abra/pulls/390 - Was implemented outside of the resolution - #537 Fix the operators tutorial - No Progress yet
Owner

Think most of these are merge-able now.

Only blocker on a release is that abra app backup restore is not really in a working state?

Think most of these are merge-able now. Only blocker on a release is that `abra app backup restore` is not really in a working state?
Owner

Only coop-cloud/abra#401 to merge and @knoflook and @wykwit are aiming to work on #537 potentially with @basebuilder by the end of january.

Only https://git.coopcloud.tech/coop-cloud/abra/pulls/401 to merge and @knoflook and @wykwit are aiming to work on https://git.coopcloud.tech/coop-cloud/organising/issues/537 potentially with @basebuilder by the end of january.
Owner

RE: #537 (comment) @wykwit @p4u1 @knoflook @basebuilder it might be worth having a quick coordination amongst yourselves to see what hours have been used and what haven't for this resolution/budget? Please send your invoices!

RE: https://git.coopcloud.tech/coop-cloud/organising/issues/537#issuecomment-19525 @wykwit @p4u1 @knoflook @basebuilder it might be worth having a quick coordination amongst yourselves to see what hours have been used and what haven't for this resolution/budget? Please send your invoices!
Author
Member

I updated the issue with the hours it took to implement this. Am also sending an invoice now.

I updated the issue with the hours it took to implement this. Am also sending an invoice now.
Member

I made some progress on #537 this is hanging for review in pull-request #248. I would like to firstly merge that in, and then make further contributions to the Operators docs to finish this issue.

Shortly after my first few contributions I was given write access to the website repos. I received positive review on #537 from @decentral1se and applied requested changes. In theory I can just merge these changes in. However, I am hesitant to do so, but perhaps I shouldn't be? 🤔

I opened #576 as a proposal towards clarifying such things more broadly.

I made some progress on #537 this is hanging for review in pull-request [#248](/coop-cloud/docs.coopcloud.tech/pulls/248). I would like to firstly merge that in, and then make further contributions to the Operators docs to finish this issue. Shortly after my first few contributions I was given *write* access to the website repos. I received positive review on #537 from @decentral1se and applied requested changes. In theory I can just merge these changes in. However, I am hesitant to do so, but perhaps I shouldn't be? 🤔 I opened #576 as a proposal towards clarifying such things more broadly.
Owner

I feel like I might be running into the meaning of #576 with this but...

I made some progress on #537 this is hanging for review in pull-request #248. I would like to firstly merge that in, and then make further contributions to the Operators docs to finish this issue.

Do throw in an invoice to the open collective for the work once you're done!

Thanks for the work!

I feel like I might be running into the meaning of https://git.coopcloud.tech/coop-cloud/organising/issues/576 with this but... > I made some progress on #537 this is hanging for review in pull-request #248. I would like to firstly merge that in, and then make further contributions to the Operators docs to finish this issue. Do throw in an invoice to the open collective for the work once you're done! Thanks for the work!
Member

Apologies my bad- I think my wording bled two things together between the issues. I'll send my invoice for 8 hrs shortly. But I still have more improvements i'd like to do on #537

Apologies my bad- I think my wording bled two things together between the issues. I'll send my invoice for 8 hrs shortly. But I still have more improvements i'd like to do on #537
Owner

Thanks @basebuilder & no worries. I'll close this off for now then since we're tracking the rest elsewhere. Well done all!

Thanks @basebuilder & no worries. I'll close this off for now then since we're tracking the rest elsewhere. Well done all!
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#547
No description provided.