[jira] [Closed] (COMDEV-172) JIRA projects may not be detected correctly
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[ 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
[jira] [Created] (COMDEV-253) Add mission statement to project web page
Isabel Drost-Fromm created COMDEV-253: - Summary: Add mission statement to project web page Key: COMDEV-253 URL: https://issues.apache.org/jira/browse/COMDEV-253 Project: Community Development Issue Type: Improvement Components: Projects Website Reporter: Isabel Drost-Fromm Attachments: add_mission_to_website.diff A while ago Rich proposed to adopt a new mission for comdev. I only heard positive feedback for that. Nothing of it is reflected in the comdev web page though. The intention of this patch is to add the proposed mission statement front and center to the comdev web page. -- 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] [Commented] (COMDEV-52) Launch ASF Mentor programme
[ https://issues.apache.org/jira/browse/COMDEV-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335714#comment-16335714 ] Isabel Drost-Fromm commented on COMDEV-52: -- Is this issue still valid? It seems fairly dated... > 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
