[jira] [Closed] (COMDEV-423) svn pubsub fallen over on apachecon.com
[ https://issues.apache.org/jira/browse/COMDEV-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-423. Resolution: Cannot Reproduce It's Community Over Code, now! :) > svn pubsub fallen over on apachecon.com > --- > > Key: COMDEV-423 > URL: https://issues.apache.org/jira/browse/COMDEV-423 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Rich Bowen >Priority: Major > > Updates to svn are no longer being reflected on > [www.apachecon.com|http://www.apachecon.com/] > Can someone please kick svnpubsub? Thanks. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-478) https://reporter.apache.org/addrelease.html?sling leads to page crash with Chrome
[
https://issues.apache.org/jira/browse/COMDEV-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Curcuru closed COMDEV-478.
Resolution: Cannot Reproduce
I can't reproduce either on Mac / Chrome {color:#5f6368}Version 114.0.5735.133
(Official Build) (arm64), and I know some work has been done on reporter since
this was reported, so... and yes, the page renders with a LOT of past
releases!{color}
{color:#5f6368}Apologies for the delay and feel free to reopen if needed.{color}
> https://reporter.apache.org/addrelease.html?sling leads to page crash with
> Chrome
> -
>
> Key: COMDEV-478
> URL: https://issues.apache.org/jira/browse/COMDEV-478
> Project: Community Development
> Issue Type: Bug
> Components: Reporter Tool
> Environment: Chrome Version 104.0.5112.101 (Official Build) (arm64)
> Mac OS 12.5.1
>Reporter: Konrad Windszus
>Priority: Major
>
> When opening the page [https://reporter.apache.org/addrelease.html?sling] it
> crashes in Google Chrome after a few seconds with Error Code 5
> ([https://support.google.com/chrome/answer/95669?visit_id=637966697117475835-2175500643=e_awsnap=1#zippy=%2Cpage-loading-error-codes-and-issues]).
> With Firefox it does load (but takes a while).
> I assume this is due to the huge amount of past releases done by Sling.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-326) Committer invite template omits PMC role details
[ https://issues.apache.org/jira/browse/COMDEV-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741622#comment-17741622 ] Shane Curcuru commented on COMDEV-326: -- More to the point, this page isn't linked from the "official" PMC guide on how to do things like add committers or PMC members, so I'd bet many PMC don't ever read it. A key topic for discussion is how to clearly reconcile - and crosslink where relevant - the a.o/dev pages (with explicit guides on how to do things) versus any informational content on community.a.o https://apache.org/dev/pmc.html#newcommitter > Committer invite template omits PMC role details > > > Key: COMDEV-326 > URL: https://issues.apache.org/jira/browse/COMDEV-326 > Project: Community Development > Issue Type: Bug > Components: Website > Environment: > https://community.apache.org/newcommitter.html#committer-invite-template >Reporter: Sebb >Priority: Major > > The committer invite template [1] is not very clear on the distinction > between an invitation as a committer, and invitation as a committer + PMC > member. > In particular, it describes the role of the committer, but largely ignores > the PMC role. > As a result, I have seen at least one acceptance reply that said "I accept to > become a committer" [2] - leaving unstated whether or not they agree to > become a PMC member. > I think any template needs to make very clear what is involved in the PMC > role, and also that the invitee has 3 choices: > - decline both invites > - accept the committer invite and decline the PMC invite > - accept both committer invite and PMC invite > [1] https://community.apache.org/newcommitter.html#committer-invite-template > [2] > https://lists.apache.org/thread.html/796c4b3e8c0f191add39c7d1b6cc154a5e316910df8120db1151c739@%3Cprivate.jackrabbit.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-437) Committer map loads with Google Maps error
[ https://issues.apache.org/jira/browse/COMDEV-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709381#comment-17709381 ] Shane Curcuru commented on COMDEV-437: -- The ComDev PMC would love it if someone steps up to fix this - check out the code and let us know if you have patches! But the other issue is we need some volunteers to publicise this, and get existing committers to update or add data. It hasn't really been surfaced for ages. And a really good question is: where is the source & server config data for the community zones server? > Committer map loads with Google Maps error > -- > > Key: COMDEV-437 > URL: https://issues.apache.org/jira/browse/COMDEV-437 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Benjamin Marwell >Priority: Major > > The web page [https://community.zones.apache.org/map.html] loads with errors. > The error shown redirects to > [https://developers.google.com/maps/documentation/javascript/error-messages?utm_source=maps_js_medium=degraded_campaign=billing#api-key-and-billing-errors] > > Maybe it should be converted to using OpenStreetMap.org. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-424) An open Source Charging Function for 5G-SA - OPENCHF
[ https://issues.apache.org/jira/browse/COMDEV-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-424. Resolution: Abandoned > An open Source Charging Function for 5G-SA - OPENCHF > - > > Key: COMDEV-424 > URL: https://issues.apache.org/jira/browse/COMDEV-424 > Project: Community Development > Issue Type: Project > Components: GSoC/Mentoring ideas >Reporter: Prajith >Priority: Major > Original Estimate: 8,760h > Remaining Estimate: 8,760h > > Dear Team, > Requesting all community members to help to together to build a OPEN SOURCE > Charging System (CHF) for 5G -SA Space for TELCOs. > This is one of the key futures for upcoming 5G-ERA for Telcos as well as new > business innovations and disruptions. > Details are attached and below link > [LinkedIn|https://www.linkedin.com/feed/update/urn%3Ali%3Aactivity%3A6825386990473674752/] > > we have to start with Open CHF first. > comments and suggestions are welcome. > Regards > Prajith -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-437) Committer map loads with Google Maps error
[ https://issues.apache.org/jira/browse/COMDEV-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-437. Resolution: Won't Fix > Committer map loads with Google Maps error > -- > > Key: COMDEV-437 > URL: https://issues.apache.org/jira/browse/COMDEV-437 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Benjamin Marwell >Priority: Major > > The web page [https://community.zones.apache.org/map.html] loads with errors. > The error shown redirects to > [https://developers.google.com/maps/documentation/javascript/error-messages?utm_source=maps_js_medium=degraded_campaign=billing#api-key-and-billing-errors] > > Maybe it should be converted to using OpenStreetMap.org. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-461) Apache APISIX: Redesign/ADD Apache APISIX Plugin icons
[ https://issues.apache.org/jira/browse/COMDEV-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-461. Resolution: Fixed > Apache APISIX: Redesign/ADD Apache APISIX Plugin icons > -- > > Key: COMDEV-461 > URL: https://issues.apache.org/jira/browse/COMDEV-461 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Ayush Das >Priority: Major > Labels: APISIX, mentor > > Ayush Das, email: [ayush24...@gmail.com|mailto:ayush24...@gmail.com] > [|mailto:ayush24...@gmail.com] > Github id - [https://github.com/iamayushdas] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-201) Puppet config for ComDev zone migrated to VM
[
https://issues.apache.org/jira/browse/COMDEV-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Curcuru closed COMDEV-201.
Resolution: Abandoned
> Puppet config for ComDev zone migrated to VM
>
>
> Key: COMDEV-201
> URL: https://issues.apache.org/jira/browse/COMDEV-201
> Project: Community Development
> Issue Type: Task
> Components: Nearby People
>Reporter: Nick Burch
>Priority: Major
> Attachments: Download your data
>
>
> Once INFRA-12005 has been completed and the VM is ready, we need to setup the
> Puppet config to replace the current ComDev solaris zone with a nice new +
> supported VM. The requirements for the puppet setup are:
> * Services
> ** httpd with mod_wsgi
> * Software
> ** python 2.x
> ** python-psycopg2
> ** python-lxml
> ** python-libxml2
> * Accounts
> ** minimum one for me, one for Sam Ruby, and one for the special svn_role
> account
> ** if possible, svn_role account needs giving its svn password (on zone
> currently) - if not can do this step manually (as done for whimsy)
> * Machine setup
> ** create a webapps folder somewhere sensible
> ** svn co https://svn.apache.org/repos/asf/comdev/nearby_people
> ** cp local_settings.py.example local_settings.py + set path of
>webapps folder in it
> ** cd data
> ** as svn_role
> *** svn co https://svn.apache.org/repos/private/committers/info
> *** svn co https://svn.apache.org/repos/private/committers/local-outreach
> ** create an empty uid-created.ldif file (will copy over latest
>ldapsearch when running, until we have better solution)
> ** elsewhere
> *** wget https://www.djangoproject.com/download/1.3.7/tarball/
> *** unpack django-1.3.7.tar.gz to /django-1.3
> * Cron
> ** for the svn_role - update for webapps path
> *** 20 * * * * cd /var/python_apps/nearby_people/data/info/ && svn up -q
> *** 40 * * * * cd /var/python_apps/nearby_people/data/local-outreach/ && svn
> up -q
> * Httpd setup
> ** ideally port 80 for community.zones.apache.org & (new name)
> ** ideally port 443 for (new name)
> ** both hosting same basic vhost contents
> ** custom vhost settings (edit for webapp path)
> {code}
> WSGIScriptAlias / /var/python_apps/nearby_people.wsgi
> Alias /admin_media/
> /var/python_apps/django-1.3/django/contrib/admin/media/
>
> SetHandler None
>
> {code}
> * Email
> ** some sort of smtp setup so that error emails get out
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-243) Community and Business Card Procedures & Guidelines
[ https://issues.apache.org/jira/browse/COMDEV-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru resolved COMDEV-243. -- Resolution: Information Provided > Community and Business Card Procedures & Guidelines > --- > > Key: COMDEV-243 > URL: https://issues.apache.org/jira/browse/COMDEV-243 > Project: Community Development > Issue Type: Task > Components: Comdev >Reporter: Sharan Foga >Assignee: Sharan Foga >Priority: Minor > > The community has decided to introduce the use of Community business cards > for all ASF contributors. > See discussion thread:[ https://s.apache.org/Nw4B] > Two formats have been agreed; Standard business card for ASF roles only and a > Community business card for more flexible use. > Some documentation needs to be created regarding the use of each card and > also ordering cards using the ASF MOO.Com account. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-243) Community and Business Card Procedures & Guidelines
[ https://issues.apache.org/jira/browse/COMDEV-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709003#comment-17709003 ] Shane Curcuru commented on COMDEV-243: -- This is effectively covered on the wiki pages: https://cwiki.apache.org/confluence/display/COMDEV/How+To%3A+Add+Project+Logos+to+Redbubble+Store > Community and Business Card Procedures & Guidelines > --- > > Key: COMDEV-243 > URL: https://issues.apache.org/jira/browse/COMDEV-243 > Project: Community Development > Issue Type: Task > Components: Comdev >Reporter: Sharan Foga >Assignee: Sharan Foga >Priority: Minor > > The community has decided to introduce the use of Community business cards > for all ASF contributors. > See discussion thread:[ https://s.apache.org/Nw4B] > Two formats have been agreed; Standard business card for ASF roles only and a > Community business card for more flexible use. > Some documentation needs to be created regarding the use of each card and > also ordering cards using the ASF MOO.Com account. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-249) GSoC [RocketMQ]Message Delivery Once Semantic Implementation
[ https://issues.apache.org/jira/browse/COMDEV-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-249. Resolution: Abandoned > GSoC [RocketMQ]Message Delivery Once Semantic Implementation > > > Key: COMDEV-249 > URL: https://issues.apache.org/jira/browse/COMDEV-249 > Project: Community Development > Issue Type: Wish > Components: GSoC/Mentoring ideas >Reporter: Von Gosling >Priority: Major > > The duplicated messages will impose the extra cost if the user needs > non-repeating messages. > In most cases, the user needs to store the consumer records to determine if a > message is duplicated, and the store stage should guarantee consistency. So > we need to support a strict and non-redundant message delivery mechanism. > In this context, we hope to design a delivery once plugin, say, you could > design a global(but need raft guarantee multi-copy data) storage, using the > hooker of RocketMQ ConsumeMessageHook to finish the task. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-304) Short code links don't work
[ https://issues.apache.org/jira/browse/COMDEV-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-304. Resolution: Won't Fix The helpwanted tool is not currently maintained. > Short code links don't work > --- > > Key: COMDEV-304 > URL: https://issues.apache.org/jira/browse/COMDEV-304 > Project: Community Development > Issue Type: Bug > Components: Help Wanted >Reporter: Sebb >Assignee: Daniel Gruno >Priority: Major > > The automated mails that are sent include a link of the form: > I would like to help out with the task listed at > https://helpwanted.apache.org/task.html?0b349bee > However this does not work. > It looks like only the long links work currently, e.g. > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-317) tabs hidden if maildata.json is empty
[ https://issues.apache.org/jira/browse/COMDEV-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-317. Resolution: Invalid > tabs hidden if maildata.json is empty > - > > Key: COMDEV-317 > URL: https://issues.apache.org/jira/browse/COMDEV-317 > Project: Community Development > Issue Type: Bug > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > See COMDEV-316 > The display tabs were hidden and there were other problems when the file > data/maildata.json was an empty JSON structure. > The Javascript render.js should be able to handle this better. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-315) Fix Russian translation for Apache Brochure
[ https://issues.apache.org/jira/browse/COMDEV-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-315. Resolution: Cannot Reproduce > Fix Russian translation for Apache Brochure > --- > > Key: COMDEV-315 > URL: https://issues.apache.org/jira/browse/COMDEV-315 > Project: Community Development > Issue Type: Bug > Components: Comdev >Reporter: Dmitry Pavlov >Assignee: Roman Shaposhnik >Priority: Major > > The Russian translation has a very messed up font kerning. > Related discussion: > https://lists.apache.org/thread.html/c926035ccb50282b9769770c8276c8c1f172ee6c68b32b37d6381cf7@%3Cdev.community.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-326) Committer invite template omits PMC role details
[ https://issues.apache.org/jira/browse/COMDEV-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708997#comment-17708997 ] Shane Curcuru commented on COMDEV-326: -- Is this still relevant? That is, is the current page with email templates the best versions of similar templates, and should we update them as ComDev PMC members feel fit? Or do these templates really belong someplace else, like under /dev/pmc or the like? > Committer invite template omits PMC role details > > > Key: COMDEV-326 > URL: https://issues.apache.org/jira/browse/COMDEV-326 > Project: Community Development > Issue Type: Bug > Components: Website > Environment: > https://community.apache.org/newcommitter.html#committer-invite-template >Reporter: Sebb >Priority: Major > > The committer invite template [1] is not very clear on the distinction > between an invitation as a committer, and invitation as a committer + PMC > member. > In particular, it describes the role of the committer, but largely ignores > the PMC role. > As a result, I have seen at least one acceptance reply that said "I accept to > become a committer" [2] - leaving unstated whether or not they agree to > become a PMC member. > I think any template needs to make very clear what is involved in the PMC > role, and also that the invitee has 3 choices: > - decline both invites > - accept the committer invite and decline the PMC invite > - accept both committer invite and PMC invite > [1] https://community.apache.org/newcommitter.html#committer-invite-template > [2] > https://lists.apache.org/thread.html/796c4b3e8c0f191add39c7d1b6cc154a5e316910df8120db1151c739@%3Cprivate.jackrabbit.apache.org%3E -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-339) understanding some stuff
[ https://issues.apache.org/jira/browse/COMDEV-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-339. Resolution: Won't Fix The helpwanted tool is currently not maintained, so closing. If we find folks with energy to 1) maintain the code, and 2) work with some PMCs to get relevant content, we can reopen it. > understanding some stuff > > > Key: COMDEV-339 > URL: https://issues.apache.org/jira/browse/COMDEV-339 > Project: Community Development > Issue Type: Question > Components: Help Wanted >Reporter: Tommaso >Priority: Major > > Hi everybody, > i have some questions i would like to ask: > 1) I noticed that last update can go beyond closure date, so probably it > changes even if i just comment under the issue (i'm not sure), is there > another reason? > 2)I don't understand if i can use Days in current status to assert resolution > time for closed issues, or if i have to consider the delta resolutiondate - > creationdate > thanks for the attention > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-372) Apache slide templates
[ https://issues.apache.org/jira/browse/COMDEV-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru resolved COMDEV-372. -- Resolution: Implemented This seems to be effectively fixed since the PRs were accepted. It would be great to see more folks with energy on improving and sharing slide templates - either here, or in the Apache Training podling. > Apache slide templates > -- > > Key: COMDEV-372 > URL: https://issues.apache.org/jira/browse/COMDEV-372 > Project: Community Development > Issue Type: Improvement > Components: Comdev >Reporter: Piergiorgio Lucidi >Priority: Minor > > It would be great to have a place and develop some generic ASF slide > templates. > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-437) Committer map loads with Google Maps error
[ https://issues.apache.org/jira/browse/COMDEV-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708988#comment-17708988 ] Shane Curcuru commented on COMDEV-437: -- FYI: The community map tool sadly doesn't have any maintainers, so current plans are to shutter it unless folks step up to volunteer to fix the code (as well as publicising it to see if more committers want to be listed). > Committer map loads with Google Maps error > -- > > Key: COMDEV-437 > URL: https://issues.apache.org/jira/browse/COMDEV-437 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Benjamin Marwell >Priority: Major > > The web page [https://community.zones.apache.org/map.html] loads with errors. > The error shown redirects to > [https://developers.google.com/maps/documentation/javascript/error-messages?utm_source=maps_js_medium=degraded_campaign=billing#api-key-and-billing-errors] > > Maybe it should be converted to using OpenStreetMap.org. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-493) Community health statistics rules issues
[ https://issues.apache.org/jira/browse/COMDEV-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17708987#comment-17708987 ] Shane Curcuru commented on COMDEV-493: -- Does this still happen? If so, what specific project are you looking at the stats for? I wonder if it's a code issue, or really just an issue with the URLs the code is using to try to detect the right lists/releases for your project. > Community health statistics rules issues > > > Key: COMDEV-493 > URL: https://issues.apache.org/jira/browse/COMDEV-493 > Project: Community Development > Issue Type: Task >Reporter: Chen Xia >Priority: Major > > Hello, may I ask how community health is counted, and how do we test whether > the work we do is effective? > Over the past month we've also sent a lot of emails to the dev mailing list, > but on the website(https://reporter.apache.org/chi.py) it looks like this: > No email sent to ANY ML in the past quarter (-2.50氣) > Also, we have released new versions before, but the statistics are that no > release data available! (-0.50氣). -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-145) Duplicated data in generated json files
[ https://issues.apache.org/jira/browse/COMDEV-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-145. Resolution: Implemented json tooling has improved a lot since then. > Duplicated data in generated json files > --- > > Key: COMDEV-145 > URL: https://issues.apache.org/jira/browse/COMDEV-145 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Sebb >Priority: Major > > There is some duplication/overlap in the json data files. > For example, chairs.json has full names of both chairs and committee. > committees.json has full name of committee and availid of chair > pmcs.json has similar info to committees.json. > I would have thought one file would be sufficient here. > people_name.json has availid and full name > people.json has availid and full name plus other data > They could surely be combined. > releases.json and releases-files have some overlapping data -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-216) Fixup styles so header/footer appear properly
[ https://issues.apache.org/jira/browse/COMDEV-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-216. Resolution: Cannot Reproduce > Fixup styles so header/footer appear properly > - > > Key: COMDEV-216 > URL: https://issues.apache.org/jira/browse/COMDEV-216 > Project: Community Development > Issue Type: Wish > Components: Reporter Tool >Reporter: Shane Curcuru >Priority: Minor > > I spent a while trying to get the footer text - which now points to the new > /about.html page, that explains where the source is - to appear, to no avail. > - Why is the content div row-12? > - Why don't we have three foundation.css rows in the page? Header - which > would be just the static title, and a link to the About page; Contents - same > as now, but without the H2 element - and Footer - which includes license etc > and can get pushed off the page if contents needs to grow. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-216) Fixup styles so header/footer appear properly
[ https://issues.apache.org/jira/browse/COMDEV-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688616#comment-17688616 ] Shane Curcuru commented on COMDEV-216: -- Works for me fine now! > Fixup styles so header/footer appear properly > - > > Key: COMDEV-216 > URL: https://issues.apache.org/jira/browse/COMDEV-216 > Project: Community Development > Issue Type: Wish > Components: Reporter Tool >Reporter: Shane Curcuru >Priority: Minor > > I spent a while trying to get the footer text - which now points to the new > /about.html page, that explains where the source is - to appear, to no avail. > - Why is the content div row-12? > - Why don't we have three foundation.css rows in the page? Header - which > would be just the static title, and a link to the About page; Contents - same > as now, but without the H2 element - and Footer - which includes license etc > and can get pushed off the page if contents needs to grow. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Created] (COMDEV-454) Report Wizard gives "[object Response]" error with underlying 503
Shane Curcuru created COMDEV-454: Summary: Report Wizard gives "[object Response]" error with underlying 503 Key: COMDEV-454 URL: https://issues.apache.org/jira/browse/COMDEV-454 Project: Community Development Issue Type: Bug Components: Reporter Tool Environment: Mac/FF Reporter: Shane Curcuru As reported elsewhere, navigating to [https://reporter.apache.org/wizard/] pops up a notification error, and does nothing else. Console shows an underlying 503: /*** ASF Board Report Wizard initializing / [wizard.js:1792:9|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] Fetching JSON resource at /reportingcycles.json [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] putting /reportingcycles.json in escrow... [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] Successfully fetched /reportingcycles.json [wizard.js:119:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] Fetching JSON resource at /api/overview [wizard.js:79:13|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] putting /api/overview in escrow... [wizard.js:96:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] URL /api/overview returned HTTP code 503, snapping! [wizard.js:132:21|https://reporter.apache.org/wizard/js/wizard.js?unified-1.4] -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-397) 7
[ https://issues.apache.org/jira/browse/COMDEV-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-397. Resolution: Invalid > 7 > - > > Key: COMDEV-397 > URL: https://issues.apache.org/jira/browse/COMDEV-397 > Project: Community Development > Issue Type: Documentation >Reporter: Javier Castro >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-333) pet school how to project
[ https://issues.apache.org/jira/browse/COMDEV-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-333. Resolution: Invalid Spam > pet school how to project > - > > Key: COMDEV-333 > URL: https://issues.apache.org/jira/browse/COMDEV-333 > Project: Community Development > Issue Type: New Feature > Components: Website >Reporter: Murat Güngör >Priority: Trivial > Labels: egi, kedi, köpek > > pet school professional dog training and dog hotel website > I > [https://petokulu.com/] > how do you think -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch
[ https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru updated COMDEV-319: - Attachment: (was: ADCLK854.pdf) > Use Whimsy JSON data instead of ldapsearch > -- > > Key: COMDEV-319 > URL: https://issues.apache.org/jira/browse/COMDEV-319 > Project: Community Development > Issue Type: Task > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch. > Should fix addrelease.py and jiraversions.py to do likewise. > (This would have avoided COMDEV-318) -- 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] [Updated] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch
[ https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru updated COMDEV-319: - Attachment: (was: -Bose Connect-.htm) > Use Whimsy JSON data instead of ldapsearch > -- > > Key: COMDEV-319 > URL: https://issues.apache.org/jira/browse/COMDEV-319 > Project: Community Development > Issue Type: Task > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch. > Should fix addrelease.py and jiraversions.py to do likewise. > (This would have avoided COMDEV-318) -- 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] [Issue Comment Deleted] (COMDEV-319) Use Whimsy JSON data instead of ldapsearch
[ https://issues.apache.org/jira/browse/COMDEV-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru updated COMDEV-319: - Comment: was deleted (was: This is fine.but some little bit confused ) > Use Whimsy JSON data instead of ldapsearch > -- > > Key: COMDEV-319 > URL: https://issues.apache.org/jira/browse/COMDEV-319 > Project: Community Development > Issue Type: Task > Components: Reporter Tool >Reporter: Sebb >Priority: Minor > > Most of reporter.a.o uses the Whimsy JSON data files rather than ldapsearch. > Should fix addrelease.py and jiraversions.py to do likewise. > (This would have avoided COMDEV-318) -- 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-320) Split apachecon.com svn repo from comdev acl
[ https://issues.apache.org/jira/browse/COMDEV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16842221#comment-16842221 ] Shane Curcuru commented on COMDEV-320: -- Rich: can you list the individuals you want to give this access to, either by name, or by description "three people who work for our contracted event producer(s)"? Also: how urgent is this: today, next week, by end of month? > Split apachecon.com svn repo from comdev acl > > > Key: COMDEV-320 > URL: https://issues.apache.org/jira/browse/COMDEV-320 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Richard Bowen >Priority: Major > > Having the apachecon website svn rep tied to the comdev acl is causing > difficulties. Specifically, we have to make someone a comdev committer for > them to edit a web page, and that's broken. > I would like to split apachecon.com svn repo from the comdev repo, and create > a new acl where we can have "committers" for that repo who are not asf > committers (think event producers) and who probably haven't signed CLAs > (because why would they?). Is this a thing we can do? Are there policy > considerations, or can we JFDI? -- 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-320) Split apachecon.com svn repo from comdev acl
[ https://issues.apache.org/jira/browse/COMDEV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16842214#comment-16842214 ] Shane Curcuru commented on COMDEV-320: -- To (I hope) better define the problem: The ApacheCon website has many time-specific demands for updating, and with our current model, various producers of events (here I believe event staff at Virtual - people not otherwise involved in our communities) will be making those updates. They need to modify content here: [https://svn.apache.org/repos/infra/apachecon/www.apachecon.com] And they will need the source there to be auto-published to the live apachecon.com site as it already is. Historically, we have had very firm policies that committer accounts enabling write access to our repos are only given out to individuals who sign an ICLA. # The simplest solution from the ASF point of view is to ask those event staff to sign an ICLA, which hopefully is non-controversial (but I understand may not be from their point of view). # The other solution is for Infra to figure out how to differentiate "special accounts that can commit to ApacheCon SVN only" from "committer accounts". I don't know if this is practical for infra. But ensuring that people without an ICLA can't commit to any project repo (among other places) is critical to our legal policies. > Split apachecon.com svn repo from comdev acl > > > Key: COMDEV-320 > URL: https://issues.apache.org/jira/browse/COMDEV-320 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Richard Bowen >Priority: Major > > Having the apachecon website svn rep tied to the comdev acl is causing > difficulties. Specifically, we have to make someone a comdev committer for > them to edit a web page, and that's broken. > I would like to split apachecon.com svn repo from the comdev repo, and create > a new acl where we can have "committers" for that repo who are not asf > committers (think event producers) and who probably haven't signed CLAs > (because why would they?). Is this a thing we can do? Are there policy > considerations, or can we JFDI? -- 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-312) Committer count disagrees with Whimsy
[ https://issues.apache.org/jira/browse/COMDEV-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789613#comment-16789613 ] Shane Curcuru commented on COMDEV-312: -- t would greatly help if we had an easy way to see the actual hardcoded data and/or code that does lookups for each tool, so we can document what they're doing and see if there are ways to simplify (while still being clear what the actual data is). * Whimsy has partial docs here (may not be updated with recent changes): ** [https://whimsy.apache.org/test/dataflow.cgi] * Projects.a.o code: ** [https://community.apache.org/about/#getcode] But it's not obvious where any special cases in the projects code might be. > Committer count disagrees with Whimsy > - > > Key: COMDEV-312 > URL: https://issues.apache.org/jira/browse/COMDEV-312 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Sebb >Priority: Major > > The total committer count on the timeline page > [https://projects.apache.org/timelines.html] (currently 7145) > disagrees with the Whimsy count shown here: > [https://whimsy.apache.org/roster/] (currently 6806) > This is a difference of over 330. > Some of this may be due to early committers who were not migrated to LDAP, > presumably because they had stopped contributing. > It's confusing to have such a discrepancy. > It would be better to use the Whimsy data file: > [https://whimsy.apache.org/public/public_ldap_people.json] > -- 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-248) add /dist/ health issues
[ https://issues.apache.org/jira/browse/COMDEV-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16322735#comment-16322735 ] Shane Curcuru commented on COMDEV-248: -- Sounds like a good idea, as long as there's enough context in the links to explain what the problem(s) are for a specific PMC. The checker.a.o site (new to me! wow!) has good descriptions in the docs, but we should be sure any reporter changes explain what the checks mean too. Separately: where is the source for the checker scripts and the checker.a.o website? > add /dist/ health issues > > > Key: COMDEV-248 > URL: https://issues.apache.org/jira/browse/COMDEV-248 > Project: Community Development > Issue Type: Improvement > Components: Reporter Tool >Reporter: Henk Penning > > checker.apache.org reports /dist/ health issues, summarized in > https://checker.apache.org/json/ > Perhaps this info can be included in the project's report. > I believe checker.apache.org only reports real problems ; > problems that the PMC should (and can) fix. > Of course I hope that including this info in the report, will result a > healtier /dist/. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-208) Mark Apache Maturity Model as not policy
[ https://issues.apache.org/jira/browse/COMDEV-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru resolved COMDEV-208. -- Resolution: Fixed > Mark Apache Maturity Model as not policy > > > Key: COMDEV-208 > URL: https://issues.apache.org/jira/browse/COMDEV-208 > Project: Community Development > Issue Type: Improvement > Components: Website >Reporter: John D. Ament >Assignee: Shane Curcuru > > This document is interpreted incorrectly as being policy or a requirement for > podlings. Please add a note to the page that this isn't the case. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-135) improve css to have the head banner stay visible when scrolling down
[ https://issues.apache.org/jira/browse/COMDEV-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247535#comment-16247535 ] Shane Curcuru commented on COMDEV-135: -- Apologies for mistakenly closing; thanks for clarifying! > improve css to have the head banner stay visible when scrolling down > > > Key: COMDEV-135 > URL: https://issues.apache.org/jira/browse/COMDEV-135 > Project: Community Development > Issue Type: Improvement > Components: Projects Website >Reporter: Hervé Boutemy > > see W3Schools CSS tutorial banner to see this in action: > http://www.w3schools.com/css/ > this would ease navigation from tab to tab in http://projects.apache.org/ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-99) [GSoC] Allura: Pagination on threaded discussions is cumbersome
[ https://issues.apache.org/jira/browse/COMDEV-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-99. --- Resolution: Unresolved Close old Allura GSOC issues per brondsem. > [GSoC] Allura: Pagination on threaded discussions is cumbersome > --- > > Key: COMDEV-99 > URL: https://issues.apache.org/jira/browse/COMDEV-99 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Wayne Witzel III > Labels: allura, gsoc2013, mentor > > Having to page through comments on a thread is kinda annoying. Things that > could make it better > * use ajax to fetch next results > * use a "more" link that appends the next comments onto the current page > * tighten up the display of each post - if the comment is short, a lot of > height is taken just for the gravatar and reply/link/edit/delete links > * ? > https://sourceforge.net/p/allura/tickets/5709/ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-100) [GSoC] Allura: Improve merge requests
[ https://issues.apache.org/jira/browse/COMDEV-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-100. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > [GSoC] Allura: Improve merge requests > - > > Key: COMDEV-100 > URL: https://issues.apache.org/jira/browse/COMDEV-100 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Wayne Witzel III > Labels: allura, gsoc2013, mentor > > Several specific issues are listed at > https://sourceforge.net/p/allura/tickets/search?q=labels:merge-requests > Additional improvements could include branch comparison, one-click merging, > commenting on individual lines/chunks of diffs > https://sourceforge.net/p/allura/tickets/6090/ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-98) [GSoC] Allura: In-Site Messaging
[ https://issues.apache.org/jira/browse/COMDEV-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-98. --- Resolution: Unresolved Close old Allura GSOC issues per brondsem. > [GSoC] Allura: In-Site Messaging > > > Key: COMDEV-98 > URL: https://issues.apache.org/jira/browse/COMDEV-98 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Wayne Witzel III > Labels: allura, gsoc2013, mentor > > Need a way to send a user a message in-site - that is, that they'll somehow > get the message when they log into the site, perhaps with some kind of a > notification that they have messages waiting. > Rationale: We have many users who are active, but who have an email address > on file that bounces. This leaves us with no way to contact them, even though > they are active. > https://sourceforge.net/p/allura/tickets/4725/ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-187) Allura - better root page and initial impressions
[ https://issues.apache.org/jira/browse/COMDEV-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-187. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > Allura - better root page and initial impressions > - > > Key: COMDEV-187 > URL: https://issues.apache.org/jira/browse/COMDEV-187 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema > Labels: gsoc2016, python, ux > > In a new Allura installation, the landing page is not very useful. It shows > a defunct category system on the left menu and the body of the page is just a > list of the "neighborhoods" (which you can browse into to find projects). > This is not great initial impression. > The categories should be removed, and the main page content should be > customizable. Some design research and brainstorming will be necessary to > determine what it should be. Maybe raw HTML that site admins can set, maybe > a standard allura wiki page. Maybe an option to redirect to a "main" project > within the site. Maybe the root is its own special project, allowing admins > to choose between a wiki page, forum, tracker, etc - plus let them have other > tools at the top level. > This probably will not take the full GSoC time and the student should plan on > other improvements to make the Allura site easier for people to use and > customize. (header/footer customizations maybe?) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-103) [GSoC] Allura: User Project Makeover
[ https://issues.apache.org/jira/browse/COMDEV-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-103. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > [GSoC] Allura: User Project Makeover > > > Key: COMDEV-103 > URL: https://issues.apache.org/jira/browse/COMDEV-103 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Wayne Witzel III > Labels: allura, gsoc2013, mentor > > Friendly user steps Grid like GitHub and BitBucket .. create Repo, Edit wiki, > Find friends, Find code > intuitive code tool, drop down instead of menu links, all user project repos > listed in left bar, all other projects listed in left bar. > User project not listed on the user project page.. > Easily take an existing repo and have a "Make Project" button. That will copy > the repo to a new full project for you. > Do not uppercase the first letter of tools automatically, especially repos. > Remove the Display vs Repo name for User Project Repos > Remove the user project itself from your list of projects, it is confusing. > Re-brand, re-name the idea of "User Project". It is great for internal use, > since a user is a project, but it is confusing and unmarketable to the > outside world. > https://sourceforge.net/p/allura/tickets/2879/ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-186) Allura - docker setup for production usage with all services
[ https://issues.apache.org/jira/browse/COMDEV-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-186. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > Allura - docker setup for production usage with all services > > > Key: COMDEV-186 > URL: https://issues.apache.org/jira/browse/COMDEV-186 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema > Labels: docker, gsoc2016, linux, python > > Allura consists of many services when running in a full environment. We have > Docker and Docker Compose configuration for *developing* allura but not for a > full production-ready installation. This project would entail setting up a > configuration with settings suitable for production and adding containers for > git, hg, svn, dns and static file serving. Some documentation exists about > manually setting up those services to work with Allura, but much further > configuration, scripting and testing would be needed to get to the full > operational environment. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-185) Allura - discussion thread improvements
[ https://issues.apache.org/jira/browse/COMDEV-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-185. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > Allura - discussion thread improvements > --- > > Key: COMDEV-185 > URL: https://issues.apache.org/jira/browse/COMDEV-185 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema > Labels: gsoc2016, javascript, mongodb, python > > In Allura, threaded discussions are used everywhere. They are the core part > of forums, and are used on each ticket, wiki page, blog post, etc. Several > improvements can be made in this specific area. This code is in python, with > a mongodb backend. Frontend JS & CSS would be necessary for some of these > items: > * better pagination through long discussions (ajax fetching, nicer display of > each item, etc) https://forge-allura.apache.org/p/allura/tickets/5709/ > * add toggle to show/hide "meta" comments (e.g. status or field changes) > https://forge-allura.apache.org/p/allura/tickets/7883/ > * when emails are converted into comments, parse the reply so only the new > text is included. https://forge-allura.apache.org/p/allura/tickets/1782/ > * performance improvements > https://forge-allura.apache.org/p/allura/tickets/4359/ > * separate list of attachments from all the comments > https://forge-allura.apache.org/p/allura/tickets/6096/ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-212) Allura - personal dashboard
[ https://issues.apache.org/jira/browse/COMDEV-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-212. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > Allura - personal dashboard > --- > > Key: COMDEV-212 > URL: https://issues.apache.org/jira/browse/COMDEV-212 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema > Labels: gsoc2017, mongodb, python > > A nice improvement to Allura project/code hosting would be a personal > dashboard when you are logged in. It would provide quick access to the > projects you are a part of, tickets you have created, tickets assigned to > you, your pull requests, activity stream of people you follow, etc. > Since there are many possible components to this, a pluggable structure like > the user profile page would be good. Some parts of a public profile (like > projects list) could be re-used on the personal dashboard too. > https://forge-allura.apache.org/p/allura/tickets/7171/ is a related Allura > ticket about seeing your own ticket votes. > https://forge-allura.apache.org/p/allura/tickets/5419/ is an additional idea > for showing projects that match your skill categories. (And many new tickets > for the whole dashboard idea would have to be created to divide it into > manageable tasks) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-101) [GSoC] Allura: Search for users
[ https://issues.apache.org/jira/browse/COMDEV-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-101. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > [GSoC] Allura: Search for users > --- > > Key: COMDEV-101 > URL: https://issues.apache.org/jira/browse/COMDEV-101 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Wayne Witzel III > Labels: allura, gsoc2013, mentor > > It would be nice to be able to search for users. Could search by any public > profile data (name, location, skills, etc). > All Artifacts get indexed by solr automatically. Not sure if we'd want to > make a User an Artifact since there is other ramifications of that, but > that'd be one potential starting point for the indexing portion of this. > https://sourceforge.net/p/allura/tickets/6091/ -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-184) Allura - Improve merge requests
[ https://issues.apache.org/jira/browse/COMDEV-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-184. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > Allura - Improve merge requests > --- > > Key: COMDEV-184 > URL: https://issues.apache.org/jira/browse/COMDEV-184 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema > Labels: git, gsoc2016, hg, python > > Allura supports merge requests for its Git and Hg functionality, but it could > be made better. This would involve python, git, and hg. Also HTML/CSS/JS. > Here are some ideas for improvement, of varying difficulty: > * automatically update when new commits are pushed > https://forge-allura.apache.org/p/allura/tickets/5993/ > * preview commits https://forge-allura.apache.org/p/allura/tickets/6581/ > * better display after merging > https://forge-allura.apache.org/p/allura/tickets/7879/ > * branch comparison https://forge-allura.apache.org/p/allura/tickets/5840/ > and/or https://forge-allura.apache.org/p/allura/tickets/7241/ > * commenting on individual lines/chunks of diffs > https://forge-allura.apache.org/p/allura/tickets/7241/ > * and more ... > https://forge-allura.apache.org/p/allura/tickets/search/?q=labels%3Amerge-reguests+AND+status%3Aopen -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-211) Allura - discussion thread improvements
[ https://issues.apache.org/jira/browse/COMDEV-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-211. Resolution: Unresolved Close old Allura GSOC issues per brondsem. > Allura - discussion thread improvements > --- > > Key: COMDEV-211 > URL: https://issues.apache.org/jira/browse/COMDEV-211 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema > Labels: css, gsoc2017, javascript, mongodb, python > > In Allura, threaded discussions are used everywhere. They are the core part > of forums, and are used on each ticket, wiki page, blog post, etc. Several > improvements can be made in this specific area. This code is in python, with > a mongodb backend. Frontend JS & CSS would be necessary for some of these > items: > * better pagination through long discussions (ajax fetching, nicer display of > each item, etc) https://forge-allura.apache.org/p/allura/tickets/5709/ > * add toggle to show/hide "meta" comments (e.g. status or field changes) > https://forge-allura.apache.org/p/allura/tickets/7883/ > * when emails are converted into comments, parse the reply so only the new > text is included. https://forge-allura.apache.org/p/allura/tickets/1782/ > * performance improvements > https://forge-allura.apache.org/p/allura/tickets/4359/ > * separate list of attachments from all the comments > https://forge-allura.apache.org/p/allura/tickets/6096/ > * etc... -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-25) JSR196 for Tomcat
[ https://issues.apache.org/jira/browse/COMDEV-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-25. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed. > JSR196 for Tomcat > - > > Key: COMDEV-25 > URL: https://issues.apache.org/jira/browse/COMDEV-25 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas > Environment: See http://wiki.apache.org/tomcat/SummerOfCode2010 >Reporter: Jean-Frederic Clere > Labels: gsoc, mentor > > Provide a JSR196 implementation (http://jcp.org/en/jsr/detail?id=196) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-26) SPDY connector for Tomcat
[ https://issues.apache.org/jira/browse/COMDEV-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-26. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed. > SPDY connector for Tomcat > - > > Key: COMDEV-26 > URL: https://issues.apache.org/jira/browse/COMDEV-26 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas > Environment: See http://wiki.apache.org/tomcat/SummerOfCode2010 >Reporter: Jean-Frederic Clere > Labels: gsoc, mentor > > Create Connector that supports the SPDY protocol (See > http://dev.chromium.org/spdy/spdy-whitepaper) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-42) Continuum: Maven modules autodetection
[ https://issues.apache.org/jira/browse/COMDEV-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-42. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed; linked URL is 404. > Continuum: Maven modules autodetection > -- > > Key: COMDEV-42 > URL: https://issues.apache.org/jira/browse/COMDEV-42 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Emmanuel Venisse > Labels: gsoc, mentor > > Need to autodetect new modules added into the Maven projects and add them > automatically into Continuum. > Continuum JIRA issue: http://jira.codehaus.org/browse/CONTINUUM-798 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-36) Archiva: Add a Project Tree view in artiact/project webapp browse
[ https://issues.apache.org/jira/browse/COMDEV-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-36. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed; linked URL is 404. > Archiva: Add a Project Tree view in artiact/project webapp browse > - > > Key: COMDEV-36 > URL: https://issues.apache.org/jira/browse/COMDEV-36 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Maria Odea Ching > Labels: gsoc, mentoring > > The Project Tree should show the POM hierarchy (parent-and-modules) with > links. > Archiva JIRA issue: http://jira.codehaus.org/browse/MRM-1209 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-40) Continuum: Services refactoring
[ https://issues.apache.org/jira/browse/COMDEV-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-40. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed; linked URL is 404. > Continuum: Services refactoring > --- > > Key: COMDEV-40 > URL: https://issues.apache.org/jira/browse/COMDEV-40 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Emmanuel Venisse > Labels: gsoc, mentor > > Need to refactor the exposed services. > Actually services are exposed with xml-rpc. In the new architecture (2.0), > they will be exposed with differents formats(rest, soap, gwt-rpc...) > To refactor them, we'll use enunciate (http://enunciate.codehaus.org/) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-38) Archiva: Add support for atomic artifact deployments to repositories
[ https://issues.apache.org/jira/browse/COMDEV-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-38. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed; linked URL is 404. > Archiva: Add support for atomic artifact deployments to repositories > > > Key: COMDEV-38 > URL: https://issues.apache.org/jira/browse/COMDEV-38 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Maria Odea Ching > Labels: gsoc, mentor > > All artifact deployments should go to a temporary location until a > checksum-verified POM arrives, and if everything is valid it gets > automatically pushed into the repository. > Related thread: > http://old.nabble.com/MRM-1351%3A-please-advise-td27742269.html -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-35) Archiva: Introduce a new event API
[ https://issues.apache.org/jira/browse/COMDEV-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-35. --- Resolution: Fixed Closing really old GSOC issues; feel free to reopen if still needed; linked URL is 404. > Archiva: Introduce a new event API > -- > > Key: COMDEV-35 > URL: https://issues.apache.org/jira/browse/COMDEV-35 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Maria Odea Ching > Labels: gsoc, mentor > > Migrate the current consumer API to an event API that can handle more than > just database scanning. > Archiva JIRA issue: http://jira.codehaus.org/browse/MRM-976 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-34) Archiva: Add support for temporary repositories used for staging
[ https://issues.apache.org/jira/browse/COMDEV-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-34. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed; linked URL is 404. > Archiva: Add support for temporary repositories used for staging > > > Key: COMDEV-34 > URL: https://issues.apache.org/jira/browse/COMDEV-34 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Maria Odea Ching > Labels: gsoc, mentor > > This is mainly for project release staging and promotion. > Archiva JIRA issue: http://jira.codehaus.org/browse/MRM-1021 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-32) Subversion: Viewspecs
[ https://issues.apache.org/jira/browse/COMDEV-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-32. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed. > Subversion: Viewspecs > - > > Key: COMDEV-32 > URL: https://issues.apache.org/jira/browse/COMDEV-32 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Stefan Sperling > Labels: gsoc, mentor > > Subversion currently supports some mechanisms for selectively building > and populating a working copy, including sparse directory support and > externals definitions. What Subversion lacks is a handy way to be told — > in one easy step — to go off and make use of those underlying features > to build a working copy that looks some specific way. Imagine being able > to tell new developers on your project to checkout a working copy using > some pre-formulated specification which results in an automated sparse > checkout that includes your trunk, branches, and then various branches > for the currently maintained versions of your software > (branches/SOME-VERSION), instead of having to tell them to first do a > --depth=empty checkout of the root, then a --set-depth=infinity update > of trunk and branches, then.. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-29) Subversion: Add support for Git/Mercurial style unidiff format extensions
[ https://issues.apache.org/jira/browse/COMDEV-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-29. --- Resolution: Unresolved Closing really old GSOC issues; feel free to reopen if still needed. > Subversion: Add support for Git/Mercurial style unidiff format extensions > - > > Key: COMDEV-29 > URL: https://issues.apache.org/jira/browse/COMDEV-29 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Ross Gardler > Labels: gsoc, mentor > > Add support for Git/Mercurial style unidiff format extensions 'svn diff' and > 'svn patch' should be able to produce and apply unidiff files containing > git-style extensions to the unidiff format. See > http://svn.apache.org/repos/asf/subversion/trunk/notes/svnpatch/svnpatch-git.txt > That would allow us to use patches for tree and mode changes. Extra brownie > points will be given to students expanding upon the git unidiff extensions by > adding support for expressing changes made > to Subversion properties (which can be text and binary data). -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-24) Security docs improvements
[ https://issues.apache.org/jira/browse/COMDEV-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-24. --- Resolution: Fixed Closing really old GSOC issues; feel free to reopen if still needed. > Security docs improvements > -- > > Key: COMDEV-24 > URL: https://issues.apache.org/jira/browse/COMDEV-24 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas > Environment: See http://wiki.apache.org/tomcat/SummerOfCode2010 >Reporter: Jean-Frederic Clere > Labels: gsoc, mentor > > Update the security pages etc to include svn revisions for each fix, update > the release notes to include the CVE reference with the fix, update the svn > logs to include the CVE reference. This will require a lot of cross-checking > to ensure that the correct CVEs and svn references are added, particularly > for the older vulnerabilities. This would include the 5.5.x, 6.0.x and 7.0.x > code-bases. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-197) Searching for a podling and clearing it only shows podlings afterwards on phonebook
[ https://issues.apache.org/jira/browse/COMDEV-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-197. Resolution: Cannot Reproduce There seems to be plenty of functionality - as sebb notes, tabbing or clicking in either Project or Podling search textbox at the top brings up a list of all projects/or/podlings, and typing part of a name searches as expected. > Searching for a podling and clearing it only shows podlings afterwards on > phonebook > --- > > Key: COMDEV-197 > URL: https://issues.apache.org/jira/browse/COMDEV-197 > Project: Community Development > Issue Type: Bug > Components: PhoneBook >Reporter: John D. Ament > > When searching for a podling on phonebook, then clearing it, the only > projects shown are podlings. > Likewise, when visiting the page for the first time, no podlings are shown. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-145) Duplicated data in generated json files
[ https://issues.apache.org/jira/browse/COMDEV-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16241297#comment-16241297 ] Shane Curcuru commented on COMDEV-145: -- Can this be closed? There have been a lot of changes how the various JSON data is generated between projects.a.o and whimsy.a.o, so we should focus on actionable changes to current code IMO. > Duplicated data in generated json files > --- > > Key: COMDEV-145 > URL: https://issues.apache.org/jira/browse/COMDEV-145 > Project: Community Development > Issue Type: Bug >Reporter: Sebb > > There is some duplication/overlap in the json data files. > For example, chairs.json has full names of both chairs and committee. > committees.json has full name of committee and availid of chair > pmcs.json has similar info to committees.json. > I would have thought one file would be sufficient here. > people_name.json has availid and full name > people.json has availid and full name plus other data > They could surely be combined. > releases.json and releases-files have some overlapping data -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-135) improve css to have the head banner stay visible when scrolling down
[ https://issues.apache.org/jira/browse/COMDEV-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru resolved COMDEV-135. -- Resolution: Fixed This was fixed long ago during a site redesign. > improve css to have the head banner stay visible when scrolling down > > > Key: COMDEV-135 > URL: https://issues.apache.org/jira/browse/COMDEV-135 > Project: Community Development > Issue Type: Improvement > Components: Projects Website >Reporter: Hervé Boutemy > > see W3Schools CSS tutorial banner to see this in action: > http://www.w3schools.com/css/ > this would ease navigation -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-55) Create JIRA filters
[ https://issues.apache.org/jira/browse/COMDEV-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-55. --- Resolution: Won't Fix We already have helpwanted.a.o and other methods to connect mentors and mentees - doing it through JIRA would not be a user-friendly way to connect people at this point. Closing. > Create JIRA filters > --- > > Key: COMDEV-55 > URL: https://issues.apache.org/jira/browse/COMDEV-55 > Project: Community Development > Issue Type: Sub-task > Components: Comdev >Reporter: Ross Gardler > > To allow mentees to find projects of interest to them we will need to > provide sufficiently granular filters. For example: > - individual project filters > - technolgoy type filters (e.g. web server, xml, content, big data) -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-41) Continuum: UI Refactoring
[ https://issues.apache.org/jira/browse/COMDEV-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-41. --- Resolution: Unresolved Closing old unused GSOC issue (feel free to reopen if you really need it) > Continuum: UI Refactoring > - > > Key: COMDEV-41 > URL: https://issues.apache.org/jira/browse/COMDEV-41 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Emmanuel Venisse > Labels: gsoc, mentor > > With the new architecture (2.0), we want to refactor the UI to be more user > friendly and more modern. > To do it, the framework to use will be GWT. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-105) broken links in apachecon pages
[ https://issues.apache.org/jira/browse/COMDEV-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-105. Resolution: Cannot Reproduce ApacheCon archive has been rearchitected since this was reported; seems to work fine. > broken links in apachecon pages > --- > > Key: COMDEV-105 > URL: https://issues.apache.org/jira/browse/COMDEV-105 > Project: Community Development > Issue Type: Bug >Reporter: Gavin > > http://www.apache.org/foundation/conferences.html has links to old apachecon > events that 404 -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Updated] (COMDEV-230) Reorg sample presentations by topic
[ https://issues.apache.org/jira/browse/COMDEV-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru updated COMDEV-230: - Component/s: Website > Reorg sample presentations by topic > --- > > Key: COMDEV-230 > URL: https://issues.apache.org/jira/browse/COMDEV-230 > Project: Community Development > Issue Type: Task > Components: Website >Reporter: Rich Bowen > > https://community.apache.org/speakers/slides.html lists slides/presentations > that have been given in the past. > While this is useful, the organization of the page is wrong for the use case. > In particular, we want people to be able to obtain information about > particular topics - the Apache Way, the Incubator, and so on. Ordering the > page by name puts the emphasis the wrong place. > So, two steps: > 1) reorder the page by topic rather than by personal name. > 2) Work towards recommended starter presentations for important topics (eg, > Apache Way) that have standard talking points, and things that must/should be > covered. > It's possible that #2 should be a separate ticket - per topic. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-220) Project
[ https://issues.apache.org/jira/browse/COMDEV-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-220. Resolution: Invalid Appears to be a bogus bug entry; closed. > Project > --- > > Key: COMDEV-220 > URL: https://issues.apache.org/jira/browse/COMDEV-220 > Project: Community Development > Issue Type: Bug > Components: GSoC/Mentoring ideas >Reporter: Isabelle E Lopez-Jarrott > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-208) Mark Apache Maturity Model as not policy
[ https://issues.apache.org/jira/browse/COMDEV-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239586#comment-16239586 ] Shane Curcuru commented on COMDEV-208: -- Happy to mark this as advisory and best practice, not policy. I also plan to rewrite/move around the intro sections to explain up front what this is at a general level, and put the history/how we got here at the bottom (but still well linked), unless someone complains soon. Not planning on changing any of the maturity items, since those should always have a discussion before changing. > Mark Apache Maturity Model as not policy > > > Key: COMDEV-208 > URL: https://issues.apache.org/jira/browse/COMDEV-208 > Project: Community Development > Issue Type: Improvement >Reporter: John D. Ament >Assignee: Shane Curcuru > > This document is interpreted incorrectly as being policy or a requirement for > podlings. Please add a note to the page that this isn't the case. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Assigned] (COMDEV-208) Mark Apache Maturity Model as not policy
[ https://issues.apache.org/jira/browse/COMDEV-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru reassigned COMDEV-208: Assignee: Shane Curcuru > Mark Apache Maturity Model as not policy > > > Key: COMDEV-208 > URL: https://issues.apache.org/jira/browse/COMDEV-208 > Project: Community Development > Issue Type: Improvement >Reporter: John D. Ament >Assignee: Shane Curcuru > > This document is interpreted incorrectly as being policy or a requirement for > podlings. Please add a note to the page that this isn't the case. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-189) 404 on committers-by-project.html
[ https://issues.apache.org/jira/browse/COMDEV-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru resolved COMDEV-189. -- Resolution: Cannot Reproduce The people.a.o/committer* pages work now, and any individual /~userid/ pages are responsibility of the individual committers. > 404 on committers-by-project.html > - > > Key: COMDEV-189 > URL: https://issues.apache.org/jira/browse/COMDEV-189 > Project: Community Development > Issue Type: Bug >Reporter: Stian Soiland-Reyes > > http://people.apache.org/committers-by-project.html#taverna used to work. Now > it is 404. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Resolved] (COMDEV-166) List last group changes older than 3 months
[ https://issues.apache.org/jira/browse/COMDEV-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru resolved COMDEV-166. -- Resolution: Fixed This appears to be fixed: ... PMC changes (from committee-info) ↑ Back to top Changes within the last 3 months: → No new PMC members in the last 3 months. → *Last PMC addition: Mon Nov 14 2016 (Sharon Foga)* → Currently 22 PMC members. ... > List last group changes older than 3 months > --- > > Key: COMDEV-166 > URL: https://issues.apache.org/jira/browse/COMDEV-166 > Project: Community Development > Issue Type: New Feature > Components: Reporter Tool >Reporter: Sebb > > It might be useful to list the last group changes that are older than 3 > months. > This would help show just how static the group membership is. > This could be appended to the existing section as: > Most recent changes since groups were created: > Latest LDAP committee group addition: date (name) or None > Latest committer addition: date (name) or None -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Closed] (COMDEV-119) Zeppelin GSoC Project: add more D3 visualization
[ https://issues.apache.org/jira/browse/COMDEV-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Curcuru closed COMDEV-119. Resolution: Done Closing - no longer pertinent to COMDEV project. > Zeppelin GSoC Project: add more D3 visualization > > > Key: COMDEV-119 > URL: https://issues.apache.org/jira/browse/COMDEV-119 > Project: Community Development > Issue Type: Task > Components: GSoC/Mentoring ideas >Reporter: Alexander Bezzubov > Labels: gsoc2015, javascript, visualization > Attachments: Changing the pivot - Restricted Level.png, Changing the > pivot - Safe Level.png, screen.png, z1.png, z2.png, z3.png > > > Zeppelin frontend web application already have rich visualization library > based on D3. > The goal of this Google Summer of Code project is to add more visualizations > from the wide range of existing ones in D3. > This might be a good opportunity for a students, interested in data > visualization to learn industry standard tools. > Stunents are welcome to reach out Zeppelin community via its developers > mailing list to discuss the dtails, see > http://zeppelin.incubator.apache.org/community.html -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
