How about creating a fork at github [1]? Github has a nice GUI, that makes reviewing easy. And as far as I know, it is even possible to integrate pull requests.
Benedikt [1] https://github.com/apache/commons-compress 2013/6/17 Bear Giles <[email protected]> > What would be the best way to start pushing code? It will be more tightly > integrated with the existing code than my earlier 'dump' contribution so I > can't just dump a source ball. I also don't want to post code snippets here > if it will cause people problems. > > Thanks, > > Bear > > > On Thu, Jun 13, 2013 at 1:46 AM, Stefan Bodewig <[email protected]> > wrote: > > > On 2013-06-12, Siegfried Goeschl wrote: > > > > > Hi folks, > > > > > don't know if this was already mentioned but providing strong > > > encryption causes administrative head-ache > > > > Actually, it doesn't. All that has to be done, is editing a page in the > > CMS, adding a notice to the README and sending a single email. Been > > there, have got the T-shirt. > > > > I even think we don't need to do anything as long as we stick to plain > > JCE. > > > > Hmm, we already have AES support in the new 7z package. I'll take care > > of the crypto policy stuff. > > > > Stefan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
