So what is the best way (official? permanent?) to link to a previous response?
In 6 months when someone has a similar question, what is the official way to link to previous answers? Equally, what is the best way to improve those answers if the answer 6 months back worked at that time, but now is invalid and a 'bad practice' due to wicket improvements? Folks so rarely use the mailing list archives ( http://wicket.apache.org/help/email.html), (not easily searched!) I doubt that is the solution. -Clint On Fri, Oct 7, 2011 at 7:32 AM, manuelbarzi <[email protected]> wrote: > it sounds great, but why not fully concentrate on wicket. apache will > adopt whatever magic-solution asa it'll be licence compliant, and > affordable by resources and directives. > > for the moment this mailing list has been a very successful machine, > and still has much to bring. outside, whatever wrapper (wicket-based > or not, may be assembled to pull all posts, order and make them as far > confortable-searcheable as low-patience eager-brains demand). > > as other expressed: markmail and nabble are pretty enough, and > managing issues by mail - on smart or not phones - is simply a > pleasure. > . > > > On Fri, Oct 7, 2011 at 12:43 PM, Josh Kamau <[email protected]> wrote: > > On a light note: > > > > we can build our version of stackoverflow as a Q/A for wicket. We can > build > > it in wicket and let everyone access the code. We can use it as a demo > > wicket application. > > > > Josh. > > > > On Fri, Oct 7, 2011 at 1:40 PM, Gaetan Zoritchak < > > [email protected]> wrote: > > > >> I fully understand the risk of relying on an external and uncontrolled > >> party. The best of breed solution would be to have SO like a Q & A > >> for wicket based on an open source implementation like Bert mentionned. > >> > >> For the mailing list, I think the advantage of reading the messages on > his > >> phone is less important than the gate of a partially closed system that > >> requires a subscription by email. See on > >> http://softwareandsilicon.com/chapter:2 # toc2 "- Freedom of Access > and > >> - Weak Group Identity" > >> > >> Markmail: > >> The traffic is constantly increasing from 1999 until late 2009 early > >> 2010 before being reduced significantly. I think the reason is due to > the > >> tool a little bit old. Even if the interface allows to search for > messages, > >> ergonomics and the quality of responses is not equivalent to what is > >> available on intenet today. > >> > >> My point is not to criticize but to point out that this is negative for > the > >> adoption of wicket. Today when I choose a technology for a project, even > >> though I prefer Wicket for its design, I have to "sell" the framework > to a > >> team that does not necessarily find it very sexy. > >> > >> Gaetan > >> > >> > >> 2011/10/7 Martijn Dashorst <[email protected]> > >> > >> > The biggest issue with moving to Stack Overflow is that we deliver our > >> > community to an external party which can do anything with the > >> > questions, show stupid ads, etc. Have no mistake: stack exchange is a > >> > commercial venture. So one criterium is to be able to pull the plug on > >> > it whenever it goes sour. While the content of stack overflow is > >> > publicly available, it is not licensed with an Apache friendly license > >> > (http://creativecommons.org/licenses/by-sa/2.5/). This issue was the > >> > biggest hurdle SO needs to take to become a viable alternative for the > >> > user list at Apache. > >> > > >> > As for this list not being visible, you can always shop around for > >> > list archive providers. Nabble has a nice forum like interface, Mark > >> > mail provides awesome search tooling. > >> > > >> > Martijn > >> > > >> > On Fri, Oct 7, 2011 at 8:49 AM, Bert <[email protected]> wrote: > >> > > I had a discussion about this with martin dashorst when we meet this > >> > > year at a conference. Apparently, he does like the idea of a SO like > >> > > Q&A site for wicket. But wicket being an Apache project, there are > >> > > certain requirement if i recall our discussion correctly. > >> > > > >> > > One of the problems is the hosting of such a side. The mailing list, > >> > > bugtracker, wicki,... are all hosted and maintained by the apache > >> > > admins. Getting a new tool into there is not easy. One could host a > >> > > solution outside of apache, but this opens questions about long term > >> > > support of the infrastructure, privacy issues and so forth. > >> > > > >> > > There are a few opensource implementations available: > >> > > > >> > > http://gitorious.org/shapado (used by debian at > http://ask.debian.net/ > >> ) > >> > > http://www.osqa.net/ > >> > > > >> > > I do like the SO style (never been a fan of mailing lists), but on > the > >> > > other side registering here is not much of a hassle. > >> > > > >> > > My 2 cent > >> > > Bert > >> > > > >> > > On Fri, Oct 7, 2011 at 07:25, Josh Kamau <[email protected]> > >> wrote: > >> > >> I like the mail. Atleast i can get the answers even on my not so > smart > >> > >> phone. > >> > >> > >> > >> Josh. > >> > >> > >> > >> On Fri, Oct 7, 2011 at 6:43 AM, Chris Colman > >> > >> <[email protected]>wrote: > >> > >> > >> > >>> >Source management and bugs are also outdated. The version on > github > >> is > >> > >>> much > >> > >>> >better. > >> > >>> > >> > >>> I recently had to get up to speed with github. Not sure what all > the > >> > >>> fuss is about. The learning curve was about 20x that of Subversion > >> and > >> > >>> I'm still not confident about how to do things or whether what I'm > >> > doing > >> > >>> is the 'right' thing to be doing. Subversion on the other hand is > >> > really > >> > >>> easy to understand (and most developers already know it) and even > >> > though > >> > >>> it has 'theoretical' shortcomings compared to a distributed VCS > like > >> > git > >> > >>> in practice I never saw any difference in performance or usage > apart > >> > >>> from git being a lot 'weirder' ;) > >> > >>> > >> > >>> > > >> > >>> >My 2 cents, > >> > >>> > > >> > >>> >Gaetan > >> > >>> > >> > >>> > --------------------------------------------------------------------- > >> > >>> To unsubscribe, e-mail: [email protected] > >> > >>> For additional commands, e-mail: [email protected] > >> > >>> > >> > >>> > >> > >> > >> > > > >> > > > --------------------------------------------------------------------- > >> > > To unsubscribe, e-mail: [email protected] > >> > > For additional commands, e-mail: [email protected] > >> > > > >> > > > >> > > >> > > >> > > >> > -- > >> > Become a Wicket expert, learn from the best: > http://wicketinaction.com > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [email protected] > >> > For additional commands, e-mail: [email protected] > >> > > >> > > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
