× Warning! This forum is in archival status. New contributions may not work.
Proposal on sample templates
  • Hi guys,

    For every Campsite release I can always see some issues/tickets which
    are not related to Campsite core but Sample Templates, especially for
    "the Custodian" classic set, for example, right now for the 3.4.3
    release most of the tickets remaining "Open" are somehow related to
    these sample templates and I have been in touch with Ljuba, Sava,
    Andrey and Claudia who are working on those tasks in order to finish
    them and then be able to start testing and release. It is not a big
    deal but still time-consuming, not only at this stage but we spend
    some time on this also in our Development Release Planning meetings
    when we go through all the issues deciding which ones will go and
    which ones won't.

    Based on this, my proposal is to manage the sample templates as if
    they were a complete separate project, and in fact it is. So, sample
    templates would have its own team, team leader, roadmap, deadlines,
    tasks, version numbering. This way we would separate also at this
    level core and data architecture from presentation :-) and that's
    always good.

    Sample templates for me are really important, they are the best way to
    show what can be really done with Campsite.

    Sample templates would still be part of Campsite, as Campsite would
    simply include the current version of the templates at release date,
    but wouldn't have to wait for sample templates in order to be
    released. As I said, sample templates team would release based on its
    own plan and could even manage not only one templates set but several.

    What do you think?


    --
    Holman Romero
    Senior Software Engineer, Sourcefabric
    holman.romero@sourcefabric.org

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420 608910633

    http://www.sourcefabric.org
  • 2 Comments sorted by
  • Vote Up0Vote Down Sava TatićSava Tatić
    Posts: 113Member, Administrator, Sourcefabric Team
    I think you have a good point here, especially time-wise.

    We should manage them as a separate project, and there should be a project
    owner (Micz?), but we should time their upgrades with minor and major
    releases. Of course, they should never hold back a release.

    So let's try to set it up like that after the 3.4.3 release.

    All the best,

    Sava

    On Thu, Sep 30, 2010 at 12:38 PM, Holman Romero <
    campsite-dev@lists.sourcefabric.org> wrote:

    > Hi guys,
    >
    > For every Campsite release I can always see some issues/tickets which
    > are not related to Campsite core but Sample Templates, especially for
    > "the Custodian" classic set, for example, right now for the 3.4.3
    > release most of the tickets remaining "Open" are somehow related to
    > these sample templates and I have been in touch with Ljuba, Sava,
    > Andrey and Claudia who are working on those tasks in order to finish
    > them and then be able to start testing and release. It is not a big
    > deal but still time-consuming, not only at this stage but we spend
    > some time on this also in our Development Release Planning meetings
    > when we go through all the issues deciding which ones will go and
    > which ones won't.
    >
    > Based on this, my proposal is to manage the sample templates as if
    > they were a complete separate project, and in fact it is. So, sample
    > templates would have its own team, team leader, roadmap, deadlines,
    > tasks, version numbering. This way we would separate also at this
    > level core and data architecture from presentation :-) and that's
    > always good.
    >
    > Sample templates for me are really important, they are the best way to
    > show what can be really done with Campsite.
    >
    > Sample templates would still be part of Campsite, as Campsite would
    > simply include the current version of the templates at release date,
    > but wouldn't have to wait for sample templates in order to be
    > released. As I said, sample templates team would release based on its
    > own plan and could even manage not only one templates set but several.
    >
    > What do you think?
    >
    >
    > --
    > Holman Romero
    > Senior Software Engineer, Sourcefabric
    > holman.romero@sourcefabric.org
    >
    > Salvátorská 10
    > 110 00 Praha 1, Czech Republic
    > +420 608910633
    >
    > http://www.sourcefabric.org
    >
    >



    --
    Sava Tatić
    Managing Director, Sourcefabric o.p.s.
    sava.tatic@sourcefabric.org

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420 2 22 36 25 40
    Skype: tictactatic

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric

  • Vote Up0Vote Down Paul BaranowskiPaul Baranowski
    Posts: 389Member, Administrator, Sourcefabric Team
    Great idea Holman.


    On Thu, Sep 30, 2010 at 6:38 AM, Holman Romero <
    campsite-dev@lists.sourcefabric.org> wrote:

    > Hi guys,
    >
    > For every Campsite release I can always see some issues/tickets which
    > are not related to Campsite core but Sample Templates, especially for
    > "the Custodian" classic set, for example, right now for the 3.4.3
    > release most of the tickets remaining "Open" are somehow related to
    > these sample templates and I have been in touch with Ljuba, Sava,
    > Andrey and Claudia who are working on those tasks in order to finish
    > them and then be able to start testing and release. It is not a big
    > deal but still time-consuming, not only at this stage but we spend
    > some time on this also in our Development Release Planning meetings
    > when we go through all the issues deciding which ones will go and
    > which ones won't.
    >
    > Based on this, my proposal is to manage the sample templates as if
    > they were a complete separate project, and in fact it is. So, sample
    > templates would have its own team, team leader, roadmap, deadlines,
    > tasks, version numbering. This way we would separate also at this
    > level core and data architecture from presentation :-) and that's
    > always good.
    >
    > Sample templates for me are really important, they are the best way to
    > show what can be really done with Campsite.
    >
    > Sample templates would still be part of Campsite, as Campsite would
    > simply include the current version of the templates at release date,
    > but wouldn't have to wait for sample templates in order to be
    > released. As I said, sample templates team would release based on its
    > own plan and could even manage not only one templates set but several.
    >
    > What do you think?
    >
    >
    > --
    > Holman Romero
    > Senior Software Engineer, Sourcefabric
    > holman.romero@sourcefabric.org
    >
    > Salvátorská 10
    > 110 00 Praha 1, Czech Republic
    > +420 608910633
    >
    > http://www.sourcefabric.org
    >
    >