EandrewJones commented on issue #266:
URL: 
https://github.com/apache/incubator-flagon-useralejs/issues/266#issuecomment-1192120929

   I could certainly fork and push to a draft PR.
   
   My opinion is that it would be best to see all three implementations, hear
   more about all three use cases, and then try to come up with a generic and
   elegant solution that covers all three.
   
   Best
   
   Evan Jones
   郑恩尉
   
   Website: www.ea-jones.com
   
   
   On Thu, Jul 21, 2022 at 10:31 PM brucearctor ***@***.***>
   wrote:
   
   > I have to imagine that any written code would be best viewable and open
   > for discussion. Ex: on a fork or branch, potentially as draft PR, etc.
   >
   > 3 different groups each with custom solutions: Are 'custom' solutions OK
   > to merge/contribute, and potentially clean up and combine later, or are
   > hoping to use what has been learned from each to develop a more generic
   > solution [ no judgement on either at this time, looking to
   > understand/establish community conventions ].
   >
   > —
   > Reply to this email directly, view it on GitHub
   > 
<https://github.com/apache/incubator-flagon-useralejs/issues/266#issuecomment-1192116413>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/AJ2T6AKX3JSAPT6ETLH4JVLVVIBZPANCNFSM52PYSGMQ>
   > .
   > You are receiving this because you were mentioned.Message ID:
   > ***@***.***>
   >
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@flagon.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to