On a bagger page, after clicking on the 'inviter' button, the appointement form opens.
On this form, the send button seems to no working.
Nothing is happening on a click although it is active.

Bonjour
J'ai une barre rouge after clic demande

As announced at https://www.malt.fr/about/hopwork-becomes-malt we should rename this in the README, the data and the website.

I've just added myself to the baggers file (I was sure I've done that YEARS ago, but anyways).
Editing that large JS/Json file is not the best experience.

Here is my idea :

• Move from 1 file for all speakers, to 1 file per speaker, maybe as a YAML file
• Having some build that will get all these YAML files and compile them to 1 JavaScript file
• Future : check that the YAML file is well formatted, check that the city is in the cities list (and fail the build if no)
• Future future : Having a build that ping speakers if they have "stale" listing asking them to update it.

I'm understanding that you need to publish in gh-pages something that can be served as a static content over data.brownbaglunch.fr, and I'm pretty sure we can figure it out :).

Would you be something useful? If so, I can dedicate some time to work on it :)

When loading baggers.html, we got some 404 errors we need to fix:

• https://fbcdn-profile-a.akamaihd.net/hprofile-ak-xfa1/v/t1.0-1/c0.0.320.320…d42dfa9348&oe=54E99E54&__gda__=1425364962_ff9796691bbf73f194716cf5924b2d57 Failed to load resource: the server responded with a status of 403 (Forbidden)
• https://pbs.twimg.com/profile_images/3538863249/7c6adb61a6b0554c019b2a26711c7afd_400x400.jpeg Failed to load resource: the server responded with a status of 404 (Not Found)
• https://pbs.twimg.com/profile_images/2284064030/r1fue8rqkl904pvija46.jpeg Failed to load resource: the server responded with a status of 404 (Not Found)
• https://pbs.twimg.com/profile_images/1749868293/id-1_small.png Failed to load resource: the server responded with a status of 404 (Not Found)
• https://pbs.twimg.com/profile_images/378800000207562580/068af47146178ce025736989f37fd862.jpeg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://www.soat.fr/wp-content/uploads/2013/06/Mathieu-parisot-mini.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• https://pbs.twimg.com/profile_images/1520756694/263927_2114421789970_1528442537_3828466_2806724_n__1_.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://m.c.lnkd.licdn.com/mpr/mpr/shrink_200_200/p/1/000/1a1/3d1/258cb42.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://m.c.lnkd.licdn.com/media/p/4/000/15f/25a/14e30e7.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://cdn4.infoq.com/images/team/fr/DridiBoukelmoune.jpg Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable)
• https://pbs.twimg.com/profile_images/2776155908/7a1460aa6728eda8e4a2ca56f425ac99.jpeg Failed to load resource: the server responded with a status of 404 (Not Found)
• https://media.licdn.com/media/p/8/000/1e1/205/29f40de.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• https://blog.crafting-labs.fr/dotclear/images/antoine-vernois.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://cltdl.fr//profile_square.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://www.brownbaglunch.fr/img/villes/BBL_Aix-en-Provence.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://raynaud.io//wp-content/uploads/2013/12/manuel.jpg Failed to load resource: the server responded with a status of 404 (Not Found)
• http://lambdanext.eu/img/cgrand.png Failed to load resource: net::ERR_TIMED_OUT
• http://www.brownbaglunch.fr/favicon.ico Failed to load resource: the server responded with a status of 404 (Not Found)

Follow up as per #175

We should have a list of associated speakers may be. Or an independant list of speakers and an independant list of talks. In the list of talks we can reference one or more speakers.
May be not ideal for PRs though.

We need to do some cleanup as asked in https://twitter.com/cyril_lakech/status/808233862455246848.

I'd propose to have one single document per speaker for example, may be we can also introduce subdirs per main city and have a structure like:

/_settings/          // Contains all json settings if any
/_city/              // Contains one file per city
/_speaker/paris/     // Contains one file per speaker
/_speaker/montreal/  // Contains one file per speaker
/_speaker/nantes/    // Contains one file per speaker

Then either try to automatically load the JSON docs (which is hard IIRC) or include all of them in a central json doc:

/baggers.js

WDYT?

As I'm adding some features to the website, I'd like to propose a new format for baggers.

Nowadays, we have:

{
   "name":"BAGGER NAME",
   "bio":"BIO",
   "picture":"Link to picture",
   "websites":[
      {
         "title":"Blog",
         "href":"LINK"
      },
      {
         "title":"GitHub",
         "href":"LINK"
      }
   ],
   "twitter":"ACCOUNT",
   "contact":"EMAIL",
   "mail":"EMAIL",
   "location":"CITY NAME",
   "sessions":[
      {
         "title":"TITLE",
         "summary":"ABSTRACT"
      }
   ],
   "tags":[
      "TAG",
      "TAG"
   ],
   "cities":[
      "CITY NAME",
      "CITY NAME"
   ]
}

Change proposal:

{
   "created":"DATE OF CREATION",
   "name":"BAGGER NAME",
   "bio":"BIO with support for HTML / Markdown",
   "picture":"Link to picture",
   "websites":[
      {
         "title":"Blog",
         "href":"LINK"
      },
      {
         "title":"GitHub",
         "href":"LINK"
      }
   ],
   "twitter":"ACCOUNT",
   "mail":"EMAIL",
   "location":"CITY NAME",
   "sessions":[
      {
         "title":"TITLE",
         "summary":"ABSTRACT",
         "tags":[
            "TAG",
            "TAG"
         ]
      }
   ],
   "cities":[
      {
         "city":"CITY NAME",
         "range":"30km"
      },
      {
         "city":"CITY NAME",
         "range":"30km"
      }
   ]
}

Main changes:

• Remove contact as we have the same information in mail
• Add created so we can have a section with the new comers and also provide stats per year
• Move tags in sessions so users will be able to choose a talk by a tag
• cities now gives from which city a speaker can talk and up to which distance. It will help to propose talks based on geo loc.

Thoughts?

Changes made to the websites field in the speakers json make both contributing and browsing the site confusing.
E.G.: When watching "Henri Tremblay"'s profile on the website, we can now see the following:

Web
Web
Web
@henri_tremblay

while before, each website was clearly specified.

EasyMock
Objenesis
Blog
@henri_tremblay

To me, this change only helps the technical side, unless it's a way for you to force speakers to only specify one "Web" entry.
In that case, we should clean the existing json to force only one entry per category, as an example.

IMO, previous format was better, and it was easy to distinguish websites technically, parsing the URL.

As for #392 http://data.brownbaglunch.fr/baggers.js is not published anymore.

@linsolas could you help?

Hello,

Ma PR a bien été mergée, mais mon profil n'apparait toujours pas sur le site : http://www.brownbaglunch.fr/

Merci d'avance,

http://data.brownbaglunch.fr/baggers.js is not published anymore.

For example Arthur Micoulet is in one of the latest commits but not present in http://data.brownbaglunch.fr/baggers.js.

The cities field changed from being an array of city to a single object containing many cities per field name.
This add some duplication in the cities name, complexifies the parsing, and I can't see any advantages in using this format

Now:

"cities": {
    "Aix-en-Provence": {
      "name": "Aix-en-Provence",
      "ville_img": "img/villes/BBL.jpg",
      "lat": 43.529742,
      "lng": 5.447427
    },
    "Avignon": {
      "name": "Avignon",
      "ville_img": "img/villes/BBL_Avignon.jpg",
      "lat": 43.941557,
      "lng": 4.8332525
    }
}

Before:

"cities": [
        {
            "name": "Tours",
            "ville_img": "img/villes/BBL_Tours.jpg",
            "lat": 47.396651,
            "lng": 0.694286
        },
        {
            "name": "Paris",
            "ville_img": "img/villes/BBL.jpg",
            "lat": 48.856614,
            "lng": 2.352222
        }
]