Opened 3 years ago

Closed 3 years ago

#20227 closed enhancement (fixed)

Remove .csv file with statistics about agreement or disagreement among the directory authorities

Reported by: karsten Owned by:
Priority: Medium Milestone:
Component: Metrics/Website Version:
Severity: Normal Keywords:
Cc: iwakeh Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Six months ago, we added a data-processing module that produces a .csv file with statistics about agreement or disagreement among the directory authorities. This data file was specifically crafted for a visualization that a volunteer was working on. But that volunteer let me know that they cannot complete the visualization anymore, and I'm not keen on finishing that code nor on maintaining it. I suggest removing the data-processing module. If we ever find that we need it back, Git history will have it for us. Thoughts?

Child Tickets

Change History (3)

comment:1 Changed 3 years ago by iwakeh

Status: newneeds_information

That's what version control is for. Only that one hardly looks back into that history.
Where to keep a reference and is there information that would be helpful taking the task up again in future?
Would completing it be a possible task to add to our volunteering page?

comment:2 Changed 3 years ago by karsten

As briefly discussed on IRC today, the main idea behind this visualization was to try out a new graphing engine. I don't think that we'd assign this task to a new volunteer. So it's probably okay to just take it out and make a local note or something. Will do.

However, I just realized that we should maybe take it out in two steps: first, stop updating the .csv file which includes taking out all code that produces it, and second, removing the .csv file. That's how we replaced connbidirect.csv with connbidirect2.csv in January 2016, and now that I look at that, I'd say it's time to take out the data page. Will do.

comment:3 Changed 3 years ago by karsten

Resolution: fixed
Status: needs_informationclosed

All done. Closing.

Note: See TracTickets for help on using tickets.