While Frictionless CI makes more sense to a developer than the old name ("Repository"), I would suggest renaming it Frictionless Workflow. Or creating something of an umbrella project which incorporates the techniques in this one.
Rationale: this project could also be very useful to people creating data pipelines, in some cases linked to ETL components, while others would be more interested in streaming data sources or other advanced scenarios. Continuous Integration is just a mechanism, mostly known as a term in software engineering, while Continuous Aggregation or Continuous Validation might be more appropriate when dealing with datasets.
Furthermore, the development of user-friendly tools related to the management of workflows using Frictionless Data standards could be well communicated and promoted through an easily recognizable term. One that is, nota bene, currently promoted by GitHub itself.
While Frictionless CI makes more sense to a developer than the old name ("Repository"), I would suggest renaming it Frictionless Workflow. Or creating something of an umbrella project which incorporates the techniques in this one.
Rationale: this project could also be very useful to people creating data pipelines, in some cases linked to ETL components, while others would be more interested in streaming data sources or other advanced scenarios. Continuous Integration is just a mechanism, mostly known as a term in software engineering, while Continuous Aggregation or Continuous Validation might be more appropriate when dealing with datasets.
Furthermore, the development of user-friendly tools related to the management of workflows using Frictionless Data standards could be well communicated and promoted through an easily recognizable term. One that is, nota bene, currently promoted by GitHub itself.
I've created a
#workflowschannel to discuss this idea, and added some thoughts in the CKAN camp at https://github.com/ckan/ideas/issues/211