heh :)
Chris, I understand your concern, but please also keep in mind that Wicket is not just for use in hobby software. I mean, assuming Wicket 1.0 gets off the ground, you're going to have real companies using this framework to get their work done.
I'm not trying to impose anything on you that you are not comfortable with. I think we can all agree that our day jobs can sometimes get a bit oppressive. I am simply saying that keeping in mind that our developers have one set of concerns and our users have another set of concerns, we should find a system that works for both of them.
From my point of view "as a company" the reason I chose to use an open-source framework by the name of Wicket has to do with:
1) It's design
2) It gives me the impression that I have more control over my dependencies than if it was a commercial product. I am under the impression (and hopefully I'm not wrong on this) that "should anything go wrong" I could fix the problem myself and the team will commit my patch to the main CVS branch (within reason).
3) The price is right
From a business point of view, the price of the framework is one of my last concerns. If anything I am probably spending more money (i.e. time) on it than I would with a commercial product. I am first and foremost concerned with the framework doing its job right and allowing me to "stay on my feet" to stay ahead of my competitors. The reason I would choose to use Wicket over JSP is that I am hoping that the turnaround time between (small) feature requests and commits is shorter with Wicket than with JSP.
Gili
Christopher Turner wrote:
I think that you are wrong to say that unassigned issues are ignored. All of the team are aware of all of the open issues. We a just picking the issues that are either the most critical for 1.0 (from our point of view) or that affect the widest spectrum of Wicket users.
My personal view is that it is better to leave an issue unassigned until you start work on it. That way, whenever any developer on the team has some time available then they can go and pick up any issue and be certain that no one else is working on it. If issues were immediately assigned to one developer then you may find that this developer has a busy week or something and that they cannot spend time fixing the issue, whereas a different developer would have had time to pick it up and sort it out but didn't because they thought someone else was working on it.
From a sanity point of view, I'd much rather dip in and out as and when time allows as opposed to feeling pressurised because I have a load of issues assigned to me with estimated fix dates. This is open-source and we are doing it for fun. I get enough of pre-assigned time-critical defects in my day job thank you very much :-(
As for a release date, the only ones that I'm focused on at the moment are release of baby v1.0, scheduled for 30th May, and the completion of nursery v1.0 as soon as possible!
Regards, Chris
> > Martijn Dashorst wrote: > > Gili, > > > > I see where you are coming from. We /also/ want to ship RC3 > as soon as > > possible. However, we have found several core problems > which should be > > fixed before we go to 1.0. These issues are mainly internal > to Wicket, > > but have great influence on usage patterns or on promised > features (for > > instance clustering support). If the currently found issues aren't > > solved, I assure you that the whole community of the serverside, > > Javalobby, and java.net will turn their backs on Wicket and that is > > something nobody wants (perhaps Howard Lewis Ship ;-). > > I am aware of these issues which is why I am not > pushing for a release > until they're fixed :) It would just be nice to have a list > of "stuff to > do before RC3" and "estimate release date". I don't mind if we modify > the list or projected release date as time goes by. It would just be > good to have so people outside the core team know what's > going on. I do > appreciate your hard work. Thank you! > > > As to the roles on the wicket team, if you have read the > mailing list > > for a while, you can easily see who is doing what. I mainly > focus on > > delivering the goods, and fix the occasional bug. Jonathan, Eelco, > > Juergen and Johan are the actual core developers, where Eelco and > > Juergen also contribute heavily on the Wicket-stuff > projects, and other > > open source projects. Chris is our main clustering guy and > is also our > > 'conscience' when our commits go sour. > > Any chance we can update the contributors page to > reflect this? It > would help direct the right questions to the right people. > > > You know, this is an open source project. As far as I know, > we provide > > quick responses to questions of our users. Sometimes an > answer is easy > > to give, and then the answer follows quickly. Other times > this is not > > the case. But we do this in our free time, and for the > Topicus guys we > > provide additional support by /using/ Wicket on our > projects. But this > > is not a free lunch! > > Yes, I find that the team replies fairly quickly to > questions posted on > the mailing list and I am thankful for that. I just want to point out > that the same is not true vis-a-vis the Issuetracker system. I've > reported some bugs over the past few months and it would be > good to know > what the target milestone is for fixing them and which team member is > going to be working on it. > > The problem with the current "hands off" attitude is > that no one seems > to be taking responsibility for issues that don't interest them. By > assigning developers open issues you ensure that they take > ownership of > it and will prioritize it in their queue of things to do. Unassigned > issues are ignored. > > I am fairly sure that with a little effort we can improve this > situation. Thanks again for all your hard work! > > Gili > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. > Get your fingers limbered up and give it your best shot. 4 > great events, 4 opportunities to win big! Highest score > wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. > Visit http://www.necitguy.com/?r=20 > _______________________________________________ > Wicket-develop mailing list [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop >
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
