Tony, I'm looking at creating a public repository to hold patches not yet in shape for inclusion in linux-omap (if not personally, then someone at TI that meets the below charter). I know there can be concern that this becomes a distraction if we start pulling in community patches. It seems it needs to be coupled with reworking systems for acceptance upstream, but we'd like for there to be something where community members can generate patches against while we are in the process of cleaning up the underlying platform bits. Do you have any recommendations or guidelines that should be followed regarding anything about such a public repository? Recommendations and guidelines can include, but not be limited to, where the repository should live, where patches and pull requests should be submitted, what types of patches should be accepted and what state they should be in, when should it be rebased, who is suitable to maintain this repository and what should be used for managing patch status (ie. patchwork and which patchwork). If this doesn't sound useful to you, then please feel free to shut me down on this. The goal is to help and it is understood that contributions to the infrastructure (dev tree, pwr mgmt, etc.) are required to be productive. Regards, Jason -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
