Awesome, that's great news, Hendrik! Much appreciated!
2016-11-17 10:42 GMT+01:00 Hendrik Ebbers <hendrik.ebbers(a)me.com>:
Hi all,
I will get a first sketch of the duke logo first week of December.
Cheers,
Hendrik
Am 13.09.2016 um 12:55 schrieb Marco Molteni <moltenma(a)gmail.com>:
Thanks for the feedback Gunnar. The Duke it's fine for me too :)
Am 13.09.2016 11:21 schrieb "Gunnar Morling" <gunnar(a)hibernate.org>:
> Hi,
>
> > Curiosity, why a Duke that stamps bean?
>
> I think the idea is to symbolize the approval/validation of beans. I like
> the idea, it's kind of funny for "insiders", and those not getting it
still
> should find the Duke an attractive being ;)
>
> Personally I think it's fine if we - the EG and those discussing on this
> list - like and get behind one logo. Let's keep surveys and alike for stuff
> where we really need some input based on people's experiences with
> validation in practice.
>
> Hendrik, so if your friend could help out with this and create a logo for
> us, that'd be awesome. The only requirement really would be that it is
> provided with a suitable license, the 3-clause BSD license that the
> original is licensed under being the preferred option.
>
> Thanks a lot for driving this,
>
> --Gunnar
>
>
>
>
>
> 2016-09-09 11:40 GMT+02:00 Marco Molteni <moltenma(a)gmail.com>:
>
>> Hendrik, excellent idea the logo. Curiosity, why a Duke that stamps
>> bean? I think the concept to create the logo is another subject that
>> requires the community feedback (an original cool logo or a business /
>> technical concept around BV ?).
>>
>> On Fri, Sep 2, 2016 at 2:09 PM, Gunnar Morling <gunnar(a)hibernate.org>
>> wrote:
>>
>>> Please still use a fork and send pull requests from that.
>>>
>>> We usually don't have feature branches in the "blessed"
upstream repos,
>>> only if several people happen to work together on a single "thing"
for a
>>> longer period of time.
>>>
>>> 2016-09-02 13:57 GMT+02:00 Hendrik Ebbers <hendrik.ebbers(a)me.com>:
>>>
>>>> Cool!
>>>>
>>>> Question: Should we still use forks or can we work with features
>>>> branches directly in then bean validation repos?
>>>>
>>>> Hendrik
>>>>
>>>> Am 02.09.2016 um 09:27 schrieb Gunnar Morling
<gunnar(a)hibernate.org>:
>>>>
>>>> Hi Hendrik,
>>>>
>>>> Great ideas! Further details inline.
>>>>
>>>> 2016-09-01 16:30 GMT+02:00 Hendrik Ebbers <hendrik.ebbers(a)me.com>:
>>>>
>>>>> Hi all,
>>>>>
>>>>> currently all JBV repos are part of
https://github.com/beanvalidation
>>>>> which is really great. 3 people are part of this team at GitHub and
I
>>>>> asked myself if I can become member of the team, too.
>>>>>
>>>>
>>>> I've set up a new team "eg-members" under the Bean
Validation GitHub
>>>> organization and sent you an invite for it (other EG members give me
your
>>>> GitHub handle if you want to be in there, too). This will show you under
>>>> the list of org members and also allows to summon other experts's
input on
>>>> commits/PRs using the "@eg-members" alias.
>>>>
>>>> I've also granted write access to that team for the relevant repos.
>>>> But please *never* push your own commits, instead always go through pull
>>>> requests reviewed by other members. Collective code review is one of our
>>>> core principles really.
>>>>
>>>> In addition I think that we need a logo for the JSR :) We could use
>>>>> this at Github, Twitter &
beanvalidation.org. I know an
illustrator
>>>>> that did a lot of Java-related images for me. If you know the
JavaOne
>>>>> voting machines: He created all the duke animations (
>>>>>
http://www.guigarage.com/2016/01/the-javaone-voting-machine/). I
>>>>> would love to ask him for a logo for the JRS. Currently I’m thinking
about
>>>>> a Duke that stamps beans. What do you think?
>>>>>
>>>>
>>>> Yes, personally I'd love to have a log, the lack of one has been
>>>> bugging me for quite a while. I'll reply to you off-list to sort out
some
>>>> details.
>>>>
>>>> Cheers,
>>>>>
>>>>> Hendrik
>>>>>
>>>>
>>>> --Gunnar
>>>>
>>>>
>>>>>
>>>>> _______________________________________________
>>>>> beanvalidation-dev mailing list
>>>>> beanvalidation-dev(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> beanvalidation-dev mailing list
>>>> beanvalidation-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> beanvalidation-dev mailing list
>>>> beanvalidation-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> beanvalidation-dev mailing list
>>> beanvalidation-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>>
>>
>>
>> _______________________________________________
>> beanvalidation-dev mailing list
>> beanvalidation-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>>
>
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
_______________________________________________
beanvalidation-dev mailing list
beanvalidation-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/beanvalidation-dev