Hi, Right now we have no idea who the staffers are and how to track their activity. Is there a way to generate a list of them along with the herds/projects they are involved in (probably getting this info from LDAP or the herds.xml file) and send it to the retirement@ alias on a monthly basis like you do with the CVS activity emails?
One idea would be to add a staff.group in LDAP
afaik, right now, the only way to tell if one is staffer or not, is to see if he belongs to the cvs group on flycatcher.
The minimum we would need is a way to difference between people having commit rights or not, that could be done in a new field in the same mail we are currently getting... but I have no preference for either solution, having a way to distinguish between them is enough for me :)
Teo told me this is a WIP for the new identity GSOC project so hopefully we will have something at the end of this summer.
yes, and for the record I'm going to introduce staff.group (or staffer.group) as suggested already
As I said in https://bugs.gentoo.org/show_bug.cgi?id=373751#c3 we need retired.group or retired-dev.group (subset of user.group), which will replace gentooStatus
sorry ignore the previous comment, wrong bug :/
(In reply to Markos Chandras from comment #4) > Teo told me this is a WIP for the new identity GSOC project so hopefully we > will have something at the end of this summer. Now that GSOC is done, do we have an update on that?
(In reply to Markos Chandras from comment #8) > (In reply to Markos Chandras from comment #4) > > Teo told me this is a WIP for the new identity GSOC project so hopefully we > > will have something at the end of this summer. > > Now that GSOC is done, do we have an update on that? Identity is still under heavy development and it's not safe for production. Also, our development activity is idle these days. I have some plans to start working on the project again in the next few weeks.
regardless of the webapp, we could add the staffer.group in LDAP even now. Markos, do you (or retirement/recruiters team) have a list of current staffers so I can add it in their LDAP account?
(In reply to Theo Chatzimichos from comment #10) > regardless of the webapp, we could add the staffer.group in LDAP even now. > Markos, do you (or retirement/recruiters team) have a list of current > staffers so I can add it in their LDAP account? Unfortunately no, but it's easy to get one by looking on cvs.gentoo.org box and see which developers are not on the cvs group. It just needs a little bit of scripting. I will have a look.
Is this request still current?
Well, it's still a problem to differentiate staffers from "normal" developers. For now I have tweaked a bit the summaries of the affected people for remembering in future runs that they need to be handled differently when reviewing their activity... but it is more like a workaround (and prone to fail :/)
So, with any LDAP/IdM redesigns off the table, back to staff.group. robbat2?
We have not really decided on how to move forward and its 5 years later.
