-
Notifications
You must be signed in to change notification settings - Fork 23
2019_02_27_Kirby Guild Meeting Summary
This page contains a meeting summary from the Kirby Guild meeting, held on February 27th, 2019.
Experience with AngularJS and Angular 2+, arranger of angular meetups (ngVikings) in Copenhagen. Before Jyske Bank, worked in a design bureau with a lot of Ionic Apps.
Have had no previous experience with Angular, but has had a lot of frontend development experience. Originally from Bankdata.
Experience with AngularJS and Angular 2+ (since the alpha days), has had a short hiatus away from “modern angular” in a years time. Previous experience with web development all of his career.
Experience with Angular, Ionic – POC’ed on this solution. “Founding father of Kirby”, idea behind this is that Kirby can be used In other context than the current one – also possible to hire external resources to develop on Kirby (exclusively).
Experience with AngularJS since early alpha days, a couple of years experience with Angular 2+,
TBD
A Component Status will be introduced in the cookbook, to see which state it’s in (preliminary, version, indication of "ready to use" etc.).
Everything Kirby-related goes into Github Issues. The Trello board can still exist, but link to Github issues instead of copying text!
Jonas will move the 3 components (feature requests) from the Trello board, to Github issues.
We went through a few of the open Github issues, a lot could the talking going on was far "too chatty" to be capture. But briefly summarized, the following was obtained:
- Jonas has taken on the task of implementing support for Endless Scroll.
- Anders S has taken on the task of creating a common README.md file
A question was brought up if "the UX’ers" have a wishlist of components they “really want”? The answer to this question was yes - Marvin is working on creating a list of these.
We'll be having Weekly meeting (going forward) – every friday (at 9:00), you'll be able to participate when not physically present (through a virtual meeting room) – hence, no requirement on a physical presence. Kirby Guild will set aside Friday as “Kirby”-day (and not participate in teams’ daily scrum).
Jakob has already booking the (recurring) meeting, for this.
A rule-set for working with Kirby is being established, the following has been noted:
- Iterative development – continuously improve on components (functionality and quality).
- Kirby Guild has set aside dedicated time, but every team (or public contributor) can work on the components (the Kirby guild has not become a Component dev team – more a curating team).
Sent out in meeting invite.
Follow this link for instructions on how to get support.
Have a look at the contribution guidelines.
The following articles can help you become a good contributor. They document our toughts and opinions on contribution related topics.
- The Good: Issue
- The Good: Branch
- The Good: Commit
- The Good: Self-review
- The Good: Pull-request
- The Good: Test
Other ways of doing things are not wrong - however a project of this size requires consistency in the way we cooperate to be manageable.
Ultimately it will help you save some time getting from a new issue to a merged PR.