These are chat archives for gitevents/core

11th
Jan 2016
Niko Nevala
@nnevala
Jan 11 2016 11:37
hello
Patrick Heneise
@PatrickHeneise
Jan 11 2016 11:39
Hey
for the CLI, I wrote a dump some time ago: gitevents/core#100
Niko Nevala
@nnevala
Jan 11 2016 11:41
cool
this is pretty much what Ian mentioned to me earlier
and I'm here to help with this stuff :)
Patrick Heneise
@PatrickHeneise
Jan 11 2016 11:41
if we create the repos etc. automatically from the bot account, that would be awesome as we can also set the org-wide webhook, create and save the production.json on gist and just paste the cloud-config / dev config for the user at the end of the process
cloud-config needs an etcd address and link to production.json to run
that's awesome, thanks a lot :)
a lot of things have been done, but there's still so much to do
Niko Nevala
@nnevala
Jan 11 2016 11:43
I set up the core locally, but I don't really know how to use it
Patrick Heneise
@PatrickHeneise
Jan 11 2016 11:43
I just invited you to the playground
  1. start the core locally
  2. start localtunnel (lt -p 3000)
  3. change the address here https://github.com/organizations/GiteventsPlayground/settings/hooks
This message was deleted
there are a few Deliveries already in the list, just click them and 'Redeliver'
then you should see them locally
you'd usually start with a new event: https://github.com/GiteventsPlayground/planning (see Plan an Event link)
and then add talks (speakers repo)
the 'plan an event' and 'submit a talk' links can be modified to adjust to each meetup, but some fields in the headers are requires (especially with events the date)
Niko Nevala
@nnevala
Jan 11 2016 11:50
does the core itself do anything with the webhook deliveries? or does it require plugins set up for me to actually see something other than requests coming in
Niko Nevala
@nnevala
Jan 11 2016 11:56
and... just to clarify, the would be to run a separate github user account (the bot account you mentioned above) to manage gitevents with, and that account would be authorized to create the relevant repositories and gists automatically
Patrick Heneise
@PatrickHeneise
Jan 11 2016 12:05
the core does a few things:
  1. pre-format event and talk objects to a unified structure
  2. commit events and talks to the gitevent repository (from github config)
  3. launch plugins with the event or talk
the gitevent repo can be for example the event main repo (in our case https://github.com/BarcelonaJS/BarcelonaJS)
just a side node, config.github.repos.gitevent was only named without 's' to have the same length as speakers and planning, this could be adjusted to gitevents or something more meaningful
Patrick Heneise
@PatrickHeneise
Jan 11 2016 13:32
@nnevala if you have any further questions, I'm usually here
Niko Nevala
@nnevala
Jan 11 2016 13:32
@PatrickHeneise thanks :)
I'll see where I get to
discussed this with Ian and I'll start by simply building a utility for building the configuration array
and build on that
Patrick Heneise
@PatrickHeneise
Jan 11 2016 13:33
ok
this is the barcelonajs config
most complete version at the moment
I'm not sure how much in sync the other config is, as there are some small changes (ISO durations etc.)
Niko Nevala
@nnevala
Jan 11 2016 13:43
yeah I see the structure is bit different to what's in the core readme
does gitevents require that you have an org in github?
Patrick Heneise
@PatrickHeneise
Jan 11 2016 13:45
no, 'org' is just the primary path, could be a user as well
Niko Nevala
@nnevala
Jan 11 2016 14:41
what's the auth plugin
I see it referenced in the config but I don't really understand what it is or where it is
Niko Nevala
@nnevala
Jan 11 2016 14:46
@PatrickHeneise could you create a repo in the gitevents org for the console app? so that I could fork it and PR into it
here you go
Niko Nevala
@nnevala
Jan 11 2016 14:50
cheers
Niko Nevala
@nnevala
Jan 11 2016 15:01
is there a preferred test framework?
@mike182uk, did you have something in mind for core?
Michael Barrett
@mike182uk
Jan 11 2016 15:02
core is using tape (https://github.com/substack/tape) at the moment, so i was going to continue with using this
Niko Nevala
@nnevala
Jan 11 2016 15:04
ok, great
Michael Barrett
@mike182uk
Jan 11 2016 15:05
on the gitevents-tito plugin i used the tap-spec formatter to make the output more spec like: tape test.js | tap spec
Patrick Heneise
@PatrickHeneise
Jan 11 2016 16:00
yeah tape is totally sufficient
well, the core doesn't really have tests at the moment
Ian Crowther
@iancrowther
Jan 11 2016 21:48