Event: {E19} Last meeting notes: (none? previously: [[/w/planning_meetings/2022-10-18/|2022-10-18]]) --- ==Attendees: In alphabetical order: - @avivey - aka "The Reviewer" - @ollehar - aka "The Mantissa master" - @valerio.bozzolan - aka "The micro Diff flooder" --- ==Agenda Items and Notes: # ReViEw SPrInT 🤩 - https://we.phorge.it/differential/ - {D25081} - author note: this is a edit in the documentation, let's check our personal installations as double-check - {D25087} - author note: this is an easy-peasy fix! - {D25099} - author note: this is simple to review together, with a beer nearby our laptop - {D25079} - author note: this is true magic - {D25078} - author note: while I was at it, we fixed the style - {D25086} + D25085 - author note: reeealy easy-peasy # Bonus points (if there is time) 🎁 - {D25066} + D25093 - author note: this is //not// super simple - but you will love it --- ==Action items: # ollehar is evaluating a migration from Mantis to Phorge - invited by valerio.bozzolan shared 5 minutes of info about Mantis # valerio.bozzolan asked some questions about Mantis. It seems: # Task Dependencies: # → Phorge has a flexible Task dependency system → example: see this nice Task: https://we.phorge.it/T15187 # → after 15 years of use, today we discovered that also Mantis "somehow have" a parent/child field (wow!) but it does not render it visually, and it's just an extra field to a Task it seems # Visibility/Edit privileges: # → Phorge has a very flexible permission system. For each damn component you can have default permissions (example: visible to: public, editable by: all users), and then a per-object permission visibility (example: single Task visible to: Security Team). Note that, if something is not visible, it's also not editable. You can say: this Task is visible only to "Security Team", or only to "Legal Team" or "Visible Only to Me" or "Visible Only to Foo and Bar. # → Mantissa, it seems it has a "Private" flag. It limits the visibility to a single specific list of users. # Task collaboration workflows # → In Phorge (having said that comments can be edited only by yourself obviously), Task descriptions can be edited in a collaborative way. In this way, the community can discuss, and co-work to produce a clear Task description, to then present it to the maintainers. But, if you want, you can set custom Editable permissions (like: only Trusted Users, only during 09:00-18:00, only during fool moon, or whatever you want) # → In Mantissa, you cannot collaborate on the Task description. Only the administrator can. # Commit hooks # → In Phorge, if a commit message has a description like `Closes T123`, then, when it's published in the main branch, it automatically closes that Task; it connects to that Task, it is mentioned in that Task, and it auto-assign the commit user to that Task as closer user. This allows immediate response, and avoids to go back and search which Tasks need to be closed. Also, it simplify internal documentation, since it's really easy to see, for each Task, what was the related implementation. # Administration levels # → In Phorge, there is a component to make questions and answers, separated from the Task system but connected to it. So, "beginners" can ask Questions, and it's onboard, without the need of a forum. The system is a bit like StackOverflow: community is invited in adding Comments to the questions, Comments to the Answers, to collaborate on the Question itself and to the Answers, so, there are high quality questions and answers. # → Mantissa does not have a forum # Wiki # → In Phorge, if you need a space to quickly create a document, like "Instructions for the newcomers", you can quickly create a Wiki page. That's an embedded component. You can decide who can edit that. People can add comments to report issues. # → In Mantissa, there is not a wiki. # Calendar # → In Phorge, if you need a reminder, for example "remember me in 4 days that I need to do that", you can just create a [[ https://we.phorge.it/calendar/ | Calendar ]] event and it automatically sends you an email when it's soon. Also, your Events are bulk-exportable to Google Calendar with a secret iCal URL that contains all the Events. Or you can import Events as well from an external iCal. # → In Mantissa, there is not a Calendar # Mockup # → In Phorge, designers can upload a Mockup like this: https://gitpull.it/M15 and do inline comments over an image # → In Mantissa, there is not such component # Answer by Email # → In Phorge, you can receive email notifications, and you can answer to them via email too. You comment is automatically published on the web interface. # → In Mantissa, answering by email is not probably possible # Automatic Rules # → In Phorge, administrators can set very powerful rules like "if something happens", "with these conditions", "do something" and it always surprising to see that it's very flexible. This is used from, automatic Tagging stuff from keywords, automatic Subscribe people if title contains something, automatic mark as Invalid if it contains weird stuff; but also: automatic do something if a commit was published. It is even able to block commits if they contain something, etc. This is something I think unique in Phorge. # → In Mantissa, probably this feature does not exist. # API # → In Phorge, you have self-documented APIs to export and import stuff: https://we.phorge.it/conduit/ . For example this creates a Task: https://we.phorge.it/conduit/method/maniphest.createtask/ . and this edit a Task: https://we.phorge.it/conduit/method/maniphest.edit/ and this search Tasks: https://we.phorge.it/conduit/method/maniphest.search/ # → Mantissa API? # avivey welcomed valerio.bozzolan in the community, listening to the following patches: # https://we.phorge.it/differential/query/GpyOvoQyv9Bv/#R # Some patches still deserves more eyes on it: # {D25099} # {D25097} # {D25080} # {D25079} ← the "Not Super Mario Coin" sound was not merged today # the changelog was updated [[ planning_meetings/2023-03-27/ ]] to mention the closed patches, that were: # {D25081} # {D25087} # {D25086} # {D25100} ----- (This page used this [[/w/planning_meetings/template/|Template]])

Event: {E19} Last meeting notes: (none? previously: [[/w/planning_meetings/2022-10-18/|2022-10-18]]) --- ==Attendees: In alphabetical order: - @avivey - aka "The Reviewer" - @ollehar - aka "The Mantissa master" - @valerio.bozzolan - aka "The micro Diff flooder" --- ==Agenda Items: # ReViEw SPrInT 🤩 - https://we.phorge.it/differential/ - {D25081} - author note: this is a edit in the documentation, let's check our personal installations as double-check - {D25087} - author note: this is an easy-peasy fix! - {D25099} - author note: this is simple to review together, with a beer nearby our laptop - {D25079} - author note: this is true magic - {D25078} - author note: while I was at it, we fixed the style - {D25086} + D25085 - author note: reeealy easy-peasy # Bonus points (if there is time) 🎁 - {D25066} + D25093 - author note: this is //not// super simple - but you will love it --- == Meeting Notes: # ollehar is evaluating a migration from Mantis to Phorge - invited by valerio.bozzolan shared 5 minutes of info about Mantis # valerio.bozzolan asked some questions about Mantis. It seems: # Task Dependencies: # → Phorge has a flexible Task dependency system → example: see this nice Task: https://we.phorge.it/T15187 # → after 15 years of use, today we discovered that also Mantis "somehow have" a parent/child field (wow!) but it does not render it visually, and it's just an extra field to a Task it seems # Visibility/Edit privileges: # → Phorge has a very flexible permission system. For each damn component you can have default permissions (example: visible to: public, editable by: all users), and then a per-object permission visibility (example: single Task visible to: Security Team). Note that, if something is not visible, it's also not editable. You can say: this Task is visible only to "Security Team", or only to "Legal Team" or "Visible Only to Me" or "Visible Only to Foo and Bar. # → Mantissa, it seems it has a "Private" flag. It limits the visibility to a single specific list of users. # Task collaboration workflows # → In Phorge (having said that comments can be edited only by yourself obviously), Task descriptions can be edited in a collaborative way. In this way, the community can discuss, and co-work to produce a clear Task description, to then present it to the maintainers. But, if you want, you can set custom Editable permissions (like: only Trusted Users, only during 09:00-18:00, only during fool moon, or whatever you want) # → In Mantissa, you cannot collaborate on the Task description. Only the administrator can. # Commit hooks # → In Phorge, if a commit message has a description like `Closes T123`, then, when it's published in the main branch, it automatically closes that Task; it connects to that Task, it is mentioned in that Task, and it auto-assign the commit user to that Task as closer user. This allows immediate response, and avoids to go back and search which Tasks need to be closed. Also, it simplify internal documentation, since it's really easy to see, for each Task, what was the related implementation. # Administration levels # → In Phorge, there is a component to make questions and answers, separated from the Task system but connected to it. So, "beginners" can ask Questions, and it's onboard, without the need of a forum. The system is a bit like StackOverflow: community is invited in adding Comments to the questions, Comments to the Answers, to collaborate on the Question itself and to the Answers, so, there are high quality questions and answers. # → Mantissa does not have a forum # Wiki # → In Phorge, if you need a space to quickly create a document, like "Instructions for the newcomers", you can quickly create a Wiki page. That's an embedded component. You can decide who can edit that. People can add comments to report issues. # → In Mantissa, there is not a wiki. # Calendar # → In Phorge, if you need a reminder, for example "remember me in 4 days that I need to do that", you can just create a [[ https://we.phorge.it/calendar/ | Calendar ]] event and it automatically sends you an email when it's soon. Also, your Events are bulk-exportable to Google Calendar with a secret iCal URL that contains all the Events. Or you can import Events as well from an external iCal. # → In Mantissa, there is not a Calendar # Mockup # → In Phorge, designers can upload a Mockup like this: https://gitpull.it/M15 and do inline comments over an image # → In Mantissa, there is not such component # Answer by Email # → In Phorge, you can receive email notifications, and you can answer to them via email too. You comment is automatically published on the web interface. # → In Mantissa, answering by email is not probably possible # Automatic Rules # → In Phorge, administrators can set very powerful rules like "if something happens", "with these conditions", "do something" and it always surprising to see that it's very flexible. This is used from, automatic Tagging stuff from keywords, automatic Subscribe people if title contains something, automatic mark as Invalid if it contains weird stuff; but also: automatic do something if a commit was published. It is even able to block commits if they contain something, etc. This is something I think unique in Phorge. # → In Mantissa, probably this feature does not exist. # API # → In Phorge, you have self-documented APIs to export and import stuff: https://we.phorge.it/conduit/ . For example this creates a Task: https://we.phorge.it/conduit/method/maniphest.createtask/ . and this edit a Task: https://we.phorge.it/conduit/method/maniphest.edit/ and this search Tasks: https://we.phorge.it/conduit/method/maniphest.search/ # → Mantissa API? # avivey welcomed valerio.bozzolan in the community, listening to the following patches: # https://we.phorge.it/differential/query/GpyOvoQyv9Bv/#R # Some patches still deserves more eyes on it: # {D25099} # {D25097} # {D25080} # {D25079} ← the "Not Super Mario Coin" sound was not merged today # the changelog was updated [[ planning_meetings/2023-03-27/ ]] to mention the closed patches, that were: # {D25081} # {D25087} # {D25086} # {D25100} ----- ==Action items: None, really.

Event: {E19} Last meeting notes: (none? previously: [[/w/planning_meetings/2022-10-18/|2022-10-18]]) --- ==Attendees: In alphabetical order: - @avivey - aka "The Reviewer" - @ollehar - aka "The Mantissa master" - @valerio.bozzolan - aka "The micro Diff flooder" --- ==Agenda Items and Notes: # ReViEw SPrInT 🤩 - https://we.phorge.it/differential/ - {D25081} - author note: this is a edit in the documentation, let's check our personal installations as double-check - {D25087} - author note: this is an easy-peasy fix! - {D25099} - author note: this is simple to review together, with a beer nearby our laptop - {D25079} - author note: this is true magic - {D25078} - author note: while I was at it, we fixed the style - {D25086} + D25085 - author note: reeealy easy-peasy # Bonus points (if there is time) 🎁 - {D25066} + D25093 - author note: this is //not// super simple - but you will love it --- ==Action items:== Meeting Notes: # ollehar is evaluating a migration from Mantis to Phorge - invited by valerio.bozzolan shared 5 minutes of info about Mantis # valerio.bozzolan asked some questions about Mantis. It seems: # Task Dependencies: # → Phorge has a flexible Task dependency system → example: see this nice Task: https://we.phorge.it/T15187 # → after 15 years of use, today we discovered that also Mantis "somehow have" a parent/child field (wow!) but it does not render it visually, and it's just an extra field to a Task it seems # Visibility/Edit privileges: # → Phorge has a very flexible permission system. For each damn component you can have default permissions (example: visible to: public, editable by: all users), and then a per-object permission visibility (example: single Task visible to: Security Team). Note that, if something is not visible, it's also not editable. You can say: this Task is visible only to "Security Team", or only to "Legal Team" or "Visible Only to Me" or "Visible Only to Foo and Bar. # → Mantissa, it seems it has a "Private" flag. It limits the visibility to a single specific list of users. # Task collaboration workflows # → In Phorge (having said that comments can be edited only by yourself obviously), Task descriptions can be edited in a collaborative way. In this way, the community can discuss, and co-work to produce a clear Task description, to then present it to the maintainers. But, if you want, you can set custom Editable permissions (like: only Trusted Users, only during 09:00-18:00, only during fool moon, or whatever you want) # → In Mantissa, you cannot collaborate on the Task description. Only the administrator can. # Commit hooks # → In Phorge, if a commit message has a description like `Closes T123`, then, when it's published in the main branch, it automatically closes that Task; it connects to that Task, it is mentioned in that Task, and it auto-assign the commit user to that Task as closer user. This allows immediate response, and avoids to go back and search which Tasks need to be closed. Also, it simplify internal documentation, since it's really easy to see, for each Task, what was the related implementation. # Administration levels # → In Phorge, there is a component to make questions and answers, separated from the Task system but connected to it. So, "beginners" can ask Questions, and it's onboard, without the need of a forum. The system is a bit like StackOverflow: community is invited in adding Comments to the questions, Comments to the Answers, to collaborate on the Question itself and to the Answers, so, there are high quality questions and answers. # → Mantissa does not have a forum # Wiki # → In Phorge, if you need a space to quickly create a document, like "Instructions for the newcomers", you can quickly create a Wiki page. That's an embedded component. You can decide who can edit that. People can add comments to report issues. # → In Mantissa, there is not a wiki. # Calendar # → In Phorge, if you need a reminder, for example "remember me in 4 days that I need to do that", you can just create a [[ https://we.phorge.it/calendar/ | Calendar ]] event and it automatically sends you an email when it's soon. Also, your Events are bulk-exportable to Google Calendar with a secret iCal URL that contains all the Events. Or you can import Events as well from an external iCal. # → In Mantissa, there is not a Calendar # Mockup # → In Phorge, designers can upload a Mockup like this: https://gitpull.it/M15 and do inline comments over an image # → In Mantissa, there is not such component # Answer by Email # → In Phorge, you can receive email notifications, and you can answer to them via email too. You comment is automatically published on the web interface. # → In Mantissa, answering by email is not probably possible # Automatic Rules # → In Phorge, administrators can set very powerful rules like "if something happens", "with these conditions", "do something" and it always surprising to see that it's very flexible. This is used from, automatic Tagging stuff from keywords, automatic Subscribe people if title contains something, automatic mark as Invalid if it contains weird stuff; but also: automatic do something if a commit was published. It is even able to block commits if they contain something, etc. This is something I think unique in Phorge. # → In Mantissa, probably this feature does not exist. # API # → In Phorge, you have self-documented APIs to export and import stuff: https://we.phorge.it/conduit/ . For example this creates a Task: https://we.phorge.it/conduit/method/maniphest.createtask/ . and this edit a Task: https://we.phorge.it/conduit/method/maniphest.edit/ and this search Tasks: https://we.phorge.it/conduit/method/maniphest.search/ # → Mantissa API? # avivey welcomed valerio.bozzolan in the community, listening to the following patches: # https://we.phorge.it/differential/query/GpyOvoQyv9Bv/#R # Some patches still deserves more eyes on it: # {D25099} # {D25097} # {D25080} # {D25079} ← the "Not Super Mario Coin" sound was not merged today # the changelog was updated [[ planning_meetings/2023-03-27/ ]] to mention the closed patches, that were: # {D25081} # {D25087} # {D25086} # {D25100} ----- (This page used this [[/w/planning_meetings/template/|Template]])==Action items: None, really.