-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You could change "widget-based" to "reusable web component-based".
Marlon On 2/15/12 8:16 AM, Hadrian Zbarcea wrote: > +1. The charter needs to be simple and clear, but I wouldn't agonize over > precise semantics of all the words, so to me it's good enough the way it is. > FWIW, I personally like the -based there (referring to widgets in the general > sense), but I would remove the user experience part from the charter as a bit > too broad and not very informative, imho. > > "a widgets-based, web-and-social mashup platform" > > My $0.02, > Hadrian > > On 02/14/2012 09:11 PM, Franklin, Matthew B. wrote: >> >> >> On 2/14/12 7:21 PM, "Bill Donaldson"<[email protected]> wrote: >> >>> On Tue, Feb 14, 2012 at 5:47 PM, Ate Douma<[email protected]> wrote: >>>> On 02/14/2012 03:31 PM, Franklin, Matthew B. wrote: >>>>> >>>>> I have created a draft of the graduation board resolution [1] and would >>>>> like to get feedback from the community regarding the proposal; >>>>> specifically, the wording of the description& scope. Ate made a great >>>>> point that we need to ensure it is narrow enough that we can execute >>>>> against >>>>> it, but broad enough to include future use cases. The rest of the >>>>> template >>>>> was filled out with the result of PPMC discussions held on >>>>> rave-private@ >>>>> >>>> Thanks for drafting up the charter Matt. >>>> >>>> The crucial part of the charter we should agree upon is indeed the >>>> description of the *scope* of the project. >>>> >>>> The proposed text currently is: >>>> >>>> [..] "a widget-based, web-and-social mashup and user experience >>>> platform" >>>> [..] >>>> >>>> While definitely a good description for the scope, I would still like to >>>> propose a very minor but possible important change, like this: >>>> >>>> "a widgets, web-and-social mashup and user experience platform" >>> >>> I believe widget-based would be more inclusive than 'widget' Widget >>> *might* imply W3C widget. >>> >>>> >>>> The reason for this slight change is that saying "a widget-based, [...]" >>>> might be interpreted as if Rave at least assumes/requires widgets to be >>>> used. >>>> >>> As a heavy user of Rave, we count on it supporting Widgets. Removing >>> Widget from the scope would narrow the scope of the project and be a >>> limiter of our future use of the platform. >>> >>> It might be better to be more specific that on the intent of widgets >>> are optional. Sorry I don't have better wording...it is a suggestion >>> if someone was so inclined. >>> >>>> I *think* (but this really is about semantics and grammar, in a >>>> non-native >>>> language for me), my proposed change makes it more optional to use >>>> widgets, >>>> as just one possible feature of the platform. >>>> >>>> IMO 'a web-and-social mashup and user experience platform' (thus without >>>> using/requiring widgets) also very much fits the bill for Rave. >>>> >>> >>> perhaps a change of the clause 'web-and-social mashup and user >>> experience platform' >>> >>> to 'web-and-social mashup user experience platform' The 'and' never >>> did much for me but I'm an engineer not an English major >> >> I like some form of what you are suggesting. I was searching for a way to >> fit all of those words in the same description and slipped the and in >> there. >> >>> >>>> WDYT? >>>> >>>> Regards, Ate >>>> >>>>> Once we have an agreed upon resolution, we can call a community VOTE >>>>> for >>>>> Graduation and proceed with the process. >>>>> >>>>> Let's get ready to graduate! >>>>> >>>>> -Matt >>>>> >>>>> [1] : >>>>> >>>>> https://issues.apache.org/jira/secure/attachment/12514364/graduation_res >>>>> olution.txt >>>>> >>>>> >>>> >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPO7RgAAoJEEfVXEODPFID7N0IAIVGCUPpI6/8oURaMsFHxHF5 wcMmB0UlHK5tHJ8zHpJUdRUSVL/Rcqq9XbD3fF3DKrKHNVCqRUAvGZKHiAFSS+/p IbQi52PhTt0oD0CmOS7u+DgtFsyFoxnyI5H9wXjBSgxC5X99Ae8+qMsKtp3EWMEg 3VLA/O47NVmKadGYRg+5GDb8x9Wyl6vxL+myovl/eiknevaxm3wrp1r2Mov9I7bq nXlG1iBlofayXhajgXjxW3/c6m8XAhmkHn3ImP6nMEY+MlswH8DhAyahkLSvT44l wk8i3wvH6f0kwjRPy9bKjKYgcUaodSeJEWswGNBnilRVTwJG+XhAd6grqx82GdU= =fyU5 -----END PGP SIGNATURE-----
