I've been working on a couple of mini apps that dumb down some of the back office stuff. For instance one that allows the user to build a catalog by adding products from a previously created catalog by showing both catalogs on the same screen(useful when you have multiple vendor catalogs in your deployment and want to create your company's catalog by picking which products to include in your categorized makeup). This of course using as little additional code as possible. Now would this be beneficial to the OFBiz community, Yes. Does it belong in the overall project. Probably not, simply because it duplicates existing catalog app functionality. It just makes it easier for non techie people to create catalogs when their vendors can supply xml versions of their catalogs. (Not to mention David and Andy et al have better things to do then try to make sense of my irregular coding habits) I want to share thi! s but have a couple of things standing in the way. #1 I do not wish to maintain it #2 I don't want to host the file for download #3 I don't want someone to be able to license it in a way that I can no longer benefit from my own contributions #4 I want anyone to be able to use it and change it to suit their needs without reservation #5 I want the OFBiz project to be able to incorporate it if they so choose without creating headaches if they decide to change to the Apache license. #6 I want it to solicit the contributions of others in a similar manner (ie not world class additions to Ofbiz, but helpful none the less) I was thinking something along the lines of what osCommerce's community does. http://www.oscommerce.com/community/contributions but again, I don't want to maintain it lol. Any suggestions? I'm also working on dumbed down mini apps for price rules and a quick lookup for what price a! customer has purchased a product for in the past. _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
Chris, This may be something that chould/should go in the "specialized" folder in the current ofbiz SVN repository. These haven't seen as much community attention outside of the main developers of them as the core applications in OFBiz, but they do get some attention so you'd probably have at least a bit of help with them. I looked at the screen shot you sent to Jira, and I think that this could become a screen in the current catalog manager just fine if you're interested in that. Enhancements and additions like this have been going into the catalog manager for a while, and there is certainly room for more as the Product and related data model is quite large and difficult to understand, so tools to help with this are worthwhile. On the licensing issue... In general all artifacts in OFBiz _should_ have one and only one copyright notice for "The Open For Business Project", and to make it clear we put the URL in there too. The implication is that the copyright is assigned to the project, however this has not been explicit in the past. If/when we move to Apache the copyright will be owned by the ASF and it will be explicit that all copyrights of contributions are assigned to the ASF. As far as #3 goes, that is one reason we are moving toward joining the ASF... contributors can feel more comfortable that their contributions will be kept in a good license and "owned" by a good organization. -David On Dec 7, 2005, at 9:24 PM, Chris Howe wrote: > I've been working on a couple of mini apps that dumb down some of > the back office stuff. For instance one that allows the user to > build a catalog by adding products from a previously created > catalog by showing both catalogs on the same screen(useful when you > have multiple vendor catalogs in your deployment and want to create > your company's catalog by picking which products to include in your > categorized makeup). This of course using as little additional > code as possible. > > Now would this be beneficial to the OFBiz community, Yes. Does it > belong in the overall project. Probably not, simply because it > duplicates existing catalog app functionality. It just makes it > easier for non techie people to create catalogs when their vendors > can supply xml versions of their catalogs. (Not to mention David > and Andy et al have better things to do then try to make sense of > my irregular coding habits) I want to share thi! s but have a > couple of things standing in the way. > > #1 I do not wish to maintain it > #2 I don't want to host the file for download > #3 I don't want someone to be able to license it in a way that I > can no longer benefit from my own contributions > #4 I want anyone to be able to use it and change it to suit their > needs without reservation > #5 I want the OFBiz project to be able to incorporate it if they so > choose without creating headaches if they decide to change to the > Apache license. > #6 I want it to solicit the contributions of others in a similar > manner (ie not world class additions to Ofbiz, but helpful none the > less) > > I was thinking something along the lines of what osCommerce's > community does. http://www.oscommerce.com/community/contributions > but again, I don't want to maintain it lol. Any suggestions? > > I'm also working on dumbed down mini apps for price rules and a > quick lookup for what price a! customer has purchased a product for > in the past. > > _______________________________________________ > Users mailing list > [hidden email] > http://lists.ofbiz.org/mailman/listinfo/users _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users smime.p7s (3K) Download Attachment |
Free forum by Nabble | Edit this page |