Cool thanks. I included the changes discussed with Nick and added it to Jira: https://issues.apache.org/jira/browse/LOG4J2-316
If you can't edit it (you should) let me know Cheers On Fri, Jul 19, 2013 at 3:18 PM, Gary Gregory <[email protected]> wrote: > If you write up the text with the changes discussed, I'll proof read the > whole thing. It seems we need the text in the JIRA first. > > Gary > > > On Fri, Jul 19, 2013 at 9:08 AM, Nick Williams > <[email protected]> wrote: >> >> That's much better, as in being clear. As for whether we should allow >> community votes, I have mixed feelings, so I'm going to abstain from >> commenting. >> >> Nick >> >> On Jul 19, 2013, at 8:04 AM, Christian Grobmeier wrote: >> >> > Nick thanks for the mispelling corrections. >> > >> > Date: ups you are right. I was living in June. Lets extend it further >> > 1 month from the date we agreed to this >> > >> > What about this: >> > >> >> HOW THE LOGO IS CHOSEN >> >> >> >> Everybody is invited to vote. The votes of Apache Logging Committers >> >> are binding. >> >> >> >> If there are more than 10 Logos submitted there will be two rounds. >> >> In the first round the 10 logos with the most +1 are entering round >> >> two. >> >> In the second round the logo with the most +1 will win the contest. >> > >> > Is that better? >> > >> > Not sure if we should allow community votes in this case or not. >> > >> > Cheers >> > Christian >> > >> > >> > >> > On Fri, Jul 19, 2013 at 2:53 PM, Nick Williams >> > <[email protected]> wrote: >> >> A few corrections/suggestions inline. >> >> >> >> On Jul 19, 2013, at 7:42 AM, Christian Grobmeier wrote: >> >> >> >>> Hello, >> >>> >> >>> here is a draft based on my ideas and based on the feedback i read >> >>> from Gary and others. >> >>> Please feel free to correct / modify / discuss it. >> >>> >> >>> I already created an Jira issue, because i think we all agreed to take >> >>> Jira for submissions. The plan is to use the text on the website, blog >> >>> and jira issue. We also might be able to get some help from Sally >> >>> >> >>> Please note, I changed the final date to 01.08. becuase the previous >> >>> date is already history :-| >> >>> >> >>> Cheers >> >>> Christian >> >>> >> >>> >> >>> >> >>> Log4j 2.0 is looking for a new logo >> >>> >> >>> Log4j 2 is very different to Log4j 1. Log4j 2 is more reliable >> >>> and fast then its predecessor and even comparable frameworks. >> >>> The team has grown after years of stagnation and there is >> >>> a lot of activity on our lists. We are already seeing the >> >>> first signs for a stable release on the horizon. >> >>> >> >>> After 12 years it is not only time to change the version >> >>> number but also time to refresh the Log4j logo. >> >>> >> >>> With our new logo we want to show the java community >> >> >> >> "Java," not "java." >> >> >> >>> that Log4j is back. >> >>> >> >>> We would like to open participation to the community >> >>> to create this new logo. >> >>> >> >>> HOW TO PARTICIPATE >> >>> >> >>> Attach your entries to the Jira: >> >>> >> >>> * https://issues.apache.org/jira/browse/LOG4J2-316 >> >>> >> >>> Each person can submit more than one logo. >> >>> Submissions will be accepted until August 01, 2013. >> >> >> >> Originally we gave them 6 weeks, now we're giving them less than two? >> >> 12 days is how many days to August 1. Doesn't seem like nearly enough time >> >> to me. I'd say August 19 (one month from today, and a Monday so they have >> >> the weekend before to finish it). >> >> >> >>> >> >>> The Logo must be licensed to >> >> >> >> "under" instead of "to?" >> >> >> >>> Apache License 2.0. >> >>> If your Logo is accepted, the creator must sign an ICLA: >> >>> http://www.apache.org/licenses/icla.txt >> >>> >> >>> While we will accept PNG image formats for the contest, >> >>> we prefer vector based formats (SVG). >> >>> >> >>> Pixelbased formats produced with Gimp or Photoshop >> >>> might be vectorized with free tools like Inkscape. >> >>> >> >>> * http://inkscape.org >> >>> >> >>> Please note that a logo should not contain too much >> >> >> >> many >> >> >> >>> details. >> >>> >> >>> HOW THE LOGO IS CHOSEN >> >>> >> >>> If more than 10 Logos are submitted, the Apache Logging committers >> >>> will reduce the numbers to 10 nominees in a public vote. >> >>> >> >>> When 10 Logos are left, the Apache Logging committers will >> >>> select the final concept. >> >> >> >> This is a little confusing. Even I'm not sure here whether this means >> >> only the committers will pick the top 10 / the winner or if there will be >> >> a >> >> vote that everyone can participate in at some point. >> >> >> >>> >> >>> The majority fo the Apache Logging PMC can veto a logo. >> >>> >> >>> The logo is finally accepted, when all votes are successful >> >>> AND the ICLA of the logo contributor is on file. >> >>> >> >>> The Log4j team >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: [email protected] >> >>> For additional commands, e-mail: [email protected] >> >>> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> > >> > >> > >> > -- >> > http://www.grobmeier.de >> > https://www.timeandbill.de >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory -- http://www.grobmeier.de https://www.timeandbill.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
