Open j-rivero opened 3 years ago
In light of the new Infrastructure program committee, I've been giving this issue (and related ones which are not explicitly logged) a fair bit of thought.
I think that the ros-buildfarm
component of the name for this repository can be assigned to its origin or provenance rather than its purpose, which like many tools in the ROS infrastructure ecosystem have expanded beyond ROS.
Does that make sense to you and is it satisfactory? I am happy to continue the conversation.
Expanding this out to the ros-infrastructure
organization. I've been wondering if the easiest thing to do wouldn't be to rename it osrf-infrastructure
now that things are organized under a unified project committee. Certainly consolidating GitHub organizations would make administration simpler, but it would also make splitting out access into smaller cells again in the future more difficult.
Since we are going to use the script for deployments in all our buildfarms we can consider to make the name/github-organization ROS agnostic. Not urgent.