Re: [proposal] going Agile

After some thinking, I think this is not easy to answer without more clarification. So I have updated the List I have once started (Now called Points of Interest). Added the going Agile topic, and will clarify the Point. So no one has to read this discussion in order to get the picture.

Re: [proposal] going Agile

How long should a reasonable demonstration period be? And what are the success criterias that has to be fulfilled? Am 17. Februar 2018 16:08:10 MEZ schrieb Patricia Shanahan : > > >On 2/17/2018 1:04 AM, Peter kovacs wrote: >> >> >> >>> +1 A practical demo of what the proposals

Re: [proposal] going Agile

On 2/17/2018 1:04 AM, Peter kovacs wrote: +1 A practical demo of what the proposals mean in practice will be far more useful than abstract discussion. How about your Idea to check all Arrays and replace them with containers? We would create a master ticket, Create sub tickets for each

Re: [proposal] going Agile

>+1 A practical demo of what the proposals mean in practice will be far >more useful than abstract discussion. > How about your Idea to check all Arrays and replace them with containers? We would create a master ticket, Create sub tickets for each case. Describing what we have to do. Then

Re: [proposal] going Agile

On 2/13/2018 2:22 PM, Andrea Pescetti wrote: Marcus wrote: @all: What do you think is the first topic we should start with? I think the only reasonable way forward is that Peter chooses one of the many available tasks (digital signatures? Java 9 support? MSVC update? .docx export? you

Re: [proposal] going Agile

Marcus wrote: @all: What do you think is the first topic we should start with? I think the only reasonable way forward is that Peter chooses one of the many available tasks (digital signatures? Java 9 support? MSVC update? .docx export? you name it) and experiments the workflow limited to

Re: [proposal] going Agile

Am 12.02.2018 um 22:15 schrieb Peter Kovacs: On 10.02.2018 13:26, Marcus wrote: Therefore let me summarize: - Use BZ for the development work (e.g, fixing a specific bug). - Work in Jira for the project tasks and technical coordination (e.g.,   Windows signing). - Use Confluence for project

Re: [proposal] going Agile

Hi - Thanks Peter for driving this topic. I don’t think we all agree, but we can (a) try to advance our project organization and (b) acknowledge how we are using the many tools we already use. > On Feb 12, 2018, at 1:15 PM, Peter Kovacs wrote: > > On 10.02.2018 13:26,

Re: [proposal] going Agile

On 10.02.2018 13:26, Marcus wrote: Therefore let me summarize: - Use BZ for the development work (e.g, fixing a specific bug). - Work in Jira for the project tasks and technical coordination (e.g.,   Windows signing). - Use Confluence for project work and as documentation base. - Take the

Re: [proposal] going Agile

How can I build only core package? I am only aware to build everything, or a certain range of modules, or I can build explicit one module. I do not want to take away the ability to build all in one step. But I think if you are only rebuilding core it saves you a lot of time. And if you can

Re: [proposal] going Agile

> On Feb 9, 2018, at 20:05, Peter Kovacs wrote: > >> On 09.02.2018 01:19, Patricia Shanahan wrote: >> On February 8, 2018, at 5:51 AM, Peter Kovacs wrote: >> >> # Devide the Project into different selfcontained parts. so we have >> smaller chunks to

Re: [proposal] going Agile

Am 10.02.2018 um 07:20 schrieb Peter Kovacs: On 09.02.2018 23:08, Marcus wrote: Am 08.02.2018 um 00:32 schrieb Andrea Pescetti: Peter Kovacs wrote: I would like to propose that we apply Agile development methods as much as we can. it depends what you mean with agile. IMHO forget Scrum as

Re: [proposal] going Agile

Am 10.02.2018 um 06:21 schrieb Peter Kovacs: Migration would be done by infra. They wrote up everything need to know: https://wiki.apache.org/general/ApacheBugzillaToJiraMigration I find it cumbersome that all our users should then use Jira to open a bug report. What about to keep Bugzilla

Re: [proposal] going Agile

On Sat, Feb 10, 2018 at 12:05 AM, Marcus wrote: > Am 09.02.2018 um 01:19 schrieb Patricia Shanahan: > >> On February 8, 2018, at 5:51 AM, Peter Kovacs wrote: >> >> # Start spreading knowledge in our development team. >>> 1) I would like to

Re: [proposal] going Agile

Openness can be a real problem. I have mainly done security fixes that had to stay on the private lists until released and disclosed. Patricia > On Feb 10, 2018, at 06:20, Peter Kovacs wrote: > > >> On 09.02.2018 23:08, Marcus wrote: >>> Am 08.02.2018 um 00:32 schrieb

Re: [proposal] going Agile

On 09.02.2018 23:08, Marcus wrote: Am 08.02.2018 um 00:32 schrieb Andrea Pescetti: Peter Kovacs wrote: I would like to propose that we apply Agile development methods as much as we can. it depends what you mean with agile. IMHO forget Scrum as we are not the community to get a commitment

Re: [proposal] going Agile

Migration would be done by infra. They wrote up everything need to know: https://wiki.apache.org/general/ApacheBugzillaToJiraMigration Again, it is not about the tool it is about the workflow. I would like to have a Kanbanboard, to get transparency what is worked on, who can I approach if I

Re: [proposal] going Agile

Am 08.02.2018 um 00:32 schrieb Andrea Pescetti: Peter Kovacs wrote: I would like to propose that we apply Agile development methods as much as we can. it depends what you mean with agile. IMHO forget Scrum as we are not the community to get a commitment for this. Kanban would be nice. At

Re: [proposal] going Agile

Am 09.02.2018 um 01:19 schrieb Patricia Shanahan: On February 8, 2018, at 5:51 AM, Peter Kovacs wrote: # Start spreading knowledge in our development team. 1) I would like to propose a Product Backlog / OIL (OpenIssue) List to priorize Issues we need to work on. The most

Re: [proposal] going Agile

On 09.02.2018 01:19, Patricia Shanahan wrote: On February 8, 2018, at 5:51 AM, Peter Kovacs wrote: # Devide the Project into different selfcontained parts. so we have smaller chunks to swallow. (Maybe we should consider breaking the compile Process into individual compile

Re: [proposal] going Agile

On February 8, 2018, at 5:51 AM, Peter Kovacs wrote: >Thank you these are good points. >On 08.02.2018 00:32, Andrea Pescetti wrote: >> Peter Kovacs wrote: >>> I would like to propose that we apply Agile development methods as >>> much as we can. >> >> Well, "as much as we can"

Re: [proposal] going Agile

+1 I am in favor, and like the way duscussions are heading. Willing to contribute in setting up project in Jira if thus goes through On Feb 8, 2018 11:21, "Peter Kovacs" wrote: > Thank you these are good points. > > On 08.02.2018 00:32, Andrea Pescetti wrote: > >> Peter Kovacs

Re: [proposal] going Agile

Thank you these are good points. On 08.02.2018 00:32, Andrea Pescetti wrote: Peter Kovacs wrote: I would like to propose that we apply Agile development methods as much as we can. Well, "as much as we can" is the key here. OpenOffice is as agile as an elephant. A lot of us use Agile in

Re: [proposal] going Agile

Peter Kovacs wrote: I would like to propose that we apply Agile development methods as much as we can. Well, "as much as we can" is the key here. OpenOffice is as agile as an elephant. A lot of us use Agile in their daily work activities, and maybe they even like it, but it's a totally