Re: Policy for adding org logos in github project

23 views
Skip to first unread message

Christophe Vandeplas

unread,
Jun 9, 2015, 3:34:28 AM6/9/15
to Andras Iklody, MISP developers, AD, Alexandre Dulaunoy
On 9 June 2015 at 09:28, Andras Iklody <andras...@gmail.com> wrote:
> On Tue, Jun 9, 2015 at 9:12 AM, AD <elh...@gmail.com> wrote:
>>
>> Do we set any policy for adding org icons in the github project?
>>
>> For example, icebrg (http://icebrg.io) is contributing data to Crimeware's
>> MISP and would like to have their logo included.
>>
>> For rackspace, we need to check with the guy first if he does not mind
>> that rackspace is referenced as using MISP (implied by the addition of the
>> logo to the MISP repo).
>
> This is a good question. The only issue I can see if that we might end up
> flooding the file management screen of admins by shipping too many logos, so
> I think it's best to think of an alternate location for logos that we
> include in the repository.
>
> But it's a great way for organisations to show that they do indeed use MISP
> and for us to be able to show a list of organsiations that openly use it.
>
> So if you guys want I can add their logo for now and we'll think of a better
> system in the meanwhile for the future :)

Perhaps an alternative is to switch to either something comparable to
gravatar. However matching orgnames to gravatar emails is probably not
the easiest.

Another option is to host ourselves a similar service:
- Orgs can register their orgname and logo using our website.
- MISP will show the local logo, and if not available, will download
it from our repository and store a copy locally. So the first time the
orgname is seen it will be downloaded from our repository/website.

That would give the benefit of centralised logo's, and also without
cluttering the admin interfaces.

Andras Iklody

unread,
Jun 9, 2015, 3:44:32 AM6/9/15
to Christophe Vandeplas, MISP developers, AD, Alexandre Dulaunoy
Indeed, the only issue is that MISP would constantly try to connect out to our server - which might look a bit bad...

AD

unread,
Jun 9, 2015, 3:59:43 AM6/9/15
to Christophe Vandeplas, Andras Iklody, MISP developers, Alexandre Dulaunoy
I like the idea of auto-fetching, i would just make it optional and instead of our own server, why not a github repo under the MISP account?

On Tue, Jun 9, 2015 at 9:34 AM, Christophe Vandeplas <chris...@vandeplas.com> wrote:

Christophe Vandeplas

unread,
Jun 9, 2015, 4:02:12 AM6/9/15
to AD, Andras Iklody, MISP developers, Alexandre Dulaunoy
On 9 June 2015 at 09:59, AD <elh...@gmail.com> wrote:
> I like the idea of auto-fetching, i would just make it optional and instead
> of our own server, why not a github repo under the MISP account?

A script on our website to allow the upload of the logos, and if
necessary that's synec to something else (github) to take away the
load when being fetched.

As images would be cached locally, load shouldn't really be a problem.

AD

unread,
Jun 9, 2015, 4:31:27 AM6/9/15
to Christophe Vandeplas, Andras Iklody, MISP developers, Alexandre Dulaunoy
What would the benefits be of having an upload script on our site vs. using git pull requests on the github repo?

Christophe Vandeplas

unread,
Jun 9, 2015, 4:34:47 AM6/9/15
to AD, Andras Iklody, MISP developers, Alexandre Dulaunoy
On 9 June 2015 at 10:31, AD <elh...@gmail.com> wrote:
> What would the benefits be of having an upload script on our site vs. using
> git pull requests on the github repo?

To discuss, but my feeling is technical complexity. People adding
organisation logo's are not necessarily technical.
Reply all
Reply to author
Forward
0 new messages