[petsc-dev] Gitlab notifications and labels

[Smith, Barry F.]

  Scott,

    Thanks for researching this and send it out. 

    Yes, I think all MR on DMPLEX should use a label DMPLEX;  I don't think having an additional DM label is worth the effort since all the meat at the moment is DMPLEX. 

     We should probably also have a TS label. Maybe others will come up over time. 

   Barry


> On Nov 14, 2019, at 6:03 PM, Scott Kruger via petsc-dev <petsc-dev at mcs.anl.gov> wrote:
> 
> 
> 
> In a conversation with Barry, he mentioned that we hadn't
> really discussed label subscription on this mailing list,
> despite the fact that this is perhaps the more useful control
> of notifications than what is in given in Settings.
> 
> Following up on this discussion, if folks go here:
>  https://gitlab.com/petsc/petsc/-/labels
> you can then subscribe to the labels that you want
> notifications for.  This is potentially the best method
> for subscribing to PETSc development notifications, and
> better than just *Participate* level which I had advocated
> for earlier.  I'll now advocate for *Participate* globally,
> and label subscription locally.
> 
> Of course, this requires all folks who start an MR/Issue
> to appropriately use labels.  But if you want a response,
> you should expect to need this to get the response you want.
> 
> And of course, this requires accurate labels.  For example,
> I notice that there is no label for folks developing
> DM, even though that is, perhaps, the most active area of
> development.  Do you require a new label?  (asks the
> not-a-dm-dev).
> 
> Scott
> 
> P.S.  This means that I will stop using @person for GPU
> discussions and just use the GPU label. Subscribe now GPU devs!
> 
> 
> 
> -- 
> Tech-X Corporation               kruger at txcorp.com
> 5621 Arapahoe Ave, Suite A       Phone: (720) 974-1841
> Boulder, CO 80303                Fax:   (303) 448-7756