Re: Vote to stop using JIRA

[Timur Shenkao <ts...@timshenkao.su>]

Hello!

In parallel e-mail thread, people shared Apache Beam experience on
community building. So I decided  not to re-invent the wheel and bring
together my personal experience and other Apache projects' knowledge.
This is like short cheat sheet:
https://drive.google.com/file/d/1L47T_E9AHYeL3SvatGYAWig0m3eTX27l to get
started.

One needs to define:
-- list of shepherds
-- components
-- mail list (like user@mxnet... or jira@mxnet)

If all PRs have corresponding JIRAs, then release notes can be generated
with a click of a button.
Labels are not mandatory but they make life much easier.


Timur

On Fri, Jun 29, 2018 at 7:08 AM, Timur Shenkao <ts...@timshenkao.su> wrote:

> I can devote some time this weekend and start writing some draft proposal.
> Then we can add it to Confluence and other people will be able to
> elaborate it.
>
> But I believe some workflow description is already present in Apache
> materials
>
> On Thu, Jun 28, 2018 at 9:23 PM, Marco de Abreu <
> marco.g.abreu@googlemail.com.invalid> wrote:
>
>> Hi Yasser,
>>
>> agree, the environment is already set up properly. The problem we have is
>> that we are lacking people who are familiar with the system and who would
>> like to help us leading the JIRA related efforts. This could include
>> things
>> like kicking off a few JIRA projects, setting up permissions properly,
>> spreading the knowledge, creating a good project management flow as well
>> as
>> mentoring us in how far we can improve.
>>
>> @Pedro: No, JIRA tickets should not be closed automatically. A JIRA ticket
>> might be a bigger story or be referenced by multiple PRs, thus it would be
>> misleading if they'd be auto-closed.
>>
>> -Marco
>>
>> On Thu, Jun 28, 2018 at 7:24 PM Pedro Larroy <
>> pedro.larroy.lists@gmail.com>
>> wrote:
>>
>> > Am I doing something wrong? When my PRs get merged, JIRA issues don't
>> get
>> > closed:
>> >
>> > https://issues.apache.org/jira/browse/MXNET-460
>> >
>> > @YiZhi Liu: as per PR instructions, a JIRA ticket is not required for
>> minor
>> > patches, only for things that you would include in release notes.
>> >
>> > Pedro.
>> >
>> > On Thu, Jun 28, 2018 at 4:15 AM Yasser Zamani <ya...@apache.org>
>> > wrote:
>> >
>> > > Hello Marco, I hope best,
>> > >
>> > > Thank you for your email, however, as I mentioned in following links,
>> I
>> > > see MXNet already has configured project management boards in Jira
>> and it
>> > > seems people have assigned related tasks there, I mean I see it's
>> already
>> > > working and we don't need an extra To Do, right?
>> > >
>> > > Regards.
>> > > On Jun 27, 2018, at 4:31 PM, Marco de Abreu <
>> > marco.g.abreu@googlemail.com
>> > > .invalid<ma...@googlemail.com.invalid>> wrote:
>> > >
>> > > Hello Yasser,
>> > > I'd like to check back with you and ask if you need any assistance or
>> if
>> > > there is anything else we can do. Please feel free to shoot me a
>> private
>> > > email so we can set up a 1:1 to discuss ideas and solutions.
>> > > -Marco
>> > >
>> > > On Wed, Jun 13, 2018 at 10:02 AM Yasser Zamani <
>> yasserzamani@apache.org>
>> > > wrote:
>> > >
>> > >
>> > >
>> > >  On 6/11/2018 8:53 PM, Marco de Abreu wrote:
>> > >  How about you set up a personal instance of JIRA (let us know if the
>> > >  public
>> > >  ones differ too much from the one we're running under Apache) and
>> play
>> > >  around a bit? We can then review the setup and migrate the necessary
>> > >  changes after everything looks good.
>> > >
>> > >  I'm pleased to say that fortunately it seems MXNet already has both
>> > >  Kanban [1] and Scrum [2] project management boards :)
>> > >
>> > >  Regards.
>> > >
>> > >  [1] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>> iew=237
>> > >  [2] https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidV
>> iew=211
>> > >
>> > >
>> >
>>
>
>