You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Olemis Lang <ol...@gmail.com> on 2012/09/18 19:14:36 UTC
Proposal of pending tasks for beginners WAS: #187: Remove row count
and results pagination from Dashboard (Was: Re: Trying to get started on
Bloodhound development)
I've been reviewing All Tickets By Milestone [1]_ and maybe these
tickets are also good targets just to start .
#119 Implement theme extensions code dashboard new enhancement
major nobody Jun 28, 2012
--
#18 Change message for self registration plugins assigned
enhancement major nobody Aug 30, 2012
--
#95 Display of owner in dashboard views should depend on the
availability of the field dashboard new enhancement major
nobody Jun 29, 2012
--
#154 Installer fails when providing repository type without a path
and vice versa installer new defect major gjm Aug 6, 2012
--
#123 Check functionality of all screens with missing
Products/Versions/Milestones/Components dashboard new task major
nobody Jul 13, 2012
--
and maybe this one (not scheduled for release 2 but definitely important ;)
#162 Convert version control user interface to Bootstrap ui design
assigned enhancement major Sep 3, 2012
--
It's just a suggestion . What do you think ?
Towards a more generic discussion I'd point out that maybe we should
have a custom field like «difficulty» highlighting prior expectations
of the skills needed to complete a task / close a ticket . A query
like difficulty=low|moderate could be used to find all such tickets
... and maybe even a link could be added in BloodhoundContribute as
well ;)
Of course , that should be setup starting from release 3 ... release 2
is almost done ;)
PS: Many things can be learned by reviewing patches submitted to the
isssue tracker as well . Most of the tickets assigned to user olemis
will have some . Those scheduled for Release 2 have been baked
«recently» ;)
.. [1] All Tickets By Milestone - report 6
(https://issues.apache.org/bloodhound/report/6)
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Gary Martin <ga...@wandisco.com>.
On 09/21/2012 03:59 PM, Branko Čibej wrote:
> On 21.09.2012 16:29, Olemis Lang wrote:
>> On 9/21/12, Gary Martin <ga...@wandisco.com> wrote:
>>> Could do but I am not sure that we should even list the higher priority
>>> work there. Would it put potential contributors off by making them feel
>>> that they would have more pressure on them when they are just finding
>>> their feet in the project?
>>>
>> ok , leave it out ... ;)
>> what about order by milestone due date , if set ? Would a similar
>> argument still be valid ?
> Contributors are, by definition, volunteers. They'll typically pick
> tasks in this order: a) things they find interesting/useful, b) things
> their employers want, c) things the project roadmap suggests. There's no
> way to force (c) before (a), so I see no good reason to try.
>
> -- Brane
>
Yeah, I don't want to be limiting contributors to a specific milestone.
I could see encouragement of those who become long term contributors to
work more on the current milestone but what I think is more likely to
happen is that more tickets that interest such contributors will start
to go into the current milestone.
New contributors should certainly be free to look at all the work and,
hopefully, we can help them to assess whether their choice of
interesting ticket is likely to rely on some other piece of work being
completed first.
With this list, I just want to see a sample of tickets, no particular
order and I'll avoid the temptation to restrict priority. At least for
now anyway.
Cheers,
Gary
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Branko Čibej <br...@wandisco.com>.
On 21.09.2012 16:29, Olemis Lang wrote:
> On 9/21/12, Gary Martin <ga...@wandisco.com> wrote:
>> Could do but I am not sure that we should even list the higher priority
>> work there. Would it put potential contributors off by making them feel
>> that they would have more pressure on them when they are just finding
>> their feet in the project?
>>
> ok , leave it out ... ;)
> what about order by milestone due date , if set ? Would a similar
> argument still be valid ?
Contributors are, by definition, volunteers. They'll typically pick
tasks in this order: a) things they find interesting/useful, b) things
their employers want, c) things the project roadmap suggests. There's no
way to force (c) before (a), so I see no good reason to try.
-- Brane
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Olemis Lang <ol...@gmail.com>.
On 9/21/12, Gary Martin <ga...@wandisco.com> wrote:
> Could do but I am not sure that we should even list the higher priority
> work there. Would it put potential contributors off by making them feel
> that they would have more pressure on them when they are just finding
> their feet in the project?
>
ok , leave it out ... ;)
what about order by milestone due date , if set ? Would a similar
argument still be valid ?
> I also would prefer to not have the pagination - it is suffering from a
> similar problem to the pagination on the dashboard. Why would you want
> to show only 5 tickets at a time when you hit the query page view?
>
That's not something we can control afaics . It's not the widget what
you are embedding in there . You are using built-in TracQuery macro .
Notice that there's no Bootstrap styling in that table .
If we only had WidgetMacro installed in the issue tracker (/me hoping
this will happen after releasing 0.2.0 ;) then something like this
will make it look the way we want to
[[WidgetMacro(TicketQuery, max=5,
query='status=!closed&keywords=~starter&owner=nobody, max=5',
title=Tasks for beginners, _wo_altlinks=false)]]
... although in this case I'd include alt links so that people would
be able to subscribe to an RSS feed and be notified of new tasks for
beginners . That'd be nice to have in this case .
> Hmm, I have just thought of another alternative to dropping pagination
> if it affects this too. Perhaps it would be simpler to provide some kind
> of extension to the query language to limit the query to the first N
> tickets.
>
... if there's no such thing at the moment ... I don't recall
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Gary Martin <ga...@wandisco.com>.
Could do but I am not sure that we should even list the higher priority
work there. Would it put potential contributors off by making them feel
that they would have more pressure on them when they are just finding
their feet in the project?
I also would prefer to not have the pagination - it is suffering from a
similar problem to the pagination on the dashboard. Why would you want
to show only 5 tickets at a time when you hit the query page view?
Hmm, I have just thought of another alternative to dropping pagination
if it affects this too. Perhaps it would be simpler to provide some kind
of extension to the query language to limit the query to the first N
tickets.
Cheers,
Gary
On 09/21/2012 02:59 PM, Olemis Lang wrote:
> should we order results by priority ?
>
> On 9/21/12, Gary Martin <ga...@wandisco.com> wrote:
>> I've adjusted the query on
>> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing - I'm
>> happy to adjust it again if necessary. The two enhancements are:
>>
>> * specify that owner should be nobody
>> o this appears to be the simplest and most reliable way to make
>> sure that the set is only unclaimed tickets although it does
>> require that we don't assign to a blank owner
>> * change count=5 to max=5
>> o the count argument appears to be for something else (although I
>> am not convinced that functionality works)
>>
>>
>> This is implemented through the following change:
>>
>> -[[TicketQuery(table, ?status=!closed&keywords=~starter, count=5)]]
>> +[[TicketQuery(table, ?status=!closed&keywords=~starter&owner=nobody,
>> max=5)]]
>>
>> I would try to offer the result with no further judgement but I don't
>> think the pagination is quite what we are after here.
>>
>> Cheers,
>> Gary
>>
>>
>> On 09/19/2012 02:23 PM, Joachim Dreimann wrote:
>>> I went ahead and tagged the #119, #18, #95, #154 and #123 as starter
>>> tickets. I've also added a table dynamically displaying 5 starter tickets
>>> to the top of the BloodhoundContributing page:
>>> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>>>
>>> Hope that helps as a starting point. Happy for others to extend it. Gary
>>> for example suggested off-list to me that tickets that are assigned to
>>> someone other than 'nobody' or accepted should be excluded, certainly a
>>> valid suggestion.
>>>
>>> Joe
>>>
>>> On 18 Sep 2012, at 23:45, Olemis Lang <ol...@gmail.com> wrote:
>>>
>>>> Well , I already added «starter» keyword in #203 ... feel free to
>>>> change it if appropriate . In the end any word is fine to me , as long
>>>> as its use becomes well-known and consistent across all the project .
>>>> ;)
>>>>
>>>> On 9/18/12, Branko Čibej <br...@wandisco.com> wrote:
>>>>> Subversion uses a keyword ("bitesize") to mark small and/or simple
>>>>> tasks
>>>>> in the issue tracker. Sadly, that issue tracker doesn't allow workflow
>>>>> customization.
>>>>>
>>>>> -- Brane
>>>>>
>>>>> On 18.09.2012 22:26, Olemis Lang wrote:
>>>>>> oh !
>>>>>> ok . I recall we also had another previous conversation about this too
>>>>>> , that's why I suggested doing so .
>>>>>>
>>>>>> Definitely workflow states are much more needed , so I think I prefer
>>>>>> keyword + workflow approach too .
>>>>>>
>>>>>> On 9/18/12, Joachim Dreimann <jo...@wandisco.com> wrote:
>>>>>>> This overlaps with two conversations we've had recently on the
>>>>>>> mailing
>>>>>>> list:
>>>>>>>
>>>>>>> 1. Adding an appropriate tag to 'starter' tickets
>>>>>>> 2. Providing appropriate ticket states, like 'awaiting review / to be
>>>>>>> reviewed' rather than 'open' for the tickets you refer to in your PS.
>>>>>>>
>>>>>>> I prefer those two approaches personally.
>>>>>>>
>>>>>>> - Joe
>>>>>>>
>>>>>>> On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
>>>>>>>
>>>>>>>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>>>>>>>> tickets are also good targets just to start .
>>>>>>>>
>>>>>>>>
>>>>>>>> #119 Implement theme extensions code dashboard new enhancement
>>>>>>>> major nobody Jun 28, 2012
>>>>>>>> --
>>>>>>>> #18 Change message for self registration plugins assigned
>>>>>>>> enhancement major nobody Aug 30, 2012
>>>>>>>> --
>>>>>>>> #95 Display of owner in dashboard views should depend on the
>>>>>>>> availability of the field dashboard new enhancement major
>>>>>>>> nobody Jun 29, 2012
>>>>>>>> --
>>>>>>>> #154 Installer fails when providing repository type without a path
>>>>>>>> and vice versa installer new defect major gjm Aug 6, 2012
>>>>>>>> --
>>>>>>>> #123 Check functionality of all screens with missing
>>>>>>>> Products/Versions/Milestones/Components dashboard new task
>>>>>>>> major
>>>>>>>> nobody Jul 13, 2012
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> and maybe this one (not scheduled for release 2 but definitely
>>>>>>>> important
>>>>>>>> ;)
>>>>>>>>
>>>>>>>> #162 Convert version control user interface to Bootstrap ui design
>>>>>>>> assigned enhancement major Sep 3, 2012
>>>>>>>> --
>>>>>>>>
>>>>>>>>
>>>>>>>> It's just a suggestion . What do you think ?
>>>>>>>>
>>>>>>>> Towards a more generic discussion I'd point out that maybe we should
>>>>>>>> have a custom field like «difficulty» highlighting prior
>>>>>>>> expectations
>>>>>>>> of the skills needed to complete a task / close a ticket . A query
>>>>>>>> like difficulty=low|moderate could be used to find all such tickets
>>>>>>>> ... and maybe even a link could be added in BloodhoundContribute as
>>>>>>>> well ;)
>>>>>>>>
>>>>>>>> Of course , that should be setup starting from release 3 ... release
>>>>>>>> 2
>>>>>>>> is almost done ;)
>>>>>>>>
>>>>>>>> PS: Many things can be learned by reviewing patches submitted to the
>>>>>>>> isssue tracker as well . Most of the tickets assigned to user olemis
>>>>>>>> will have some . Those scheduled for Release 2 have been baked
>>>>>>>> «recently» ;)
>>>>>>>>
>>>>>>>> .. [1] All Tickets By Milestone - report 6
>>>>>>>> (https://issues.apache.org/bloodhound/report/6)
>>>>> --
>>>>> Certified & Supported Apache Subversion Downloads:
>>>>> http://www.wandisco.com/subversion/download
>>>>>
>>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Olemis.
>>>>
>>>> Blog ES: http://simelo-es.blogspot.com/
>>>> Blog EN: http://simelo-en.blogspot.com/
>>>>
>>>> Featured article:
>>
>
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Olemis Lang <ol...@gmail.com>.
should we order results by priority ?
On 9/21/12, Gary Martin <ga...@wandisco.com> wrote:
> I've adjusted the query on
> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing - I'm
> happy to adjust it again if necessary. The two enhancements are:
>
> * specify that owner should be nobody
> o this appears to be the simplest and most reliable way to make
> sure that the set is only unclaimed tickets although it does
> require that we don't assign to a blank owner
> * change count=5 to max=5
> o the count argument appears to be for something else (although I
> am not convinced that functionality works)
>
>
> This is implemented through the following change:
>
> -[[TicketQuery(table, ?status=!closed&keywords=~starter, count=5)]]
> +[[TicketQuery(table, ?status=!closed&keywords=~starter&owner=nobody,
> max=5)]]
>
> I would try to offer the result with no further judgement but I don't
> think the pagination is quite what we are after here.
>
> Cheers,
> Gary
>
>
> On 09/19/2012 02:23 PM, Joachim Dreimann wrote:
>> I went ahead and tagged the #119, #18, #95, #154 and #123 as starter
>> tickets. I've also added a table dynamically displaying 5 starter tickets
>> to the top of the BloodhoundContributing page:
>> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>>
>> Hope that helps as a starting point. Happy for others to extend it. Gary
>> for example suggested off-list to me that tickets that are assigned to
>> someone other than 'nobody' or accepted should be excluded, certainly a
>> valid suggestion.
>>
>> Joe
>>
>> On 18 Sep 2012, at 23:45, Olemis Lang <ol...@gmail.com> wrote:
>>
>>> Well , I already added «starter» keyword in #203 ... feel free to
>>> change it if appropriate . In the end any word is fine to me , as long
>>> as its use becomes well-known and consistent across all the project .
>>> ;)
>>>
>>> On 9/18/12, Branko Čibej <br...@wandisco.com> wrote:
>>>> Subversion uses a keyword ("bitesize") to mark small and/or simple
>>>> tasks
>>>> in the issue tracker. Sadly, that issue tracker doesn't allow workflow
>>>> customization.
>>>>
>>>> -- Brane
>>>>
>>>> On 18.09.2012 22:26, Olemis Lang wrote:
>>>>> oh !
>>>>> ok . I recall we also had another previous conversation about this too
>>>>> , that's why I suggested doing so .
>>>>>
>>>>> Definitely workflow states are much more needed , so I think I prefer
>>>>> keyword + workflow approach too .
>>>>>
>>>>> On 9/18/12, Joachim Dreimann <jo...@wandisco.com> wrote:
>>>>>> This overlaps with two conversations we've had recently on the
>>>>>> mailing
>>>>>> list:
>>>>>>
>>>>>> 1. Adding an appropriate tag to 'starter' tickets
>>>>>> 2. Providing appropriate ticket states, like 'awaiting review / to be
>>>>>> reviewed' rather than 'open' for the tickets you refer to in your PS.
>>>>>>
>>>>>> I prefer those two approaches personally.
>>>>>>
>>>>>> - Joe
>>>>>>
>>>>>> On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
>>>>>>
>>>>>>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>>>>>>> tickets are also good targets just to start .
>>>>>>>
>>>>>>>
>>>>>>> #119 Implement theme extensions code dashboard new enhancement
>>>>>>> major nobody Jun 28, 2012
>>>>>>> --
>>>>>>> #18 Change message for self registration plugins assigned
>>>>>>> enhancement major nobody Aug 30, 2012
>>>>>>> --
>>>>>>> #95 Display of owner in dashboard views should depend on the
>>>>>>> availability of the field dashboard new enhancement major
>>>>>>> nobody Jun 29, 2012
>>>>>>> --
>>>>>>> #154 Installer fails when providing repository type without a path
>>>>>>> and vice versa installer new defect major gjm Aug 6, 2012
>>>>>>> --
>>>>>>> #123 Check functionality of all screens with missing
>>>>>>> Products/Versions/Milestones/Components dashboard new task
>>>>>>> major
>>>>>>> nobody Jul 13, 2012
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> and maybe this one (not scheduled for release 2 but definitely
>>>>>>> important
>>>>>>> ;)
>>>>>>>
>>>>>>> #162 Convert version control user interface to Bootstrap ui design
>>>>>>> assigned enhancement major Sep 3, 2012
>>>>>>> --
>>>>>>>
>>>>>>>
>>>>>>> It's just a suggestion . What do you think ?
>>>>>>>
>>>>>>> Towards a more generic discussion I'd point out that maybe we should
>>>>>>> have a custom field like «difficulty» highlighting prior
>>>>>>> expectations
>>>>>>> of the skills needed to complete a task / close a ticket . A query
>>>>>>> like difficulty=low|moderate could be used to find all such tickets
>>>>>>> ... and maybe even a link could be added in BloodhoundContribute as
>>>>>>> well ;)
>>>>>>>
>>>>>>> Of course , that should be setup starting from release 3 ... release
>>>>>>> 2
>>>>>>> is almost done ;)
>>>>>>>
>>>>>>> PS: Many things can be learned by reviewing patches submitted to the
>>>>>>> isssue tracker as well . Most of the tickets assigned to user olemis
>>>>>>> will have some . Those scheduled for Release 2 have been baked
>>>>>>> «recently» ;)
>>>>>>>
>>>>>>> .. [1] All Tickets By Milestone - report 6
>>>>>>> (https://issues.apache.org/bloodhound/report/6)
>>>>
>>>> --
>>>> Certified & Supported Apache Subversion Downloads:
>>>> http://www.wandisco.com/subversion/download
>>>>
>>>>
>>>
>>> --
>>> Regards,
>>>
>>> Olemis.
>>>
>>> Blog ES: http://simelo-es.blogspot.com/
>>> Blog EN: http://simelo-en.blogspot.com/
>>>
>>> Featured article:
>>
>
>
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Gary Martin <ga...@wandisco.com>.
I've adjusted the query on
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing - I'm
happy to adjust it again if necessary. The two enhancements are:
* specify that owner should be nobody
o this appears to be the simplest and most reliable way to make
sure that the set is only unclaimed tickets although it does
require that we don't assign to a blank owner
* change count=5 to max=5
o the count argument appears to be for something else (although I
am not convinced that functionality works)
This is implemented through the following change:
-[[TicketQuery(table, ?status=!closed&keywords=~starter, count=5)]]
+[[TicketQuery(table, ?status=!closed&keywords=~starter&owner=nobody, max=5)]]
I would try to offer the result with no further judgement but I don't
think the pagination is quite what we are after here.
Cheers,
Gary
On 09/19/2012 02:23 PM, Joachim Dreimann wrote:
> I went ahead and tagged the #119, #18, #95, #154 and #123 as starter tickets. I've also added a table dynamically displaying 5 starter tickets to the top of the BloodhoundContributing page:
> https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
>
> Hope that helps as a starting point. Happy for others to extend it. Gary for example suggested off-list to me that tickets that are assigned to someone other than 'nobody' or accepted should be excluded, certainly a valid suggestion.
>
> Joe
>
> On 18 Sep 2012, at 23:45, Olemis Lang <ol...@gmail.com> wrote:
>
>> Well , I already added «starter» keyword in #203 ... feel free to
>> change it if appropriate . In the end any word is fine to me , as long
>> as its use becomes well-known and consistent across all the project .
>> ;)
>>
>> On 9/18/12, Branko Čibej <br...@wandisco.com> wrote:
>>> Subversion uses a keyword ("bitesize") to mark small and/or simple tasks
>>> in the issue tracker. Sadly, that issue tracker doesn't allow workflow
>>> customization.
>>>
>>> -- Brane
>>>
>>> On 18.09.2012 22:26, Olemis Lang wrote:
>>>> oh !
>>>> ok . I recall we also had another previous conversation about this too
>>>> , that's why I suggested doing so .
>>>>
>>>> Definitely workflow states are much more needed , so I think I prefer
>>>> keyword + workflow approach too .
>>>>
>>>> On 9/18/12, Joachim Dreimann <jo...@wandisco.com> wrote:
>>>>> This overlaps with two conversations we've had recently on the mailing
>>>>> list:
>>>>>
>>>>> 1. Adding an appropriate tag to 'starter' tickets
>>>>> 2. Providing appropriate ticket states, like 'awaiting review / to be
>>>>> reviewed' rather than 'open' for the tickets you refer to in your PS.
>>>>>
>>>>> I prefer those two approaches personally.
>>>>>
>>>>> - Joe
>>>>>
>>>>> On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
>>>>>
>>>>>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>>>>>> tickets are also good targets just to start .
>>>>>>
>>>>>>
>>>>>> #119 Implement theme extensions code dashboard new enhancement
>>>>>> major nobody Jun 28, 2012
>>>>>> --
>>>>>> #18 Change message for self registration plugins assigned
>>>>>> enhancement major nobody Aug 30, 2012
>>>>>> --
>>>>>> #95 Display of owner in dashboard views should depend on the
>>>>>> availability of the field dashboard new enhancement major
>>>>>> nobody Jun 29, 2012
>>>>>> --
>>>>>> #154 Installer fails when providing repository type without a path
>>>>>> and vice versa installer new defect major gjm Aug 6, 2012
>>>>>> --
>>>>>> #123 Check functionality of all screens with missing
>>>>>> Products/Versions/Milestones/Components dashboard new task major
>>>>>> nobody Jul 13, 2012
>>>>>> --
>>>>>>
>>>>>>
>>>>>>
>>>>>> and maybe this one (not scheduled for release 2 but definitely
>>>>>> important
>>>>>> ;)
>>>>>>
>>>>>> #162 Convert version control user interface to Bootstrap ui design
>>>>>> assigned enhancement major Sep 3, 2012
>>>>>> --
>>>>>>
>>>>>>
>>>>>> It's just a suggestion . What do you think ?
>>>>>>
>>>>>> Towards a more generic discussion I'd point out that maybe we should
>>>>>> have a custom field like «difficulty» highlighting prior expectations
>>>>>> of the skills needed to complete a task / close a ticket . A query
>>>>>> like difficulty=low|moderate could be used to find all such tickets
>>>>>> ... and maybe even a link could be added in BloodhoundContribute as
>>>>>> well ;)
>>>>>>
>>>>>> Of course , that should be setup starting from release 3 ... release 2
>>>>>> is almost done ;)
>>>>>>
>>>>>> PS: Many things can be learned by reviewing patches submitted to the
>>>>>> isssue tracker as well . Most of the tickets assigned to user olemis
>>>>>> will have some . Those scheduled for Release 2 have been baked
>>>>>> «recently» ;)
>>>>>>
>>>>>> .. [1] All Tickets By Milestone - report 6
>>>>>> (https://issues.apache.org/bloodhound/report/6)
>>>
>>> --
>>> Certified & Supported Apache Subversion Downloads:
>>> http://www.wandisco.com/subversion/download
>>>
>>>
>>
>> --
>> Regards,
>>
>> Olemis.
>>
>> Blog ES: http://simelo-es.blogspot.com/
>> Blog EN: http://simelo-en.blogspot.com/
>>
>> Featured article:
>
Re: Proposal of pending tasks for beginners WAS: #187: Remove row count and results pagination from Dashboard (Was: Re: Trying to get started on Bloodhound development)
Posted by Joachim Dreimann <jo...@wandisco.com>.
I went ahead and tagged the #119, #18, #95, #154 and #123 as starter tickets. I've also added a table dynamically displaying 5 starter tickets to the top of the BloodhoundContributing page:
https://issues.apache.org/bloodhound/wiki/BloodhoundContributing
Hope that helps as a starting point. Happy for others to extend it. Gary for example suggested off-list to me that tickets that are assigned to someone other than 'nobody' or accepted should be excluded, certainly a valid suggestion.
Joe
On 18 Sep 2012, at 23:45, Olemis Lang <ol...@gmail.com> wrote:
> Well , I already added «starter» keyword in #203 ... feel free to
> change it if appropriate . In the end any word is fine to me , as long
> as its use becomes well-known and consistent across all the project .
> ;)
>
> On 9/18/12, Branko Čibej <br...@wandisco.com> wrote:
>> Subversion uses a keyword ("bitesize") to mark small and/or simple tasks
>> in the issue tracker. Sadly, that issue tracker doesn't allow workflow
>> customization.
>>
>> -- Brane
>>
>> On 18.09.2012 22:26, Olemis Lang wrote:
>>> oh !
>>> ok . I recall we also had another previous conversation about this too
>>> , that's why I suggested doing so .
>>>
>>> Definitely workflow states are much more needed , so I think I prefer
>>> keyword + workflow approach too .
>>>
>>> On 9/18/12, Joachim Dreimann <jo...@wandisco.com> wrote:
>>>> This overlaps with two conversations we've had recently on the mailing
>>>> list:
>>>>
>>>> 1. Adding an appropriate tag to 'starter' tickets
>>>> 2. Providing appropriate ticket states, like 'awaiting review / to be
>>>> reviewed' rather than 'open' for the tickets you refer to in your PS.
>>>>
>>>> I prefer those two approaches personally.
>>>>
>>>> - Joe
>>>>
>>>> On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
>>>>
>>>>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>>>>> tickets are also good targets just to start .
>>>>>
>>>>>
>>>>> #119 Implement theme extensions code dashboard new enhancement
>>>>> major nobody Jun 28, 2012
>>>>> --
>>>>> #18 Change message for self registration plugins assigned
>>>>> enhancement major nobody Aug 30, 2012
>>>>> --
>>>>> #95 Display of owner in dashboard views should depend on the
>>>>> availability of the field dashboard new enhancement major
>>>>> nobody Jun 29, 2012
>>>>> --
>>>>> #154 Installer fails when providing repository type without a path
>>>>> and vice versa installer new defect major gjm Aug 6, 2012
>>>>> --
>>>>> #123 Check functionality of all screens with missing
>>>>> Products/Versions/Milestones/Components dashboard new task major
>>>>> nobody Jul 13, 2012
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>> and maybe this one (not scheduled for release 2 but definitely
>>>>> important
>>>>> ;)
>>>>>
>>>>> #162 Convert version control user interface to Bootstrap ui design
>>>>> assigned enhancement major Sep 3, 2012
>>>>> --
>>>>>
>>>>>
>>>>> It's just a suggestion . What do you think ?
>>>>>
>>>>> Towards a more generic discussion I'd point out that maybe we should
>>>>> have a custom field like «difficulty» highlighting prior expectations
>>>>> of the skills needed to complete a task / close a ticket . A query
>>>>> like difficulty=low|moderate could be used to find all such tickets
>>>>> ... and maybe even a link could be added in BloodhoundContribute as
>>>>> well ;)
>>>>>
>>>>> Of course , that should be setup starting from release 3 ... release 2
>>>>> is almost done ;)
>>>>>
>>>>> PS: Many things can be learned by reviewing patches submitted to the
>>>>> isssue tracker as well . Most of the tickets assigned to user olemis
>>>>> will have some . Those scheduled for Release 2 have been baked
>>>>> «recently» ;)
>>>>>
>>>>> .. [1] All Tickets By Milestone - report 6
>>>>> (https://issues.apache.org/bloodhound/report/6)
>>>>
>>>
>>
>>
>> --
>> Certified & Supported Apache Subversion Downloads:
>> http://www.wandisco.com/subversion/download
>>
>>
>
>
> --
> Regards,
>
> Olemis.
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Olemis Lang <ol...@gmail.com>.
Well , I already added «starter» keyword in #203 ... feel free to
change it if appropriate . In the end any word is fine to me , as long
as its use becomes well-known and consistent across all the project .
;)
On 9/18/12, Branko Čibej <br...@wandisco.com> wrote:
> Subversion uses a keyword ("bitesize") to mark small and/or simple tasks
> in the issue tracker. Sadly, that issue tracker doesn't allow workflow
> customization.
>
> -- Brane
>
> On 18.09.2012 22:26, Olemis Lang wrote:
>> oh !
>> ok . I recall we also had another previous conversation about this too
>> , that's why I suggested doing so .
>>
>> Definitely workflow states are much more needed , so I think I prefer
>> keyword + workflow approach too .
>>
>> On 9/18/12, Joachim Dreimann <jo...@wandisco.com> wrote:
>>> This overlaps with two conversations we've had recently on the mailing
>>> list:
>>>
>>> 1. Adding an appropriate tag to 'starter' tickets
>>> 2. Providing appropriate ticket states, like 'awaiting review / to be
>>> reviewed' rather than 'open' for the tickets you refer to in your PS.
>>>
>>> I prefer those two approaches personally.
>>>
>>> - Joe
>>>
>>> On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
>>>
>>>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>>>> tickets are also good targets just to start .
>>>>
>>>>
>>>> #119 Implement theme extensions code dashboard new enhancement
>>>> major nobody Jun 28, 2012
>>>> --
>>>> #18 Change message for self registration plugins assigned
>>>> enhancement major nobody Aug 30, 2012
>>>> --
>>>> #95 Display of owner in dashboard views should depend on the
>>>> availability of the field dashboard new enhancement major
>>>> nobody Jun 29, 2012
>>>> --
>>>> #154 Installer fails when providing repository type without a path
>>>> and vice versa installer new defect major gjm Aug 6, 2012
>>>> --
>>>> #123 Check functionality of all screens with missing
>>>> Products/Versions/Milestones/Components dashboard new task major
>>>> nobody Jul 13, 2012
>>>> --
>>>>
>>>>
>>>>
>>>> and maybe this one (not scheduled for release 2 but definitely
>>>> important
>>>> ;)
>>>>
>>>> #162 Convert version control user interface to Bootstrap ui design
>>>> assigned enhancement major Sep 3, 2012
>>>> --
>>>>
>>>>
>>>> It's just a suggestion . What do you think ?
>>>>
>>>> Towards a more generic discussion I'd point out that maybe we should
>>>> have a custom field like «difficulty» highlighting prior expectations
>>>> of the skills needed to complete a task / close a ticket . A query
>>>> like difficulty=low|moderate could be used to find all such tickets
>>>> ... and maybe even a link could be added in BloodhoundContribute as
>>>> well ;)
>>>>
>>>> Of course , that should be setup starting from release 3 ... release 2
>>>> is almost done ;)
>>>>
>>>> PS: Many things can be learned by reviewing patches submitted to the
>>>> isssue tracker as well . Most of the tickets assigned to user olemis
>>>> will have some . Those scheduled for Release 2 have been baked
>>>> «recently» ;)
>>>>
>>>> .. [1] All Tickets By Milestone - report 6
>>>> (https://issues.apache.org/bloodhound/report/6)
>>>
>>
>
>
> --
> Certified & Supported Apache Subversion Downloads:
> http://www.wandisco.com/subversion/download
>
>
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Branko Čibej <br...@wandisco.com>.
Subversion uses a keyword ("bitesize") to mark small and/or simple tasks
in the issue tracker. Sadly, that issue tracker doesn't allow workflow
customization.
-- Brane
On 18.09.2012 22:26, Olemis Lang wrote:
> oh !
> ok . I recall we also had another previous conversation about this too
> , that's why I suggested doing so .
>
> Definitely workflow states are much more needed , so I think I prefer
> keyword + workflow approach too .
>
> On 9/18/12, Joachim Dreimann <jo...@wandisco.com> wrote:
>> This overlaps with two conversations we've had recently on the mailing
>> list:
>>
>> 1. Adding an appropriate tag to 'starter' tickets
>> 2. Providing appropriate ticket states, like 'awaiting review / to be
>> reviewed' rather than 'open' for the tickets you refer to in your PS.
>>
>> I prefer those two approaches personally.
>>
>> - Joe
>>
>> On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
>>
>>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>>> tickets are also good targets just to start .
>>>
>>>
>>> #119 Implement theme extensions code dashboard new enhancement
>>> major nobody Jun 28, 2012
>>> --
>>> #18 Change message for self registration plugins assigned
>>> enhancement major nobody Aug 30, 2012
>>> --
>>> #95 Display of owner in dashboard views should depend on the
>>> availability of the field dashboard new enhancement major
>>> nobody Jun 29, 2012
>>> --
>>> #154 Installer fails when providing repository type without a path
>>> and vice versa installer new defect major gjm Aug 6, 2012
>>> --
>>> #123 Check functionality of all screens with missing
>>> Products/Versions/Milestones/Components dashboard new task major
>>> nobody Jul 13, 2012
>>> --
>>>
>>>
>>>
>>> and maybe this one (not scheduled for release 2 but definitely important
>>> ;)
>>>
>>> #162 Convert version control user interface to Bootstrap ui design
>>> assigned enhancement major Sep 3, 2012
>>> --
>>>
>>>
>>> It's just a suggestion . What do you think ?
>>>
>>> Towards a more generic discussion I'd point out that maybe we should
>>> have a custom field like «difficulty» highlighting prior expectations
>>> of the skills needed to complete a task / close a ticket . A query
>>> like difficulty=low|moderate could be used to find all such tickets
>>> ... and maybe even a link could be added in BloodhoundContribute as
>>> well ;)
>>>
>>> Of course , that should be setup starting from release 3 ... release 2
>>> is almost done ;)
>>>
>>> PS: Many things can be learned by reviewing patches submitted to the
>>> isssue tracker as well . Most of the tickets assigned to user olemis
>>> will have some . Those scheduled for Release 2 have been baked
>>> «recently» ;)
>>>
>>> .. [1] All Tickets By Milestone - report 6
>>> (https://issues.apache.org/bloodhound/report/6)
>>
>
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Re: Proposal of pending tasks for beginners WAS: #187: Remove row
count and results pagination from Dashboard (Was: Re: Trying to get started
on Bloodhound development)
Posted by Olemis Lang <ol...@gmail.com>.
oh !
ok . I recall we also had another previous conversation about this too
, that's why I suggested doing so .
Definitely workflow states are much more needed , so I think I prefer
keyword + workflow approach too .
On 9/18/12, Joachim Dreimann <jo...@wandisco.com> wrote:
> This overlaps with two conversations we've had recently on the mailing
> list:
>
> 1. Adding an appropriate tag to 'starter' tickets
> 2. Providing appropriate ticket states, like 'awaiting review / to be
> reviewed' rather than 'open' for the tickets you refer to in your PS.
>
> I prefer those two approaches personally.
>
> - Joe
>
> On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
>
>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>> tickets are also good targets just to start .
>>
>>
>> #119 Implement theme extensions code dashboard new enhancement
>> major nobody Jun 28, 2012
>> --
>> #18 Change message for self registration plugins assigned
>> enhancement major nobody Aug 30, 2012
>> --
>> #95 Display of owner in dashboard views should depend on the
>> availability of the field dashboard new enhancement major
>> nobody Jun 29, 2012
>> --
>> #154 Installer fails when providing repository type without a path
>> and vice versa installer new defect major gjm Aug 6, 2012
>> --
>> #123 Check functionality of all screens with missing
>> Products/Versions/Milestones/Components dashboard new task major
>> nobody Jul 13, 2012
>> --
>>
>>
>>
>> and maybe this one (not scheduled for release 2 but definitely important
>> ;)
>>
>> #162 Convert version control user interface to Bootstrap ui design
>> assigned enhancement major Sep 3, 2012
>> --
>>
>>
>> It's just a suggestion . What do you think ?
>>
>> Towards a more generic discussion I'd point out that maybe we should
>> have a custom field like «difficulty» highlighting prior expectations
>> of the skills needed to complete a task / close a ticket . A query
>> like difficulty=low|moderate could be used to find all such tickets
>> ... and maybe even a link could be added in BloodhoundContribute as
>> well ;)
>>
>> Of course , that should be setup starting from release 3 ... release 2
>> is almost done ;)
>>
>> PS: Many things can be learned by reviewing patches submitted to the
>> isssue tracker as well . Most of the tickets assigned to user olemis
>> will have some . Those scheduled for Release 2 have been baked
>> «recently» ;)
>>
>> .. [1] All Tickets By Milestone - report 6
>> (https://issues.apache.org/bloodhound/report/6)
>
>
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Proposal of pending tasks for beginners WAS: #187: Remove row count and results pagination from Dashboard (Was: Re: Trying to get started on Bloodhound development)
Posted by Joachim Dreimann <jo...@wandisco.com>.
This overlaps with two conversations we've had recently on the mailing list:
1. Adding an appropriate tag to 'starter' tickets
2. Providing appropriate ticket states, like 'awaiting review / to be reviewed' rather than 'open' for the tickets you refer to in your PS.
I prefer those two approaches personally.
- Joe
On 18 Sep 2012, at 18:14, Olemis Lang <ol...@gmail.com> wrote:
> I've been reviewing All Tickets By Milestone [1]_ and maybe these
> tickets are also good targets just to start .
>
>
> #119 Implement theme extensions code dashboard new enhancement
> major nobody Jun 28, 2012
> --
> #18 Change message for self registration plugins assigned
> enhancement major nobody Aug 30, 2012
> --
> #95 Display of owner in dashboard views should depend on the
> availability of the field dashboard new enhancement major
> nobody Jun 29, 2012
> --
> #154 Installer fails when providing repository type without a path
> and vice versa installer new defect major gjm Aug 6, 2012
> --
> #123 Check functionality of all screens with missing
> Products/Versions/Milestones/Components dashboard new task major
> nobody Jul 13, 2012
> --
>
>
>
> and maybe this one (not scheduled for release 2 but definitely important ;)
>
> #162 Convert version control user interface to Bootstrap ui design
> assigned enhancement major Sep 3, 2012
> --
>
>
> It's just a suggestion . What do you think ?
>
> Towards a more generic discussion I'd point out that maybe we should
> have a custom field like «difficulty» highlighting prior expectations
> of the skills needed to complete a task / close a ticket . A query
> like difficulty=low|moderate could be used to find all such tickets
> ... and maybe even a link could be added in BloodhoundContribute as
> well ;)
>
> Of course , that should be setup starting from release 3 ... release 2
> is almost done ;)
>
> PS: Many things can be learned by reviewing patches submitted to the
> isssue tracker as well . Most of the tickets assigned to user olemis
> will have some . Those scheduled for Release 2 have been baked
> «recently» ;)
>
> .. [1] All Tickets By Milestone - report 6
> (https://issues.apache.org/bloodhound/report/6)