You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by Konstantinos Tsakalozos <ko...@canonical.com> on 2016/06/10 12:35:34 UTC

Opening up the Juju charm development process

Hi everyone,

As some of you have noticed we are working on Juju charms for the Bigtop
components. We would like to further open up the development process and
allow community members to get involved.

To this end we are considering creating JIRA tickets early in our
development cycle and updating them as we progress. In this way, we will be
able to collaborate with the community and receive feedback/contributions
on-time. In the future, we would like to synchronise our work with the
release cycles of Bigtop so that we can plan for the items to be included
on each Bigtop release.

Would it be ok if we create JIRA tickets for the upcoming work at the
planning of our sprints (a couple of weeks ahead from doing the actual
working)?

Also (excuse my ignorance here), when is decided what would go to the next
Bigtop release? Is this discussed here on the list or is there some open
meeting at some point? I am very new to the Bigtop ways.

Thank you,
Konstantinos Tsakalozos

Re: Opening up the Juju charm development process

Posted by Konstantin Boudnik <co...@apache.org>.
Hi Konstantinos!

Thanks for bringing this discussion up on the list! So the answer is yes on
all counts. The dev process is much like any other: open a ticket, exchange
the comments there, feel free to involve dev@ if you need to (if you don't see
much response from the community on the JIRA ticket).

Releases are driven by us, so basically we do them whenever we feel it is a
good time for a release (ie we have another updated components, improvements
in the stack to share with the users, etc.), and we have cycles for it. Doing
the release isn't that hard, but requires a bit of time from RM and others to
give it a test. Say right now we have started the discussion on 1.2 release,
which hopefully will produce something tangible in a few weeks.

So please remember that there's no secret committee that makes decisions for
the project. It just people who're doing the actual work ;)
 
Cheers,
  Cos

On Fri, Jun 10, 2016 at 03:35PM, Konstantinos Tsakalozos wrote:
> Hi everyone,
> 
> As some of you have noticed we are working on Juju charms for the Bigtop
> components. We would like to further open up the development process and
> allow community members to get involved.
> 
> To this end we are considering creating JIRA tickets early in our
> development cycle and updating them as we progress. In this way, we will be
> able to collaborate with the community and receive feedback/contributions
> on-time. In the future, we would like to synchronise our work with the
> release cycles of Bigtop so that we can plan for the items to be included
> on each Bigtop release.
> 
> Would it be ok if we create JIRA tickets for the upcoming work at the
> planning of our sprints (a couple of weeks ahead from doing the actual
> working)?
> 
> Also (excuse my ignorance here), when is decided what would go to the next
> Bigtop release? Is this discussed here on the list or is there some open
> meeting at some point? I am very new to the Bigtop ways.
> 
> Thank you,
> Konstantinos Tsakalozos