+1,
I had started something similar, at least on the website side, with best
practices and required branding items.
Please consider adding it to the "example" project :
https://github.com/apache/apache-website-template
On Sun, Oct 2, 2016 at 9:05 AM, Dylan Bethune-Waddell <
dylan.bethune.wadd.
Hi,
Chang my vote to +1 binding as I managed to get it ti compile.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
> On Oct 2, 2016, at 11:55 AM, Roman Shaposhnik wrote:
>
>
> ultimately
> decided that expecting a bit more up-front community action was a
> prudent choice.
>
> What I'd like to see is a proof that ASF or no ASF the community wants to take
> matters into its own hands and fork away. For now
The benefits of such an example project to the open source community would
extend to projects that do not yet or will never incubate at Apache. If there
is some consideration given to that group from the outset, even more so.
Wouldn't this broadcast The Apache Way to a wider audience and let tho
On Sat, Oct 1, 2016 at 8:05 AM, Niclas Hedhman wrote:
> Agree with you on all points, Taylor.
>
> And I am even quite surprised to see the number of people backing the
> project, yet Apache is adamant to get involved. It feels a little bit like
> the "Community over Code" and "Independent of any C
On Sun, Oct 2, 2016 at 4:17 AM, Stian Soiland-Reyes wrote:
> Hi,
>
> There's been many discussions recently around what is the best practice for
> git tagging, release procedures, licencing notes, web site publishing etc.
>
> The landscape is always changing as technologies and INFRA procedures
>
+1 (binding)
Checked:
- signature
- DISCLAIMER, NOTICE, LICENSE
- ASF headers
I didn't try to build.
Regards
JB
On 09/30/2016 07:16 PM, Mike Drob wrote:
Resending this after being told that I used an incorrect subject format.
On 2016-09-29 21:20 (-0500), "Mike Drob" wrote:
Dear IPMC, please
It sounds like a good idea.
+1
Regards
JB
On 10/02/2016 01:17 PM, Stian Soiland-Reyes wrote:
Hi,
There's been many discussions recently around what is the best practice for
git tagging, release procedures, licencing notes, web site publishing etc.
The landscape is always changing as technolo
All,
You can also build using mvn clean install
-DcreateDependencyReducedPom=false (which is what I did).
John
On Sun, Oct 2, 2016 at 8:53 AM Drew Farris wrote:
> Mike,
>
> If this release can only be built with Maven 3.0.4, would it make sense to
> set up the enforcer plugin to fail the build
Mike,
If this release can only be built with Maven 3.0.4, would it make sense to
set up the enforcer plugin to fail the build if an attempt is made to build
with something other than that version? It could help others avoid some
gnashing of teeth and document the specific requirement.
Drew
On Sa
As someone currently trying to set up the process for a new podling, this
would have made my life so much simpler. We've been working on it for
about 3 months now setting it up, trying to glean information from various
sites, and trying to figure out which information is outdated.
It sounds like
Hi,
There's been many discussions recently around what is the best practice for
git tagging, release procedures, licencing notes, web site publishing etc.
The landscape is always changing as technologies and INFRA procedures
evolve (yay!). Hunting around the different existing projects for
inspir
12 matches
Mail list logo
