Let me answer here for the whole thread. There are lot of issues to cover, I think the github way would work here, so the project you've created for the purpose seems ok to me.
https://github.com/btrfs8-revamp I assume way more dicussions than actual patches and coding, the web platform offers commenting at the exact locations of files, issue tracking works better than over mail. Initially we'd cover all the stuff mentioned in this thread, naming, conventions etc. After we agree we can start changing code in btrfs-progs. We can ask for feedback wider audience in the mailinglist if needed, possibly with a draft that would be reviewed already. After we write comprehensive guidelines for the UI, we can add it to btrfs-progs, I really want to avoid high churn in that repository for things that are not related to code. For that the revamp repository is good, the only requirement is a github account. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
