Re: Apache Policy Quiz

[Greg Stein]

Every single question that I answered gave me a "not quite right". Even
when it asked if an Apache product can be distributed under Cat-X and I
said "No", it said "not quite right". That was a simple yes/no, and an
obvious "no" answer. ... That was the final straw after a series of
multiple-choice questions that I got "not quite right", thinking maybe I
missed some nuance. Not at all. When it said my "no" answer wasn't right...
Well.

The quiz logic seems broken.


On Wed, Jan 24, 2018 at 7:49 PM, Justin Mclean 
wrote:

> Hi,
>
> A while back I posted a little logo game. [1] Well after a few comments on
> the incubator list around projects possibly graduating without fully
> understanding ASF policy, and some issues with recent release got me
> thinking is there another way we can present this information. So I made a
> little multiple choice quiz on ASF policy. [2] Give it a try [3] and tell
> me what you think. (It’s probably harder and not as fun as the logo game
> but aimed at a different audience.)
>
> Currently it only has a dozen or so questions with some variation, so you
> may get the same question asked but it’s likely to have different answers
> in a different order. Anyway if people think this is useful perhaps we can
> expand it with more questions and broaden the scope to include other areas
> like the Apache Way, how the foundation works and the like.
>
> I may of made mistakes and it likely some words and sentences probably
> need correcting. Proof readers and PRs welcome.
>
> BTW it doesn’t save your scores anywhere so if you get a question wrong
> only you will know but hopefully you might learn something. Have a record
> of number of people taking the quiz and results by incubating project might
> be interesting but probably a little invasive.
>
> Thanks,
> Justin
>
> 1. https://github.com/justinmclean/ApacheLogos
> 2. https://github.com/justinmclean/ApacheQuiz
> 3. https://rawgit.com/justinmclean/ApacheQuiz/master/compiled/index.html
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Apache Policy Quiz

[Justin Mclean]

Hi,

A while back I posted a little logo game. [1] Well after a few comments on the 
incubator list around projects possibly graduating without fully understanding 
ASF policy, and some issues with recent release got me thinking is there 
another way we can present this information. So I made a little multiple choice 
quiz on ASF policy. [2] Give it a try [3] and tell me what you think. (It’s 
probably harder and not as fun as the logo game but aimed at a different 
audience.)

Currently it only has a dozen or so questions with some variation, so you may 
get the same question asked but it’s likely to have different answers in a 
different order. Anyway if people think this is useful perhaps we can expand it 
with more questions and broaden the scope to include other areas like the 
Apache Way, how the foundation works and the like.

I may of made mistakes and it likely some words and sentences probably need 
correcting. Proof readers and PRs welcome.

BTW it doesn’t save your scores anywhere so if you get a question wrong only 
you will know but hopefully you might learn something. Have a record of number 
of people taking the quiz and results by incubating project might be 
interesting but probably a little invasive.

Thanks,
Justin

1. https://github.com/justinmclean/ApacheLogos
2. https://github.com/justinmclean/ApacheQuiz
3. https://rawgit.com/justinmclean/ApacheQuiz/master/compiled/index.html
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Commented] (COMDEV-248) add /dist/ health issues (fwd)

[Henk P. Penning]

Hi,

  FYI ; the updated reporter is now in production ;

  diffs :

  
http://svn.apache.org/viewvc/comdev/reporter.apache.org/trunk/site/getjson.py?view=diff=1822083=1822084=1822084

  
http://svn.apache.org/viewvc/comdev/reporter.apache.org/trunk/site/js/render.js?view=diff=1822113=1822114=1822114

  Regards,

  HPP

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

-- Forwarded message --
Date: Tue, 23 Jan 2018 17:55:23 +0100 (CET)
From: Henk P. Penning 
To: dev@community.apache.org
Subject: Re: [jira] [Commented] (COMDEV-248) add /dist/ health issues

On Mon, 22 Jan 2018, Shane Curcuru wrote:


 Date: Mon, 22 Jan 2018 16:07:20 -0500
 From: Shane Curcuru 
 To: dev@community.apache.org
 Subject: Re: [jira] [Commented] (COMDEV-248) add /dist/ health issues

 Here's my +1 as a ComDev PMC member asking for Henk to get access to the
 projects-vm where code behind the reporter tool (and other tools) lives,
 so that he can continue the below work.

 This is related to COMDEV-248 and:

  https://issues.apache.org/jira/browse/INFRA-15867

 Once this is debugged, we should look for volunteers to check their
 project's reports for the new "Dist Checker" section of reports, and
 make any suggestions for improving the docs.


Hi,

  Please try the new (test) reporter at

https://reporter.apache.org/index-hppdev.html

   The new reporter adds a section "Dist Checker", but only if
   the checker[1] has found some errors in /dist/$project/ ;
   that is, those projects mentioned under "projects with problems"
   by the checker [e.g. aries, bigtop, cloudstack, ... ].

  [1] https://checker.apache.org/

  Any feedback is most welcome ; thanks ; groeten,

  Henk Penning

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/


 Shane Curcuru wrote on 1/18/18 9:45 AM:

 For those who don't know Henk, he's built tooling and websites for
 checking and understanding keysigning and releases here at Apache for
 ages and ages.  This would be a great addition to the reporter tool.

 My only comment (for later) is to ensure that when issues are found in a
 project, we make sure that the documentation about what the problem is
 and how to fix is clear for newer committers.  Henk's already written
 this kind of stuff in the README page though, so that should be easy:

   https://checker.apache.org/doc/README.html


 Henk P. Penning wrote on 1/18/18 9:26 AM:

 Hi,

   Regarding : https://issues.apache.org/jira/browse/COMDEV-248

   Talked with Shane Curcuru on infra hipchat.

   BASE = https://checker.apache.org/json/

   The idea is to include $BASE info in https://reporter.apache.org/ ;
   conditionally : nothing is shown if there are no issues to report.

   The idea is :

   -- periodically fetch the BASE on projecs-vm.apache.org

   -- to fix "getjson.py" so the output of (for instance)
  https://reporter.apache.org/getjson.py?only=httpd
  contains an attribute like
    { ..., "checker" : { "httpd": { "problem_count" : N } }, ... }

   -- fix render.js to (conditionally) show the count + one or two
 references.

   The plan is to :

   -- confer with Daniel Gruno, the main author of reporter.
   -- deploy a copy of getjson.py (as getjson-dev.py) and take it from
 there.

   As I'm new to community-dev and projects-vm.apache.org,
   I have these questions :

   -- Is this plan the proper way to fix stuff in reporter.apache.org ?
   -- Can I get access to projects-vm.apache [necessary to understand
  the current code ; not everything is in svn or git] ?

   Thanks ; regards,

   Henk Penning -- apache.org infrastructure ; dist & mirrors

    _
 Henk P. Penning, ICT-beta R Uithof MG-403    _/ \_
 Faculty of Science, Utrecht University    T +31 30 253 4106 / \_/ \
 Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
 http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

 -
 To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
 For additional commands, e-mail: dev-h...@community.apache.org







 -- 


 - Shane
  https://www.apache.org/foundation/marks/resources

 -
 To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
 For additional commands, e-mail: 

Feedback on dist health checker (was: [jira] [Commented] (COMDEV-248) add /dist/ health issues)

[sebb]

On 23 January 2018 at 16:55, Henk P. Penning  wrote:
...
> Hi,
>
>   Please try the new (test) reporter at
>
> https://reporter.apache.org/index-hppdev.html
>
>   The new reporter adds a section "Dist Checker", but only if
>   the checker[1] has found some errors in /dist/$project/ ;
>   that is, those projects mentioned under "projects with problems"
>   by the checker [e.g. aries, bigtop, cloudstack, ... ].
>
>   [1] https://checker.apache.org/
>
>   Any feedback is most welcome ; thanks ; groeten,

Seems to work OK.

I think the Dist checker section should always be present otherwise
one does not know if it has been run or not. It should perhaps say
something like: all files have valid sigs and hashes OR no release
files found (e.g. Whimsy).

Since the checks relate to releases, perhaps the information should be
presented in the Releases section rather than separately.

Also it appears that the checker does not check if the KEYS file is
present nor if it contains the required keys.

The Aries errors (sig expired) are caused by a very old release.
It looks like they have not published any recent releases to dist.
Maybe the tool could check the dist contents against the releases database.

>   Henk Penning

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Resolved] (COMDEV-202) Ability to tag tasks with mailing list threads discussing / working on the help wanted task

[Sebb (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb resolved COMDEV-202.
-
Resolution: Won't Fix

> Ability to tag tasks with mailing list threads discussing / working on the 
> help wanted task
> ---
>
> Key: COMDEV-202
> URL: https://issues.apache.org/jira/browse/COMDEV-202
> Project: Community Development
>  Issue Type: Improvement
>  Components: Help Wanted
>Reporter: Nick Burch
>Priority: Major
>
> The first time someone emails the list to volunteer for a given task, there's 
> often a few posts detailing more on the task and what's needed. When 
> subsequent people volunteer, they seem to come in "blind" and new threads are 
> started. Often, information on the task gets scattered through several threads
> With the shiny new lists.apache.org interface giving the ability to view 
> threads and even participate, it would be good if we (as committers) could 
> later edit a task to provide details of one or more mailing list threads for 
> a task. The interface would then link through to those under a heading like 
> "work so far" or "discussions so far". That way, additional volunteers coming 
> across the task can see more on what's needed, see the progress, and then 
> join the existing thread to help



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Reopened] (COMDEV-202) Ability to tag tasks with mailing list threads discussing / working on the help wanted task

[Sebb (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebb reopened COMDEV-202:
-

> Ability to tag tasks with mailing list threads discussing / working on the 
> help wanted task
> ---
>
> Key: COMDEV-202
> URL: https://issues.apache.org/jira/browse/COMDEV-202
> Project: Community Development
>  Issue Type: Improvement
>  Components: Help Wanted
>Reporter: Nick Burch
>Priority: Major
>
> The first time someone emails the list to volunteer for a given task, there's 
> often a few posts detailing more on the task and what's needed. When 
> subsequent people volunteer, they seem to come in "blind" and new threads are 
> started. Often, information on the task gets scattered through several threads
> With the shiny new lists.apache.org interface giving the ability to view 
> threads and even participate, it would be good if we (as committers) could 
> later edit a task to provide details of one or more mailing list threads for 
> a task. The interface would then link through to those under a heading like 
> "work so far" or "discussions so far". That way, additional volunteers coming 
> across the task can see more on what's needed, see the progress, and then 
> join the existing thread to help



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Old JIRA issues - close?

[Isabel Drost-Fromm]

On Tue, Jan 23, 2018 at 02:41:12PM +0100, Bertrand Delacretaz wrote:
> On Tue, Jan 23, 2018 at 1:39 PM, Isabel Drost-Fromm  wrote:
> > ...Would it
> > make sense to close the ones that haven't received any activity since 
> > 2016?...
> 
> +1, if needed they can be reopened or recreated.

Done - it took me a while to realize that JIRA has a bulk transition tool, so 
sorry
for the spam I caused initially.

Fingers crossed only the correct issues were returned by the search I used
to seed the bulk change.

Isabel


-- 
Sorry for any typos: Mail was typed in vim, written in mutt, via ssh (most 
likely involving some kind of mobile connection only.)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-172) JIRA projects may not be detected correctly

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-172.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> JIRA projects may not be detected correctly
> ---
>
> Key: COMDEV-172
> URL: https://issues.apache.org/jira/browse/COMDEV-172
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> The MTOMCAT JIRA project is used by a Tomcat project, but Tomcat otherwise 
> uses Bugzilla only.
> The code does not currently detect that the MTOMCAT key is associated with 
> Tomcat.
> There may be other such PMCs that have undetected JIRA projects.
> It's probably not feasible to insist that all such orphan JIRA projects are 
> listed in a PMC Category, so some other means is needed to document these 
> anomalies, e.g. a json file that is manually maintained.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-171) Skip the JIRA query if the project does not use it

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-171.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Skip the JIRA query if the project does not use it
> --
>
> Key: COMDEV-171
> URL: https://issues.apache.org/jira/browse/COMDEV-171
> Project: Community Development
>  Issue Type: Improvement
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> The JIRA queries are expensive, so it would be useful to be able to skip them 
> if it is known that the project does not use JIRA.
> It should be possible to use the data/JIRA/projects.json file for this.
> It looks like the "key" field would be suitable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-176) getjson.py reads project.json file for details of the PMC

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-176.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> getjson.py reads project.json file for details of the PMC
> -
>
> Key: COMDEV-176
> URL: https://issues.apache.org/jira/browse/COMDEV-176
> Project: Community Development
>  Issue Type: Bug
>Reporter: Sebb
>Priority: Major
>
> The getjson.py script method getProjectData reads 
> site/json/projects/.json.
> However the method is being used to find the PMC name and chair and 
> shortdesc. It should be using details of the PMC, not the project which 
> happens to share its name



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-182) Tidy up handling of data/ changes

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-182.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Tidy up handling of data/ changes
> -
>
> Key: COMDEV-182
> URL: https://issues.apache.org/jira/browse/COMDEV-182
> Project: Community Development
>  Issue Type: Bug
>  Components: Projects Website
>Reporter: Sebb
>Priority: Major
>
> At present, projects.a.o relies on manual intervention to update the index 
> files under data/
> committees.xml
> projects.xml
> The cron job currently moves RDF files from data/committees/ to 
> data/committees-retired/ if it detects that a PMC has been retired.
> However it does not attempt to update the xml files, and the SVN 
> projects_role is not able to commit files under data/
> This means that the workspace on people.a.o gets out of date.
> The data/ area is also updated manually.
> This makes it difficult to commit changes without running the risk of locking 
> the workspace on people.a.o.
> The cronjobs should not attempt to tidy up the RDF files in this area; that 
> should be left to manual intervention.
> There needs to be a separate script to tidy the data/ tree.
> The cronjobs should report any discrepancies, but not attempt to resolve them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-174) projects.json is inaccurate for graduated podlings

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-174.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> projects.json is inaccurate for graduated podlings
> --
>
> Key: COMDEV-174
> URL: https://issues.apache.org/jira/browse/COMDEV-174
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> The entries in projects.json come from scraping the page
> http://people.apache.org/committer-index.html
> This includes both LDAP groups and auth groups that are defined in the 
> asf-authorization-template file.
> The script takes note of when a group is first seen, any subsequent changes 
> are regarded as additions to the group.
> The reporter tool is supposed to show what changes the PMC has made.
> However, when a podling graduates, the template group is converted into the 
> corresponding LDAP unix group. This means that changes to the podling group 
> are recorded from the start of the podling rather than the start of the PMC. 
> One way to fix this might be to ignore changes that occurred before the PMC 
> creation date. Unfortunately the exact creation date is not currently 
> recorded in the committee-info data file (only the month/year is stated). It 
> should be possible to deduce the actual date from the earliest joining dates 
> (assuming these are accurate).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-191) Add HTrace distributed tracing for s3 and other alternative Hadoop FS implementations

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-191.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Add HTrace distributed tracing for s3 and other alternative Hadoop FS 
> implementations
> -
>
> Key: COMDEV-191
> URL: https://issues.apache.org/jira/browse/COMDEV-191
> Project: Community Development
>  Issue Type: New Feature
>Reporter: Colin P. McCabe
>Priority: Major
>  Labels: gsoc, gsoc2016, mentor
>
> The Apache HTrace distributed tracing framework allows developers and system 
> administrators to get an end-to-end view of system performance, in a manner 
> similar to XTrace or Dapper.  See http://htrace.incubator.apache.org/
> s3, GCS, WASB, and other cloud blob stores are becoming increasingly 
> important in Hadoop.  But we don't have distributed tracing for these yet.  
> It would be interesting to add distributed tracing here.  It would enable 
> collecting really interesting data like probability distributions of PUT and 
> GET requests to s3 and their impact on MR jobs, etc.  We should add HTrace 
> distributed tracing for s3 and other alternative Hadoop FS implementations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-183) Add HTrace distributed tracing integration to YARN

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-183.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Add HTrace distributed tracing integration to YARN
> --
>
> Key: COMDEV-183
> URL: https://issues.apache.org/jira/browse/COMDEV-183
> Project: Community Development
>  Issue Type: New Feature
>Reporter: Colin P. McCabe
>Priority: Major
>  Labels: Gsoc2016, gsoc, mentor
>
> Distributed tracing allows users to follow a request through the entire 
> distributed system, crossing network and project boundaries.  The Apache 
> HTrace project has added distributed tracing to HDFS and HBase (among other 
> projects).  We should add tracing to YARN so that MapReduce, spark, and other 
> frameworks can make use of it.
> Tracing should identify which yarn rpcs were made, and also tag top level 
> trace spans with the yarn job that they are associated with.  That would let 
> us analyze information relevant to a particular YARN job or set of jobs.  
> There are a lot of interesting projects here-- detecting hardware failures in 
> production clusters, analyzing patterns in MR or Spark jobs, etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-192) Add a Kudu backend for Apache HTrace

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-192.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Add a Kudu backend for Apache HTrace
> 
>
> Key: COMDEV-192
> URL: https://issues.apache.org/jira/browse/COMDEV-192
> Project: Community Development
>  Issue Type: New Feature
>Reporter: Colin P. McCabe
>Priority: Major
>  Labels: gsoc, gsoc2016, mentor
>
> The Apache HTrace distributed tracing framework allows developers and system 
> administrators to get an end-to-end view of system performance, in a manner 
> similar to XTrace or Dapper. See http://htrace.incubator.apache.org/
> Kudu is a key/value store optimized for analytic workloads, with excellent 
> performance and latency on large datasets.  See 
> https://blog.cloudera.com/blog/2015/09/kudu-new-apache-hadoop-storage-for-fast-analytics-on-fast-data/
>   It is columnar and supports predicate push-down and many other 
> optimizations.  Storing HTrace traces in Kudu would allow us to run SQL 
> queries on the data and get rapid responses (via either Impala, Spark, or 
> other execution engines).  This would enable near-realtime analysis of HTrace 
> data.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-196) 404 at https://projects.apache.org/create.html

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-196.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> 404 at https://projects.apache.org/create.html
> --
>
> Key: COMDEV-196
> URL: https://issues.apache.org/jira/browse/COMDEV-196
> Project: Community Development
>  Issue Type: Bug
>  Components: Comdev
>Reporter: Jacques Le Roux
>Priority: Major
>
> This page is missing, though still referenced in Google



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-200) Feature's created by Oregon State University senior project group who partnered with Ross Gardler to create tools fto help this project grow

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-200.
-
Resolution: Fixed

Hasn't been touched in years. Please reopen if still needed

> Feature's created by Oregon State University senior project group who 
> partnered with Ross Gardler to create tools fto help this project grow
> 
>
> Key: COMDEV-200
> URL: https://issues.apache.org/jira/browse/COMDEV-200
> Project: Community Development
>  Issue Type: New Feature
>  Components: Comdev
> Environment: Docker Container, Web Based Application
>Reporter: Justin Bruntmyer
>Priority: Major
>  Labels: features, patch
> Attachments: patch.diff
>
>
> The patch file associated with this issue contains fixes to some things and 
> adds new features to the application. This patch includes a fix to the people 
> page that lists imported members. The fix allows the page to load quicker and 
> without crashing in browsers. A feature added in this patch includes the tool 
> of tweeting at a person who has been imported. Another feature is the 
> implementation of account creation and login system which commands such as 
> ‘import events’ are hidden behind (you must be logged-in in order to do 
> this). Another feature added is listing tweets about events via the 
> application and not via the application. There is also a feature for 
> exporting a lists of information as an EXCEL file that contains people 
> information. This patch also includes visual improvements of the website in 
> some locations such as the individual people pages and event pages. This 
> patch includes tweaks to the hashtag sorting in finding events. The feature 
> of Google Maps being used is also included by showing a map along with 
> markers for each imported location and a way to search in a certain radius of 
> an area. The radius circle is hard-coded but a user can search to find events 
> nearby. Lastly, this patch includes a people section where you can view only 
> hosts of events and see individual pages about the hosts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-198) Support for podlings

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-198.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Support for podlings
> 
>
> Key: COMDEV-198
> URL: https://issues.apache.org/jira/browse/COMDEV-198
> Project: Community Development
>  Issue Type: New Feature
>  Components: Reporter Tool
>Reporter: John D. Ament
>Priority: Major
>
> It would be great if reporter could work for podlings as well as TLPs.  Not 
> all features are needed if I had to guess, but the board report format would 
> be useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-202) Ability to tag tasks with mailing list threads discussing / working on the help wanted task

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-202.
-
Resolution: Fixed

Hasn't been touched in years. Please reopen if still needed

> Ability to tag tasks with mailing list threads discussing / working on the 
> help wanted task
> ---
>
> Key: COMDEV-202
> URL: https://issues.apache.org/jira/browse/COMDEV-202
> Project: Community Development
>  Issue Type: Improvement
>  Components: Help Wanted
>Reporter: Nick Burch
>Priority: Major
>
> The first time someone emails the list to volunteer for a given task, there's 
> often a few posts detailing more on the task and what's needed. When 
> subsequent people volunteer, they seem to come in "blind" and new threads are 
> started. Often, information on the task gets scattered through several threads
> With the shiny new lists.apache.org interface giving the ability to view 
> threads and even participate, it would be good if we (as committers) could 
> later edit a task to provide details of one or more mailing list threads for 
> a task. The interface would then link through to those under a heading like 
> "work so far" or "discussions so far". That way, additional volunteers coming 
> across the task can see more on what's needed, see the progress, and then 
> join the existing thread to help



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-203) Timezone issues with release dates

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-203.
-
Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed

> Timezone issues with release dates
> --
>
> Key: COMDEV-203
> URL: https://issues.apache.org/jira/browse/COMDEV-203
> Project: Community Development
>  Issue Type: Bug
>  Components: Reporter Tool
>Reporter: Sebb
>Priority: Major
>
> Release dates are stored as seconds since the epoch in the 
> data/release/committe.json files. In theory all the dates should convert to 
> midnight UTC on the release date.
> If dates are obtained from JIRA, they are converted using the Python method 
> time.mktime() which uses the local timezone. This is done on the reporter.a.o 
> host, which is currently running UTC. However the host was originally set up 
> in a different timezone, so some of the dates don't convert to midnight. It 
> should have used calendar.gmtime() instead.
> If the dates are obtained from the user, then the -MM-DD string is 
> converted using Javascript using (new Date(,mm,dd)).getTime() which 
> assumes the local timezone. The converted value is passed back as an integer 
> to the python script. It should use Date.UTC(,mm,dd) instead. Or it could 
> pass back the date string for conversion by the Python code.
> It's easy enough to fix new dates going forward.
> However there are existing dates that will need correction.
> The dates are all converted assuming a local time of midnight, so when they 
> are converted back again, the local time offset will show up as a number of 
> hours since midnight. This can be used to adjust the value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Closed] (COMDEV-52) Launch ASF Mentor programme

[Isabel Drost-Fromm (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COMDEV-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Isabel Drost-Fromm closed COMDEV-52.

Resolution: Won't Fix

Hasn't been touched in years. Please reopen if still needed.

> Launch ASF Mentor programme
> ---
>
> Key: COMDEV-52
> URL: https://issues.apache.org/jira/browse/COMDEV-52
> Project: Community Development
>  Issue Type: Task
>  Components: Comdev
>Reporter: Ross Gardler
>Priority: Critical
>
> The ASF mentoring programme is designed to assist people who wish to 
> understand how the ASF works.
> See http://community.apache.org/mentoringprogramme.html
> This is a parent task to track the creation and implementation of the mentor 
> programme.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org