Re: freemarker asf branding

2016-07-01 Thread Lalish-Menagh, Trevor
Could we use the disclaimer at the bottom of the Apache Blur site:
https://incubator.apache.org/blur/ and just change "Blur" to "FreeMarker?"

"Apache Blur is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator. Incubation is required
of all newly accepted projects until a further review indicates that the
infrastructure, communications, and decision making process have stabilized
in a manner consistent with other successful ASF projects. While incubation
status is not necessarily a reflection of the completeness or stability of
the code, it does indicate that the project has yet to be fully endorsed by
the ASF."

On Fri, Jul 1, 2016 at 1:11 PM, Daniel Dekany  wrote:

> There was no attachment in your mail.
>
> The only information I have found is "Incubator Logo Podlings websites
> SHOULD contain the Apache Incubator Project logo as sign of
> affiliation.". There's not even link to the logo, not to mention to
> the source of the logo (which I suppose is
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/images/egg-logo-source.svg
> ).
> So the whole thing is totally informal. Surely they won't complain if
> you re-rasterize the SVG in a different resolution, nor that if you
> remove that black border.
>
>
> Friday, July 1, 2016, 7:39:33 PM, Lee wrote:
>
> > Hey Sergio,
> >
> > I'll update the website with the logo. I was thinking of putting it
> > in the left column on the website. Is that visible enough? Are we
> > allowed to remove the border from the logo? The left-column is 210px
> > wide and the logo is 229px. If I remove the border and the
> > whitespace then it's 207px and fits nicely (see attached).  If we
> > can't remove the border, can we resize it?
> >
> > Thanks,
> > Evangelia
> >
> > On Fri, Jul 1, 2016 at 12:07 AM, Sergio Fernández 
> wrote:
> > Those who follow general@incubator, IPMC has started (led by John D.
> > Ament) to audit podlings' branding:
> >
> >   https://wiki.apache.org/incubator/BrandingAuditJune2016
> >
> > FreeMarker is fine. But "Podlings websites SHOULD contain the Apache
> > Incubator Project logo as sign of affiliation". Since it's a "SHOULD" is
> > fine; but I'd recommend to add the Incubator logo somewhere in the site
> > template.
> >
> > Thanks!
> >
> > --
> > Sergio Fernández
> > Partner Technology Manager
> > Redlink GmbH
> > m: +43 6602747925
> > e: sergio.fernan...@redlink.co
> > w: http://redlink.co
> >
>
> --
> Thanks,
>  Daniel Dekany
>
>


-- 
Trevor Lalish-Menagh
about.me/trevmex


Re: Proposed policy change: Don't require CLA from contributos

2017-06-21 Thread Lalish-Menagh, Trevor
That sounds great. Lowering the barrier of entry is always good!

One thing that I am working on with the TODO Group is a tool for
ensuring compliance to repo rules (like Copyright headers):
https://github.com/todogroup/repolinter Might be useful here if we
could tie it in somehow.

On Wed, Jun 21, 2017 at 3:47 AM, Daniel Dekany  wrote:
> Currently we strictly require a CLA (by which I mean an ICLA or CCLA)
> for any contributions to be accepted, as
> http://freemarker.org/contribute.html says.
>
> This practice was inherited from the pre-ASF times, when without
> lawyers available, we tried to be on the safe side. But based on
> https://issues.apache.org/jira/browse/LEGAL-156 and
> https://wiki.apache.org/couchdb/CommitPolicy and some other mails we
> can make things simpler for contributors (not to be confused with
> committers).
>
> So I propose that we say that:
>
> - People sending contributions with GitHub pull requests need no CLA.
>   But, before merging, we must check that:
>   - The mail about the pull request was received to
> notificati...@freemarker.incubator.apache.org, so that there's
> a record of this even in the ASF infrastructure.
>   - The files in the pull request has the standard ASF copyright
> headers, or no copyright headers in files where that's normally
> not present. There's no other conflicting copyright information
> included either (like a such LICENSE file).
> - People sending in patches as attachment to FreeMarker Jira issues
>   need no CLA. But, before merging, we must check that:
>   - It's clear from the wording of the issue that the user wishes to
> contribute (as opposed to, for example, just showing an example).
>   - Copyright headers are in order, just as with GitHub pull request.
>
> If someone contributes a bigger feature, yet they isn't a committer,
> we might still ask a CLA though. But that can be dealt with when such
> thing happens.
>
> --
> Thanks,
>  Daniel Dekany
>



-- 
Trevor Lalish-Menagh
about.me/trevmex


Re: FreeMarker has graduated to TLP!

2018-03-23 Thread Lalish-Menagh, Trevor
How exciting! Congrats to all the dedicated volunteers that made this a reality!

On Fri, Mar 23, 2018 at 1:27 PM, Jacques Le Roux
 wrote:
> Congratulations Daniel and to all the persons who participated to this
> endeavour. A new one begins :)
>
> Jacques
>
>
>
> Le 23/03/2018 à 20:59, Daniel Dekany a écrit :
>>
>> To quote the relevant part from the ASF Board Meeting Summary of March
>> 21, 2018:
>>
>>The following resolutions were passed unanimously:
>>
>>  A. Establish the Apache FreeMarker Project (Dániel Dékány VP)
>>
>> So now that this uncertainty was eliminated, we can feel much more
>> motivated to push FM ahead. We were awarded with the additional trust
>> associated to the "Apache" brand, so let's put code behind it that
>> fits the modern standards, by which I mean FM3. Of course, FM2 also
>> needs to be maintained, even receive new features. But I believe FM3
>> is absolutely necessary for growth, adoption in new projects.
>>
>> It will take a while until all the "paper work" and infrastructural
>> changes are done
>> (https://incubator.apache.org/guides/transferring.html). But we don't
>> have to wait for all of that to release 2.3.28 as non-incubating, so I
>> hope that will be done sometimes next week.
>>
>



-- 
Trevor Lalish-Menagh
about.me/trevmex