On 11/10/14, 10:03 PM, "Justin Mclean" <jus...@classsoftware.com> wrote:
>Hi, > >> The loaded app appears to be somewhat resizable. If you load the SWF >> directly [3] without wrapper you can resize it and the text retains its >> font size. Try resizing the TDF window. For me, the text in the >> Flexicious app scales, indicating that it is loaded into a sandbox and >> therefore not being communicated with like the other local example apps. > >Which is what we want as it is the most secure. Sorry not sure exactly >what you are objecting to here. Would be better if fit 100% of the >available height and width, but I certainly don't see that as a blocker. It is moot as we’ve switched strategies, but we could have decided to use Marshall Plan to have the 3rd party content display just like any other local example app. Depending on the size of your browser window, in the original strategy, the 3rd party app could come up scaled such that the text was almost unreadable. IMO, that wasn’t a good enough first impression for our third parties, and thus, at least Ardisia requested a preference for the new strategy of just linking to 3rd party sites. > >> I’m not sure what your point is. > >Which is I still don't know how you (or other PMC members) would vote if >I made a RC. It is still not clear that if I made a release and called a >vote that it would get 3 +1's or not and in this new no RC process I >gather you can't make a RC or vote until that is reasonable clear. >Correct? I would prefer that we remove Flexicious from 3rdparty.xml before cutting a release, but otherwise, if you make an RC off the head of the release branch, I expect to vote +1 unless someone shows up with a huge critical problem we don’t currently know about (or the signature is bad or some other data corruption). The notice files look fine, the build script works, the few examples I poked at worked. Before you go do all that work, we should try to get agreement from others on whether to temporarily take Flexicious out of the xml file, and get at least one other PMC member to examine the source package on the CI server. If you’ve looked it over, and I’ve looked it over, and one other PMC member has as well, that should be your 3 +1 votes. So, fellow PMC members, can we: 1) get your thoughts on taking Flexicious out of 3rdparty.xml so that their app doesn’t show up scaled? When they reply with a bitmap to use like Ardisia did, then we’ll add it to the flex.a.o version which is what most folks use anyway. 2) get at least one of you to check out the source package on the CI server? If you want you can use the approval script by getting the ApproveTDF.xml in the develop branch, copying it to an empty folder and then running: ant -e -f ApproveTDF.xml -Drelease.version=1.2 -Dno.asc Please make sure to review the README/RELEASE_NOTES/LICENSE/NOTICE files. For me the build takes 30 to 40 minutes so plan accordingly. Thanks, -Alex
