Re: [flyspray] Re: Requesting help for 1.0
30 views
Skip to first unread message
Jouni Ahto
Feb 2, 2015, 8:48:32 AM2/2/15
to flys...@googlegroups.com
Now this is mostly another answer to point 2 made by galactic void and
already once answered by Jordan. Seems that I have some 1-3 month between
projects (unless something happens) and do not have anything urgent on my
todo list. And we are using Flyspray as a bug tracker in the company. So
getting 1.0 ready for release is something that interests me quite much.
And I have quite much free programming time available for the projects use
for a while. Unfortunately, my PHP skills are somewhat rusty.
I wouldn't like to have to bother myself by looking at the todo list and
trying to analyze which ones are really a must, which ones not. Just send
me a list and I'll go through it and fix anything I can. I know myself
already a few one, not even reported yet, mostly PostgreSQL related, which
is a lot of stricter in database queries having "GROUP BY", and one
missing feature, in a tasks subtasks and tasks preventing closing, column
"Assigned to" still read "Assignees TODO". Haven't got yet any idea how to
implement it.
The only new feature I'd like to see in 1.0, and can implement myself, is
related to effort tracking. Seeing "estimated effort" and "actual effort
done" should be split into two different group privileges. There are a lot
of new features I'd like to see later, like recursively going through
subtasks and counting the total effort needed, tracking how far we
actually are implementing something etc. And I am willing to provide a
patch for version 1.X or 2.0, but not for 1.0. As I see it, the main thing
is to just get 1.0 out of door.
By the way, 1.0 dev is already good enough so we went into production
30.1., just commented out or we are just not using a few not-yet-working
features.
On 07/15/2014 04:30 AM, Jordan Mendler wrote:
>
> 1. Is the plan to continue using adodb or use the PDO branch?
>
>
> The plan is to keep using what is in the main line. If someone wants to
volunteer to work on this and stabilize/support a different library I am
happy to switch over. But for me personally, I don't care enough to invest
my time making the change over other features that are more important to
me.
>
I wouldn't recommend switching unless someone has really a lot of free
time. ADOdb has the nice feature of being capable of reading a database
independent schema from xml-file, also comparing it to a perhaps already
existing database, and either creating a new one or making necessary
modifications to an existing one. No such feature in PDO. So that would
once again totally break both the setup and upgrade processes, which are
the messes I've been slowly trying to fix this year. In the hope that if I
can make it even possible, someone actually does it for a test version and
finds the remaining bugs. And hopefully, sends a patch...
>
> 2. There is a todo list for 1.0 in the Flyspray issue tracker. Is
this up to date? Are there other features wanted for 1.0?
>
>
> It is more or less up to date. We can include other features if someone
volunteers to implement them. From my perspective, I currently have 2
engineers working on Flyspray for the next couple of months so my two
priorities are (1) implementing the features we need for our organization
as part of 1.0 and (2) fixing show-stopping bugs to ensure that 1.0 is
stable and bug-free.
>
> Beyond that, it would be great to include additional features and
improvements, but given the lack of manpower I am not sure how likely that
is right now without additional people contributing.
>
>
> 3. Would there be any objections to composer for dependencies?
>
>
> I would put this out to a vote. I do not feel strongly one way or
another, so am game for whatever people prefer.
>
Seems that decision has already been made.
-- Jouni Ahto
already once answered by Jordan. Seems that I have some 1-3 month between
projects (unless something happens) and do not have anything urgent on my
todo list. And we are using Flyspray as a bug tracker in the company. So
getting 1.0 ready for release is something that interests me quite much.
And I have quite much free programming time available for the projects use
for a while. Unfortunately, my PHP skills are somewhat rusty.
I wouldn't like to have to bother myself by looking at the todo list and
trying to analyze which ones are really a must, which ones not. Just send
me a list and I'll go through it and fix anything I can. I know myself
already a few one, not even reported yet, mostly PostgreSQL related, which
is a lot of stricter in database queries having "GROUP BY", and one
missing feature, in a tasks subtasks and tasks preventing closing, column
"Assigned to" still read "Assignees TODO". Haven't got yet any idea how to
implement it.
The only new feature I'd like to see in 1.0, and can implement myself, is
related to effort tracking. Seeing "estimated effort" and "actual effort
done" should be split into two different group privileges. There are a lot
of new features I'd like to see later, like recursively going through
subtasks and counting the total effort needed, tracking how far we
actually are implementing something etc. And I am willing to provide a
patch for version 1.X or 2.0, but not for 1.0. As I see it, the main thing
is to just get 1.0 out of door.
By the way, 1.0 dev is already good enough so we went into production
30.1., just commented out or we are just not using a few not-yet-working
features.
On 07/15/2014 04:30 AM, Jordan Mendler wrote:
>
> 1. Is the plan to continue using adodb or use the PDO branch?
>
>
> The plan is to keep using what is in the main line. If someone wants to
volunteer to work on this and stabilize/support a different library I am
happy to switch over. But for me personally, I don't care enough to invest
my time making the change over other features that are more important to
me.
>
I wouldn't recommend switching unless someone has really a lot of free
time. ADOdb has the nice feature of being capable of reading a database
independent schema from xml-file, also comparing it to a perhaps already
existing database, and either creating a new one or making necessary
modifications to an existing one. No such feature in PDO. So that would
once again totally break both the setup and upgrade processes, which are
the messes I've been slowly trying to fix this year. In the hope that if I
can make it even possible, someone actually does it for a test version and
finds the remaining bugs. And hopefully, sends a patch...
>
> 2. There is a todo list for 1.0 in the Flyspray issue tracker. Is
this up to date? Are there other features wanted for 1.0?
>
>
> It is more or less up to date. We can include other features if someone
volunteers to implement them. From my perspective, I currently have 2
engineers working on Flyspray for the next couple of months so my two
priorities are (1) implementing the features we need for our organization
as part of 1.0 and (2) fixing show-stopping bugs to ensure that 1.0 is
stable and bug-free.
>
> Beyond that, it would be great to include additional features and
improvements, but given the lack of manpower I am not sure how likely that
is right now without additional people contributing.
>
>
> 3. Would there be any objections to composer for dependencies?
>
>
> I would put this out to a vote. I do not feel strongly one way or
another, so am game for whatever people prefer.
>
Seems that decision has already been made.
-- Jouni Ahto
Jordan Mendler
Feb 5, 2015, 10:25:13 PM2/5/15
to flys...@googlegroups.com
PHP is quite easy so you can brush up on it pretty quickly. If you will be making a lot of changes, I am happy to grant you commit access on github. Let me know!
________________________
Jordan Mendler
The Veloz Group
President & Chief Technology Officer
President & Chief Technology Officer
www.thevelozgroup.com
Reply all
Reply to author
Forward
0 new messages