If we choose to proceed in this direction, we'll need a community-accessible site that hosts a public Google calendar. Does this already exist, or do we need to create one?
On Tue, Jan 26, 2016 at 10:28 PM, William Markito <[email protected]> wrote: > The javascript integration you did looks really good to me... Although the > Brazilian calendar might be too much given the number of holidays... :P > > A separate website would be a bit confusing since it would not be handled > or managed within the project or by committers of the project, which might > be a similar problem for a google calendar but might more doable... > > About your second question the calendar widget would take of it once the > events pass. For now, I'm not sure we need to be much concerned since it's > also good for people to see events that already happened so they can find > content... > > Just my 2 cents. > > On Tue, Jan 26, 2016 at 5:13 PM Dave Barnes <[email protected]> wrote: > > > This was a proof-of-concept, but the redesign needs more thought. I > think a > > separate site will allow more flexibility in presentation and design. > > > > I'm not sure how much information most publicly-visible Google calendars > > provide, but this example's pretty slim. Doesn't begin to rival the > > appearance or level of detail of the existing implementation. > > > > Those of us who care need to come up with a design. My first question has > > to do with existing resources: > > Is there a website already in existence that could serve as a host for > > calendar postings from the community? > > > > Second question: In the meantime, how shall we handle updates to the > > existing site? The Jan 31 event will go 'stale' in less than a week. > > > > On Tue, Jan 26, 2016 at 4:47 PM, Dan Smith <[email protected]> wrote: > > > > > +1 Good idea! > > > > > > -Dan > > > > > > On Tue, Jan 26, 2016 at 3:44 PM, Greg Chase <[email protected]> > wrote: > > > > > > > +1 for supporting Brazilian Holidays > > > > > > > > +1 for a calendar service that makes it easier for the community to > > > > contribute events. > > > > > > > > On Tue, Jan 26, 2016 at 3:26 PM, Dave Barnes <[email protected]> > > wrote: > > > > > > > > > First pass, using the calendar of Brazilian Holidays - look just > > below > > > > the > > > > > Pivotal events: > > > > > > > > > > > http://ec2-52-33-216-127.us-west-2.compute.amazonaws.com/community/ > > > > > > > > > > On Tue, Jan 26, 2016 at 7:43 AM, Nitin Lamba <[email protected]> > > wrote: > > > > > > > > > > > +1 for data-driven event calendar! William's suggested solution > is > > > > > > available as a jQuery plugin [1]. > > > > > > > > > > > > Nitin > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > > http://www.jqueryscript.net/social-media/jQuery-Plugin-To-Display-Google-Calendar-Feeds-On-Your-Website.html > > > > > > > > > > > > ________________________________________ > > > > > > From: William Markito <[email protected]> > > > > > > Sent: Tuesday, January 26, 2016 12:00 AM > > > > > > To: [email protected] > > > > > > Subject: Re: Proposal: Move Events to a non-Repo website > > > > > > > > > > > > Hi Dave, I think it's a great idea! In fact, I'd rather have it > > > some > > > > > how > > > > > > (javascript ?) pull that data from a Google Calendar feed or > > > something > > > > > like > > > > > > that to automate the updates. > > > > > > > > > > > > +1 > > > > > > > > > > > > On Mon, Jan 25, 2016 at 4:34 PM Dave Barnes <[email protected]> > > > > wrote: > > > > > > > > > > > > > RFF (Request for Feedback) > > > > > > > > > > > > > > Apache Geode website design suggestion: Replace the volatile > > Events > > > > > > section > > > > > > > of the Geode website with a link to a community events site > > that's > > > > not > > > > > > part > > > > > > > of the Apache Geode source code repo. That way, the events can > be > > > > > updated > > > > > > > quickly by community members without the delay, overhead, and > > > > potential > > > > > > > code corruption resulting from updating calendar items in the > > code > > > > > repo. > > > > > > > > > > > > > > > > > > > > > > > > > > > >
