Open iancrowther opened 8 years ago
That sounds great. The setup could be a lot simpler though.
Minimal requirements: GitHub Org:
What's currently working (more or less):
proposals.json
to events-YYYY.json
, to have a yearly historyThe optimal deployment should be a Docker container that gets the initial config from a Gist. If the config changes, just re-deploy the container. No CLI, no generators, no trouble ;).
My personal "best solution" would be:
proposals.json
optional: if there's another issue linked to the milestone (for example an article, links, jobs etc.) these should be included in the newsletter.
Gitevents is a plugable event management system layered on top of GitHub. Making use of the Github API and WebHooks, GitEvents allows event organisers to automate tasks by interacting with issues.
GitEvents promotes service plugins as we understand every event is different.
GitEvents and its plugins must be self hosted and at its most basic, is made up of two components, the core and the webhook.
tbd
tbd
Currently GitEvents listens to talk proposal issues and generates a json object that your event website can consume via the client API.
Setup this repo with the following labels:
We would like to be able to init the repo from the cli in order to enter the basic config keys and select your plugins, similiar to yeoman.
It would be great to be able to enter your dteails and automatically deploy GitEvents and your selected plugins onto your prefered cloud provider. For the purpose of the hackday, we could use Heroku + Papertrail.
We would like to be able to automatically tweet speaker details once a talk proposal has been accepted for a milestoned event.
We would like to be able to create a new ti.to event and setup the ticket releases via the API. Due to the lack of a milestone webhook, we need to have a think about how to trigger the creation of a new event.
We want to be able to send emails
We started to create a bot that would validate a talk proposal issues and reply if the interface was not adgered to.
There is a need to simplify the workflow within this core module. There is also a need for unit tests. We have been discussing using a 3rd party database such as firebase to reduce js state and logic.
We want the capability to deploy with easy via docker. Primarily deployed to digital ocean as docker container, listening to web hooks. The optimal deployment should be a Docker container that gets the initial config from a Gist. If the config changes, just re-deploy the container. No CLI, no generators, no trouble ;).
We need a website to explain what GitEvents is. This could be driven from the README
We need some help to flesh out the doc's. There are a lot of concepts to explain in order to get this system working for you. We need to make the onbaording doc's much more concise. It would be amazing to have a visualisation of the end 2 end work flow
We could use CodeShip + MetalSmith to create a CI chain to build and deploy either GitEvents or the Website.
proposals.json
we need to digest this into README etc.
agreed
gitevents What is it? Plugable Event management through github. Create issues to fire web hooks requests to the services you require via plugins.
What is core? core is a shell repo used to trigger webhooks via github issues
What can i do with this? create a talk proposal via a github issues. add a milstone which is the event date.
how to setup you github org 3 repos.
Minimum Requirements a github account a github repo
set a purpose for the repo:
once you decide the purpose, you can execute gi-labels
we need to be able to deploy plugins to digital ocean