You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we have two ways of tracking people in openedx-webhooks, with people.yaml and salesforce-export.csv . people.yaml is getting pretty out of date.
Figure out what peopl.yaml still being used for and get rid of it if possible.
If we're using it to see which contributors are CCs, we can instead look at what repos they have write permission to and what org they're from to determine that.
The text was updated successfully, but these errors were encountered:
It is also possible to have all the CC data in Salesforce and then add it to the salesforce export. It would just come out as a text field with a different delimiter if there are multiple values. Eg, a list of repos would come out as a string in the CSV that is semicolon delimited.
Given that we can track this data explicitly in salesforce and then just export it along with the other data, we should move in that direction. Once all the data is in salesforce we can update the openedx-webhooks code to pull the data from there and drop the yaml files all together.
We'll also want to update any relevant processes so that data in salesforce is kept up to date.
Right now we have two ways of tracking people in openedx-webhooks, with
people.yaml
andsalesforce-export.csv
.people.yaml
is getting pretty out of date.Figure out what peopl.yaml still being used for and get rid of it if possible.
If we're using it to see which contributors are CCs, we can instead look at what repos they have
write
permission to and what org they're from to determine that.The text was updated successfully, but these errors were encountered: