Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of joachim.dreimann@wandisco.com
 designates 74.125.82.175 as permitted sender)
From: Joachim Dreimann <joachim.dreimann@wandisco.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_E3F5BDE6-6A45-412C-B7B4-28F65F008A0E"
Message-Id: <6E30A1AF-F64B-4462-A750-DA3CAB12B560@wandisco.com>
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
Subject: 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)
Date: Wed, 19 Sep 2012 14:23:13 +0100
References: 
 <CAGMZAuOvjo9C4jnk4ggf40d0XQBAqh8hC3jPqaxBaAxOJMvfFg@mail.gmail.com>
 <6D7037F7-4045-4A96-BD42-AF6B66501764@wandisco.com>
 <CAGMZAuMJgKfU--DYnLkC4QRQC92tokuf5Whye1r2eVVE+=n7Vg@mail.gmail.com>
 <5058DA29.3090405@wandisco.com>
 <CAGMZAuMh-rGTpaw_6+kT=nBQAnopwrcKAv-vDNn5CgvwNPpORg@mail.gmail.com>
To: bloodhound-dev@incubator.apache.org
In-Reply-To: 
 <CAGMZAuMh-rGTpaw_6+kT=nBQAnopwrcKAv-vDNn5CgvwNPpORg@mail.gmail.com>

--Apple-Mail=_E3F5BDE6-6A45-412C-B7B4-28F65F008A0E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

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.=20

Joe

On 18 Sep 2012, at 23:45, Olemis Lang <olemis@gmail.com> wrote:

> Well , I already added =C2=ABstarter=C2=BB 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 .
> ;)
>=20
> On 9/18/12, Branko =C4=8Cibej <brane@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.
>>=20
>> -- Brane
>>=20
>> 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 .
>>>=20
>>> Definitely workflow states are much more needed , so I think I =
prefer
>>> keyword + workflow approach too .
>>>=20
>>> On 9/18/12, Joachim Dreimann <joachim.dreimann@wandisco.com> wrote:
>>>> This overlaps with two conversations we've had recently on the =
mailing
>>>> list:
>>>>=20
>>>> 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.
>>>>=20
>>>> I prefer those two approaches personally.
>>>>=20
>>>> - Joe
>>>>=20
>>>> On 18 Sep 2012, at 18:14, Olemis Lang <olemis@gmail.com> wrote:
>>>>=20
>>>>> I've been reviewing All Tickets By Milestone [1]_ and maybe these
>>>>> tickets are also good targets just to start .
>>>>>=20
>>>>>=20
>>>>> #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
>>>>> --
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> and maybe this one (not scheduled for release 2 but definitely
>>>>> important
>>>>> ;)
>>>>>=20
>>>>> #162 	Convert version control user interface to Bootstrap 	=
ui design
>>>>> 	assigned 			enhancement 	major 		=
Sep 3, 2012
>>>>> --
>>>>>=20
>>>>>=20
>>>>> It's just a suggestion . What do you think ?
>>>>>=20
>>>>> Towards a more generic discussion I'd point out that maybe we =
should
>>>>> have a custom field like =C2=ABdifficulty=C2=BB highlighting prior =
expectations
>>>>> of the skills needed to complete a task / close a ticket . A query
>>>>> like difficulty=3Dlow|moderate could be used to find all such =
tickets
>>>>> ... and maybe even a link could be added in BloodhoundContribute =
as
>>>>> well ;)
>>>>>=20
>>>>> Of course , that should be setup starting from release 3 ... =
release 2
>>>>> is almost done ;)
>>>>>=20
>>>>> 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
>>>>> =C2=ABrecently=C2=BB ;)
>>>>>=20
>>>>> .. [1] All Tickets By Milestone - report 6
>>>>>      (https://issues.apache.org/bloodhound/report/6)
>>>>=20
>>>=20
>>=20
>>=20
>> --
>> Certified & Supported Apache Subversion Downloads:
>> http://www.wandisco.com/subversion/download
>>=20
>>=20
>=20
>=20
> --=20
> Regards,
>=20
> Olemis.
>=20
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>=20
> Featured article:


--Apple-Mail=_E3F5BDE6-6A45-412C-B7B4-28F65F008A0E--