Issues on Github

Now, that we’re in touch with Phalcon Team members, and knowing that they're a small crew of two/three developers, I'd discuss the roadmap from remaining issues open in Github.

I’ve been working a bit on classify current issues based on labels:

  • NFR (New feature requests): 192
  • Bugs (Low/Medium/High): 67 + 6 = 74
  • Need information/feedback: 45
  • Unclassified: 184

and have come up with conclusions below:

  • A greater number of issues represent requests for framework improvements, new features or changes in the actual behavior. Likewise, most of them have no answers from any member of Phalcon Team.

  • The second slice of cake, something I called "unclassified". Nobody has taken the time to see if it is a new request or a bug. A fairly simple task that does not require advanced technical knowledge.

  • 74 bugs opened many of them quite old (more than 1 year). Any idea when they will be addressed?

To that end, I strongly want to know the opinion of phalcon team members regarding this. As there is no one dedicated to the framework, I hope it does not take too long to respond.



84.5k

Yeah, there are many new feature requests, in the past, people weren't able to implement the features they needed because of the lack of experience and knowledge working with C extensions, Zephir is changing the picture.

Our resources are limited and as I mentioned before, we are not fully dedicated to this project, we work in our spare time, we tried to move forward Zephir and Phalcon 2 as a solution to this problem. The truth is that we are an open-source project and we also require the community to help fix problems, as it's something that benefits everyone.

Thanks for answering, I'm not blame you all, maybe the community is not being very collaborative with you?

however, you know only know how the framework works, only you know what can affect or improve a functionality. Your feedback is very important, maybe that will help put things going?

btw, I see funding is going well, but probably far from the goal, maybe the link should be more visible?

Yeah, there are many new feature requests, in the past, people weren't able to implement the features they needed because of the lack of experience and knowledge working with C extensions, Zephir is changing the picture.

Our resources are limited and as I mentioned before, we are not fully dedicated to this project, we work in our spare time, we tried to move forward Zephir and Phalcon 2 as a solution to this problem. The truth is that we are an open-source project and we also require the community to help fix problems, as it's something that benefits everyone.

edited Nov '14

I'm fairly new to Phalcon still, but I'd like to contribute to this discussion.

@walterwhitep - I see your concerns. However, as @Phalcon said, it has been difficult in the past for people to contribute. I'm a full time PHP developer, a student, and a young man who enjoys his social life when I have time for it. I want to contribute to Phalcon, but I simply don't have to time to learn C and I can better spend my time by focusing on the languages that make me money and power my projects.

Once 2.0 is out and things are rolling full steam ahead, count me in. I will gladly and almost certainly become a contributor to Phalcon utilizing Zephir when the time comes. I have been looking for an open source project to contribute to, and Phalcon has my interests.

Also @Phalcon, in regards to funding, I did not know that was even happening until I read this thread. If you want to raise money, then that effort needs to be more prominent.

What I can do is sit and go through the list of all issues and correctly classify them. If they are NFRs then we will have to put those in the back burner for the time being and concentrate on the verified bugs.

Note that we are currently working on two codebases, 1.x and 2.x which makes things a bit tricky in terms of time management.

For 2.0 bugs, unless they are catastrophic i.e. segfaults etc. most people could read the code and figure out what is wrong using tests. That way we will fix more bugs faster. For 1.x we will need to wait until they get fixed.

1.x will remain active for quite a while so we need to support that too :)

@Nikolaos, @phalcon Do you have an approximate date on which bug issues will be addressed? We don't want to start a development if there is a high possibility of facing a bug a nobody replies in months

What I can do is sit and go through the list of all issues and correctly classify them. If they are NFRs then we will have to put those in the back burner for the time being and concentrate on the verified bugs.

Note that we are currently working on two codebases, 1.x and 2.x which makes things a bit tricky in terms of time management.

For 2.0 bugs, unless they are catastrophic i.e. segfaults etc. most people could read the code and figure out what is wrong using tests. That way we will fix more bugs faster. For 1.x we will need to wait until they get fixed.

1.x will remain active for quite a while so we need to support that too :)

@Tyler it's good to know that more hands are joining Phalcon development. Phalcon Team started yesterday a campaign to raise funds in order to ensure the development of Phalcon/Zephir next year. I'm really surprised it doesn't have more visibility. Hope donations increase over time.

https://pledgie.com/campaigns/27405

I'm fairly new to Phalcon still, but I'd like to contribute to this discussion.

@walterwhitep - I see your concerns. However, as @Phalcon said, it has been difficult in the past for people to contribute. I'm a full time PHP developer, a student, and a young man who enjoys his social life when I have time for it. I want to contribute to Phalcon, but I simply don't have to time to learn C and I can better spend my time by focusing on the languages that make me money and power my projects.

Once 2.0 is out and things are rolling full steam ahead, count me in. I will gladly and almost certainly become a contributor to Phalcon utilizing Zephir when the time comes. I have been looking for an open source project to contribute to, and Phalcon has my interests.

Also @Phalcon, in regards to funding, I did not know that was even happening until I read this thread. If you want to raise money, then that effort needs to be more prominent.

@walterwhitep I cannot see because I haven't analyzed the list yet. Hopefully I can have a solid answer after this weekend.

@Nikolaos, @phalcon Do you have an approximate date on which bug issues will be addressed? We don't want to start a development if there is a high possibility of facing a bug a nobody replies in months

What I can do is sit and go through the list of all issues and correctly classify them. If they are NFRs then we will have to put those in the back burner for the time being and concentrate on the verified bugs.

Note that we are currently working on two codebases, 1.x and 2.x which makes things a bit tricky in terms of time management.

For 2.0 bugs, unless they are catastrophic i.e. segfaults etc. most people could read the code and figure out what is wrong using tests. That way we will fix more bugs faster. For 1.x we will need to wait until they get fixed.

1.x will remain active for quite a while so we need to support that too :)

edited Dec '14

@niden : concerning 1.x version, i'm (in the good way) surprised on your answer, as I don't find it active at all... How can we help ?

21d without answer, that's what i mean by not active at all :-)