[DISCUSSION] JIRA issues for web and wiki pages

[Pierre Smits]

Hi all,

Currently we only register issues related to the OFBiz code. But we also
see a lot of comments in wiki pages regarding corrections. These comments
can exists quite a long time and it seems that these are frequently
overlooked.

Should we not also have a setup in JIRA regarding the web and wiki pages?

This helps us to stay aware of bugs and improvements thereof, and help us
to track contributors and patches. Having JIRA issues for this seems to be
done also in a number of other Apache projects.

Regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

[Ron Wheeler]

It would be good to have a well organized and supported system for
tracking defects of all types including documentation.
The JIRA has a very very helpful features that would allow us to
identify the importance of problems, any version dependencies, assigned
person, etc.

Ron

On 21/10/2014 7:45 AM, Pierre Smits wrote:

> Hi all,
>
> Currently we only register issues related to the OFBiz code. But we also
> see a lot of comments in wiki pages regarding corrections. These comments
> can exists quite a long time and it seems that these are frequently
> overlooked.
>
> Should we not also have a setup in JIRA regarding the web and wiki pages?
>
> This helps us to stay aware of bugs and improvements thereof, and help us
> to track contributors and patches. Having JIRA issues for this seems to be
> done also in a number of other Apache projects.
>
> Regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>

--
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: [phone], ext 102

[Jacques Le Roux]

I believe, the problem is more about people not knowing where to post things, else of course Jira is a perfect fit.
Though I (hopefully I'm not alone) normally monitor Confluence (including comments) but https://issues.apache.org/jira/browse/INFRA-8323
Anyway I normally receive all changes by mail.

Pierre, do you have something specific in mind about overlooked comments, I mean a list, etc.?

Jacques

Le 21/10/2014 14:43, Ron Wheeler a écrit :

> It would be good to have a well organized and supported system for tracking defects of all types including documentation.
> The JIRA has a very very helpful features that would allow us to identify the importance of problems, any version dependencies, assigned person, etc.
>
> Ron
>
> On 21/10/2014 7:45 AM, Pierre Smits wrote:
>> Hi all,
>>
>> Currently we only register issues related to the OFBiz code. But we also
>> see a lot of comments in wiki pages regarding corrections. These comments
>> can exists quite a long time and it seems that these are frequently
>> overlooked.
>>
>> Should we not also have a setup in JIRA regarding the web and wiki pages?
>>
>> This helps us to stay aware of bugs and improvements thereof, and help us
>> to track contributors and patches. Having JIRA issues for this seems to be
>> done also in a number of other Apache projects.
>>
>> Regards,
>>
>> Pierre Smits
>>
>> *ORRTIZ.COM <http://www.orrtiz.com>*
>> Services & Solutions for Cloud-
>> Based Manufacturing, Professional
>> Services and Retail & Trade
>> http://www.orrtiz.com
>>
>
>

[Jacques Le Roux]

Le 21/10/2014 17:01, Jacques Le Roux a écrit :
> I believe, the problem is more about people not knowing where to post things, else of course Jira is a perfect fit.
> Though I (hopefully I'm not alone) normally monitor Confluence (including comments) but https://issues.apache.org/jira/browse/INFRA-8323
> Anyway I normally receive all changes by mail.

Also please read my comment to Julien about how to handle changes in not open Confluence spaces: http://markmail.org/message/yk2l3d22qenipqwz
It's easier for committers than to have to check multi-places :/
Of course when those comments are about issues in code Jiras should be opened

Jacques

>
> Pierre, do you have something specific in mind about overlooked comments, I mean a list, etc.?
>
> Jacques
>
> Le 21/10/2014 14:43, Ron Wheeler a écrit :
>> It would be good to have a well organized and supported system for tracking defects of all types including documentation.
>> The JIRA has a very very helpful features that would allow us to identify the importance of problems, any version dependencies, assigned person, etc.
>>
>> Ron
>>
>> On 21/10/2014 7:45 AM, Pierre Smits wrote:
>>> Hi all,
>>>
>>> Currently we only register issues related to the OFBiz code. But we also
>>> see a lot of comments in wiki pages regarding corrections. These comments
>>> can exists quite a long time and it seems that these are frequently
>>> overlooked.
>>>
>>> Should we not also have a setup in JIRA regarding the web and wiki pages?
>>>
>>> This helps us to stay aware of bugs and improvements thereof, and help us
>>> to track contributors and patches. Having JIRA issues for this seems to be
>>> done also in a number of other Apache projects.
>>>
>>> Regards,
>>>
>>> Pierre Smits
>>>
>>> *ORRTIZ.COM <http://www.orrtiz.com>*
>>> Services & Solutions for Cloud-
>>> Based Manufacturing, Professional
>>> Services and Retail & Trade
>>> http://www.orrtiz.com
>>>
>>
>>
>

[Pierre Smits]

Jacques,

The problem is indeed where to post the issues. There is no solution
available to do patches to pages in the website and improvement comments in
the restricted spaces are all over the place. And regarding the latter
aspect these comments can stay visible for quite some time due to busy
schedules (and other interests) of those capable to implement the changes.
Having those comments there for a longer time is not good regarding
branding and adoption.

Having a JIRA setup for the website and restricted spaces will provide the
one place and will create insights about what is still open, what is fixed
and and when. Plus it helps identifying those committers that could become
committers.

All in all not a bad suggestion and improvement.

Regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Tue, Oct 21, 2014 at 5:01 PM, Jacques Le Roux <
[hidden email]> wrote:

> I believe, the problem is more about people not knowing where to post
> things, else of course Jira is a perfect fit.
> Though I (hopefully I'm not alone) normally monitor Confluence (including
> comments) but https://issues.apache.org/jira/browse/INFRA-8323
> Anyway I normally receive all changes by mail.
>
> Pierre, do you have something specific in mind about overlooked comments,
> I mean a list, etc.?
>
> Jacques
>
> Le 21/10/2014 14:43, Ron Wheeler a écrit :
>
>  It would be good to have a well organized and supported system for
>> tracking defects of all types including documentation.
>> The JIRA has a very very helpful features that would allow us to identify
>> the importance of problems, any version dependencies, assigned person, etc.
>>
>> Ron
>>
>> On 21/10/2014 7:45 AM, Pierre Smits wrote:
>>
>>> Hi all,
>>>
>>> Currently we only register issues related to the OFBiz code. But we also
>>> see a lot of comments in wiki pages regarding corrections. These comments
>>> can exists quite a long time and it seems that these are frequently
>>> overlooked.
>>>
>>> Should we not also have a setup in JIRA regarding the web and wiki pages?
>>>
>>> This helps us to stay aware of bugs and improvements thereof, and help us
>>> to track contributors and patches. Having JIRA issues for this seems to
>>> be
>>> done also in a number of other Apache projects.
>>>
>>> Regards,
>>>
>>> Pierre Smits
>>>
>>> *ORRTIZ.COM <http://www.orrtiz.com>*
>>> Services & Solutions for Cloud-
>>> Based Manufacturing, Professional
>>> Services and Retail & Trade
>>> http://www.orrtiz.com
>>>
>>>
>>
>>

[Jacques Le Roux]

Le 21/10/2014 22:53, Pierre Smits a écrit :
> Jacques,
>
> The problem is indeed where to post the issues. There is no solution
> available to do patches to pages in the website and improvement comments in
> the restricted spaces are all over the place.

Long ago, the community decided to go with comments. I don't see a need to change that. Not all comments in Confluence are important or even relevant.

> And regarding the latter
> aspect these comments can stay visible for quite some time due to busy
> schedules (and other interests) of those capable to implement the changes.
> Having those comments there for a longer time is not good regarding
> branding and adoption.

If you are really interested/concerned simply add comments where you find relevant and I will do a complete review.

>
> Having a JIRA setup for the website and restricted spaces will provide the
> one place and will create insights about what is still open, what is fixed
> and and when. Plus it helps identifying those committers that could become
> committers.

If there are important things to tackle in Confluence which are neglected then of course the way is to create a Jira task type issue.
I will add a Confluence component option for this (in Jira only of course!).

Jacques

>
> All in all not a bad suggestion and improvement.
>
> Regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Tue, Oct 21, 2014 at 5:01 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> I believe, the problem is more about people not knowing where to post
>> things, else of course Jira is a perfect fit.
>> Though I (hopefully I'm not alone) normally monitor Confluence (including
>> comments) but https://issues.apache.org/jira/browse/INFRA-8323
>> Anyway I normally receive all changes by mail.
>>
>> Pierre, do you have something specific in mind about overlooked comments,
>> I mean a list, etc.?
>>
>> Jacques
>>
>> Le 21/10/2014 14:43, Ron Wheeler a écrit :
>>
>>   It would be good to have a well organized and supported system for
>>> tracking defects of all types including documentation.
>>> The JIRA has a very very helpful features that would allow us to identify
>>> the importance of problems, any version dependencies, assigned person, etc.
>>>
>>> Ron
>>>
>>> On 21/10/2014 7:45 AM, Pierre Smits wrote:
>>>
>>>> Hi all,
>>>>
>>>> Currently we only register issues related to the OFBiz code. But we also
>>>> see a lot of comments in wiki pages regarding corrections. These comments
>>>> can exists quite a long time and it seems that these are frequently
>>>> overlooked.
>>>>
>>>> Should we not also have a setup in JIRA regarding the web and wiki pages?
>>>>
>>>> This helps us to stay aware of bugs and improvements thereof, and help us
>>>> to track contributors and patches. Having JIRA issues for this seems to
>>>> be
>>>> done also in a number of other Apache projects.
>>>>
>>>> Regards,
>>>>
>>>> Pierre Smits
>>>>
>>>> *ORRTIZ.COM <http://www.orrtiz.com>*
>>>> Services & Solutions for Cloud-
>>>> Based Manufacturing, Professional
>>>> Services and Retail & Trade
>>>> http://www.orrtiz.com
>>>>
>>>>
>>>

[Pierre Smits]

Thanks, Jacques.

Regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Wed, Oct 22, 2014 at 11:29 AM, Jacques Le Roux <
[hidden email]> wrote:

>
> Le 21/10/2014 22:53, Pierre Smits a écrit :
>
>> Jacques,
>>
>> The problem is indeed where to post the issues. There is no solution
>> available to do patches to pages in the website and improvement comments
>> in
>> the restricted spaces are all over the place.
>>
>
> Long ago, the community decided to go with comments. I don't see a need to
> change that. Not all comments in Confluence are important or even relevant.
>
>  And regarding the latter
>> aspect these comments can stay visible for quite some time due to busy
>> schedules (and other interests) of those capable to implement the changes.
>> Having those comments there for a longer time is not good regarding
>> branding and adoption.
>>
>
> If you are really interested/concerned simply add comments where you find
> relevant and I will do a complete review.
>
>
>> Having a JIRA setup for the website and restricted spaces will provide the
>> one place and will create insights about what is still open, what is fixed
>> and and when. Plus it helps identifying those committers that could become
>> committers.
>>
>
> If there are important things to tackle in Confluence which are neglected
> then of course the way is to create a Jira task type issue.
> I will add a Confluence component option for this (in Jira only of
> course!).
>
> Jacques
>
>
>> All in all not a bad suggestion and improvement.
>>
>> Regards,
>>
>> Pierre Smits
>>
>> *ORRTIZ.COM <http://www.orrtiz.com>*
>> Services & Solutions for Cloud-
>> Based Manufacturing, Professional
>> Services and Retail & Trade
>> http://www.orrtiz.com
>>
>> On Tue, Oct 21, 2014 at 5:01 PM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>  I believe, the problem is more about people not knowing where to post
>>> things, else of course Jira is a perfect fit.
>>> Though I (hopefully I'm not alone) normally monitor Confluence (including
>>> comments) but https://issues.apache.org/jira/browse/INFRA-8323
>>> Anyway I normally receive all changes by mail.
>>>
>>> Pierre, do you have something specific in mind about overlooked comments,
>>> I mean a list, etc.?
>>>
>>> Jacques
>>>
>>> Le 21/10/2014 14:43, Ron Wheeler a écrit :
>>>
>>>   It would be good to have a well organized and supported system for
>>>
>>>> tracking defects of all types including documentation.
>>>> The JIRA has a very very helpful features that would allow us to
>>>> identify
>>>> the importance of problems, any version dependencies, assigned person,
>>>> etc.
>>>>
>>>> Ron
>>>>
>>>> On 21/10/2014 7:45 AM, Pierre Smits wrote:
>>>>
>>>>  Hi all,
>>>>>
>>>>> Currently we only register issues related to the OFBiz code. But we
>>>>> also
>>>>> see a lot of comments in wiki pages regarding corrections. These
>>>>> comments
>>>>> can exists quite a long time and it seems that these are frequently
>>>>> overlooked.
>>>>>
>>>>> Should we not also have a setup in JIRA regarding the web and wiki
>>>>> pages?
>>>>>
>>>>> This helps us to stay aware of bugs and improvements thereof, and help
>>>>> us
>>>>> to track contributors and patches. Having JIRA issues for this seems to
>>>>> be
>>>>> done also in a number of other Apache projects.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Pierre Smits
>>>>>
>>>>> *ORRTIZ.COM <http://www.orrtiz.com>*
>>>>> Services & Solutions for Cloud-
>>>>> Based Manufacturing, Professional
>>>>> Services and Retail & Trade
>>>>> http://www.orrtiz.com
>>>>>
>>>>>
>>>>>
>>>>