Re: Who is in charge of collective.zipfiletransport?

I'am not in charge, but some hints...

- its always a good idea to look at the commit log:
   https://github.com/collective/collective.zipfiletransport/commits/master

- its a good idea to mention one or two of the activest committers 
github usernames prefixes with an @ in the issue/pull request to ping them.

- adding changes to docs/HISTORY.txt increases the chance of a quick 
release.

Also a technical question: How spreaded is ZIP64? Is this supported by 
every tool today (I've no idea about ZIP, so excuse this question if its 
silly)? If not it would be good to have it as an configuration option.

HTH Jens

On 2014-02-19 17:47, Manuel Vázquez Acosta wrote:
> Hi,
>
> I have created an issue some weeks ago in
> https://github.com/collective/collective.zipfiletransport/issues/1
>
> I haven't received any response.  So I created a fork a draft a fix and
> request the pull (*).
>
> Is there anyone who's in charge of this product?
>
> Best regards,
> Manuel.
>
>
> (*)  Although I have push access to the repo, I haven't the time right
> now to commit to test the fix.
>
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
>


-- 
Klein & Partner KG, member of BlueDynamics Alliance


------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Plone-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-developers