[Tendrl-devel] bugs

[Jeff Applewhite]

Hi All

Just a couple points of clarification.

First of all the Jira hosting was obtained free of charge through
Atlassian. I applied for their Open Source license request[1] and it was
granted. So they demonstrate support of Open Source development at least in
this fashion. Their source is not open (but then neither is Github itself).
I am not aware of any Github policy WRT open source projects and free
hosting for project management functionality (but then it is quite new).

Secondly there is no requirement to have a Jira account to *view epics,
stories, tasks, bugs, etc. in Jira because that is one of the requirements
for participating in the open source program. They require that you modify
your project to be open to anonymous viewers and I have done that. If you
want to *participate in the development, testing, or be assigned to a
story, etc. you will need an account and those accounts are unlimited with
the licensing we have. If that is a significant barrier to developer
participation then I tend to doubt the eagerness of said developer to
actually contribute. It literally takes an email to this list and one of
the 4 or 5 admins we have will create the account. They will get an email,
set their password, and login. Simple as that.

On bugs..

It seems the preponderance of commenters prefer Github issues for speed and
developer friendliness. Let software continue to eat the world..
Let's call it case closed on that.

Thanks

Jeff

[1]  https://www.atlassian.com/software/views/open-source-license-request

On Wed, Sep 21, 2016 at 4:21 AM, Martin Kudlej <mkudlej at redhat.com> wrote:

> Hi all,
>
> Jira:
> pros: it scales better than Trello, planning features are much better than
> in Github and Bugzilla
> cons: it is not close to code
>
> Bugzilla:
> Well here I'm not that objective because I'm used to work with BZ and I
> can do there planning and issue tracking.
> pros: it's full featured issue tracking system, there are couple of tools
> integrated with it
> cons: it's not close to code and it's hard to do planning there
>
> Github:
> pros: close to code
> cons: lack of planning features for project like Tendrl. need to
> synchronize with external tools.
>
> I vote for Jira as single point for storing everything about Tendrl. I
> think planning and issue tracking should be on one place because
> synchronization between 2 or more tools can generate mistakes, mess and
> additional effort.
>
>
> --
> Best Regards,
> Martin Kudlej.
> RHSC/USM Senior Quality Assurance Engineer
> Red Hat Czech s.r.o.
>
> Phone: +420 532 294 155
> E-mail:mkudlej at redhat.com
> IRC:   mkudlej at #brno, #gluster, #storage-qa, #rhs, #rh-ceph,
> #usm-meeting @ redhat
>                   #tendrl-devel @ freenode
>



-- 
Jeff Applewhite
Principal Product Manager
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/tendrl-devel/attachments/20160921/9114db45/attachment.htm>