It sounds to me like you're saying that the license under which code is
offered (to anybody who encounters it) is independent of the license
declaration attached to the project.
This makes sense to me, presuming that we still agree that the license
declaration (header or license file) is the best
It might be relevant that that both of those tools appear to be licensed
under ASL 2.0, which explicitly permits redistribution (presumably outside
the private area?). I would think it confusing to have an open source
license on software which is expected to remain private, or otherwise
restricted
Hi all,
I'm just getting familiar with the incubator project, because I am
anticipating working with some future projects which might submit proposals
to go through incubation, and I'd like to gain some greater familiarity
with how things operate in this space. I've already started reading through
The page at
http://incubator.apache.org/learn/theapacheway.html
needs to be updated to reflect the new location of the ComDev mailing
lists. It is no longer commun...@apache.org (and
community-subscr...@apache.org), but is instead d...@community.apache.org
(and dev-subscr...@community.apache.org).
Can I get edit access to the Wiki?
Username: ChristopherTubbs
Thanks!
On Tue, Apr 19, 2016 at 12:15 PM Nick Burch wrote:
> On Tue, 19 Apr 2016, Christopher wrote:
> > Can I get edit access to the Wiki?
> >
> > Username: ChristopherTubbs
>
> Karma grant
Integration ===
* Travis CI on the GitHub mirror is fine (flag set to build only if
''.travis.yml'' file is present)
== Initial Committers ==
* Keith Turner (kturner at apache dot org)
* Mike Walch (mike.walch at ptech-llc dot com)
* Corey Nolet (cjnolet at apache
On Fri, Apr 29, 2016 at 9:04 AM Edward Capriolo
wrote:
> I would suggest, my feeling is that tools that work with more than one
> nosql have a better chance at success. Are there plans for hbase/Cassandra
> support?
>
>
To directly answer the question, no, there are no current plans for
supporti
On Tue, Apr 19, 2016 at 1:21 PM Christopher wrote:
> For the incubator consideration, the Fluo developers submit the following
> proposal:
> https://wiki.apache.org/incubator/FluoProposal
>
> = Fluo Proposal =
>
> == Abstract ==
>
> Fluo is a distributed system for inc
On Tue, May 10, 2016 at 3:52 PM Christopher wrote:
> On Tue, Apr 19, 2016 at 1:21 PM Christopher wrote:
>
>> For the incubator consideration, the Fluo developers submit the following
>> proposal:
>> https://wiki.apache.org/incubator/FluoProposal
>>
>> [
On Wed, May 18, 2016 at 12:54 PM Jean-Baptiste Onofré
wrote:
> Hi Mike,
>
> it's what we are doing at Beam.
>
> A PR submission result:
> - to a mail on the mailing list
> - to a comment in Jira (if the PR contains commit with issue ID).
>
>
The GitHub integration is very useful, as it tracks the
+1 (non-binding)
On Tue, May 24, 2016 at 7:41 PM Drew Farris wrote:
> +1 (binding)
>
> On Tue, May 24, 2016, 5:27 PM Andrew Purtell wrote:
>
> > +1 (binding)
> >
> >
> > On Mon, May 23, 2016 at 10:56 PM, Daniel Gruno
> > wrote:
> >
> > > Since it seems the discussion has died down, I am now ca
In preparation for a 1.0.0-incubating release of Fluo, the Fluo team is
first separately releasing a parent POM. This release passed a PPMC vote on
the Fluo dev@ list here:
https://lists.apache.org/thread.html/2f801cc81b7eab1f3438da23d8973626755a77e9038f80cce2b30ae9@%3Cdev.fluo.apache.org%3E
Pleas
consistent formatting and style checks to maven projects using
this parent POM.
On Sat, Jul 30, 2016 at 2:24 PM John D. Ament wrote:
> What is io.fluo and why does this depend on it? Sounds like a branding
> issue.
>
> On Jul 30, 2016 14:14, "Christopher" wrote:
>
>
On Sat, Jul 30, 2016 at 9:55 PM Justin Mclean
wrote:
> Hi,
>
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachefluo-1003
> > Source (official release artifact):
> >
> https://repository.apache.org/content/repositories/orgapachefluo-1003/org/apache/fluo/fluo-parent/
On Sat, Jul 30, 2016 at 10:07 PM Justin Mclean
wrote:
> Hi,
>
> Also you seem to non approved releases [1] on your Apache website [2]
> please remove these or make it clear that these are not Apache releases
> (which I assume is the case).
>
>
Good catch. Thanks. Those releases were non-Apache re
Thanks Justin. I have a few questions still.
On Sat, Jul 30, 2016 at 10:26 PM Justin Mclean
wrote:
> Hi,
>
> +1 binding
>
> I checked:
> - release name includes incubating
> - signature and hashes correct
> - DISCLAIMER exits
> - LICENSE and NOTICE correct. Although you might want to add
> “(inc
On Sat, Jul 30, 2016 at 10:52 PM Justin Mclean
wrote:
> Hi,
>
> Looking a bit further the the Apache Fluo web site I see a couple of
> concerning things, but presumably this is part of a ongoing effort and will
> be sorted out before graduation:
> - It seems the main source of distribution is git
On Mon, Aug 1, 2016 at 9:37 AM John D. Ament wrote:
> I'm -1 until the website issues are resolved.
>
> - Make sure its clear that any existing releases are not apache endorsed.
> - Make sure the website points to resources contained within the ASF, e.g.
> fluo-dev is a bit of an oddity same for
On Sat, Jul 30, 2016 at 11:14 PM Justin Mclean
wrote:
> No it doesn’t put the files in the mirrors. [6] The dev area is not
> mirrored. You can release them with a simple svn move command.
>
Since the policy allows for the use of the staging repositories at
repository.apache.org for voting, and
On Mon, Aug 1, 2016 at 3:50 PM John D. Ament wrote:
> On Mon, Aug 1, 2016 at 10:29 AM Keith Turner wrote:
>
> > On Mon, Aug 1, 2016 at 9:36 AM, John D. Ament
> > wrote:
> > > I'm -1 until the website issues are resolved.
> > >
> > > - Make sure its clear that any existing releases are not apach
On Mon, Aug 1, 2016 at 5:23 PM John D. Ament wrote:
> On Mon, Aug 1, 2016 at 4:21 PM Christopher wrote:
>
> > On Mon, Aug 1, 2016 at 3:50 PM John D. Ament
> > wrote:
> >
> > > On Mon, Aug 1, 2016 at 10:29 AM Keith Turner wrote:
> > >
> > &
On Mon, Aug 1, 2016 at 5:32 PM Craig Russell
wrote:
>
> Apache will not allow an independent organization to use an Apache brand
> name outside the brand guidelines.
>
>
I think the relevant portion is in
http://www.apache.org/foundation/marks/#domains:
"You may not use ASF trademarks such as "Ap
On Mon, Aug 1, 2016 at 6:22 PM Craig Russell
wrote:
> Hi Christopher,
>
> > On Aug 1, 2016, at 3:00 PM, Christopher wrote:
> >
> > Why would this be a concern for http://fluo.io, but not sites like
> > http://www.stratahadoopworld.com/ or http://accumulosummit.c
Consider this vote canceled, until we can work through some of the issues
identified in the thread.
On Sat, Jul 30, 2016 at 2:14 PM Christopher wrote:
> In preparation for a 1.0.0-incubating release of Fluo, the Fluo team is
> first separately releasing a parent POM. This release passed
I also wish to point out that the FluoProposal (
http://wiki.apache.org/incubator/FluoProposal) explicitly included an
intent/wish/request to continue using the Fluo logo (which includes the
name) on Fluo's historical sites. That proposal was accepted by the IPMC
(albeit without an explicit judgmen
On Mon, Aug 1, 2016 at 8:09 PM John D. Ament wrote:
> Ok, now I'm a bit confused. I'll try my best to state my points of
> clarification in line.
>
> On Mon, Aug 1, 2016 at 7:37 PM Christopher wrote:
>
> > I also wish to point out that the FluoProposal (
>
On Tue, Aug 2, 2016 at 1:02 AM Alex Harui wrote:
>
>
> On 8/1/16, 6:52 PM, "Christopher" wrote:
>
> >> My recommendation is that fluo.io be donated to the ASF and a new
> domain
> >> name chosen for the non-ASF community backed site.
> >>
&g
On Wed, Aug 3, 2016 at 9:14 AM Vice President, Brand Management <
vp-br...@apache.org> wrote:
>
> In particular, using another third party's potential branding mis-use to
> justify your desired uses of an Apache brand is a danger sign, and one
> that likely will draw more scrutiny to your question
IPMC,
Can anybody clarify the right location for releases and release candidates
in dist.apache.org while in incubator?
A: For release candidates, would it be:
A1: https://dist.apache.org/repos/dist/dev/incubator/fluo
or
A2: https://dist.apache.org/repos/dist/dev/fluo
?
B: For releases, is i
On Fri, Aug 5, 2016 at 6:52 PM Julian Hyde wrote:
> It’s A1 and B1. By the time you graduate, the old releases will have moved
> to archive.apache.org/repos/dist/incubator/fluo <
> http://archive.apache.org/repos/dist/incubator/fluo>, but same problem.
> Incubator releases are not “proper" Apache
> On Fri, Aug 5, 2016 at 3:59 PM, Christopher wrote:
> > On Fri, Aug 5, 2016 at 6:52 PM Julian Hyde wrote:
> >
> >> It’s A1 and B1. By the time you graduate, the old releases will have
> moved
> >> to archive.apache.org/repos/dist/incubator/fluo <
>
On Mon, Aug 8, 2016 at 3:34 AM Mark Struberg
wrote:
> Another possible option would be to move it to our CMS.
>
> That would bring us SVN for the people who prefer vi, but also a graphical
> UI for editing.
> And it would make people make familiar with our CMS.
I prefer the Wiki over CMS. I fin
IPMC,
Please consider the following candidates for Fluo Parent POM 1-incubating
and Fluo Build Resources 1.0.0-incubating. There are two artifacts, which
we are releasing together. They do not contain Fluo itself, but are
prerequisites for the Maven build of Fluo, which will be released via Maven
On Mon, Aug 8, 2016 at 6:29 PM John D. Ament wrote:
> +1 release contents look good. Thank you for your due diligence on this
> release.
>
> I'll reply separately about the other comments, to not throw off this
> thread.
>
> Nitpick: Check your signature, may not be valid:
>
> gpg: WARNING: This
On Mon, Aug 8, 2016 at 9:00 PM John D. Ament wrote:
> Christopher,
>
> I wanted to start a separate thread regarding some of your branding
> comments below, to make sure we're all on the same page.
>
> On Mon, Aug 8, 2016 at 5:24 PM Christopher wrote:
>
> > I
On Mon, Aug 8, 2016 at 8:47 PM Justin Mclean
wrote:
> Hi,
>
> +1 binding
>
> I checked:
> - incubating in release name
> - DISCLAIMER exists
> - LICENSE and NOTICE fine
> - No binaries in the release
> - can compile from source
>
> Only one small niggle is that "build-resources-1.0.0-incubating”
Just a quick reminder about this vote, which expires tomorrow. So far,
there are +3
On Tue, Aug 9, 2016 at 1:38 PM Josh Elser wrote:
> Forwarding my (binding) +1 from the PPMC vote.
>
> Christopher wrote:
> > IPMC,
> >
> > Please consider the following candi
This vote passes with +3 (johndament, jmclean, elserj), and no -1.
Thanks all!
On Wed, Aug 10, 2016 at 4:27 PM Christopher wrote:
> Just a quick reminder about this vote, which expires tomorrow. So far,
> there are +3
>
>
> On Tue, Aug 9, 2016 at 1:38 PM Josh Elser wrote:
>
On Fri, Aug 19, 2016 at 6:18 AM Mark Struberg
wrote:
> Good links.
>
> I’d like to add some information for projects who use GIT with maven:
>
> First and important: configure the maven-release-plugin to operate
> ‚locally‘
> https://github.com/apache/deltaspike/blob/master/pom.xml#L123
>
> The i
By "source package must be able to build itself", are you suggesting that
simple projects must create scripts inside the source itself to execute a
simple tar/zip command (for example), instead of just documenting those
lines? That seems a bit frivolous to me.
On Sun, Aug 21, 2016 at 1:59 AM Alex
As I understand things, the licensing information you provide in your
artifacts should reflect everything contained within that artifact. You do
not need to provide license/notice information for dependencies which are
not bundled in your artifact.
On Tue, Sep 20, 2016 at 3:01 PM Donald Szeto wro
Dear IPMC,
Please vote for the following release candidate of Apache Fluo
1.0.0-incubating.
PPMC vote thread:
https://lists.apache.org/thread.html/8b6ec5f17e277ed2d01e8df61eb1f1f42266cd30b9e114cb431c1c17@%3Cdev.fluo.apache.org%3E
Staged dist artifacts:
https://dist.apache.org/repos/dist/dev/incu
Bump. Just want to remind IPMC this vote ends tonight at 11pm Eastern.
On Fri, Sep 30, 2016 at 10:55 PM Christopher wrote:
> Dear IPMC,
>
> Please vote for the following release candidate of Apache Fluo
> 1.0.0-incubating.
>
> PPMC vote thread:
>
> https://list
rote:
> +1 binding
> - signatures and checksums are good
> - builds from source and tests pass except GarbageCollectionIteratorIT
> - source tarball matches tag
> - L&N and headers look good
> - DISCLAIMER is good and file names contain incubating
>
> On Fri, Sep 30, 20
On Tue, Oct 4, 2016 at 6:25 PM Josh Elser wrote:
>
>
> Stian Soiland-Reyes wrote:
> > On 3 October 2016 at 06:30, Luciano Resende
> wrote:
> >> +1,
> >>
> >> I had started something similar, at least on the website side, with best
> >> practices and required branding items.
> >>
> >> Please consi
Forwarding this post from the Fluo dev list, to get wider Incubator
feedback.
Keith's comment shows the importance of labels in the issue tracker (which
is a known limitation in ASF's use of GitHub issues) to try to reach out to
new contributors.
Does anybody have any other suggestions for trying
I believe the DEPENDENCIES file is produced by the Apache Parent POM's
execution of the maven-remote-resources-plugin, and it is generated when
the 'apache-release' profile is active during a release.
On Sat, Oct 29, 2016 at 2:07 AM Dan Halperin
wrote:
> Hi Justin,
>
> Thanks for excellent detai
Sorry if these questions have already been answered, but I'm still a bit
confused, so if anybody can answer I'd be grateful.
Why is GA for podlings being considered before GA for TLPs? Or, is GitHub
already generally available to TLPs, and I missed that? If I didn't miss
anything, what are the arg
I think it could also be confusing for users of the Maven version didn't
match the IPMC released version identifier.
If anything, it probably makes more sense to have the '-incubating' in the
groupId , since it's the endorsement of the foundation which is in the
interim state. The groupId typicall
and avoid
human-error and oversight in what could otherwise be very complicated
releasing.)
> John
>
> [1]:
> http://incubator.apache.org/guides/release-java.html#best-practice-maven
> [2]: http://www.apache.org/dev/repository-faq.html
>
>
> On Tue, Dec 27, 2016 at 9:19 PM
On Wed, Dec 28, 2016 at 8:09 AM John D. Ament wrote:
> On Wed, Dec 28, 2016 at 5:35 AM Daniel Dekany wrote:
>
> > Wednesday, December 28, 2016, 4:12:06 AM, Christopher wrote:
> >
> > [snip]
> > > The one complication here is that the release artifact (source
ripts from HTTP sources when the page itself is loaded with HTTPS.
Projects may wish to check their sites to ensure that their javascript/css
resources are loading correctly when using HTTPS.
--
Christopher
, the page is explicitly marked "Not
Secure".
The end result is that project websites may not be presented to their users
in the way the developers intended.
On Fri, Jan 13, 2017 at 12:54 PM Martin Gainty wrote:
> Hi Christopher
>
>
> did you try disabling default x-domain b
___
> From: Christopher
> Sent: Friday, January 13, 2017 1:17 PM
> To: general@incubator.apache.org
> Subject: Re: HTTPS project sites
>
> No, I did not. This issue has nothing to do with same origin policy (which
> most users should never try to disable). It's about mixed c
SL-everywhere afaict; so seems that we would want to keep
> the HTTP option when in HTTP.
>
> Would love to see Infra providing a 'how many hardcoded http/https' report
> for each subdomain :)
>
> Hen
>
> On Fri, Jan 13, 2017 at 5:18 PM, Christopher wrote:
gt; can cause conflict when serving from a local file system as it'll assume
> > file://.
> >
> > Though I'm not sure what your proposing Christopher other than a issue
> that
> > needs to be added to htrace's jira page.
> >
> > ~ Evan
> >
>
On Tue, Jun 6, 2017 at 6:03 PM sebb wrote:
> On 6 June 2017 at 21:15, Keith Turner wrote:
> > Dear IPMC,
> >
> > Please vote for the following release candidate of Apache Fluo
> > 1.1.0-incubating.
> >
> > PPMC vote thread:
> >
> https://lists.apache.org/thread.html/c815b7a22fab10281ab2d4e88418a
On Tue, Jun 6, 2017 at 6:29 PM sebb wrote:
> On 6 June 2017 at 23:25, Christopher wrote:
> > On Tue, Jun 6, 2017 at 6:03 PM sebb wrote:
> >
> >> On 6 June 2017 at 21:15, Keith Turner wrote:
> >> > Dear IPMC,
> >> >
> >> > Pl
On Tue, Jun 6, 2017 at 6:47 PM sebb wrote:
> On 6 June 2017 at 23:38, Christopher wrote:
> > On Tue, Jun 6, 2017 at 6:29 PM sebb wrote:
> >
> >> On 6 June 2017 at 23:25, Christopher wrote:
> >> > On Tue, Jun 6, 2017 at 6:03 PM sebb wrote:
> >> &g
I've updated the svn staging area to comply with the currently documented
policy.
On Tue, Jun 6, 2017 at 8:59 PM Christopher wrote:
> On Tue, Jun 6, 2017 at 6:47 PM sebb wrote:
>
>> On 6 June 2017 at 23:38, Christopher wrote:
>> > On Tue, Jun 6, 2017 at 6:29 PM se
(FWIW, http://www.apache.org/dev/release-publishing.html#distribution_dist
documents
file conventions from INFRA-8959, but not yet INFRA-13756, but all 3 are
out of sync with the policy linked previously in this thread. It's a very
confusing situation. I've emailed private@infra, David, and Greg, t
On Wed, Jun 7, 2017 at 5:28 PM sebb wrote:
> On 7 June 2017 at 01:59, Christopher wrote:
> > On Tue, Jun 6, 2017 at 6:47 PM sebb wrote:
> >
> >> On 6 June 2017 at 23:38, Christopher wrote:
> >> > On Tue, Jun 6, 2017 at 6:29 PM sebb wrote:
> >> &
Ping IPMC to take a look at this release candidate from Fluo. It currently
has only one +1 from carried over from PPMC vote by mentor, and no other
votes.
On Wed, Jun 7, 2017 at 6:48 PM sebb wrote:
> On 7 June 2017 at 23:36, Christopher wrote:
> > On Wed, Jun 7, 2017 at 5:28 PM se
Here's a good blog post on how to add an additional identity/email to the
existing gpg key, if Keith wished to add his apache email address. It's not
much effort, and it wouldn't change the signatures at all. It would just
link the existing signature to the apache identity.
https://www.katescomment
are
appointed to serve as the initial members of the Apache Fluo Project:
* Billie Rinaldi
* Chris McTague
* Christopher Tubbs
* Corey J. Nolet
* Drew Farris
* Josh Elser
* Keith Turner
* Mike Walch
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
to the office of V
don't graduate by then, the new
committer will appear on our next report. (And will appear on our first
board report if we do graduate.) Our podling status page does include him,
however.
> John
>
> On Mon, Jul 3, 2017 at 4:15 PM John D. Ament
> wrote:
>
> > Hi Christop
esponsibility to regularly evaluate whether to accept bulk code as
subprojects, by opening those flood gates and distracting the PMC from its
primary responsibilities to its existing code.
> (3) Corollary - it seems a large number of Fluo Initial Committers were
> also Accumulo PMC. (I not int
I used the whimsy tool to generate the draft proposal included in this
thread. Very convenient!
My intention was to let this thread sit for the weekend, and start a VOTE
thread on Monday if no new discussion activity.
On Sun, Jul 9, 2017 at 8:38 AM John D. Ament wrote:
> Will the podling be prog
As a project which was born and raised on GitHub, Fluo makes very heavy use
of the issue tracker for day to day decision making and asyncronous
discussions, using GitHub issues and pull requests. We're a R-t-C
community, and a lot of that discussion occurs during code reviews on the
issue tracker.
erve as the initial members of the Apache Fluo Project:
* Billie Rinaldi
* Chris McTague
* Christopher Tubbs
* Corey J. Nolet
* Drew Farris
* Josh Elser
* Keith Turner
* Mike Walch
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Keith Turner be appointed
to the office of Vice President, Apach
ofbizci.net/oci-2/
>
> On Wed, Jul 12, 2017 at 8:45 PM, Dave Fisher
> wrote:
>
> > +1 (binding)
> > > On Jul 10, 2017, at 1:44 PM, Christopher wrote:
> > >
> > > Hello IPMC,
> > >
> > > The recent DISCUSS thread on the topic of Fluo
Is there any documentation detailing how to file a proper and complete JIRA
for graduation?
For example, which components should be put in the JIRA, issue type, etc.
It seems to me that good docs in this regard could save INFRA a lot of
headaches, and could help projects understand which infrastru
a sub-task, as instructed.
On Mon, Jul 24, 2017 at 8:12 PM John D. Ament wrote:
> Christopher,
>
> Please review [
> <
> https://incubator.apache.org/guides/transferring.html#first_steps_outside_the_incubator
> >
> 1]
>
> If something seems off - we just did a re
one should set as the component (I set "TLP Admin").
"""
It's minor stuff, but still a bit confusing. I'm sure we'll get it ironed
out.
On Wed, Jul 26, 2017 at 2:10 PM John D. Ament
wrote:
> Looks like the link to
> https://issues.apache.org/jira/service
+1
However, I would personally prefer to see all projects using git-wip
automatically migrated to GitBox, and have the old host(s) redirect to
gitbox, so the migration is completely transparent. It doesn't force any
projects to use GitBox features, but I can't see any downside, and it gives
everyb
than me. :)
On Fri, Jul 28, 2017 at 5:45 PM Greg Stein wrote:
> The service is not in general release, so no: we won't be mass-migrating
> projects, and we reserve the right to halt migration requests.
>
> On Jul 28, 2017 13:30, "Christopher" wrote:
>
> > +1
&g
It seems Fluo is on the podling reporting schedule for August, but since
we've just graduated, we're not sure if we need to submit a final report,
or just focus on our own first TLP report.
Any guidance here?
On Tue, Aug 1, 2017 at 3:47 AM wrote:
> Dear podling,
>
> This email was sent by an au
explain how
to remove us from the podling reporting schedule. Thanks.
On Tue, Aug 1, 2017 at 5:14 PM Christopher wrote:
> It seems Fluo is on the podling reporting schedule for August, but since
> we've just graduated, we're not sure if we need to submit a final report,
>
minders. I think you
> will
> > need to wait for John.
> >
> > The Board accepted your resolution. You are a TLP and the Incubator no
> > longer needs your report.
> >
> > Regards,
> > Dave
> >
> > > On Aug 2, 2017, at 11:49 AM, Christopher
On Wed, Aug 30, 2017 at 5:08 PM Julian Hyde wrote:
> What is the correct forum for discussing release distribution policy?
>
>
Good question. I hope it's this one, since this is where the discussion is
happening.
> Current policy [1] states:
>
> Every artifact distributed to the public throu
nk P. Penning wrote:
> On Fri, 1 Sep 2017, Christopher wrote:
>
> > Date: Fri, 1 Sep 2017 03:29:58 +0200
> > From: Christopher
> > To: general@incubator.apache.org
> > Subject: Re: Digests in releases
> >
> > On Wed, Aug 30, 2017 at 5:08 PM Julian Hyde wr
Should the Apache Incubator update the README on all retired podlings, to
more clearly indicate their retired status?
For example, from the README at https://github.com/apache/incubator-pirk ,
it's not obvious that the podling is retired.
I know there's a RETIRED.txt file, but that's easily overl
t from my iPhone
>
> > On Nov 2, 2017, at 1:56 PM, Christopher wrote:
> >
> > Should the Apache Incubator update the README on all retired podlings, to
> > more clearly indicate their retired status?
> >
> > For example, from the README at https://github.com/apache/incub
seem to have anything to do with this donation,
though. Does it make sense to remind people to do X before Y, when Y is a
NOOP for them?
Thanks,
Christopher
On Mon, Apr 16, 2018 at 8:28 PM Roman Shaposhnik
wrote:
> On Mon, Apr 16, 2018 at 4:18 PM, Christopher wrote:
> > Two questions about IP CLEARANCE:
> >
> > There is a line item in the template for making sure that files are
> updated
> > to reflect ASF copyright
On Mon, Apr 16, 2018 at 10:34 PM Dave Fisher wrote:
>
>
> Sent from my iPhone
>
> > On Apr 16, 2018, at 7:16 PM, Christopher wrote:
> >
> > On Mon, Apr 16, 2018 at 8:28 PM Roman Shaposhnik
> > wrote:
> >
> >>> On Mon, Apr 16, 2018 at 4:18
Have you tried the tool at
https://whimsy.apache.org/committers/moderationhelper.cgi ?
On Tue, Apr 17, 2018 at 2:06 PM Gian Merlino wrote:
> Hi incubators,
>
> Is there a tool somewhere to review the membership of a mailing list?
>
> We (Druid) are working on migrating our mailing lists now. As
he
next 72 hours.
Thanks,
Christopher Tubbs
[1]:
https://lists.apache.org/thread.html/921012ad4be72642e81e1f06aee1bdb6c973e85f76f91bc12c180a84@%3Cdev.fluo.apache.org%3E
[2]:
https://incubator.apache.org/ip-clearance/fluo-astralway-code-repos.html
[3]:
https://svn.apache.org/repos/asf/incubator/pu
IP Clearance passes by lazy consensus.
On Mon, Apr 23, 2018 at 6:08 PM Christopher wrote:
> The Apache Fluo PMC has voted[1] to receive a large contribution from the
> "Astralway" team on GitHub. The IP Clearance page has been updated[2],
> though recent SVN updates to th
On Wed, May 23, 2018 at 12:16 AM Greg Stein wrote:
> On Mon, May 21, 2018 at 2:52 AM Justin Mclean
> wrote:
>
> > Hi,
> >
> > > Javascript code that is minified or combined in any major way is much
> > more
> > > like binary code in that respect. It is true that somebody *could*
> > inspect
> >
Ideally, the GitHub traffic would go to a separate list... yes?
On Thu, Jun 3, 2021 at 12:42 PM Julian Hyde wrote:
>
> How much will this increase the email traffic?
>
> > On Jun 3, 2021, at 9:39 AM, Dave Fisher wrote:
> >
> > Unless there is an objection I will turn on GitHub Issues on
> > htt
No. These are generated as part of Maven, and are described as part of
the Maven2 repository layout[1]. They are (optionally) used by the
artifact resolver in the Maven client to validate artifacts when they
are retrieved from a server using the Maven2 repository layout.
It's possible that the too
n the meantime, I'll proceed to delete the now defunct Jenkins job.
Thanks,
Christopher
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Corrected an email typo.
Deleted as it is deprecated.
Chris
Index: project.xml
===
--- project.xml (revision 57139)
+++ project.xml (working copy)
@@ -121,10 +121,9 @@
-[EMAIL PROTECTED]
+[EMAIL PROTECTED
Added InstanceService in NodeContextImpl ctor and used it in saving
instance data instead of having a local variable "instanceData".
This bug is not obvious when using in-memory persistence.
Chris
Index: src/test/org/apache/agila/impl/NodeContextImplTestCase.java
coming soon.
On Mon, 20 Dec 2004 22:06:54 -0800 (PST), Hemali Kunjeer
<[EMAIL PROTECTED]> wrote:
> Hello,
> Where i can get agila documents for reference?
>
>
> -
> Do you Yahoo!?
> Meet the all-new My Yahoo! â Try it today!
>
--
Hi Kumaran,
First step is to subscribe on the following mailing lists:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
We'll discuss Agila there.
Source is available at:
http://svn.apache.org/repos/asf/incubator/agila/trunk/
Cheers!
--
Chris
On Thu, 13 Jan 2005 18:36:46 -0700, kumx thum <[EMAIL PROTECTE
+1 (non-binding)
On 30 November 2010 06:52, Dan Peterson wrote:
> Hi everyone,
>
> Please vote on the acceptance of Wave into the Apache incubator.
>
> The proposal is available at:
> http://wiki.apache.org/incubator/WaveProposal
> (for your convenience, a snapshot is also copied below)
>
> The
I can understand why Subversion should be made a top level project quickly,
but I personally believe the namespace change is a reasonable request in
order to graduate for all the same reasons that convinced me Pivot should
change its namespace.
It sends the wrong message not to change given the im
1 - 100 of 132 matches
Mail list logo
