Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Pete Smith
    @kineopete
    Hi folks, I wanted to set this room up to crowdsource the agenda for our next face to face roadmap meeting at the City & Guilds offices in London on the 1st October. The main purpose of the session is to discuss anything outstanding/contentious about the impending releases, plan the features/functionality that need to go into the next ones and discuss/agree the technologies and frameworks we should be adopting in these future releases.
    I've booked two rooms - I'm hoping that most sessions will be interesting and relevant to both the framework and authoring tool sides of the project, but I expect that we will want to have separate sessions when discussing the detail of current releases
    Pete Smith
    @kineopete

    To get the discussion rolling, things I think we should be covering are:
    v4 Framework - accessibility implementation v5 Framework - theme refactor
    v0.7 AAT - modularisation refactor xAPI plugin
    *New tech - Vue vs React vs Something else, ES6

    I think we should also talk about our project processes and how we can streamline and speed up releases

    please expand on the above, nominate new sessions and offer to present on any of the subjects above....
    canstudios-paulh
    @canstudios-paulh
    hey @kineopete is "v0.7 AAT - modularisation refactor xAPI plugin" all one thing?
    Pete Smith
    @kineopete
    hey Paul, it absolutely isn't - should be two separate bullets
    v0.7 AAT - modularisation refactor
    xAPI plugin
    sorry!
    canstudios-paulh
    @canstudios-paulh
    its ok - was only a little bit confused.
    lc-thomasberger
    @lc-thomasberger
    Framework build Tool / chain. Especially in combination with the Authoringtool. Right now we are stuck with the process / possibilities that grunt offers us. This makes things like live-reload and style amends for courses in the AT really hard. We might discuss different buildtools or if we create out own build chain.
    How can we support different Framework-Versions in one AT-Instance. This can be done as part of a tenant-architecture (master Tenant get's it's own Framework and Plugin repository) or inside the Tool directly. It is also good to discuss this topic in a larger group so that both streams are aware of this.
    lc-thomasberger
    @lc-thomasberger
    Re-integrate the adapt-cli into the AT? It might be useful to handle plugin-management, Framework build and such things inside the cli. The AT could then require the cli and execute the tasks.
    Those are just some basic ideas and thoughts that might make sense to discuss across both streams
    canstudios-paulh
    @canstudios-paulh
    @lc-thomasberger we think that each tenant would want to support multiple framework versions, with the option to attempt to upgrade a project. So definately worth talking this through.
    lc-thomasberger
    @lc-thomasberger
    Yes, for MVP we decided that we only have one master tenant so only one framework (and version). I think though that it is easier to handle different Framework versions using tenants than updating the Tool itself. At least on the long run. So I think we should maybe rethink Tenant Management MVP requirements. But again, this are just some thoughts. Happy to discuss this in the meeting.
    Brian Quinn
    @brian-learningpool
    hi @kineopete, any idea on what time things will kick off next Monday?
    Pete Smith
    @kineopete
    Hi Brian, we'll start at 10.30 to give people time to assemble/find the office
    canstudios-paulh
    @canstudios-paulh
    is the meeting at this office "1 Giltspur St, London EC1A 9DD”?
    Pete Smith
    @kineopete
    hey Paul, sorry, just spotted your message. That's the one....
    I've just emailed the agenda around - please shout if you don't get the email!
    canstudios-paulh
    @canstudios-paulh
    thanks @kineopete