Hi Adam, glad to see you back.
First of all an off topic (I apologize for it but I ): the guy at Freemarker.org is still waiting for your CLA that is necessary to include your patch into the next Freemarker release (we are currently using a Freemarker jar modified by you and we should fix it asap); please get in touch with him and/or resend the CLA when you can. Thank you. As regards the debian folder, I am sure it was working but it is also true that it is a very specific component and that no one in this community (apart you) showed interest or even attempted to maintain it (I am sure no one apart from you would be able to): these are all good reasons for moving it out to the official trunk and releases; however I see it a good tool that you could provide distribute outside of the official project. You can think of the best way to do this (it seems you already have some) but I also want to mention (since you are very busy) that there is no rush as the component was stale for a long time and we could bring it back into the future if/when the community will show an interest on it. Kind regards, Jacopo On Nov 15, 2012, at 6:49 PM, Adam Heath wrote: > On 11/15/2012 10:54 AM, Jacopo Cappellato wrote: >> This is now completed at rev. 1409880 >> >> https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic >> >> Jacopo >> >> On Jul 26, 2012, at 8:09 AM, Jacopo Cappellato wrote: >> >>> ... the removal will be documented, as usual, in the "Attic" page: >>> >>> https://cwiki.apache.org/confluence/display/OFBADMIN/OFBiz+Attic > > Hmm, sad. I understand the reasoning, and I've been super busy at > work, and missed both the original email and this final one. Ean had > to poke me about it. > > The debian folder *does* function, and will produce proper > debian-policy-compliant debs. The only reason you don't see it > uploaded to debian.org(I am also a debian developer, or used to be), > is that ofbiz embeds outside libraries in side it, and that is not > allowed for an upload to debian main. > > I'd like to keep this around, but I also understand the desire to keep > ofbiz upstream clean. Here are my thoughts, based on a discussion Ean > and I *just* had here at work. > > 1: Create a fork of ofbiz on github. Git is much better for > distributed development. > 2: Re-add this debian folder from the attic. > 3: Import any changes I might have locally. This should be small, as > I was mostly upstream(I need to check a few older branches). > 3: Announce this branch as the location for debian development. > *Only* changes to make debian integration should be placed here. > 4: Start filing issue trees in jira for pure upstream work. This > would include things like removing embedded libraries(maybe a > post-download kinda thing).
