Having an Examples blog is a great thing. I saw the calendar invite. I couldn't see the calendar I think because default to logging in under a different email and don't really want this stuff mixed into to my default calendar.
My only concern is the scheduling. IMO, scheduling is difficult with volunteers. Folks get busy with their $dayjob and may run out of time. We should accept entries from anyone, even non-committers, at any time. So what if we get a burst here and it goes quiet for a while? Carlos, if you want to volunteer to keep track of the last post date, then if a week goes by without a new post you could ask on the mailing list for a volunteer to write the next post. And anyone reading this email is welcome to write a post or suggest a topic. That will likely be the biggest question for me: what should I write about? Anyway, thanks for getting this started. My 2 cents, -Alex On 2/13/18, 3:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" <carlos.rov...@gmail.com on behalf of carlosrov...@apache.org> wrote: >Hi Olaf > >2018-02-13 11:31 GMT+01:00 Olaf Krueger <m...@olafkrueger.net>: > >> >I'd like to read thoughts from others in the team. >> >> This is a really good idea, Carlos! >> If I understand you right you'd like to say that we want to publish a >>post >> every two weeks and because we're about 10 to 15 people who will >>contribute >> this means that anybody of us has to write an article approx every 6 >> months?! >> And you want us to manage the scheduling of the blog posts by using the >> google calendar? >> > >That's right! I think if we all participate will 10-11, and about 6 months >between repeat author. >Maybe, as examples are very easy to do we can talk more later if we do >this >each week...we'll see as we develop it right? > > >> >> >Below the source code, we should have the result displayed in an >>iframe. >> +1 >> >> Another suggestion: >> Peter de Haan posts always contain some simple explanations. >> Regarding the "Hello world" post, I think it would be interesting for >> people >> to learn something about the code, e.g. for what is >> "js:SimpleCSSValuesImpl", "js:initialView" and "js:View" needed. >> Maybe it makes sense to link something to the docs or to add some simple >> explanation? >> > >That's a very good idea. I'll try to update the hello world with this >suggestions :) > > >> >> I'll check out the google calendar... >> >> Thanks, >> Olaf >> >> >> >> >> >> >> >> >> >> -- >> Sent from: >>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-ro >>yale-development.20373.n8.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com >>%7Cd2453e80427a4a2db4a708d572d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C >>0%7C0%7C636541170132357067&sdata=IW1I%2BZebS7gSyrBako0WCHBAG8eo1b3NPVnfC% >>2BvUyTA%3D&reserved=0 >> > > > >-- >Carlos Rovira >https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2 >Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cd2453e80427a4a2db4a708d5 >72d259e3%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636541170132357067&s >data=YBsn0zhxZd98toKr%2BrZP1GwprmRzcmM5NesejiabbJo%3D&reserved=0