As one of the NetBeans Day UK organisers, I like Geertjan’s definition but think 2 clarifications would help.
1. Does ALL the content have to be NetBeans or the vast majority? In the past we have had a very small minority of talks at NetBeans day which have of a more general nature but fit in well with the general theme (ie design patterns in Java). Personally just feel we need to be clear if event is totally exclusive or not to provide a clear guide. 2. I think we should also clarify if we are allowed to charge or have sponsorship for the events. At UK, we have had sponsors so we can run a free event with food. Kind Regards, MArk > On 8 Mar 2018, at 12:26, Geertjan Wielenga <[email protected]> > wrote: > > Hi all, > > Following the mentor advice below, we need documented consensus on what > defines an 'Apache NetBeans Day', i.e., the requirements for an event to be > able to be named 'Apache NetBeans Day'. > > https://lists.apache.org/thread.html/afc1177e52a4436b99a40b73128c02de7a33af580b5aca444adc074d@%3Cdev.netbeans.apache.org%3E > > I propose that Apache NetBeans Days are defined as a class of events which > happen regularly, with a clear definition of what makes an event be part of > that class: > 1. Have its opening keynote focus on the current state and roadmap of > NetBeans. > 2. Have all demos done throughout the event in NetBeans. > 3. Must be discussed/notified via the Apache NetBeans dev mailing list. > > Here's the central location where Apache NetBeans Events are defined: > > https://netbeans.apache.org/community/events.html > > Following Apache lazy consensus (https://www.apache.org/ > foundation/voting.html#LazyConsensus), i.e., no voting or responses of any > kind are needed, except if you object. If no one objects within 24 hours, > we'll assume lazy consensus and implement the above proposal. > > Thanks, > > Gj
