+1

On Sat, 19 Jan, 2019, 8:44 PM James Dailey <[email protected] wrote:

> Hi Daniel -
>
> Thanks for sharing. It's a decent update to the logo in my view.
>
> I know that Myrle was at the last FOSDEM conference last year in
> Brussels.  I don't myself know if fineract will be represented. For the
> good of the list, https://fosdem.org/2019/ is an open source conference,
> volunteer run.  I hope we're going to be represented and am glad you have
> stickers!! ;)
>
> The current logo is visible http://fineract.apache.org/   (attached)
> and the proposed one is here  https://i.imgur.com/1w9X0Cb.png.   (66kb)
>
> Our process here is to have a member propose a change and, by
> lazy-consensus, if no one has a significant objection, we can adopt that
> change. A logo change is useful if it enhances our image in public forums
> (fora?) like FOSDEM. The downside is all of the existing materials we
> have... uhm... printed?...as far as I know that's not an issue.
>
> So, I propose fineract adopt the new logo.  If approved, I'll upload the
> changed logo to the git repos in the appropriate places.   +1 from me.
>
> Any objections, comment, additional backers?
>
> Thanks,
> @jdailey67
>
>
> [image: image.png]
>
>
>
>
> On Sat, Jan 19, 2019 at 1:05 AM Daniel Gruno <[email protected]> wrote:
>
>> Hi, awesome Fineract people.
>>
>> I was looking through the FOSDEM sticker orders, and thus the Fineract
>> logo, and I was wondering if you as a project were willing to get the
>> logo touched up a bit before then?
>>
>> My proposed touch-up can be found at https://i.imgur.com/1w9X0Cb.png,
>> and if you would like to use this, I can get the original SVG uploaded
>> to our central database and hopefully it will make it to FOSDEM in time
>> :). And if you prefer to stick with the original logo, that's also
>> totally cool - just throwing this to you in case.
>>
>> Whatever the outcome, if you could please let me and/or Sharan Foga
>> ([email protected]) know which one you prefer within a day or two, we
>> can get the stickers sorted.
>>
>> With regards,
>> Daniel.
>>
>

Reply via email to