Mary Nicole Hicks wrote: > > ----- QUOTE Mary Nicole Hicks ----- > I think that the Zend framework team needs to add a registry of 3rd party > ZF modules to their site. Just something similar to > https://addons.mozilla.org/en-US/firefox/ would do the job. > ----- QUOTE END ----- >
Matthew Weier O'Phinney-3 wrote: > > ----- QUOTE Matthew Weier O'Phinney-3 ----- > - We've discussed this a number of times > - The ZF team at Zend is very small > - Fairly busy > - hint, hint -- if somebody or a group of you would like to work on > such an application, we may be able to host it on the ZF site, and give > credit to the authors. > ----- QUOTE END ----- > Is there a bare list of features that such a thing would need. If there is very little time that anyone can spend on it, then I think number of features would need to be cut down to the bare minumim. To me, the bare minumim would be a list of links in a wiki somewhere. Although this would be far from being like https://addons.mozilla.org/en-US/firefox/, but it would be a start. Vince42 wrote: > > ----- QUOTE Vince42 ----- > I guess as long as we still suffer from the absence of standards > regarding self-contained modules, this would rather lead to confusion > than to a big success. > > Don't get me wrong: I don't expect the ambitious developer not to see > that it is always difficult to incorporate other people's work, but I > really think that for a newcomer such a site at the current stage would > be rather counter-productive as it induces some wrong expectations. > ----- QUOTE END ----- > It is for that reason that I think such a system would need to start small. Out of the way of newcomers, but in a place on the site where the ambitious developer can learn to bookmark. umpirsky wrote: > > ----- QUOTE umpirsky ----- > We can create new thread and share zend oriented api. All of us have sth > implemented, I have started tr.im API class, extended twitter API > class...someone probably have pay-pal e.t.c why not zip and share it right > there on mail list? They might not be perfect, but can be used to see way > sth is implemented, and why not making it better. Simply attach what works > for you. > What do you think? > > Regards, > Saša Stamenkovic > ----- QUOTE END ----- > This is why I think that the modules should be setup at a place like http://sourceforge.net/ with links from the framework.zend.com site. Currently there is code for modules scattered around on blogs and threads. Often no one will update code on threads or blogs, so to find a tr.im API class or extended twitter API class that works after ZF has moved along a few versions is hard. When I do find a broken 3rd party tr.im API class or extended twitter API class that has been broken by a ZF update, I want to help fix it. Although I might not be the best coder, I can find the broken parts or bugs and help fix them. The bonus is that places like http://sourceforge.net/ have issue trackers for when these 3rd part classes break. As long as all the linked modules are free, open source and are hosted on a web-based source code repository then collaboration is able to happen. Having this as a requirement to be linked to would help encourage people to put classes into web-based source code repositories. -- View this message in context: http://www.nabble.com/Module-Sharing-and-framework.zend.com-tp24421433p24436535.html Sent from the Zend Framework mailing list archive at Nabble.com.
