Roy Fielding said once that participation in a project should be like
going to a party. Using JIRA makes it sound more like work than a party.
However, at a party, you can see when I'm heading to the beer keg or game
console or who I'm talking to, and maybe this thread is looking for
something li
Agreed. There is just too much to do and too little time. I pick and
chose what to work on based on how I feel like (do I want to copy
paste a kazillion license headers, or do I want to deep dive into the
compiler to fix a bug?) and I'd rather not have to "waste" time to
first enter a JIRA ticket f
On 1/10/14 6:17 PM, "Justin Mclean" wrote:
>Hi,
>
>> Hmm. That wouldn't be my preference. Do other projects do this?
>In general yes but each project is different and can do what they want
>basically.
The framework is still pre-alpha and I would find it very difficult to
develop a new framewor
Hi,
> Hmm. That wouldn't be my preference. Do other projects do this?
In general yes but each project is different and can do what they want
basically.
> JIRA is not my favorite tool. Regarding history, the commit logs should be
> sufficient.
For people not familiar with the code or who are
Hmm. That wouldn't be my preference. Do other projects do this? JIRA is
not my favorite tool. Regarding history, the commit logs should be
sufficient.
What kind of information are you really looking for? Was it not clear
that I've been working on the installer and ant_on_air for a while now?
Hi,
I've noticed that Alex and Peter tend to work on something for a while and then
the first we know about it is when it's checked in.
A possibly better process would be to raise each change as a new
feature/improvement in JIRA, that way there would be better visibility to
what's been worked
