Understood, but PPMC members won't be watching the github instance -- we will only be watching the official Apache resources such as the GIT / SVN / Jira, so there is pretty much no chance of anything coming back. Discussion and code that happen outside Apache "don't happen" (that is how all apache projects work). I don't see any PPMC blindly accepting changes that happen from outside into the official code base -- as that opens up another legal surface that could hurt the project (and I certify that you didn't take that change from a copyrighted project? Not to say that would be the case, but that is a real legal threat we have to deal with these days)
-Nick On Mon, Feb 13, 2012 at 11:02 AM, Martin Heidegger <m...@leichtgewicht.at>wrote: > On 14/02/2012 00:57, Nicholas Kwiatkowski wrote: > >> I know people have talked about making a mirror of the SVN (and soon, Git) >> repos on GitHub, but any changes committed to those mirrors will be >> orphaned. >> > > Any branch ever made in any system is by itself orphaned without constant > merging. > To get it back to the trunk the merge has to be done somehow. Currently > the process > involves Jira for all non-commiters. Github would make a discussion and > collaboration > possible before bringing a certain idea to Apache Flex. > > yours > Martin. >
