On Apr 13, 2013 11:44 PM, "Alex Harui" <aha...@adobe.com> wrote: > > Is the Git whiteboard read-write? Are there any issues with opening it if > we do end up going to Github? If not, can you request that it be opened? > I'm not sure how you were going about that for the other repos. > > Thanks, > -Alex
Mark, maybe you can create a public GitHub project for now to share your code? Then you will have to manually check it into wherever we decide to host the whiteboard. Logistically speaking that would be least cumbersome process. Thanks, Om > > > On 4/13/13 11:37 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote: > > > On Apr 13, 2013 11:13 PM, "Alex Harui" <aha...@adobe.com> wrote: > >> > >> Reviving: > >> > >> Mark Kessler has some stuff that should be on a whiteboard. Can we make > > the > >> git whiteboard read-write while a couple of you experiment with Github? > >> > >> -Alex > >> > > > > I have been experimenting with GitHub for the past couple of days. Close > > to something viable. > > > > I also tried to get in touch with GitHub support, still waiting for a > > response from them. > > > > Feel free to do what needs to be done in the meantime. > > > > Thanks, > > Om > > > >> > >> On 4/9/13 12:58 AM, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote: > >> > >>> On Tue, Apr 9, 2013 at 8:23 AM, Dave Fisher <dave2w...@comcast.net> > > wrote: > >>>> ...The gist is that this PMC is responsible for keeping the IP in > > shape and > >>>> doing the work in the open.... > >>> > >>> I'd also add that whoever commits (or pushes, in the Git model) to the > >>> Apache repository (where all releases must be cut from) takes > >>> responsibility for what they commit, under the iCLA that they signed. > >>> > >>> So it's ultimately up to that committer to make sure they have the > >>> right to commit what they're committing, and that the provenance of > >>> every line of code can be clearly established. > >>> > >>> Backing a contribution with an https://issues.apache.org issue where > >>> the contributor clearly expresses their intention to donate the code > >>> to Apache Flex is helpful, and having an iCLA for that contributor > >>> helps put the burden on them for checking that it's their own code > >>> that they are contributing. > >>> > >>> -Bertrand > >> > >> -- > >> Alex Harui > >> Flex SDK Team > >> Adobe Systems, Inc. > >> http://blogs.adobe.com/aharui > >> > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui >
