Re: [jira] [Deleted] (COMDEV-296) Twitter.com/alhadif1 follow
On Mon, Feb 4, 2019, 02:41 Sebb (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/COMDEV-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Sebb deleted COMDEV-296: > > > > > Twitter.com/alhadif1 follow > > > > > > Key: COMDEV-296 > > URL: https://issues.apache.org/jira/browse/COMDEV-296 > > Project: Community Development > > Issue Type: Bug > >Reporter: Saad > >Priority: Trivial > > > > Twitter.com/alhadif1 follow > > > > -- > 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] [Deleted] (COMDEV-296) Twitter.com/alhadif1 follow
[ https://issues.apache.org/jira/browse/COMDEV-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb deleted COMDEV-296: > Twitter.com/alhadif1 follow > > > Key: COMDEV-296 > URL: https://issues.apache.org/jira/browse/COMDEV-296 > Project: Community Development > Issue Type: Bug >Reporter: Saad >Priority: Trivial > > Twitter.com/alhadif1 follow -- 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-296) Twitter.com/alhadif1 follow
[ https://issues.apache.org/jira/browse/COMDEV-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb closed COMDEV-296. --- Garbage > Twitter.com/alhadif1 follow > > > Key: COMDEV-296 > URL: https://issues.apache.org/jira/browse/COMDEV-296 > Project: Community Development > Issue Type: Bug > Components: Help Wanted >Reporter: Saad >Priority: Trivial > > Twitter.com/alhadif1 follow -- 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-304) Short code links don't work
[
https://issues.apache.org/jira/browse/COMDEV-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759524#comment-16759524
]
Sebb commented on COMDEV-304:
-
{color:#22}URL: {color}[http://svn.apache.org/viewvc?rev=1852849&view=rev]
{color:#22}Log:{color}
{color:#22}COMDEV-304 - short code links don't work{color}
{color:#22}Temporary work-round{color}
{color:#22}Modified:{color}
{color:#22}
comdev/{color}[helpwanted.apache.org/site/tasks.lua|http://helpwanted.apache.org/site/tasks.lua]
> 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
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Help with task: Ensure all Apache TLPs have Wikipedia pages
I would like to help out with the task listed at https://helpwanted.apache.org/task.html?0b349bee
[jira] [Commented] (COMDEV-304) Short code links don't work
[ https://issues.apache.org/jira/browse/COMDEV-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759420#comment-16759420 ] Sebb commented on COMDEV-304: - It looks like the problem is that the _id: field does not support wild-card search. I cannot find the elasticsearch mapping definitions anywhere, so it's difficult to know how to fix this. I suspect the ES mappings will need to be updated to include a copy of the _id that can be searched for - or maybe store the short id itself. The code will then need to be updated to use the new field. > 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 >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 (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-304) Short code links don't work
[ https://issues.apache.org/jira/browse/COMDEV-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759421#comment-16759421 ] Sebb commented on COMDEV-304: - As a work-round, I suppose the code could retrieve just the _ids and look for a match; the full _id could then be used to retrieve the data. Whilst this would be very inefficient, the database does not have that many entries. > 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 (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Assigned] (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 ] Sebb reassigned COMDEV-304: --- Assignee: Daniel Gruno > 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 (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-303) Better error handling when fetching DOAPs
[ https://issues.apache.org/jira/browse/COMDEV-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated COMDEV-303: - Comment: was deleted (was: Please help me to be suggetion it.) > Better error handling when fetching DOAPs > - > > Key: COMDEV-303 > URL: https://issues.apache.org/jira/browse/COMDEV-303 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Sebb >Priority: Major > Attachments: parseprojects.log > > > If parseprojects.py cannot access a DOAP because of a network error, it > should not necessarily treat the file as obsolete. > Also there appears to be a second exception when handling the first; it's not > clear if this is a bug in the Python library or in the script. See attached > log. > Ideally the script should include more info in the e-mail it sends at the end > (e.g. it could store the first N failed fetches) -- 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-303) Better error handling when fetching DOAPs
[ https://issues.apache.org/jira/browse/COMDEV-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated COMDEV-303: - Comment: was deleted (was: JIRA Concepts - Issues JIRA tracks issues, which can be bugs, feature requests, or any other tasks you want to track. Each issue has a variety of associated information including: the issue typea summarya description of the issuethe project which the issue belongs tocomponents within a project which are associated with this issueversions of the project which are affected by this issueversions of the project which will resolve the issuethe environment in which it occursa priority for being fixedan assigned developer to work on the taska reporter - the user who entered the issue into the systemthe current status of the issuea full history log of all field changes that have occurreda comment trail added by usersif the issue is resolved - the resolutionIssue Types JIRA can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section. For Regular Issues BugA problem which impairs or prevents the functions of the product. Epic New FeatureA new feature of the product, which has yet to be developed. Story ImprovementAn improvement or enhancement to an existing feature or task. Wish Task SVN->GIT Migration New TLP New TLP - Common Tasks Blog - New Blog Request Blogs - New Blog User Account Request Blogs - Access to Existing Blog New Bugzilla Project SVN->GIT Mirroring IT HelpFor general IT problems and questions. Created by JIRA Service Desk. AccessFor new system accounts or passwords. Created by JIRA Service Desk. Choose from below ... RTC TCK Challenge Dependency upgradeUpgrading a dependency to a newer version Request Question Temp Brainstorming UmbrellaAn overarching type made of sub-tasks Requirement Comment Planned WorkAssigned specifically to Contractors by the VP Infra or or other VP/ Board Member. Outage Project Office Hours Proposal GitBox Request Dependency New Confluence Wiki New Git Repo Github Integration Sub-task Priority Levels An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels in the administration section. BlockerBlocks development and/or testing work, production could not run CriticalCrashes, loss of data, severe memory leak. Major Minor Trivial StatusesStatus Categories Helps identify where an issue is in its lifecycle. Issues move from To Do to In Progress when work starts on them, and later move to Done when all work is complete. Done Represents anything for which work has been completed" style="background: rgb(20, 137, 44); border: 1px solid rgb(20, 137, 44); border-radius: 3px; color: rgb(255, 255, 255); display: inline-block; font-size: 11px; font-weight: bold; line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center; text-decoration: none; text-transform: uppercase; vertical-align: text-bottom; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width: 12em; word-wrap: normal; word-break: normal;">DONE" style="background: rgb(255, 211, 81); border: 1px solid rgb(255, 211, 81); border-radius: 3px; color: rgb(89, 67, 0); display: inline-block; font-size: 11px; font-weight: bold; line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center; text-decoration: none; text-transform: uppercase; vertical-align: text-bottom; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width: 12em; word-wrap: normal; word-break: normal;">IN PROGRESS" style="background: rgb(204, 204, 204); border: 1px solid rgb(204, 204, 204); border-radius: 3px; color: rgb(51, 51, 51); display: inline-block; font-size: 11px; font-weight: bold; line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center; text-decoration: none; text-transform: uppercase; vertical-align: text-bottom; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width: 12em; word-wrap: normal; word-break: normal;">NO CATEGORY" style="background: rgb(74, 103, 133); border: 1px solid rgb(74, 103, 133); border-radius: 3px; color: rgb(255, 255, 255); display: inline-block; font-size: 11px; font-weight: bold; line-height: 10.89px; margin: 0px; padding: 2px 5px; text-align: center; text-decoration: none; text-transform: uppercase; vertical-align: text-bottom; white-space: nowrap; overflow: hidden; text-overflow: ellipsis; max-width: 12em; word-wrap: normal; word-break: normal;">TO DO Issue Statuses Each issue has a status, which indicates the stage of the issue. In the default workflow, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions. Open The issue is open and ready for the assignee to start work on it." style="b
[jira] [Issue Comment Deleted] (COMDEV-270) GSOC 2018 OFBiz Onpage help tool
[ https://issues.apache.org/jira/browse/COMDEV-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated COMDEV-270: - Comment: was deleted (was: Hi guys. Can i get all applycation form by outomatic.) > GSOC 2018 OFBiz Onpage help tool > > > Key: COMDEV-270 > URL: https://issues.apache.org/jira/browse/COMDEV-270 > Project: Community Development > Issue Type: New Feature > Components: GSoC/Mentoring ideas >Reporter: Shi Jinghai >Priority: Critical > Labels: gsoc2018 > > Sometimes we want to tell OFBiz user that we add a new important function on > a page he/she is viewing, or help user understand the steps on a page without > leaving that page. > Obviously, JQuery-pagewalkthrough[1] is a good choice to be the front end of > onpage helps, and developers can create/edit the multi-language content of > helps in OFBiz content component. > The target of this task is to implement this Onpage help tool and several > example pages for OFBiz trunk. > > 1. [https://github.com/jwarby/jquery-pagewalkthrough] > -- 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-303) Better error handling when fetching DOAPs
[ https://issues.apache.org/jira/browse/COMDEV-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavin updated COMDEV-303: - Comment: was deleted (was: JIRA can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section. ) > Better error handling when fetching DOAPs > - > > Key: COMDEV-303 > URL: https://issues.apache.org/jira/browse/COMDEV-303 > Project: Community Development > Issue Type: Bug > Components: Projects Tool >Reporter: Sebb >Priority: Major > Attachments: parseprojects.log > > > If parseprojects.py cannot access a DOAP because of a network error, it > should not necessarily treat the file as obsolete. > Also there appears to be a second exception when handling the first; it's not > clear if this is a bug in the Python library or in the script. See attached > log. > Ideally the script should include more info in the e-mail it sends at the end > (e.g. it could store the first N failed fetches) -- 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-287) Projects Directory About. Link broken
[
https://issues.apache.org/jira/browse/COMDEV-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gavin updated COMDEV-287:
-
Comment: was deleted
(was: On "About" Projects Directory page :
https://projects.apache.org/about.html
Link "COMDEV Jira issue in the "Projects" component" is broken
)
> Projects Directory About. Link broken
> -
>
> Key: COMDEV-287
> URL: https://issues.apache.org/jira/browse/COMDEV-287
> Project: Community Development
> Issue Type: Bug
> Components: Projects Tool
>Reporter: Vincent Tuybens
>Assignee: Hervé Boutemy
>Priority: Trivial
>
> On "About" Projects Directory page : [https://projects.apache.org/about.html]
> Link "{color:#0066cc}COMDEV Jira issue in the "Projects" component{color}" is
> broken.
--
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-304) Short code links don't work
[ https://issues.apache.org/jira/browse/COMDEV-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated COMDEV-304: Issue Type: Bug (was: Task) > 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 >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 (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
RE: GSoC Application and GSoC Paperwork was Re: ULI TIME SENSITIVE - Re: GSoC 2019 Org applications now open
Kevin thank you for your "context" much appreciated. Now I have an understanding of where you were coming from and I appreciate that. Have a good weekend Thomas S. Pappas, MSA | Senior Vice President of Finance & Administration | Virtual, Inc. D: +1-781-876-8914 F: +1-781-623-8460 tpap...@virtualinc.com 401 Edgewater Place, Suite 600, Wakefield, MA 01880 Wakefield | Nashville | Reston/Washington, DC | Palo Alto -Original Message- From: Kevin A. McGrail Sent: Saturday, February 2, 2019 1:15 PM To: Tom Pappas Cc: Ulrich Stärk ; Daniel Ruggeri ; fundrais...@apache.org; dev@community.apache.org; Maxim Solodovnik ; ment...@community.apache.org Subject: Re: GSoC Application and GSoC Paperwork was Re: ULI TIME SENSITIVE - Re: GSoC 2019 Org applications now open On 2/2/2019 1:00 PM, Tom Pappas wrote: > Kevin here is the disconnect. You noted in your previous email “to > light a fire under the committee”, which infers one exists. My > earlier note saying I had not heard of one which is accurate one does > not currently exist. You with your cut and paste below proves that > out with the stated “setup” of a committee. So to be clear I was > noting one does not exist and that is accurate. Hope this clears up > any confusion on this matter so we can put that to rest and move on to > more pressing issues. Agreed. Please read my statement as light a fire under getting a committee established and then moving. But to be clear, I view the finance committee as existing now with a member of 1. Just like when I started with fundraising. As long as you are a President's committee, all you need is Sam's blessing and you can spread your wings a bit to get things moving. There are certain shackles we know about like the endowment that the board has preempted from anyone else at the current time. Regards, KAM -- Kevin A. McGrail VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 - To unsubscribe, e-mail: fundraising-unsubscr...@apache.org For additional commands, e-mail: fundraising-h...@apache.org - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
