Re: Moving JBoss FreeMarker IDE (Eclipse plugin) to the ASF?

[Jacopo Cappellato]

On Tue, Mar 13, 2018 at 4:47 PM, Daniel Dekany  wrote:

> [...]
> It's our turn. I'm really just waiting to hear if the other PPMC
> members think that this should be attempted (like, if we want that
> code at all), then I will ask ASF Legal.
>
>
I don't feel much comfortable in commenting on license/legal stuff because
of my lack of confidence on the subject :-(
However I think that we can start by stating our interest in accepting the
codebase donation from RedHat/JBoss.
Then we could figure out the exact steps that need to be followed by them
and by us (trying to minimize the workload n their part as much as
possible) and then we will decide if it is a feasible plan.

Jacopo

Re: Started graduation resolution DISCUSS on general@incubator.a.o

[Jacopo Cappellato]

On Mon, Feb 26, 2018 at 10:09 AM, Daniel Dekany  wrote:

> [...] Though it's not clear from
> https://incubator.apache.org/guides/graduation.html#
> graduating_to_a_top_level_project
> if after the board decision when can we actually do a non-incubating
> release. Pretty much immediately?
>

Correct.

Jacopo

Re: Proposal for FREEMARKER-84: More flexible handlig of missing templates

[Jacopo Cappellato]

On Fri, Feb 16, 2018 at 8:04 AM, Daniel Dekany  wrote:

> Some more opinions guys? Especially as we got one opinion against the
> feature.
>

Just to clarify my opinion: I am not against this feature; I simply don't
consider it a must since there are some workaround to get a similar
behavior. But if it will be implemented I will be happy too.

Jacopo

Re: Proposal for FREEMARKER-84: More flexible handlig of missing templates

[Jacopo Cappellato]

For less common use cases like this my preference is to defer the
implementation to the template developer rather than adding complexity to
the language.
If I understand the use case that originated this request, something
similar could be achieved with a simple trick like the following:
1) the calling code would be:
<#include "possibly-missing-template.ftl" ignore_missing=true>
<#if !processed??>
The template was not found or processed!

2) somewhere in possibly-missing-template.ftl (i.e. at the bottom of it) we
add an assign directive like:
<#assign processed=true>

There are some cons to this approach (the most relevant one is that the
referenced template has to contain the #assign directive) but FM users
could live with this approach and in the meantime we could try to get their
feedback to better understand how much this requirement is desired to
justify a change to the codebase.

Jacopo

On Sun, Feb 11, 2018 at 10:02 PM, Daniel Dekany  wrote:

> See the RFE here:
> https://issues.apache.org/jira/browse/FREEMARKER-84
>
> As you see, the first consensus was introducing `.last_include_found`,
> but it has two problems:
>
> * Sometimes it happens that if, and only if the template exists then
>   you want to do (usually print) something *before* it. Problem is, by
>   the time you know that from `.last_include_found`, it's too late, as
>   the template was already processed.
>
> * Like many global state variables in general, this can lead to some
>   confusing edge cases and hard-to-follow code. Like, if `#include`
>   throws an exception, which is then handled by the user with
>   `#attempt`/`#recover`, then `.last_include_found` may or may not be
>   updated, as perhaps we haven't yet reached the point where it can be
>   told if the template exists. (Consider an expression evaluation
>   error in the `#include` parameter, or an I/O error due to which we
>   can't access the template directory). Also there are some public
>   `include` methods in the `Environment` API, but they can't set this
>   variable, as they return a `Template`, and the variable must be set
>   after the `Template` was processed, unless the template was missing.
>   (If you can't figure out why it must be done that way, that proves
>   again how tricky this is... think about includes inside includes.)
>
> So, I propose the solution below. Maybe somewhat difficult to grasp
> first, but it meant to be used rarely, and mostly by "experts"...
> Let's hope SO and examples in the Manual will help people though. (-;
>
> Introduce a new special variable (see
> https://freemarker.apache.org/docs/ref_specvar.html) called
> "get_optional_template", which is a TemplateMethodModelEx with these
> parameters:
>
> 1. template name (maybe a relative path, resolved as #include/#import
> does it) 2. A hash that can have the following keys: "parse",
> "encoding" (similarly to
> https://freemarker.apache.org/docs/ref_directive_include.
> html#ref.directive.include).
>
> Example method call (the `.` prefix is the special variable reference
> syntax):
>
>   <#assign t = .get_optional_template("foo.ftl", { 'encoding': 'utf-8' })>
>
> The method returns a hash (`t` above) that contains the following keys:
>
> - "include": directive (or missing); `<@t.include />` has similar
>   effect as `<#include "foo.ftl">`
>
> - "import": method (or missing); returns a namespace. `<#assign f =
>   t.import()>` has similar effect as `<#import 'foo.ftl' as f>`
>
> - "exists": boolean; returns if the template was found.
>
> The method call loads the target template eagerly, i.e., it won't wait
> until `t.include`, `t.exist` etc. is actually used.
>
> Note that the hash is returned even if the template wasn't found (but
> then it won't contain "include" and "import", and "exists" will be
> `false`). If some other error occurs, like an I/O error other than a
> "template not found", or the template has invalid syntax, it will
> throw exception (just like #include).
>
> Use cases:
>
> - `#include` with fallback templates or fallback macro (note how we
>   can use the `exp!defaultExp` operator):
>
>   <@.get_optional_template('foo.ftl')
>   !.get_optional_template('bar.ftl').include
>   !defaultMacro  />
>
> - Doing something before `#include` if the template exists:
>
> <#assign t = .get_optional_template('foo.ftl')>
> <#if t.exists>
>   Do before existing template
>   <@t.include />
> 
>
> Opinions?
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [RESULT][VOTE] Graduate Apache FreeMarker Project from Incubator to TLP

[Jacopo Cappellato]

I think the last final steps should be:
1) send the charter proposal, already prepared by Daniel, to the Incubator
general list for review before the vote [*]
2) start the graduation vote in the Incubator general list; see "The
Recommendation Vote" [**]

Then (if the recommendation vote will be successful) we will submit the
resolution to the Board.

Regards,

Jacopo

[*] https://incubator.apache.org/guides/graduation.html#preparing_a_charter
[**] https://incubator.apache.org/guides/graduation.html#the_
recommendation_vote


On Tue, Feb 6, 2018 at 6:23 AM, Ralph Goers 
wrote:

> I am confused. Who are we waiting for to do what?
>
> Ralph
>
> > On Feb 3, 2018, at 4:39 AM, Daniel Dekany  wrote:
> >
> > Good! (And sounds like communication is lacking on the other side...)
> > Now you aren't red on
> > https://whimsy.apache.org/roster/ppmc/freemarker#reporting.
> >
> > There are two other red items though, and I have to admit that I don't
> > know where does it get that false information from:
> >
> > * No Release Yet/Missing ASF Copyright Headers on Source Code
> > * No Release Yet/Binary has licensing issues
> >
> > Do we still miss some project meta info file somewhere? Where are
> > these Whimsy-related things documented? Are we supposed to care at
> > all?
> >
> > I have just checked https://whimsy.apache.org/roster/ppmc/ofbiz...
> > well guys, you don't even have Software Grant and IP Clearance. So I
> > guess this Whimsy thing is still in early stage... or OFBiz needs a
> > good lawyer. (-;
> >
> >
> > Friday, February 2, 2018, 11:02:38 PM, David E Jones wrote:
> >
> >> It looks like this is now taken care of (user jonesde now on the IPMC
> list):
> >>
> >> http://home.apache.org/phonebook.html?ctte=incubator
> >>
> >> -David
> >>
> >>
> >> On Wed, Jan 31, 2018 at 9:23 PM, Sergio Fernández 
> wrote:
> >>
> >>> Please David, engage again with private@incubator.a.o to see what's
> going
> >>> on. I don't recall your issue been discussed, but I may missed it.
> >>>
> >>> On Jan 30, 2018 06:39, "Daniel Dekany"  wrote:
> >>>
>  Monday, January 29, 2018, 7:16:21 PM, David E Jones wrote:
> 
> > On Mon, Jan 29, 2018 at 8:59 AM, Daniel Dekany 
>  wrote:
> >
> >> Monday, January 29, 2018, 4:35:38 PM, Sergio Fernández wrote:
> >>
> >>> Great, Daniel!
> >>>
> >>> Let's move to the next step and open the vote at
> >>> general@incubator.a.o
> >> ;-)
> >>
> >> David has started discussing the issue with his Mentor status on Jan
> >> 24. I'm waiting for that to be resolved. Not sure if there's any
> >> progress. David, did they answer? Because then that wasn't CC-ed to
> >> the private list.
> >
> >
> > I got a reply from John D. Ament on Jan 24th saying he was sending
>  notice,
> > but I haven't seen anything since and not sure if I should even
> expect
>  any
> > sort of email notification or if it's something I'd have to hunt
> around
>  for
> > or follow up on.
> >
> > FWIW I'm not on the Incubator PMC list yet (my ASF username is
>  'jonesde'):
> >
> > http://people.apache.org/phonebook.html?pmc=incubator
> >
> > I also don't know if my failure to respond to John's email in June
> will
> > cause any issues, or in general what to expect with all this so I
> >>> really
> > can't say much.
> 
>  If the process is like here, they have vote (at least 3 days), then
>  wait for 3 days so the board can veto the decision, and only then mail
>  you... I hope they have started the process. If they won't report back
>  in a few days, it would be good if you ask them.
> 
> > -David
> 
>  --
>  Thanks,
>  Daniel Dekany
> 
> 
> >>>
> >
> > --
> > Thanks,
> > Daniel Dekany
> >
> >
>
>
>

Re: Status file date issues

[Jacopo Cappellato]

>
> > Daniel Dekany  wrote:

So, David, can
> you join the IPMC? I know, it's annoying and all, but rule are rules.
>

David, since you are an ASF member you can simply send an email to the
general@incubator list asking to be added to the IPMC.

Jacopo

Re: Resolution draft for graduation, members

[Jacopo Cappellato]

On Mon, Jan 8, 2018 at 6:30 AM, Ralph Goers 
wrote:

> You would probably be better served by having someone else volunteer to be
> PMC chair. My reasoning for that is exactly for the same reason you put
> yourself there. You are the most active committer and obviously aren’t
> going anywhere. Having someone else be chair insures that someone else is
> staying fairly involved in the activities of the project, even if they
> aren’t the most active committer. You need at least 3 active PMC members so
> use any opportunity you can to make sure you stay above that mark.
>
> Ralph
>

This is a valuable argument but my preference is that we begin with Daniel
and possibly consider this opportunity in the future: I think it is
important, for the continuity of the history of the project (before/after
graduation), to assign the PMC chair role to the most influential person in
the FreeMarker community (which is also an ASF member); also, at the moment
there are no issues in identifying +3 active PMC members and my hope is
that people will stay involved with the project because they care and not
because of the responsibility assigned to them.

Jacopo

Re: Resolution draft for graduation, members

[Jacopo Cappellato]

Looks great to me and of course you are the best person for the VP role!

Jacopo

On Fri, Jan 5, 2018 at 10:08 PM, Daniel Dekany <ddek...@apache.org> wrote:

> Here's the Resolution you will vote on (at least that's my plan) in
> the graduation VOTE here on the poddling list. Anyone sees any
> oversight in it?
>
> As of the list of project members, I have listed everyone who said
> that he/she intends to stay so far. Anyone else? In the current list,
> everyone intends to be in the PMC as well.
>
> About the "be appointed to the office of Vice President" thing. Who
> should be it? I have written there myself for now, as I'm by far the
> most involved with the project. But maybe someone else fits that role
> better. I don't fancy titles, no offense taken in that case.
>
> And, as always... if you can, please check if we miss any formal
> requirements for graduation!
>
> 
>
> Establish the Apache FreeMarker Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to
> the public, related to a template engine.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache FreeMarker Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache FreeMarker Project be and hereby is
> responsible for the creation and maintenance of software
> related to a template engine, and be it further
>
> RESOLVED, that the office of "Vice President, Apache FreeMarker" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache FreeMarker Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache FreeMarker Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache FreeMarker Project:
>
>   * Dániel Dékány   <ddek...@apache.org>
>   * David E. Jones  <jone...@apache.org>
>   * Jacopo Cappellato   <jaco...@apache.org>
>   * Jacques Le Roux <jler...@apache.org>
>   * Sergio Fernández<wik...@apache.org>
>   * Woonsan Ko  <woon...@apache.org>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dániel Dékány
> be appointed to the office of Vice President, Apache FreeMarker,
> to serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache FreeMarker Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator FreeMarker podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator FreeMarker podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Please check and sign off our Podling Report for January!

[Jacopo Cappellato]

It looks great to me, thank you Daniel.The only change I would do is to add
Woonsan also in the section: "When were the last committers or PPMC members
elected?".

Jacopo

On Wed, Dec 27, 2017 at 10:34 PM, Daniel Dekany  wrote:

> Dear PPMC members!
>
> Please read the draft of our report on
> https://wiki.apache.org/incubator/January2018, and tell if you agree
> and what would you change!
>
> Then, when the deadline (Wed, January 03) is close, please also sign
> it off, if you agree.
>
> A problem I have noticed that from the original template David E.
> Jones was missing. I have added him back, as he's a Mentor as far as I
> know, even if not an Incubato comitter. Maybe I shouldn't have for
> that reason. David also red on our status page, and is not listed as a
> Mentor, at https://whimsy.apache.org/roster/ppmc/freemarker, saying
> "not listed as an incubator committer". But he is listed as a mentor
> on http://incubator.apache.org/projects/freemarker.html. I guess this
> should be resolved. Like he should be an Incubator committer I guess.
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Attempting graduation?

[Jacopo Cappellato]

The very next steps should be:
1) run a vote in this list to make sure the community is happy to graduate;
see "Community Graduation Vote" [*]
2) when the vote #1 starts, send an email to the Incubator general list to
inform them that the vote is running
I suggest to perform them now.

Then the next steps will be (assuming the vote has passed):
3) prepare the graduation proposal; see "Preparing a Charter" [**]
4) send the proposal to the Incubator general list for review before the
vote
5) start the graduation vote in the Incubator general list; see "The
Recommendation Vote" [***]

Then (if the recommendation vote will be successful) we will submit the
resolution to the Board.

Regards,

Jacopo

[*]
https://incubator.apache.org/guides/graduation.html#community_graduation_vote
[**] https://incubator.apache.org/guides/graduation.html#preparing_a_charter
[***]
https://incubator.apache.org/guides/graduation.html#the_recommendation_vote
On Sun, Dec 17, 2017 at 5:21 PM, Sergio Fernández <wik...@apache.org> wrote:

> Right. Sorry for the confusion. When I said "committed" I wanted to say
> people engadget with the project after graduation, so PMC members in short.
>
> I believe Daniel already got this list pretty clear.
>
> On Dec 16, 2017 14:07, "Ralph Goers" <ralph.go...@dslextreme.com> wrote:
>
> > The board needs a list of the PMC members, not necessarily committers,
> > although it is unusual that a podling will become a TLP with committers
> who
> > aren’t PMC members.
> >
> > Ralph
> >
> > > On Dec 15, 2017, at 10:37 AM, Sergio Fernández <wik...@apache.org>
> > wrote:
> > >
> > > HI Daniel,
> > >
> > > the graduation resolution is a formal text that has to be submitted to
> > the
> > > ASF Board to communicate the graduation of the podling. Further
> > information
> > > at
> > > https://incubator.apache.org/guides/graduation.html#
> > submission_of_the_resolution_to_the_board
> > >
> > > It has to be drafted internally, voted first by the PPMC and secondly
> by
> > > the IPMC (not that different than voting a release).
> > >
> > > The text is pretty standard. The two main things to decide are: 1) who
> is
> > > going to be the Freemarker VP 2) list of committed to the new TLP
> > >
> > > I drafted one in the past
> > > https://svn.apache.org/repos/asf/marmotta/graduation/resolution.txt
> > than we
> > > can use as an example for moving forward with this.
> > >
> > > On Fri, Dec 15, 2017 at 5:09 AM, Daniel Dekany <ddek...@apache.org>
> > wrote:
> > >
> > >> I would like to revie this thread.
> > >>
> > >> Again, I would like to encourage others to check if we miss some
> > >> formal requirements, other than the VOTE thread here. I bet there are
> > >> some little things at least.
> > >>
> > >> Also https://incubator.apache.org/guides/graduation.html talks about
> > >> things like propose a "resolution" general incubator list before a
> > >> VOTE, etc. (OFBiz is brough up as a good example there.) Anyone
> > >> intends to tackle these?
> > >>
> > >>
> > >> Wednesday, November 8, 2017, 1:34:24 AM, Daniel Dekany wrote:
> > >>
> > >>> So, we have released 2.3.27, and has changed the domain of the home
> > >>> page (not of try.freemarker.org though... is that a problem?).
> What's
> > >>> next? Anyone?
> > >>>
> > >>>
> > >>> Monday, October 23, 2017, 3:18:54 PM, Daniel Dekany wrote:
> > >>>
> > >>>> Monday, October 23, 2017, 4:04:54 PM, Jacopo Cappellato wrote:
> > >>>>
> > >>>>> +1 for the migration.
> > >>>>> And right after that I think we should start the graduation
> process.
> > >>>>
> > >>>> Agreed regarding graduation. (We certainly should release 2.3.27
> > >>>> before that, but it's very close anyway, hopefully.)
> > >>>>
> > >>>> Related:
> > >>>>
> > >>>> -
> > >>>> https://cwiki.apache.org/confluence/display/FREEMARKER/
> > >> Apache+FreeMarker+Project+Maturity+Model
> > >>>>
> > >>>> - http://incubator.apache.org/projects/freemarker.html:
> > >>>>  Here some dates are year only.
> > >>>>
> > >>>> - https://whimsy.apache.org/roster/pp

Re: try.freemarker.apache.org instead of try.freemarker.org?

[Jacopo Cappellato]

I don't know if there will be issues with a certificate for sub-sub domain
but I agree with the extra careful approach outlined in your email because
I think it is better to cope with some small headaches now but do our best
to be prepared asap for a successful graduation.

Thanks,

Jacopo

On Wed, Nov 29, 2017 at 9:51 AM, Daniel Dekany  wrote:

> Just as a reminder, I'm planning to request try.freemarker.apache.org,
> from Infra and then redirect try.freemarker.org to it, because I'm
> worried that the IPMC will dislike that we use try.freemarker.org as
> the canonical address of the online template tester. It will also use
> https and a LetsEncrypt certificate (we can't use the *.apache.org
> cert on a VM).
>
> BTW, using a sub-sub domains is a bit extreme. I'm not aware of any
> gotchas in out case, but if anyone is aware some, like LetsEncrypt
> doesn't support them or something, please stop me! (Also, as this way
> we will receive the cookies of freemarker.apache.org, but certainly we
> will able to cope with that, if it ever causes a problem.)
>
> Any comments? And do you (especially PPMC members) agree?
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [ANNOUNCE] Apache FreeMarker 2.3.27-incubating released

[Jacopo Cappellato]

Congratulations!

Jacopo

On Sat, Nov 4, 2017 at 1:20 AM, Daniel Dekany  wrote:

> Thank you Woonsan!
>
> Anything to improve on the release process itself, and on its
> documentation? (I did some updates in the how-to, on the places where
> you had questions, so apart from those.)
>
>
> Friday, November 3, 2017, 2:34:34 PM, Woonsan Ko wrote:
>
> > The Apache FreeMarker (incubating) community is pleased to announce
> > the release of Apache FreeMarker 2.3.27 (incubating).
> >
> > Change log:
> > http://freemarker.org/docs/versions_2_3_27.html
> >
> > You can get binary and source packages from here:
> > http://freemarker.org/freemarkerdownload.html
> >
> > Or with Maven:
> >
> >   
> > org.freemarker
> > freemarker
> > 2.3.27-incubating
> >   
> >
> > Disclaimer: Apache FreeMarker 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.
> >
> >
> > Woonsan Ko
> > on behalf of Apache FreeMarker Podling Project Management Committee
> >
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Changing official domain to freemarker.apache.org now? Was: Migrating [try.]freemarker.org to HTTPS, anyone?

[Jacopo Cappellato]

On Tue, Oct 24, 2017 at 3:12 AM, Ralph Goers 
wrote:

> There is no requirement that you ever get rid of the freemarker.org
> domain. This is not the first project to have its own domain.
>

Exactly. For example OFBiz owns the ofbiz.org domain since before the
graduation (2006) and since then the ASF has maintained the redirection to
the canonical ofbiz.apache.org.

Jacopo

Re: Changing official domain to freemarker.apache.org now? Was: Migrating [try.]freemarker.org to HTTPS, anyone?

[Jacopo Cappellato]

+1 for the migration. And right after that I think we should start the
graduation process.

Jacopo

On Mon, Oct 23, 2017 at 11:48 AM, Daniel Dekany  wrote:

> As this issue that we aren't using an apache.org domain comes up again
> and again, I propose that we switch to freemarker.apache.org now. Also
> to try.freemarker.apache.org. Anybody for or against it?
>
>
> Friday, October 20, 2017, 10:18:01 PM, Ralph Goers wrote:
>
> >
> >> On Oct 20, 2017, at 5:59 AM, Daniel Dekany  wrote:
> >>
> >> Friday, October 20, 2017, 12:24:30 PM, Jacques Le Roux wrote:
> >>
> >>> Le 01/10/2017 à 23:27, Daniel Dekany a écrit :
>  Sunday, October 1, 2017, 8:26:53 PM, Jacques Le Roux wrote:
> 
> > Le 23/09/2017 à 08:44, Daniel Dekany a écrit :
> >> Friday, September 22, 2017, 11:17:59 PM, Jacques Le Roux wrote:
> >>
> >>> Le 22/09/2017 à 22:22, Daniel Dekany a écrit :
>  Google doesn't like plain HTTP sites as we know (SEO), also I hear
>  that starting from October they want to show warning in Chrome if
> you
>  have forms on your page. We do have forms... On all page under
>  http://freemarker.org/docs/ there's a search field, and
>  http://try.freemarker.org/ is nothing but a form.
> 
>  Anyone want to tackle this? Or part of this?
> 
> >>> I did that for OFBiz. I can have a look before October.
> >> That would be great, thanks!
> >>
> >>> Jacques
> >>>
> >>>
> > Sorry, OFBiz still being my priority, I was not able to do it yet.
> > But I should be able to start this week, most likely Monday...
>  No problem, and thanks for keep us informed!
> 
> > Jacques
> >>> Sorry again, my current contract has changed and I'll not be available
> before November
> >>> I'm though trying the new release in OFBiz right now, so far all seems
> OK :)
> >>
> >> The latest Chrome doesn't (yet?) show any warnings on our site, so no
> >> problem. (Maybe they only do it if there's a password filed, for now.)
> >>
> >> Thanks for the checking the release!
> >
> > I should also point out that in the last board report the issue of
> > freemarker not yet having an apache.org  web
> > site came up. I would suggest that the project make that transition
> > sooner than later if graduation is desired.
> >
> > Ralph
> >
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [VOTE] Release Apache FreeMarker 2.3.27 (incubating)

[Jacopo Cappellato]

+1 (binding)

Jacopo

On Mon, Oct 16, 2017 at 9:30 PM, Woonsan Ko  wrote:

> Hi all,
>
> Please vote on releasing FreeMarker 2.3.27-incubating! If this voting
> passes, another similar voting will be started on
> gene...@incubator.apache.org, and if that passes too, then we can
> release this version.
>
> Note that because there weren't many deep changes since
> 2.3.26-incubating, we have no Release Candidate this time. Thus, it's
> important that you don't skip testing this release with your dependent
> projects.
>
> Release Notes:
> http://freemarker.org/builds/2.3.27-voting/documentation/_ht
> ml/versions_2_3_27.html
>
> Before proceed, you should know that FreeMarker 2.3.x, for a long
> time, always releases a normal and a "gae" variant on the same time,
> which are technically two independent source trees (Git branches). The
> "gae" variant contains a few small modification in the Java source
> code to be Google App Engine compliant, and has freemarker-gae as the
> Maven artifact name. Otherwise the normal and the "gae" branches are
> identical. Hence they will be voted on together.
>
> The commits to be voted upon are:
> - Normal (non-gae) variant:
>   https://git-wip-us.apache.org/repos/asf?p=incubator-freemark
> er.git;a=commit;h=8e501b8ab83fb7d312791a4907ca94ef8acaf3e5
>   Commit hash: 8e501b8ab83fb7d312791a4907ca94ef8acaf3e5
> - "gae" variant:
>   https://git-wip-us.apache.org/repos/asf?p=incubator-freemark
> er.git;a=commit;h=cf2ae45d174d07a38d096958a44977cb79b1a68d
>   Commit hash: cf2ae45d174d07a38d096958a44977cb79b1a68d
>
> The artifacts to be voted upon are located here:
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.27-incubating/source/
> where the source release artifacts are:
> - Normal (non-gae) variant:
>   apache-freemarker-2.3.27-incubating-src.tar.gz
> - "gae" variant:
>   apache-freemarker-gae-2.3.27-incubating-src.tar.gz
>
> See the README inside them for build instructions!
>
> The release artifacts are signed with the following key:
> https://pgp.mit.edu/pks/lookup?op=vindex=on;
> search=0xA25D65D27C13ADCE
>
> Note that for convenience, we also provide binaries:
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.27-incubating/binaries/
> and Maven artifacts in the ASF staging repositories:
> - https://repository.apache.org/content/repositories/staging/o
> rg/freemarker/freemarker/2.3.27-incubating/
> - https://repository.apache.org/content/repositories/staging/o
> rg/freemarker/freemarker-gae/2.3.27-incubating/
>
> Please try out the package and vote!
>
> The vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached.
>
> [ ] +1 Release this package as Apache FreeMarker 2.3.27-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Please add "(binding)" if your vote is binding.
>
>
> Woonsan Ko
> on behalf of the Apache FreeMarker project team
>

Re: Preparing for 2.3.27 - please check the change log

[Jacopo Cappellato]

+1

Jacopo

On Wed, Sep 20, 2017 at 8:13 PM, Daniel Dekany  wrote:

> We have quite a few bug fixes piled up, so I it's time for a new
> release. There's a few very minor new feature as well (mostly in
> response to issues raised on StackOverflow). Please review them, also
> tell if you want some more changes to get into 2.3.27!
>
> Here's the change log (so far):
> http://freemarker.org/builds/fm2.3.27/versions_2_3_27.html
>
> I plan to start the usual release process early next week.
>
> --
> Best regards,
>  Daniel Dekany
>
>

Re: Please reivew (then sign) our July poddlin report

[Jacopo Cappellato]

Looks good. Signed.

Thank you

Jacopo

On Sun, Jul 2, 2017 at 12:05 AM, Daniel Dekany  wrote:

> PPMC members, please review (then sign) our July poddlin report!
> https://wiki.apache.org/incubator/July2017
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: FreeMarker Online Tester legal status and hosting

[Jacopo Cappellato]

I have pinged the Infra team in HipChat and they are wating for the
assignee of the ticket to come online and provide some feedback.
I will keep you posted (but you can also join the chat room if you like at
https://apache.hipchat.com/chat/room/669587 )

Jacopo

On Wed, May 31, 2017 at 10:45 AM, Daniel Dekany <ddek...@apache.org> wrote:

> Infra doesn't answer after several attempts in the recent months, for
> whatever reason, so I think at this point it's reasonable to go with
> the assumption that they never will, and we need to find some other
> persons to speak to. So, should I bring this up on incubator-general,
> or where?
>
>
> Tuesday, May 2, 2017, 7:49:18 PM, Jacques Le Roux wrote:
>
> > Le 02/05/2017 à 13:23, Daniel Dekany a écrit :
> >> Tuesday, May 2, 2017, 12:19:47 PM, Jacopo Cappellato wrote:
> >>
> >>> On Tue, May 2, 2017 at 11:42 AM, Daniel Dekany <ddek...@apache.org>
> wrote:
> >>>
> >>>> We have received the source code donation of said service form
> >>>> Kenshoo. Pradeep has changed the license headers and renamed the
> >>>> packages, and did some other cleanup. While we plan to do further
> >>>> development, the service works, and should be deployed to somewhere,
> >>>> so that it can take over from http://freemarker-online.kenshoo.com/.
> >>>>
> >>>> Can someone help in moving this issue ahead:
> >>>> https://issues.apache.org/jira/browse/INFRA-13246 "Create a demo VM
> >>>> for the Freemarker project". Infra has certainly no right to decide if
> >>>> we can receive such a resource, and we should bringing this up on the
> >>>> right forum. On incubator-general is guess.
> >>>>
> >>>> Also, anyone is aware of any legal obstacle that prevents deploying
> >>>> this service to Apache infrastructure?
> >>>>
> >>> I don't and I think we can proceed to contact infra to setup the
> instance
> >>> and work with them to resolve any possible technical concern.
> >> But Infra doesn't progress with that issue. It was created on January
> >> the 7th. I have added a new comment now (though it's "Internal", so I
> >> don't know if you see it):
> >>
> >>What's need for this issue to progress? We could deploy the service
> >>right now if we had a virtual machine. Ideally, it should be visible
> >>under http://freemarker.org/tester/ (ASF owns the freemarker.org
> >>domain), or http://tester.freemarker.org/.
> >>
> >>> It is great to see such a great progress on this, kudos!
> >>>
> >>> Jacopo
> > I will ask infra on Hipchat, a nudge often works ;)
> >
> > Jacques
> >
> >
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: FreeMarker Online Tester legal status and hosting

[Jacopo Cappellato]

On Tue, May 2, 2017 at 11:42 AM, Daniel Dekany  wrote:

> We have received the source code donation of said service form
> Kenshoo. Pradeep has changed the license headers and renamed the
> packages, and did some other cleanup. While we plan to do further
> development, the service works, and should be deployed to somewhere,
> so that it can take over from http://freemarker-online.kenshoo.com/.
>
> Can someone help in moving this issue ahead:
> https://issues.apache.org/jira/browse/INFRA-13246 "Create a demo VM
> for the Freemarker project". Infra has certainly no right to decide if
> we can receive such a resource, and we should bringing this up on the
> right forum. On incubator-general is guess.
>
> Also, anyone is aware of any legal obstacle that prevents deploying
> this service to Apache infrastructure?
>

I don't and I think we can proceed to contact infra to setup the instance
and work with them to resolve any possible technical concern.
It is great to see such a great progress on this, kudos!

Jacopo

New ASF Member from FreeMarker Community

[Jacopo Cappellato]

Good news: Daniel Dekany from the FreeMarker community has been invited to
become member of the Apache Software Foundation.

Many congratulations Daniel!!!

Jacopo

Re: Please reivew (then sign) our April poddlin report

[Jacopo Cappellato]

Thank you, signed!

Jacopo

On Mon, Apr 3, 2017 at 12:05 PM, Daniel Dekany  wrote:

> Here it is:
> https://wiki.apache.org/incubator/April2017
>
> I have applied all changes Jacopo has recommended.
>
> I have added a sentence about the age of the project, so that they
> will be in the right context when reading about the community growth
> problem.
>
> Note that they have added a point about "How would you assess the
> podling's maturity?", which I have filled.
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Poddling report draft - needs discussion

[Jacopo Cappellato]

The reports looks great to me but see some minor comments inline:

On Sun, Apr 2, 2017 at 12:35 PM, Daniel Dekany <ddek...@apache.org> wrote:

> See below. It's more "interesting" than usual (graduation issues...),
> so we should definitely discuss this before I upload it.
>
>
> FreeMarker
>
> FreeMarker is a template engine, i.e. a generic tool to generate text
> output based on templates. FreeMarker is implemented in Java as a
> class library for programmers.
>
> FreeMarker has been incubating since 2015-07-01.
>
> Three most important issues to address in the move towards graduation:
>
>   The project is still struggling to find a way to "convert" active
>   users into committers.


I would change the the above sentence to convey a more positive message:

"The project is constantly exploring new ways to "convert" active users
into committers, since we have a very large user base and a rather small
group of committers."


>  This was actually expected, given the age

  (and topic) of the project.

While the FreeMarker 3 line, which was
>   started quite recently, will be much more appealing for
>   contributors, development on that direction will certainly take a
>   long time. In other respects the project is mature and ready for
>   graduation.
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   We are eager to graduate, but we don't think that the problem with
>   the number of active contributors will be solved in the near future.
>

As you know, in my opinion FreeMarker is ready to become a TLP; with this
said, personally
I would change the above sentence into:

"We are eager to graduate but we were hoping to increase the number of
active contributors more before the graduation. However, since the
community is slowly growing and we have completed all the Incubation tasks,
we are now more inclined to discuss the graduation now and then proceed as
a top level project."


>   One of the practical problems with being stuck in the Incubator is
>   that many users stick to the last non-incubating release as that has
>   no "-incubating" in the Maven coordinates, missing out on fixes and
>   features done in the recent two years. We brought up the issue with
>   the Maven coordinate on gene...@incubator.apache.org (saying that
>   because our Maven coordinate doesn't contain "apache", "incubating"
>   is meaningless in there), but there was no consensus.
>
> How has the community developed since the last report?
>
>   We have welcomed a new committer, Woonsan Ko.
>
>   A few new people has shown up to help out with our Twitter channel
>   (such as making a new logo for it, and helping to make it more
>   active), and to work modernizing our build scripts.
>
>   The starting of the FreeMarker 3 branch has generated some technical
>   discussion.
>
> How has the project developed since the last report?
>
>   We have created a Project Maturity Model page at
>   https://cwiki.apache.org/confluence/display/FREEMARKER/
> Apache+Freemarker+Project+Maturity+Model
>
>   We have started the FreeMarker 3 branch, whose goal is to get rid of
>   backward compatibility burden that holds back the project quite much
>   at this point, and doesn't allow us to fully capitalize on the
>   experiences of the last 15 years. In out current situation it's also
>   very important that then new branch, as it advances, will be
>   technically far more appealing than the legacy branch for
>   contributors. Also, the new branch uses org.apache packages and
>   Maven coordinates (which FreeMarker 2 can't do).
>
>   We have received a bigger contribution from Kenshoo, the source code
>   of an online template evaluator service, which we plan to use on our
>   home page, helping users to try and learn the template language.
>
>   We have released a new micro version (2.3.26), focuses on fixes and
> smaller improvements.
>

I would add:

"This is the third (is it right? please check) release issued during the
incubation"


>
>   We have added a How-To page for committers (http://freemarker.org/
> committer-howto.html),
>   which gives detailed instructions on making releases, handling pull
> requests,
>   updating the project home page, and more.
>
>   We have worked some on our Twitter channel, such as we have a new
>   logo and some posts.
>
> When were the last committers or PMC members elected?
>
>   2017-02-13 Woonsan Ko, committer (non-PMC)
>
> Date of last release:
>
>   2017-03-25
>
> Signed-off-by:
>
>   [ ](freemarker) Jacopo Cappellato
>   [ ](freemarker) Jean-Frederic Clere
>   [ ](freemarker) David E. Jones
>   [ ](freemarker) Ralph Goers
>   [ ](freemarker) Sergio Fernández
>

I like it! Thanks

Jacopo


>
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [VOTE] Release Apache FreeMarker 2.3.26 (incubating)

[Jacopo Cappellato]

+1 (binding)

signature is ok
sha checksum is ok
md5 checksum is ok
build and tests are successful
tests on Apache OFBiz release branch 15.12 are successful

Jacopo



On Wed, Mar 15, 2017 at 10:57 PM, Daniel Dekany  wrote:

> Hi all,
>
> Please vote on releasing FreeMarker 2.3.26-incubating! If this voting
> passes, another similar voting will be started on
> gene...@incubator.apache.org, and if that passes too, then we can
> release this version.
>
> Note that because there weren't many deep changes since
> 2.3.25-incubating, we have no Release Candidate this time. Thus, it's
> important that you don't skip testing this release with your dependant
> projects.
>
> Release Notes:
> http://freemarker.org/builds/2.3.26-voting/documentation/_
> html/versions_2_3_26.html
>
> Before proceed, you should know that FreeMarker 2.3.x, for a long
> time, always releases a normal and a "gae" variant on the same time,
> which are technically two independent source trees (Git branches). The
> "gae" variant contains a few small modification in the Java source
> code to be Google App Engine compliant, and has freemarker-gae as the
> Maven artifact name. Otherwise the normal and the "gae" branches are
> identical. Hence they will be voted on together.
>
> The commits to be voted upon are:
> - Normal (non-gae) variant:
>   https://git-wip-us.apache.org/repos/asf?p=incubator-
> freemarker.git;a=commit;h=876fffcfaf66bd212b02a931fdd2c69f6e0c297e
>   Commit hash: 876fffcfaf66bd212b02a931fdd2c69f6e0c297e
> - "gae" variant:
>   https://git-wip-us.apache.org/repos/asf?p=incubator-
> freemarker.git;a=commit;h=43564859db4bec23e161c6fa5a32882e8bd9e40a
>   Commit hash: 43564859db4bec23e161c6fa5a32882e8bd9e40a
>
> The artifacts to be voted upon are located here:
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.26-incubating/source/
> where the source release artifacts are:
> - Normal (non-gae) variant:
>   apache-freemarker-2.3.26-incubating-src.tar.gz
> - "gae" variant:
>   apache-freemarker-gae-2.3.26-incubating-src.tar.gz
>
> See the README inside them for build instructions!
>
> The release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/ddekany.asc
> (Note: At the moment it looks slightly outdated compared to the
> source,
> http://pgp.mit.edu/pks/lookup?op=vindex=0x1939A2520BAB1D90, but
> I assume it will catch up eventually.)
>
> Note that for convenience, we also provide binaries:
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/
> engine/2.3.26-incubating/binaries/
> and Maven artifacts in the ASF staging repository:
> https://repository.apache.org/content/repositories/staging/
> org/freemarker/freemarker/2.3.26-incubating/
>
> Please try out the package and vote!
>
> The vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached.
>
> [ ] +1 Release this package as Apache FreeMarker 2.3.26-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Please add "(binding)" if your vote is binding.
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: New committer: Woonsan Ko

[Jacopo Cappellato]

Welcome Woonsan!

Jacopo

On Sun, Feb 12, 2017 at 7:42 PM, Daniel Dekany  wrote:

> The Project Management Committee (PMC) for Apache FreeMarker
> (incubating) has invited Woonsan Ko to become a committer and we are
> pleased to announce that he has accepted.
>
> Woonsan Ko has been an active FreeMarker user for years while using
> FreeMarker as primary template engine for web content management
> applications. He is willing to contribute more and help the Apache
> FreeMarker community more proactively. He is working at Hippo, a
> BloomReach company, as a lead solution architect. He has been
> contributing to Apache Portals and Apache Commons SCXML projects as
> well for years.
>
> Being a committer enables easier contribution to the project since
> there is no need to go via the patch submission process. This should
> enable better productivity.
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [RESULT][VOTE] Which logo?

[Jacopo Cappellato]

On Wed, Feb 1, 2017 at 9:36 AM, Julien NICOLAS 
wrote:

>
> I don't know what is needed but I transfert all rights of my logos to the
> freemarker project. :)


Julien has already filed a ICLA so we should be good with that.

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

Oh yes, I see the same when I open the page in a different browser! Please
ignore and thanks.

Jacopo

On Mon, Jan 23, 2017 at 4:17 PM, Daniel Dekany <ddek...@freemail.hu> wrote:

> Monday, January 23, 2017, 4:00:06 PM, Jacopo Cappellato wrote:
>
> > On Mon, Jan 23, 2017 at 3:39 PM, Daniel Dekany <ddek...@freemail.hu>
> wrote:
> >
> >>
> >> I don't know, it's visible for me. Maybe you haven't waited for the
> >> publishing commit, or it's a browser cache issue?
> >>
> >>
> > Weird... do you see the link under the COMMUNITY group in the left bar?
>
> Yes, it looks like this:
>
> Community
>
> Report bugs
> Bugs still in the old tracker
> Report security vulnerability
> Ask help on Stack Overflow
> ...
>
> > Jacopo
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

On Mon, Jan 23, 2017 at 3:36 PM, Daniel Dekany  wrote:

>
> I have just went ahead and published what you have written on the site
> (with some minor edits).
>
> The related pages:
> http://freemarker.org/report-security-vulnerabilities.html
> And I have also added this:
> http://freemarker.org/committer-howto.html#handle-security-vulnerabilities
>
> I have also updated the wiki page to to refer to these under QU30, and
> set its status to YES.
>

Thanks, they look great to me.

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

On Mon, Jan 23, 2017 at 3:39 PM, Daniel Dekany  wrote:

>
> I don't know, it's visible for me. Maybe you haven't waited for the
> publishing commit, or it's a browser cache issue?
>
>
Weird... do you see the link under the COMMUNITY group in the left bar?

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

Hi Daniel,

thanks for your commit. I have noticed that there is no link to the new
security page in the left bar but it used to generate one when I tested in
my local box. Is it intentional or I am missing something?

Jacopo

On Mon, Jan 23, 2017 at 8:45 AM, Jacopo Cappellato <
jacopo.cappell...@gmail.com> wrote:

> On Sun, Jan 22, 2017 at 6:10 PM, Daniel Dekany <ddek...@freemail.hu>
> wrote:
>
>>
>> Thanks! But, do all PMC members get a notification if there's a mail
>> waiting for moderation at private@freemarker.i.a.o? Does somebody know
>> that (or else I will try it)?
>>
>
> Only the mailing list moderators will receive the message and I am not
> sure who they are currently. I think I am (I think I have received some
> "moderator" email from private@freemarker) and you should too.
> We should ask Infra about the list of moderators for our three lists and
> also ask them to update it with the people that are volunteering for this
> task.
> And we can also ask infra to setup a security@freemarker list.
> But we could also proceed with the above two steps right after a
> successful graduation when FreeMarker will be a full-fledged top level
> project.
> What do you think?
>
> Jacopo
>
>

Re: incubator-freemarker-docgen git commit: Changed footer layout to accept arbitrary long copyright text. Added copyrightSuffix setting, where you can add the trademark notes and such.

[Jacopo Cappellato]

On Fri, Jan 6, 2017 at 8:39 PM,  wrote:

> Repository: incubator-freemarker-docgen
> Updated Branches:
>   refs/heads/master 05ddf9339 -> f968b192e
>
>
> Changed footer layout to accept arbitrary long copyright text. Added
> copyrightSuffix setting, where you can add the trademark notes and such.
> [...]
>
> http://git-wip-us.apache.org/repos/asf/incubator-freemarker-docgen/blob/
> f968b192/src/main/org/freemarker/docgen/templates/footer.ftlh
> --
> diff --git a/src/main/org/freemarker/docgen/templates/footer.ftlh
> b/src/main/org/freemarker/docgen/templates/footer.ftlh
> index ac43e17..29d9a27 100644
> --- a/src/main/org/freemarker/docgen/templates/footer.ftlh
> +++ b/src/main/org/freemarker/docgen/templates/footer.ftlh
>
> @@ -73,7 +72,8 @@
>
>  © ${copyrightStartYear?string('0')
> }<#rt>
>  <#lt><#if transformStartTime?string('')?number !=
> copyrightStartYear>–${transformStartTime?string('')}
> -http://schema.org/Organization;
> itemprop="copyrightHolder" 
> href="http://freemarker.org;>${copyrightHolder}.
> All rights reserved.<#t>
> +http://schema.org/Organization;
> itemprop="copyrightHolder" href="http://freemarker.org;>$
> {copyrightHolder}<#t>
> +<#if copyrightSuffix??>. ${copyrightSuffix}<#t>
>
>  
>

This is minor but I think we should change the url of the "copyright
holder" from freemarker.org to apache.org.

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

On Sun, Jan 22, 2017 at 6:10 PM, Daniel Dekany  wrote:

>
> Thanks! But, do all PMC members get a notification if there's a mail
> waiting for moderation at private@freemarker.i.a.o? Does somebody know
> that (or else I will try it)?
>

Only the mailing list moderators will receive the message and I am not sure
who they are currently. I think I am (I think I have received some
"moderator" email from private@freemarker) and you should too.
We should ask Infra about the list of moderators for our three lists and
also ask them to update it with the people that are volunteering for this
task.
And we can also ask infra to setup a security@freemarker list.
But we could also proceed with the above two steps right after a successful
graduation when FreeMarker will be a full-fledged top level project.
What do you think?

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

On Sun, Jan 22, 2017 at 2:44 PM, Daniel Dekany  wrote:

>
> Though it's still a good point that we should say something to the
> users... Right now, the best they can do is figuring out who the key
> personal are, and write to them privately.
>
>
This is a good point: I have created a pull request in which I propose a
simple page to describe how to report security vulnerabilities.

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

On Sat, Jan 21, 2017 at 2:56 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

>
> For QU30 we can easily ask infra to create a security ML.
> For the wiki page at least a link to http://www.apache.org/security
> /#vulnerability-handling would help.
>

We could, but we can also postpone this decision, even after graduation: in
fact it is not mandatory at all to have all questions resolved positively.

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

On Sat, Jan 21, 2017 at 2:56 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> [...]

Note that for instance OFBiz only links to its security ML from
> http://www.apache.org/security/projects.html
>
> BTW out of subject and it's maybe late for OFBiz (was not a requirement
> then), but why not creating a such page for OFBiz (I already suggested so
> months ago w/o answers)?


Jacques, may I ask you to not discuss OFBiz in this list?

Thank you

Jacopo

Re: FreeMarker Project Maturity Model Assessment

[Jacopo Cappellato]

Michael and I did our first pass at the Project's Maturity Model document:

https://cwiki.apache.org/confluence/display/FREEMARKER/Apache+Freemarker+Project+Maturity+Model

I think it is pretty much complete and clearly shows that this project is
based on healthy foundations and governed according to The Apache Way.
It would be nice if any of you could help adding some more details to the
questions LC20 and LC30, and in general your comments/edits are welcome!

Thanks,

Jacopo

On Sat, Jan 14, 2017 at 6:00 PM, Michael Brohl <michael.br...@ecomify.de>
wrote:

> Hi all,
>
> I have created a wiki page (https://cwiki.apache.org/confluence/x/KBUIB)
> inspired by the Apache ranger example and added the first responses for a
> start.
>
> Feel free to add, edit, remark. Any help is appreciated.
>
> Regards,
>
> Michael
>
>
> Am 07.01.17 um 16:55 schrieb Jacopo Cappellato:
>
>> Hi all,
>>
>>
>> in preparation to the FreeMarker project's graduation, it would be useful
>> to prepare the Project Maturity Model Assessment.
>>
>> For more information on the Project Maturity Model see:
>> http://community.apache.org/apache-way/apache-project-maturity-model.html
>>
>> This is an example of the answers provided by a project that is under
>> graduation vote now:
>>
>> https://cwiki.apache.org/confluence/display/RANGER/Apache+
>> Ranger+Project+Maturity+Model
>>
>> This is not mandatory, but I think that taking time to diligently complete
>> the answers may be useful for this project both as an internal assessment
>> and as a document that we will share to the Incubator PMC when they will
>> be
>> called to vote for the graduation.
>>
>> What do you think?
>> Any volunteer to create a page in our wiki that we could use to work at
>> the
>> document together?
>>
>> Kind regards,
>>
>> Jacopo
>>
>>
>
>

Re: Proposed Tweet re: Logo Vote

[Jacopo Cappellato]

On Fri, Jan 20, 2017 at 9:19 AM, Julien NICOLAS <julien.nico...@nereide.fr>
wrote:

> Hi Jacopo,
>
> First, you have really said that choosing a new logo shape and colour is a
> minor decision ?! This is because you don't know the power of the good
> colour ! XD
>

I didn't mean to say it is a *minor* decision! :-)
It is in fact an *important* decision that is probably easier to comment
than other more technical ones.

Regards,

Jacopo


>
> Then, I understand the explanation of the bike shed effect but, I'm quite
> sure this is because of taste. If a problem need to be fixed, the community
> will found a technical solution without starting a discussion on the colour
> of the method ^^. Add a colour issue in this problem, and the thread will
> be longer ;)
>
> Thanks for this sharing, I'll share it also :)
>
> Julien.
>
>
>
> On 19/01/2017 18:23, Jacopo Cappellato wrote:
>
>> On Thu, Jan 19, 2017 at 1:24 PM, Daniel Dekany <ddek...@freemail.hu>
>> wrote:
>>
>> ...
>>> (On the same time, the more technical questions remain unanswered. Not
>>> surprisingly anyway, so it's fine, I was just surprised how many are
>>> reading this list regularly, based on the number of vote answers.)
>>>
>>
>> Yeah quite natural :-)
>>
>> “the amount of discussion is inversely proportional to the complexity of
>> the topic that has been around for a long time”
>>
>>
>> See "the bike shed effect" for fun:
>> http://tribune.com.pk/story/201969/the-bike-shed-effect/
>>
>> Jacopo
>>
>>
>

Re: Proposed Tweet re: Logo Vote

[Jacopo Cappellato]

On Thu, Jan 19, 2017 at 1:24 PM, Daniel Dekany  wrote:

> ...
> (On the same time, the more technical questions remain unanswered. Not
> surprisingly anyway, so it's fine, I was just surprised how many are
> reading this list regularly, based on the number of vote answers.)


Yeah quite natural :-)

“the amount of discussion is inversely proportional to the complexity of
the topic that has been around for a long time”


See "the bike shed effect" for fun:
http://tribune.com.pk/story/201969/the-bike-shed-effect/

Jacopo

Re: [VOTE] Which logo, now with a new contender (#1.5)

[Jacopo Cappellato]

On Thu, Jan 19, 2017 at 1:30 PM, Daniel Dekany  wrote:

> A new choice! So now in theory I should cancel this vote and start a
> new one. But I guess we can be less formal in this case. After all,
> changing a logo is backward compatible (an almost disturbing feeling
> if you have maintained FM... <-; ).
>

:-)


>
> I change my vote to +1 for #1.5.
>

I am also going to change my vote with a +1 for #1.5

Jacopo


>
>
> Monday, January 16, 2017, 11:07:29 PM, Julien NICOLAS wrote:
>
> > Hello,
> >
> > I prefer #1.
> >
> > But... If I can provide a new one regarding comments
> > (https://drive.google.com/open?id=0B5BwTaGcWGtNS2VaTDhCcDVLQTQ) I prefer
> > #1.5 ;)
> >
> > Regards,
> >
> > Julien.
> >
> >
> > On 16/01/2017 12:11, Daniel Dekany wrote:
> >> We will replace our square logo at Twitter
> >> (https://twitter.com/freemarker), and probably will use the same logo
> >> in the future elsewhere too.
> >>
> >> Which one do you prefer from the *top* row (1, 2, 3)?
> >> https://drive.google.com/open?id=0B5BwTaGcWGtNLU0wQmFiUElFc2c
> >>
> >> (The bottom row is for file icons, but currently we won't use them
> >> anywhere.)
> >>
> >> Thanks for Julien Nicolas for providing these!
> >>
> >
> >
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Proposed Tweet re: Logo Vote

[Jacopo Cappellato]

+1
I like it, thanks

Il 19 Gen 2017 12:37 PM, "Sharan Foga"  ha scritto:

> Hi Everyone
>
> As we have a current vote in progress about the twitter logo, I'd like to
> tweet about it and maybe get some additional involvement from the
> freemarker twitter followers. The proposed tweet is as follow:
>
> - Help us choose our new twitter logo. Check out the options and vote for
> your favourite! https://s.apache.org/UuC1
>
> What do people think?
>
> Thanks
> Sharan
>

Re: [VOTE] Which logo?

[Jacopo Cappellato]

I like the first.

Jacopo

On Mon, Jan 16, 2017 at 12:11 PM, Daniel Dekany  wrote:

> We will replace our square logo at Twitter
> (https://twitter.com/freemarker), and probably will use the same logo
> in the future elsewhere too.
>
> Which one do you prefer from the *top* row (1, 2, 3)?
> https://drive.google.com/open?id=0B5BwTaGcWGtNLU0wQmFiUElFc2c
>
> (The bottom row is for file icons, but currently we won't use them
> anywhere.)
>
> Thanks for Julien Nicolas for providing these!
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Refining the Freemarker product description to follow trademark best practices

[Jacopo Cappellato]

On Thu, Jan 12, 2017 at 1:58 PM, Daniel Dekany  wrote:

>
> Huh? It's software. There are no FreeMarker cars and FreeMarker
> motorcycles and FreeMarker trucks ... FreeMarker is the product
> itself. It's not like BMW, it's like BMW i3, where BMW is Apache in
> our case. We use *that* as an adjective: Apache FreeMarker.
>

Well, actually both "Apache FreeMarker" and "FreeMarker" are trademarks of
the Apache Software Foundation; and we apply them to the project and our
product (the template engine).


> The rewording is quote convoluted in our case (since the rest of the
> sentence basically tells what a template engine is). But let's not
> waste time with it, I say. I would wait and see if they actually pick
> on this (I couldn't believe it...).


I am sure that no one will complain about this little detail; as you have
mentioned several other projects are doing something similar (including
OFBiz!): there is still not much awareness about how to treat trademarks.
This is just a small detail I have noticed but there is no need to take
action now if this community likes the current definition.

>
> This one at least doesn't hurt (much), so let's do it, and thanks for
> noticing.
>
>
Cheers,

Jacopo

Updated the Incubator STATUS page of the Freemarker project

[Jacopo Cappellato]

For your information, I have updated our STATUS page [*] with the following
minor changes:

1) mentioned that freemarker.org is owned by the ASF
2) added reference to the new Wiki space
3) added one missing date to the todo list (which is now complete!)

Jacopo


[*] http://incubator.apache.org/projects/freemarker.html

Re: Proposed Tweets for Freemarker Twitter Account

[Jacopo Cappellato]

Sharan,

I love each of them, thank you.
One small remark below:

On Tue, Jan 10, 2017 at 11:50 AM, Sharan Foga  wrote:

> [...]
> Interested in a simple Freemarker UI? Share your ideas and collaborate
> with us
> https://s.apache.org/yQUr


For clarity, this maybe should be reworded into:

"Interested in a simple online testing tool for Freemarker templates? Share
your ideas and collaborate with us"

Jacopo

Relevant extract from the Incubator report to the Board

[Jacopo Cappellato]

Hi all,

I would like to highlight the following paragraph from the draft of this
month's Incubator report:

==
The following appear to be close from maturity model:

  - Airflow
  - BatchEE
  - FreeMarker
  - Metron
==

We are getting closer to a successful graduation so let's keep going in the
right direction!

Jacopo

Re: Completing the copyright footer of the FreeMarker website

[Jacopo Cappellato]

On Fri, Jan 6, 2017 at 8:55 PM, Daniel Dekany  wrote:

> I have added the trademark notice to the footer (see on
> http://freemarker.org/). I have removed the "All rights reserved."
> part, as it weren't used on the OFBiz page either. (The Manual wasn't
> regenerated, so it's footer is not update... can wait until 2.3.26, I
> assume.)
>
>
Thank you Daniel, it looks great to me.

Jacopo

Re: Using Social Media to Help Promote Freemarker

[Jacopo Cappellato]

Hi Denis,

welcome! Please see inline:

On Sat, Jan 7, 2017 at 9:37 AM, Denis Bredelet  wrote:

> I am thinking of contributing a very simple UI for FreeMarker. Something
> able to read a single template and process it with a datamodel pulled from
> various sources (user interface window, properties file, XML file…)
>
> Would that be useful and help with advertising FreeMarker?
>

Definitely! Please see the thread "About a Freemarker template evaluator
service" in which we are discussing to setup an official project virtual
machine to provide this online service to our users.


>
> I have some code to use as a starting point on my website:
> http://bredelet.com/Denis/FreeMarker%20first%20steps.html
>
> Maybe this could come as a separate JAR to avoid loading UI classes
> unnecessarily.


We could figure out the technical details in the other thread.

Cheers,

Jacopo

Re: Using Social Media to Help Promote Freemarker

[Jacopo Cappellato]

On Thu, Jan 5, 2017 at 6:36 PM, Daniel Dekany  wrote:

> Hi,
>
> First of all, thanks for the offer! We don't really have social media
> presence (or other marking), so surely it would be helpful if we can
> improve there. Now, I'm not a social media consumer, and I'm pretty
> much only ever dealt with technical issues, so I'm quite frankly
> clueless regarding the content.


I totally understand what you mean :-) You and I are on the same page

Especially as it's a quite small
> project, compared to something like OfBiz, there are fewer happenings
> too, and they mostly just dry things like some technical stuff being
> fixed. Actually, sometimes there's a new feature that can be
> interesting technically, and perhaps someone could post something like
> a mini article about that, somewhere. Other than that... any ideas,
> directions?
>

I had the same concerns with OFBiz but then... Sharan came and the activity
became more interesting!
Maybe what we could do is the following:
1) Daniel: do you have access to this account [*]? Or do you know who could
own it? The first step would be to gain access to it
2) Sharan: maybe you could propose some tweets to this list and then, after
community approval, post them there? and maybe, after the first satisfying
ones, you could post them directly and we will review them and fine tune
our messages over time?

All in all, it would be nice to make some good noise about FreeMarker :-)

Jacopo

[*] https://twitter.com/freemarker

Re: About a Freemarker template evaluator service

[Jacopo Cappellato]

On Tue, Jan 3, 2017 at 4:15 PM, Christoph Rüger 
wrote:

> +1
>
> watch out for security / template injection attacks: e.g. see
> http://blog.portswigger.net/2015/08/server-side-template-injection.html
>
> set
>
> configuration.setNewBuiltinClassResolver(TemplateClassResolver.
> ALLOWS_NOTHING_RESOLVER);
>
>
Thank you Christoph, much appreciated.
And many thanks for filing the ICLA for FreeMarker (we have received it
yesterday) and for your help to the project!

Jacopo

Re: Comitter how-to page, step-by-step instructions for making releases

[Jacopo Cappellato]

On Thu, Jan 5, 2017 at 1:32 AM, Daniel Dekany  wrote:

> I did and bravely published a page to help future Committers (by which
> I mean people who can commit directly into the Apache repo, and
> certainly can do releases too). It's mostly to help in technical
> things, such as it describes how to make a FreeMarker release. But
> there's some project policies there too. Please take look, tell me
> what to change, what to add:
>
> http://freemarker.org/committer-howto.html
>
> If anyone wants to edit it, it's here:
> https://git-wip-us.apache.org/repos/asf/incubator-freemarker-site.git.
> GitHub mirror: https://github.com/apache/incubator-freemarker-site.
> Branch: master
> File: src/main/docgen/book.xml
>
> --
> Thanks,
>  Daniel Dekany
>
>
Daniel, thank you for writing it down, it is a great resource and I wish
all other Apache projects had similar ones: it would make life easier to
new committers and release managers.
I may have some minor editing (that I will submit as a GitHub pull request)
but it would be great if others in this community may review it and provide
their feedback, proof read it etc...

Jacopo

Re: About a Freemarker template evaluator service

[Jacopo Cappellato]

Thank you Jacques! Are you going to submit the request to the Infra team?
As soon as we have it setup we will plan the next moves. Please keep this
list posted with any progress or questions you may have to complete this
task.

Jacopo

On Tue, Jan 3, 2017 at 12:53 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Le 03/01/2017 à 09:32, Jacopo Cappellato a écrit :
>
>> Hi all,
>>
>> a couple of days ago Daniel brought to my attention the site/service:
>>
>> http://freemarker-online.kenshoo.com/
>>
>> They provide a nice online tool to evaluate any Freemarker template by
>> providing the template code and its context.
>>
>> Wouldn't be nice is we could offer that or a similar service to the users
>> and potential adopters of Freemarker? I think it would be a very useful
>> tool and also a good mechanism to attract new consumers.
>>
>> If there is an interest in this community then we could move in two
>> directions:
>>
>> 1) get in touch with the maintainers of freemarker-online and see if they
>> are interested to contribute their work [*] or join our community and help
>> to build a similar one here; if they are not interested then we could
>> discuss if it would make sense to build our own here
>>
>> 2) get in touch with the Infra team and explore the possibility to set up
>> a
>> virtual machine to dedicated to our project that we could use to deploy a
>> similar service, from our official website
>>
>> I can volunteer to try to get in touch with them (#1); any volunteers for
>> #2 (or even #1)?
>>
>> Kind regards,
>>
>> Jacopo
>>
>> [*] which is licensed with the AL2.0 and available here:
>> https://github.com/kenshoo/freemarker-online
>>
>> Hi Jacopo,
>
> I can take care of 2, I'm used to these kind of things for OFBiz
> I guess 1 is a prerequisite and I'm not well placed for this task.
>
> Jacques
>
>

Re: PPMC members, please check our January Poddling Report!

[Jacopo Cappellato]

On Wed, Jan 4, 2017 at 4:39 PM, David E Jones  wrote:

>
> Thank you Jacopo. Looking at it again a little bit ago it still shows as
> immutable. My guess is that my permission got
> reset and I'll need to request it again. It's very helpful that you signed
> it for me as I'm on site with a client today
> and not sure how quickly someone will get to adding the permission anyway.
>
> -David
>
>
Thank you David! I was unsure if it was appropriate for me to edit it for
you and I am glad it was helpful :-)

Jacopo

Re: PPMC members, please check our January Poddling Report!

[Jacopo Cappellato]

Signed off! Thank you

Jacopo

On Tue, Jan 3, 2017 at 10:26 AM, Daniel Dekany <ddek...@freemail.hu> wrote:

> I have added our report to
> https://wiki.apache.org/incubator/January2017. PPMC members, please
> read it, and sign it off if you agree!
>
>
> Tuesday, January 3, 2017, 8:53:12 AM, Jacopo Cappellato wrote:
>
> > On Mon, Jan 2, 2017 at 8:18 PM, Daniel Dekany <ddek...@freemail.hu>
> wrote:
> >
> >>
> >> Is there any "political" reason for not mentioning that we also plan
> >> to try to make the project more attractive and more approachable by
> >> making a branch which drops the very much significant legacy burden?
> >> Or it's not a good idea until it's only a plan.
> >
> >
> > It makes perfect sense to add what you have proposed to the report; in
> fact
> > I think that in our last report there was already a mention to it. Will
> you
> > take care of updating/completing the report and add it to the official
> Wiki
> > page?
> >
> > Thanks,
> >
> > Jacopo
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [DRAFT] FreeMarker report - January 2017

[Jacopo Cappellato]

It would be also great if any of you could write a short summary (i.e. a
sentence or two) of the changes to the codebase we did in the last quarter
and add it to the section "How has the project developed since the last
report?"

Jacopo

On Tue, Jan 3, 2017 at 8:53 AM, Jacopo Cappellato <
jacopo.cappell...@gmail.com> wrote:

> On Mon, Jan 2, 2017 at 8:18 PM, Daniel Dekany <ddek...@freemail.hu> wrote:
>
>>
>> Is there any "political" reason for not mentioning that we also plan
>> to try to make the project more attractive and more approachable by
>> making a branch which drops the very much significant legacy burden?
>> Or it's not a good idea until it's only a plan.
>
>
> It makes perfect sense to add what you have proposed to the report; in
> fact I think that in our last report there was already a mention to it.
> Will you take care of updating/completing the report and add it to the
> official Wiki page?
>
> Thanks,
>
> Jacopo
>

About a Freemarker template evaluator service

[Jacopo Cappellato]

Hi all,

a couple of days ago Daniel brought to my attention the site/service:

http://freemarker-online.kenshoo.com/

They provide a nice online tool to evaluate any Freemarker template by
providing the template code and its context.

Wouldn't be nice is we could offer that or a similar service to the users
and potential adopters of Freemarker? I think it would be a very useful
tool and also a good mechanism to attract new consumers.

If there is an interest in this community then we could move in two
directions:

1) get in touch with the maintainers of freemarker-online and see if they
are interested to contribute their work [*] or join our community and help
to build a similar one here; if they are not interested then we could
discuss if it would make sense to build our own here

2) get in touch with the Infra team and explore the possibility to set up a
virtual machine to dedicated to our project that we could use to deploy a
similar service, from our official website

I can volunteer to try to get in touch with them (#1); any volunteers for
#2 (or even #1)?

Kind regards,

Jacopo

[*] which is licensed with the AL2.0 and available here:
https://github.com/kenshoo/freemarker-online

Re: [DRAFT] FreeMarker report - January 2017

[Jacopo Cappellato]

On Mon, Jan 2, 2017 at 8:18 PM, Daniel Dekany  wrote:

>
> Is there any "political" reason for not mentioning that we also plan
> to try to make the project more attractive and more approachable by
> making a branch which drops the very much significant legacy burden?
> Or it's not a good idea until it's only a plan.


It makes perfect sense to add what you have proposed to the report; in fact
I think that in our last report there was already a mention to it. Will you
take care of updating/completing the report and add it to the official Wiki
page?

Thanks,

Jacopo

[DISCUSS] graduation (again!)

[Jacopo Cappellato]

Hi all,

we have discussed this already some months ago and I think it is time to
restart the conversation now: does this community feel ready to graduate to
a Top Level Project (TLP) at the ASF?

I think that the incubation phase has been very useful for the FreeMarker
project/community: FreeMarker has now clearly defined and documented
copyrights ownership, the community has learned how to produce and publish
clean and neat releases, all the assets and infrastructure have been
migrated to the ASF, the community has learned how to smoothly interact and
work with the ASF ecosystem (e.g. the ASF Infra, the Incubator general
list).
I feel that there is not much more that FreeMarker can learn from the
incubation and that it is time to think about graduation.

The developer community is still small, but it is independent, diverse and
clearly capable of maintaining the FreeMarker product and supporting the
large user community: attracting new developer will always be one of the
primary goals of this project, but this will not change when the project
will be a TLP out of the Incubator.

What do you think?

Jacopo

Re: Podling Report Reminder - October 2016

[Jacopo Cappellato]

In this report, under the section "Not yet ready to graduate", Freemarker
is listed under the group "No release".
However this is not accurate since Freemarker did a release in the
Incubator:

http://freemarker.org/freemarkerdownload.html

Would it be possible to update this section? Freemarker should be moved to
the group "Community growth"

Thank you,

Jacopo

On Fri, Oct 7, 2016 at 7:27 AM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 19 October 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, October 05).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/October2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Please read and sign the Podling Report

[Jacopo Cappellato]

Thank you Daniel, looks good to me.
I have signed it, but it would be nice to add a sentence to log that we
have positively completed the verifications about possible name conflicts.

Regards,

Jacopo

On Tue, Oct 4, 2016 at 12:06 AM, Daniel Dekany  wrote:

> Ugh... subject fixed.
>
>
> Monday, October 3, 2016, 8:01:58 PM, Daniel Dekany wrote:
>
> > Hello,
> >
> > Dear PPMC members, please see if you agree and if you want to
> > add/remove something, then sign when you think the report is ready:
> >
> > https://wiki.apache.org/incubator/October2016#preview
> >
> > Thanks!
> >
> >
> > Sunday, October 2, 2016, 3:13:39 PM, johndam...@apache.org wrote:
> >
> >> Dear podling,
> >>
> >> This email was sent by an automated system on behalf of the Apache
> >> Incubator PMC. It is an initial reminder to give you plenty of time to
> >> prepare your quarterly board report.
> >>
> >> The board meeting is scheduled for Wed, 19 October 2016, 10:30 am PDT.
> >> The report for your podling will form a part of the Incubator PMC
> >> report. The Incubator PMC requires your report to be submitted 2 weeks
> >> before the board meeting, to allow sufficient time for review and
> >> submission (Wed, October 05).
> >>
> >> Please submit your report with sufficient time to allow the Incubator
> >> PMC, and subsequently board members to review and digest. Again, the
> >> very latest you should submit your report is 2 weeks prior to the board
> >> meeting.
> >>
> >> Thanks,
> >>
> >> The Apache Incubator PMC
> >>
> >> Submitting your Report
> >>
> >> --
> >>
> >> Your report should contain the following:
> >>
> >> *   Your project name
> >> *   A brief description of your project, which assumes no knowledge of
> >> the project or necessarily of its field
> >> *   A list of the three most important issues to address in the move
> >> towards graduation.
> >> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> >> aware of
> >> *   How has the community developed since the last report
> >> *   How has the project developed since the last report.
> >>
> >> This should be appended to the Incubator Wiki page at:
> >>
> >> http://wiki.apache.org/incubator/October2016
> >>
> >> Note: This is manually populated. You may need to wait a little before
> >> this page is created from a template.
> >>
> >> Mentors
> >> ---
> >>
> >> Mentors should review reports for their project(s) and sign them off on
> >> the Incubator wiki page. Signing off reports shows that you are
> >> following the project - projects that are not signed may raise alarms
> >> for the Incubator PMC.
> >>
> >> Incubator PMC
> >>
> >
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [mentors] Check out FreeMarker status page

[Jacopo Cappellato]

Please see inline:

On Thu, Jun 30, 2016 at 7:59 PM, Daniel Dekany <ddek...@freemail.hu> wrote:

> I'm fine with it, and thanks for working on this.
>
> However, one important question wasn't yet answered. Who of the
> mentors want to be in the PMC after graduation? So far we only have
> Sergio Fernández. (And as of non-mentors, me, also Evangelia said that
> he plans to remain.)
>

I also have expressed the desire to be part of the PMC, if you agree.


>
> Also, I plant to create a document about making releases and about the
> project specific development policy. I would put that under the
> "Community" category on freemarker.org. Do you think that can increase
> our changes? (The best would be if someone else makes the next release
> based on that, but certainly we won't wait that much with the
> graduation attempt.)
>

That document would be a good asset for the project!

Jacopo


>
>
> Thursday, June 30, 2016, 6:18:47 PM, Jacopo Cappellato wrote:
>
> > I have spent some time reading the graduation guidelines, specifically
> [*].
> >
> > Here I am quoting the preparation steps before graduation:
> > Preparations
> >
> >- Complete (and sign off) tasks documented in the status file
> ><http://incubator.apache.org/guides/graduation.html#notes-status>
> >- Ensure suitable names
> ><http://incubator.apache.org/guides/graduation.html#notes-names> for
> >project name and product names
> >- Demonstrate ability to create Apache releases
> ><http://incubator.apache.org/guides/graduation.html#releases>
> >- Demonstrate community readiness
> ><http://incubator.apache.org/guides/graduation.html#community>
> >- Ensure Mentors
> >
> > <
> http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Mentor
> >
> > and IPMC
> >
> > <
> http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Incubator+Project+Management+Committee+%28PMC%29
> >
> > have
> >no remaining issues
> ><http://incubator.apache.org/guides/graduation.html#notes-issues>
> >
> >
> > The first two items (status page update and suitable names search) are in
> > progress.
> > Demonstrate ability to create releases is already done.
> > Demonstrate community readiness is done with the only concern about the
> > ability to attract new committers and nominate new PMC members: this is
> our
> > weak point, not diversity and openess.
> > The last point, is performed with two votes: an internal vote in this
> list
> > to make sure that the FreeMarker PMC and the community are happy about
> > requesting the graduation; the second vote will happen in the general
> list
> > to make sure that the IPMC is happy to recommend to the ASF Board the
> > graduation (for this vote we will also prepare the resolution for
> > graduation).
> >
> > I would say that before we start the community vote we should complete
> the
> > first two items (status page updates and suitable names search) that are
> > currently in progress: after that I will start a vote thread in this list
> > and if successful we will prepare a charter and start a vote/discussion
> on
> > the general list.
> >
> > What do you think?
> >
> > Jacopo
> >
> > References:
> >
> > [*] http://incubator.apache.org/guides/graduation.html
> >
> > On Tue, Jun 28, 2016 at 8:34 AM, Sergio Fernández <wik...@apache.org>
> wrote:
> >
> >> Cool, thanks!
> >>
> >> On Mon, Jun 27, 2016 at 10:25 PM, Daniel Dekany <ddek...@freemail.hu>
> >> wrote:
> >>
> >> > Since there was a date there, I assume it the name checked, even if
> >> > informally. But, I have opened an issue for it now:
> >> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-107
> >> >
> >> > And thanks for the status page commit!
> >> >
> >> >
> >> > Monday, June 27, 2016, 8:52:26 AM, Sergio Fernández wrote:
> >> >
> >> > > After you I went though the podling status page gather some
> >> > > concrete dates from what I found in my inbox, jira, etc.
> >> > >
> >> > > Actually there is a talks:
> >> > >
> >> > >   Make sure that the requested project name does not already exist.
> >> > >   Please follow the guide to ensure a suitable project/product name.
> >> > >
> >> > > that I can find traces at trademarks jira:
&

Re: [mentors] Check out FreeMarker status page

[Jacopo Cappellato]

I have spent some time reading the graduation guidelines, specifically [*].

Here I am quoting the preparation steps before graduation:
Preparations

   - Complete (and sign off) tasks documented in the status file
   
   - Ensure suitable names
    for
   project name and product names
   - Demonstrate ability to create Apache releases
   
   - Demonstrate community readiness
   
   - Ensure Mentors
   

and IPMC
   

have
   no remaining issues
   


The first two items (status page update and suitable names search) are in
progress.
Demonstrate ability to create releases is already done.
Demonstrate community readiness is done with the only concern about the
ability to attract new committers and nominate new PMC members: this is our
weak point, not diversity and openess.
The last point, is performed with two votes: an internal vote in this list
to make sure that the FreeMarker PMC and the community are happy about
requesting the graduation; the second vote will happen in the general list
to make sure that the IPMC is happy to recommend to the ASF Board the
graduation (for this vote we will also prepare the resolution for
graduation).

I would say that before we start the community vote we should complete the
first two items (status page updates and suitable names search) that are
currently in progress: after that I will start a vote thread in this list
and if successful we will prepare a charter and start a vote/discussion on
the general list.

What do you think?

Jacopo

References:

[*] http://incubator.apache.org/guides/graduation.html

On Tue, Jun 28, 2016 at 8:34 AM, Sergio Fernández  wrote:

> Cool, thanks!
>
> On Mon, Jun 27, 2016 at 10:25 PM, Daniel Dekany 
> wrote:
>
> > Since there was a date there, I assume it the name checked, even if
> > informally. But, I have opened an issue for it now:
> > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-107
> >
> > And thanks for the status page commit!
> >
> >
> > Monday, June 27, 2016, 8:52:26 AM, Sergio Fernández wrote:
> >
> > > After you I went though the podling status page gather some
> > > concrete dates from what I found in my inbox, jira, etc.
> > >
> > > Actually there is a talks:
> > >
> > >   Make sure that the requested project name does not already exist.
> > >   Please follow the guide to ensure a suitable project/product name.
> > >
> > > that I can find traces at trademarks jira:
> > > https://issues.apache.org/jira/browse/PODLINGNAMESEARCH
> > >
> > > Have we checked by any other mean?
> > >
> > > I know Freemarker is a well-established brand since 14 years; but I
> > > guess I'd go though the process just to have the formal ok from legal.
> > >
> > > Cheers,
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Sun, Jun 26, 2016 at 7:21 PM, John D. Ament 
> > wrote:
> > > On Sun, Jun 26, 2016 at 1:01 PM Daniel Dekany 
> > wrote:
> > >
> > >> I'm asking this primarily from mentors:
> > >> http://incubator.apache.org/projects/freemarker.html
> > >>
> > >> There are two thins to note:
> > >>
> > >> - "Add all active committers in the STATUS file."
> > >>   What STATUS file?
> > >>
> > >
> > > The file at content/projects/freemarker.xml which renders as
> > > http://incubator.apache.org/projects/freemarker.html
> > >
> > >
> > >
> > >>
> > >> - For many things I have just added a year instead of year-month-day.
> > >>   I hope nobody will care.
> > >>
> > >
> > > Yep, IPMC will care.
> > > You'll want to list out all of your reports - if you can include
> 04/2016
> > as
> > > well.
> > > Many of the dates you have for 07/2015 should be the day you entered
> > > incubation, which is 2015-07-01
> > >
> > > Your name search should be a link to the podlingnamesearch JIRA for
> > > freemarker, I can't find one for the project, so I would recommend that
> > you
> > > create one.
> > >
> > >
> > >>
> > >> --
> > >> Thanks,
> > >>  Daniel Dekany
> > >>
> > >>
> > >
> > >
> > >
> >
> > --
> > Thanks,
> >  Daniel Dekany
> >
> >
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: Podling Report Reminder - July 2016

[Jacopo Cappellato]

Hi Daniel,

the report looks good to me, thank you.
Maybe we could rephrase the following section:

=
Most important issues to address in the move towards graduation:

  1. Find more active contributors, discuss how to proceed without that
  2. Fill blanks left on the status page
=

into this one:

=
Most important issues to address in the move towards graduation:

  1. Make sure that the project's status page is updated
  2. Discuss the project's graduation on the general list

=

Jacopo

On Wed, Jun 29, 2016 at 11:28 PM, Daniel Dekany  wrote:

> Here's what I intend to submit. Because we want to mention the
> graduation discussion, I thought it's better if you look at it first:
>
>
> FreeMarker
>
> FreeMarker is a template engine, i.e. a generic tool to generate text
> output
> based on templates. FreeMarker is implemented in Java as a class library
> for
> programmers.
>
> FreeMarker has been incubating since 2015-07-01. The FreeMarker project
> exists and produces releases since around 2001.
>
> Most important issues to address in the move towards graduation:
>
>   1. Find more active contributors, discuss how to proceed without that
>   2. Fill blanks left on the status page
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   There were no changes
>
> How has the project developed since the last report?
>
>   The project has made a new public release, which come with new features,
> bug fixes,
>   and documentation improvements. Discussion was started about the
> possibility of
>   graduation. Some missing information on the status page was filled, and
> a formal
>   "podling name search" was started.
>
> Date of last release:
>
>   2016-06-26
>
> When were the last committers or PMC members elected?
>
>   2015-10-21 Nan Lei, committer (non-PMC)
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Podling Report Reminder - July 2016

[Jacopo Cappellato]

Indeed a good chance! And it is exactly one year since the graduation
started.

Maybe we could do an internal vote to formally express the FreeMarker PMC
willingness to graduate, based on this:

Organizational acceptance of responsibility for the project

   - If graduating to a new PMC, has the board voted to accept it?


(from http://incubator.apache.org/projects/freemarker.html)

Cheers,

Jacopo

On Mon, Jun 27, 2016 at 8:36 AM, Sergio Fernández  wrote:

> Good chance to report about the latest release and the graduation issues
> discussion.
>
> On Sun, Jun 26, 2016 at 11:02 PM,  wrote:
>
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 20 July 2016, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, July 06).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > http://wiki.apache.org/incubator/July2016
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: Graduation issues

[Jacopo Cappellato]

makes sense, thank you Sergio.

Jacopo

On Mon, Jun 20, 2016 at 12:55 PM, Sergio Fernández <wik...@apache.org>
wrote:

> On Mon, Jun 20, 2016 at 11:31 AM, Jacopo Cappellato <
> jacopo.cappell...@gmail.com> wrote:
> >
> > Should I start the thread today? Should I send you a preview of the
> message
> > as soon as it is ready so that you can all comment and improve it?
> >
>
> What about wait until the current vote is over and release published?
> I think that's a bit better timing...
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: Graduation issues

[Jacopo Cappellato]

I agree that it is the right time to discuss graduation.
In my opinion the incubation process for Freemarker has been successful and
for this reason I will vote +1 for the graduation.
As anticipated when we initially discussed the incubation, one critical
aspect of the Freemarker project was its small committer's base; under this
aspect the incubation process didn't do any magic and frankly speaking I
was not expecting it to happen.
However, as mentioned by Daniel and Sergio, the project is mature but there
are plans for the future that will keep the community busy, not just
maintaining the old code.
This community has still to find a more effective way to attract new
committers but this should not be a blocker to become a top level project @
ASF.
It is however important to verify that we will have, even after graduation,
a PMC group capable of casting at least 3 positive votes on releases.

Jacopo

On Tue, Jun 14, 2016 at 1:55 PM, Sergio Fernández  wrote:

> Hi Daniel,
>
> On Mon, Jun 13, 2016 at 9:18 PM, Daniel Dekany 
> wrote:
>
> > I think we can start some discussion about that even now. Or at least
> > I will tell what do I think about the state of the project.
> >
>
> Great step. Thanks.
>
> The main problem is the number of active developers, which is 1, me.
> >
>
> I'm aware...
>
> https://github.com/apache/incubator-freemarker/graphs/contributors?from=2015-07-01=c
>
>
> > What if I'm hit by a truck tomorrow? We can hope that if there's a bug
> > that concerns many, then someone will eventually fix it. After all the
> > owner (ASF) won't be gone, the release infrastructure is there, etc.
> > But as far as non-bugfix development goes, it's certain that things
> > would stop. Some may say that that's OK for a project that's
> > backward-compatibility-locked for 12 years now (the 2.x line is
> > actually 14 years old).
>
>
> Well, I'd say that's critical, but the community of a project is more than
> the developers who code. And the Freemarker community is much bigger than
> what you could think.
>
> For instance if you consider my personal case: I volunteered for mentor
> because I knew the project for so long. I even code some extensions (
> http://marmotta.apache.org/ldpath/template.html). Definitively I used
> Freemarker much more in the past than currently, but Web development has
> changed a lot, moving more stuff to the frontend (10 years ago we didn't
> have AngularJS).
>
> So I'd say there are many people like me out there, using every day
> solutions based on Freemarker. People who are not that close to the source
> base, but familiar enough to be able to jump in at any time a provide a
> patch.
>
>
>
> > But of course that's just slow death if a
> > project can't counter its old design problems and can't evolve to
> > tackle new problems anymore. So indeed 2.x should switch to
> > maintenance eventually (but ATM there are still things that can be
> > done in 2.x), but only to give place for 3.x. Anyway, how to catch
> > long standing developers? I don't think that 2.x have a real chance
> > for that, because of all the legacy code burden piled up. (Some Apache
> > projects have many paid contributors, but I think FM isn't the kind of
> > project that can have that, so it's important that the developers want
> > to fiddle with it for free.) So the 3.x jump will be necessary, and
> > then, maybe, we can have a developer base growth (template engines
> > isn't hot topic anymore, so I just mean having a few developers
> > around). But 3.x is far away (if it will happen at all), and we can't
> > hang around in the incubator forever.
>
>
> Well, we can consider 2.3.x feature-complete, and 2.3.25-incubating a
> maintenance release. The world has change a lot in template business in
> these 14 years. But I'm pretty sure FreeMarker has its place there, and 3.x
> could bring some many great ideas that may attract potential new
> contributors. And that's what I see as future of this project.
>
>
> > So, do you believe there's any chance to graduate with the current
> > developer base?
> >
>
> Definitively that has been always the major issue with this podling.
> Honestly I'm not sure. But following with all my argumentation that the
> community is much bigger that what shows the development team, I'd say
> could be at least discussed with the IPMC.
>
> Looking forward to hear every body else's opinions.
>
> Cheers,
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>

Re: Podling Report Reminder - April 2016

[Jacopo Cappellato]

The report looks good and I have signed it off.
Some minors suggestions:
* instead of answering "There were no changes" to the question "How has the
community developed since the last report?", we could say a sentence about
the fact that the community is quite but active, most of the effort went in
the effort of preparing/voting the new releases and that the questions and
proposals from users have been addressed and discussed in the mailing lists
* question "How has the project developed since the last report?": we could
add a sentence that says that this time the release process went smoothly
after the practice done during the previous release

Regards,

Jacopo




On Tue, Apr 5, 2016 at 8:34 AM, Daniel Dekany <ddek...@freemail.hu> wrote:

> I.e., to Mentors, please sign it off on
> http://wiki.apache.org/incubator/April2016!
>
>
> Tuesday, April 5, 2016, 2:01:30 AM, Lee wrote:
>
> > Wiki updated. Thanks!
> >
> > On Sun, Apr 3, 2016 at 11:40 PM, Sergio Fernández <wik...@apache.org>
> wrote:
> >
> >> Sounds good, Lee. Please, add it to the wiki by this Wednesday awaiting
> to
> >> gather some more feedback. Thanks.
> >>
> >> On Sun, Apr 3, 2016 at 7:25 AM, Lee <evangel...@gmail.com> wrote:
> >>
> >> > Here is the draft, I am waiting on access to update the wiki.
> >> >
> >> > FreeMarker
> >> >
> >> > FreeMarker is a template engine, i.e. a generic tool to generate text
> >> > output
> >> > based on templates. FreeMarker is implemented in Java as a class
> library
> >> > for
> >> > programmers.
> >> >
> >> > FreeMarker has been incubating since 2015-07-01.
> >> >
> >> > The most important issues to address in the move towards graduation:
> >> >
> >> >   1. Finding more active contributors
> >> >
> >> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> >> aware
> >> > of?
> >> >
> >> >   None
> >> >
> >> > How has the community developed since the last report?
> >> >
> >> >   There were no changes
> >> >
> >> > How has the project developed since the last report?
> >> >
> >> > FreeMarker had two public releases: A Release Candidate (so that users
> >> can
> >> > test it), and one final release. Apart from the new features and
> fixes,
> >> we
> >> > have adjusted the source code and build process to follow Apache best
> >> > practices more closely, and to be more appealing for contributors
> >> > (switching to Java 5, fixing formatting where it didn't fit the modern
> >> Java
> >> > conventions).
> >> >
> >> > The legal/policy issue with the web site domain (INFRA-10787) was
> >> settled,
> >> > and we are using our historical domain again (freemarker.org) until
> >> > graduation.
> >> >
> >> > Date of last release:
> >> >
> >> >   2016-03-28
> >> >
> >> > When were the last committers or PMC members elected?
> >> >
> >> >   2015-10-21 Nan Lei, committer (non-PMC)
> >> >
> >> > Signed-off-by:
> >> >
> >> >   [ ](freemarker) Jacopo Cappellato
> >> >   [ ](freemarker) Jean-Frederic Clere
> >> >   [ ](freemarker) David E. Jones
> >> >   [ ](freemarker) Ralph Goers
> >> >   [ ](freemarker) Sergio Fernández
> >> >
> >> > Shepherd/Mentor notes:
> >> >
> >> > On Sat, Apr 2, 2016 at 2:06 AM, Lee <evangel...@gmail.com> wrote:
> >> >
> >> > > I can draft it. I'll work on it tomorrow night.
> >> > >
> >> > > On Friday, April 1, 2016, Sergio Fernández <wik...@apache.org>
> wrote:
> >> > >
> >> > >> ping, any volunteer for drafting the report?
> >> > >>
> >> > >>
> >> > >> On Tue, Mar 29, 2016 at 1:03 PM, <johndam...@apache.org> wrote:
> >> > >>
> >> > >> > -
> >> > >> > Apologies if you received this multiple times
> >> > >> > -
> >> > >> >
> >> > >> > Dear podling,
> >> > >> >
> >> > >> > This email was sent by an aut

Re: [VOTE] Release Apache FreeMarker 2.3.24 (incubating)

[Jacopo Cappellato]

+1 for both releases (binding)

The release files look good, I have built the jar from source files and
tested in the OFBiz framework.

Jacopo



On Mon, Mar 21, 2016 at 12:02 AM, Daniel Dekany  wrote:

> Hi all,
>
> Please vote on releasing FreeMarker 2.3.24-incubating! This will be
> our first stable release (not just a Release Candidate) from the ASF.
> If this voting passes, another similar voting will be started on
> gene...@incubator.apache.org, and if that passes too, then we can
> release this version.
>
> Release Notes:
> http://freemarker.org/builds/2.3.24-unvoted/_html/versions_2_3_24.html
>
> Before proceed, you should know that FreeMarker 2.3.x, for a long
> time, always releases a normal and a "gae" variant on the same time,
> which are technically two independent source trees (Git branches). The
> "gae" variant contains a few small modification in the Java source
> code to be Google App Engine compliant, and has freemarker-gae as the
> Maven artifact name. Otherwise the normal and the "gae" branches are
> identical. Hence they will be voted on together.
>
> The commits to be voted upon are:
> - Normal (non-gae) variant:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4a723fc1e89c3f258b00e6ee40ba3c60d076aa89
>   Commit hash: 4a723fc1e89c3f258b00e6ee40ba3c60d076aa89
> - "gae" variant:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=4b8df1fd03c21495e646ac1721734811564317f5
>   Commit hash: 4b8df1fd03c21495e646ac1721734811564317f5
>
> The artifacts to be voted upon are located here:
>
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/source/
> where the source release artifacts are:
> - Normal (non-gae) variant:
>   apache-freemarker-2.3.24-incubating-src.tar.gz
> - "gae" variant:
>   apache-freemarker-gae-2.3.24-incubating-src.tar.gz
>
> See the README inside them for build instructions!
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/ddekany.asc
>
> Note that for convenience, we also provide binaries:
>
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-incubating/binaries/
> and Maven artifacts in the ASF staging repository:
> https://repository.apache.org/content/repositories/staging/org/freemarker/
>
> Please try out the package and vote!
>
> The vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached.
>
> [ ] +1 Release this package as Apache FreeMarker 2.3.24-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Please add "(binding)" if your vote is binding.
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [VOTE] Release FreeMarker 2.3.24-rc01-incubating, attempt 3

[Jacopo Cappellato]

Yes, you are right; I was confused because I have actually tested them when
I have voted +1 to the previous attempt (you have announced the new vote in
the same time I have casted mine).

Here is my vote:

+1

Jacopo


On Sat, Jan 16, 2016 at 10:20 PM, Daniel Dekany <ddek...@freemail.hu> wrote:

> Those also look fine to me. The artifacts has the new NOTICE files,
> and the the sha1 and md5 checksums are correct.
>
> --
> Thanks,
>  Daniel Dekany
>
>
> Saturday, January 16, 2016, 4:34:54 PM, Jacopo Cappellato wrote:
>
> > I was talking about the files here:
> >
> >
> https://repository.apache.org/content/repositories/staging/org/freemarker/freemarker/2.3.24-rc01-incubating/
> >
> > Jacopo
> >
> > On Fri, Jan 15, 2016 at 8:52 PM, Daniel Dekany <ddek...@freemail.hu>
> wrote:
> > Friday, January 15, 2016, 9:46:31 AM, Jacopo Cappellato wrote:
> >
> >> Hi Daniel,
> >>
> >> the release files and the hashes/signatures seem to be the same of the
> >> previous attempt. Maybe I am missing something but I was expecting a new
> >> version of them so that we could test the integrity of the bundles.
> >
> > Which one? They seem to me up to date
> > (
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-rc01-incubating/binaries/apache-freemarker-2.3.24-rc01-incubating-bin.tar.gz.md5
> ,
> > etc.)
> >
> > OTOH I see something funny with the sha512 files. If I check them out
> > with SVN, they are fine. But if I download them from the web URL, they
> > come down gzip-ed... But I assume this glitch has nothing to do with
> > the release files.
> >
> >> Regards,
> >>
> >> Jacopo
> >>
> >>
> >> On Thu, Jan 14, 2016 at 1:11 AM, Daniel Dekany <ddek...@freemail.hu>
> wrote:
> >>
> >>> I did an update. No functionality/stability changes, only legal ones
> >>> and some build script change:
> >>>
> >>> - NOTICE file changes:
> >>>   - Added missing META-INF/NOTICE to the Maven javadoc artifact
> >>>   - More precise and readable font-related section in the binary
> >>> distribution
> >>>   - Customized META-INF/NOTICE in freemkarker.jar, to fit this
> >>> particular artifact.
> >>> - `ant maven-dist` now selects the appropriate target Maven repo
> >>>   (snapshot VS staging) based on the version number.
> >>>
> >>> All the links remain as there were. Except, the Git commit hashes
> >>> change to this:
> >>>
> >>> Normal version:
> >>>   "2.3" branch commit hash: b9ca91dd5c3b04121f5ddcb9f6194c1e7931ba2c
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=b9ca91dd5c3b04121f5ddcb9f6194c1e7931ba2c
> >>>
> >>> Google App Engine ("gae") compliant version:
> >>>"2.3-gae" branch  commit hash:
> 0c71d8f99323577d9683d924c51d617eb0346d15
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=0c71d8f99323577d9683d924c51d617eb0346d15
> >>>
> >>> Please review and vote!
> >>>
> >>> --
> >>> Thanks,
> >>>  Daniel Dekany
> >>>
> >>>
> >>> Thursday, January 7, 2016, 10:29:32 PM, Daniel Dekany wrote:
> >>>
> >>> > Dear Mentors, and everyone else!
> >>> >
> >>> > Here's the 2nd attempt on 2.3.24-rc01-incubating. Nothing has changed
> >>> > that affects FreeMarker's functionality/stability. These are merely
> >>> > fixes related to licensing files and Apache packaging conventions.
> >>> >
> >>> > As previously, if you can, please test the release with your own
> >>> > FreeMarker-dependent projects, and in general try to find rough
> edges,
> >>> > tell your insights. The binary with full documentation and change
> log:
> >>> >
> >>> >
> >>> >
> >>>
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-rc01-incubating/binaries/apache-freemarker-2.3.24-rc01-incubating-bin.tar.gz
> >>> >
> >>> > Git:
> >>> >
> >>> >   Normal version:
> >>> >   "2.3" branch commit hash: ce1dc19b3ccfb734af551c2d694a3a3d1039f7fa
> >>> >
> >>> >
> >>>
> https://git-wip-us.apache.org/repos/asf?p=incu

Re: [VOTE] Release FreeMarker 2.3.24-rc01-incubating, attempt 3

[Jacopo Cappellato]

I was talking about the files here:

https://repository.apache.org/content/repositories/staging/org/freemarker/freemarker/2.3.24-rc01-incubating/

Jacopo

On Fri, Jan 15, 2016 at 8:52 PM, Daniel Dekany <ddek...@freemail.hu> wrote:

> Friday, January 15, 2016, 9:46:31 AM, Jacopo Cappellato wrote:
>
> > Hi Daniel,
> >
> > the release files and the hashes/signatures seem to be the same of the
> > previous attempt. Maybe I am missing something but I was expecting a new
> > version of them so that we could test the integrity of the bundles.
>
> Which one? They seem to me up to date
> (
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-rc01-incubating/binaries/apache-freemarker-2.3.24-rc01-incubating-bin.tar.gz.md5
> ,
> etc.)
>
> OTOH I see something funny with the sha512 files. If I check them out
> with SVN, they are fine. But if I download them from the web URL, they
> come down gzip-ed... But I assume this glitch has nothing to do with
> the release files.
>
> > Regards,
> >
> > Jacopo
> >
> >
> > On Thu, Jan 14, 2016 at 1:11 AM, Daniel Dekany <ddek...@freemail.hu>
> wrote:
> >
> >> I did an update. No functionality/stability changes, only legal ones
> >> and some build script change:
> >>
> >> - NOTICE file changes:
> >>   - Added missing META-INF/NOTICE to the Maven javadoc artifact
> >>   - More precise and readable font-related section in the binary
> >> distribution
> >>   - Customized META-INF/NOTICE in freemkarker.jar, to fit this
> >> particular artifact.
> >> - `ant maven-dist` now selects the appropriate target Maven repo
> >>   (snapshot VS staging) based on the version number.
> >>
> >> All the links remain as there were. Except, the Git commit hashes
> >> change to this:
> >>
> >> Normal version:
> >>   "2.3" branch commit hash: b9ca91dd5c3b04121f5ddcb9f6194c1e7931ba2c
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=b9ca91dd5c3b04121f5ddcb9f6194c1e7931ba2c
> >>
> >> Google App Engine ("gae") compliant version:
> >>"2.3-gae" branch  commit hash:
> 0c71d8f99323577d9683d924c51d617eb0346d15
> >>
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=0c71d8f99323577d9683d924c51d617eb0346d15
> >>
> >> Please review and vote!
> >>
> >> --
> >> Thanks,
> >>  Daniel Dekany
> >>
> >>
> >> Thursday, January 7, 2016, 10:29:32 PM, Daniel Dekany wrote:
> >>
> >> > Dear Mentors, and everyone else!
> >> >
> >> > Here's the 2nd attempt on 2.3.24-rc01-incubating. Nothing has changed
> >> > that affects FreeMarker's functionality/stability. These are merely
> >> > fixes related to licensing files and Apache packaging conventions.
> >> >
> >> > As previously, if you can, please test the release with your own
> >> > FreeMarker-dependent projects, and in general try to find rough edges,
> >> > tell your insights. The binary with full documentation and change log:
> >> >
> >> >
> >> >
> >>
> https://dist.apache.org/repos/dist/dev/incubator/freemarker/engine/2.3.24-rc01-incubating/binaries/apache-freemarker-2.3.24-rc01-incubating-bin.tar.gz
> >> >
> >> > Git:
> >> >
> >> >   Normal version:
> >> >   "2.3" branch commit hash: ce1dc19b3ccfb734af551c2d694a3a3d1039f7fa
> >> >
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=ce1dc19b3ccfb734af551c2d694a3a3d1039f7fa
> >> >
> >> >   Googla App Engine ("gae") compliant version:
> >> >   "2.3-gae" branch  commit hash:
> >> > 6166efe1d02fe89a98c7d87ab26a608e2d560492
> >> >
> >> >
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-freemarker.git;a=commit;h=6166efe1d02fe89a98c7d87ab26a608e2d560492
> >> >
> >> >   (Tagging will happen if and when it indeed becomes to a release.)
> >> >
> >> > Maven (jar, javadoc and source artifacts):
> >> >
> >> >   Repository:
> >> > https://repository.apache.org/content/repositories/staging/
> >> >
> >> >   Browse (Mentors please check contents):
> >> >
> >> >
> >>
> https://repository.apache.org/content/reposi

Re: Signing the Januray report (and mailing list subscriptions)

[Jacopo Cappellato]

The report looks good to me, thank you Daniel.
One minor suggestion: you could add the name of the new committer near the
date of the addition at the bottom of the report.

Jacopo

On Sun, Jan 3, 2016 at 1:51 PM, Daniel Dekany  wrote:

> Dear FreeMarker Mentors!
>
> Please review and sign off the January report if you find the time
> (until the end of Wed, January 6th):
> https://wiki.apache.org/incubator/January2016
>
> Also, if by any chance, any of you isn't subscribed to both
> dev@freemarker.incubator.apache.org and
> priv...@freemarker.incubator.apache.org, please subscribe (this mail
> was BCC-ed to your personal addresses), and note that then you have
> missed that I have started VOTE for a making a Release Candidate
> release.
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: Should freemarker.org remain the canonical domain?

[Jacopo Cappellato]

I think that the project should keep it, and it should redirect to the
actual domain:

freemarker.org --> freemarker.incubator.apache.org (now)
freemarker.org --> freemarker.apache.org (after graduation)

We did something similar with OFBiz and its ofbiz.org domain.

Jacopo


On Tue, Nov 3, 2015 at 11:57 PM, Daniel Dekany  wrote:

> Infra has managed to set up the DNS (but some other issue has popped
> up, so now I suddenly can't update the site content, so we are still
> screwed... a different mater anyway). But to my surprise, they
> redirect http://freemarker.org to
> http://freemarker.incubator.apache.org/ (via HTTP 301, temporal
> redirection). When I asked infra about this
> (https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-10604
> ),
> they said that it's how it normally goes, and I should speak to
> tradema...@apache.org if I want to keep freemarker.org as the
> canonical URL.
>
> So, should I ask them? I believe that's the project's interest, so
> personally, I'm in favor of keeping freemarker.org as the canonical
> project domain, until we graduate from incubation. What do you think?
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: PPMC members, please read and sign the October report

[Jacopo Cappellato]

Thanks, the report looks good to me, I have signed it.

Jacopo

On Wed, Oct 7, 2015 at 3:59 AM, Daniel Dekany  wrote:

> https://wiki.apache.org/incubator/October2015
>
> --
> Thanks,
>  Daniel Dekany
>
>

Re: [Mentors] Starting IP clearance process?

[Jacopo Cappellato]

On Sep 21, 2015, at 7:02 PM, Daniel Dekany <ddek...@freemail.hu> wrote:

> OK. If it's good enough for ASF, it's surely good for me.
> 
> (What will bit a bit funny though, is that in the last monthly report
> I have stated that we are starting the IP clearance soon, also some
> PPMC members have signed that. Now it turns out that it was already
> done... Whatever.)

It should be fine, you could write something like this in your next report:

the IP clearance process is now complete given that:
1) FreeMarker was already licensed under the ASL 2.0
2) Software License Agreements have been collected (and have been filed by the 
ASF Secretary) for the former copyright owners that are no more active and 
involved in the project
3) Contributor License Agreements have been collected (and have been filed by 
the ASF Secretary) for the main contributors of the project, that are now 
committers of the incubating project
4) notices in the project mailing lists and website have been published to 
announce that the project is now incubating @ASF and to invite potential 
contributors to participate in the new home
5) license headers have been updated to reflect the new copyright

To all, please review my notes above and correct them if you see any errors.

Jacopo

> 
> -- 
> Thanks,
> Daniel Dekany
> 
> 
> Monday, September 21, 2015, 9:43:54 AM, Jacopo Cappellato wrote:
> 
>> 
>> On Sep 20, 2015, at 6:09 PM, Daniel Dekany <ddek...@freemail.hu> wrote:
>> 
>>> I also hope that there's no much to do at this point, however, my
>>> understanding was that clearance has to be voted:
>>> http://incubator.apache.org/guides/mentor.html#poding-ip-clearance
>> 
>> I am saying we are done because of the following document
>> (referenced by the document you mention above):
>> 
>> http://incubator.apache.org/ip-clearance/index.html
>> 
>> and specifically:
>> 
>> "This form is not for new projects. This is for projects and PMCs
>> that have already been created and are receiving a code donation into an 
>> existing codebase."
>> 
>> This also adds some interesting details:
>> 
>> http://incubator.apache.org/guides/mentor.html#initial-ip-clearance
>> 
>> quoting:
>> 
>> "Existing codebases need to be imported through the standard IP
>> clearance process. This means that a Software Grant Agreement (SGA)
>> or Contributor License Agreement (CLA) need to be submitted for all
>> copyright owners. This process may take a while so it is best to
>> start as soon as the podling is accepted. The acceptance of the
>> initial codebases is approved by the IPMC as part of the acceptance
>> motion. So, no vote is required by the PPMC."
>> 
>>> 
>>> BTW, at the end of September, I hope to be able to do
>>> 2.3.24-RC1-incubating at last, and I hope there will be no
>>> bureaucratic obstacles. Let me know if any of you know of any!
>> 
>> I don't. A tool that is useful to prepare and audit the release is the 
>> following:
>> 
>> http://creadur.apache.org/rat/
>> 
>> Regards,
>> 
>> Jacopo
>> 
>>> 
>>> -- 
>>> Thanks,
>>> Daniel Dekany
>>> 
>>> 
>>> Sunday, September 20, 2015, 5:14:17 PM, Jacopo Cappellato wrote:
>>> 
>>>> Daniel,
>>>> 
>>>> I think we are done with the IP clearance process at this point,
>>>> the required CLAs and SFAs are all filed.
>>>> 
>>>> Kind regards,
>>>> 
>>>> Jacopo
>>>> 
>>>> References:
>>>> http://incubator.apache.org/guides/mentor.html#initial-clean-up
>>>> http://incubator.apache.org/guides/mentor.html#initial-ip-clearance
>>>> 
>>>> 
>>>> On Sep 12, 2015, at 3:31 PM, Daniel Dekany <ddek...@freemail.hu> wrote:
>>>> 
>>>>> Saturday, September 12, 2015, 10:49:37 AM, Sergio Fernández wrote:
>>>>> 
>>>>>> Daniel, sorry, I'll try to go through this on Monday.
>>>>>> 
>>>>>> For provenance purposes what it's important is to have tagged in both 
>>>>>> repos
>>>>>> (original and asf) the concrete version that has been donated.
>>>>> 
>>>>> I have added "donated-to-asf" tags in both the GitHub and ASF repos.
>>>>> More precisely, as the "freemarker" repository (as opposed to the
>>>>> "site" and "docgen" repos) has 3 branches ("2.3-gae", "2.3" and
>>>&

Re: [Mentors] Starting IP clearance process?

[Jacopo Cappellato]

On Sep 20, 2015, at 6:09 PM, Daniel Dekany <ddek...@freemail.hu> wrote:

> I also hope that there's no much to do at this point, however, my
> understanding was that clearance has to be voted:
> http://incubator.apache.org/guides/mentor.html#poding-ip-clearance

I am saying we are done because of the following document (referenced by the 
document you mention above):

http://incubator.apache.org/ip-clearance/index.html

and specifically:

"This form is not for new projects. This is for projects and PMCs that have 
already been created and are receiving a code donation into an existing 
codebase."

This also adds some interesting details:

http://incubator.apache.org/guides/mentor.html#initial-ip-clearance

quoting:

"Existing codebases need to be imported through the standard IP clearance 
process. This means that a Software Grant Agreement (SGA) or Contributor 
License Agreement (CLA) need to be submitted for all copyright owners. This 
process may take a while so it is best to start as soon as the podling is 
accepted. The acceptance of the initial codebases is approved by the IPMC as 
part of the acceptance motion. So, no vote is required by the PPMC."

> 
> BTW, at the end of September, I hope to be able to do
> 2.3.24-RC1-incubating at last, and I hope there will be no
> bureaucratic obstacles. Let me know if any of you know of any!

I don't. A tool that is useful to prepare and audit the release is the 
following:

http://creadur.apache.org/rat/

Regards,

Jacopo

> 
> -- 
> Thanks,
> Daniel Dekany
> 
> 
> Sunday, September 20, 2015, 5:14:17 PM, Jacopo Cappellato wrote:
> 
>> Daniel,
>> 
>> I think we are done with the IP clearance process at this point,
>> the required CLAs and SFAs are all filed.
>> 
>> Kind regards,
>> 
>> Jacopo
>> 
>> References:
>> http://incubator.apache.org/guides/mentor.html#initial-clean-up
>> http://incubator.apache.org/guides/mentor.html#initial-ip-clearance
>> 
>> 
>> On Sep 12, 2015, at 3:31 PM, Daniel Dekany <ddek...@freemail.hu> wrote:
>> 
>>> Saturday, September 12, 2015, 10:49:37 AM, Sergio Fernández wrote:
>>> 
>>>> Daniel, sorry, I'll try to go through this on Monday.
>>>> 
>>>> For provenance purposes what it's important is to have tagged in both repos
>>>> (original and asf) the concrete version that has been donated.
>>> 
>>> I have added "donated-to-asf" tags in both the GitHub and ASF repos.
>>> More precisely, as the "freemarker" repository (as opposed to the
>>> "site" and "docgen" repos) has 3 branches ("2.3-gae", "2.3" and
>>> "master"), there we have "2.3-gae-donated-to-asf" and
>>> "2.3-donated-to-asf" and "master-donated-to-asf", respectively.
>>> 
>>> -- 
>>> Thanks,
>>> Daniel Dekany
>>> 
>>>> On Sep 12, 2015 10:02 AM, "Daniel Dekany" <ddek...@freemail.hu> wrote:
>>>> 
>>>>> Just wanted to bring the below mail to your attention, as it was now 9
>>>>> days without any reaction.
>>>>> 
>>>>> 
>>>>> This is a forwarded message
>>>>> From: Daniel Dekany <ddek...@freemail.hu>
>>>>> To: dev@freemarker.incubator.apache.org
>>>>> Date: Thursday, September 3, 2015, 12:56:50 AM
>>>>> Subject: [Mentors] Starting IP clearance process?
>>>>> 
>>>>> ===8<==Original message text===
>>>>> Dear Mentors (and others who want to help),
>>>>> 
>>>>> We have the 3 repos (freemarker, docgen, site) imported as you might
>>>>> noticed from the flood of commit messages (sorry...), and I have
>>>>> changed the copyright headers, ensured that the 3 standard legal files
>>>>> (NOTICE, LICENSE and DISCLAIMER) are there, and removed files that I
>>>>> have spotted with unclear copyright. So, gloss over the 3 projects if
>>>>> you want to, and then I think I should add a tag like "ip-clearance",
>>>>> and the more official review could be started. Or something like
>>>>> that... Please advise!
>>>>> 
>>>>> --
>>>>> Thanks,
>>>>> Daniel Dekany
>>>>> 
>>>>> 
>>>>> 
>>>>> ===8<===End of original message text===
>>>>> 
>>>>> 
>>> 
>> 
>> 
>