[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website
[ https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17789579#comment-17789579 ] Julian Hyde commented on SDAP-491: -- Good points. Thank you, [~curcuru]! > Adopt an official logo for SDAP and add it to the website > - > > Key: SDAP-491 > URL: https://issues.apache.org/jira/browse/SDAP-491 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Riley Kuttruff >Assignee: Riley Kuttruff >Priority: Major > Attachments: SDAP logo Apache TM.png, SDAP logo bold Apache TM.png, > SDAP logo bold.png, SDAP logo.png, more_sdap_logos.jpg, > sdap_logo_finalists.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website
[ https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788874#comment-17788874 ] Julian Hyde commented on SDAP-491: -- [~rkk], No, the project vote just sets broad direction (and demonstrates consensus) and execution is left to the discretion of people doing the work. > Adopt an official logo for SDAP and add it to the website > - > > Key: SDAP-491 > URL: https://issues.apache.org/jira/browse/SDAP-491 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Riley Kuttruff >Assignee: Riley Kuttruff >Priority: Major > Attachments: SDAP logo Apache TM.png, SDAP logo bold Apache TM.png, > SDAP logo bold.png, SDAP logo.png, more_sdap_logos.jpg, > sdap_logo_finalists.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website
[ https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788871#comment-17788871 ] Julian Hyde commented on SDAP-491: -- The vote is currently under way, but both of the finalists use the 'worm' font for the TM mark. It is conventional to use an ordinary sans serif font for the TM (see [examples|https://brandmarketingblog.com/articles/design/logos-with-tm/]) and we should fix that before the logo is finalized. I don't know what are the branding best practices but I suspect an SVG version and/or a version with transparent background would be useful. > Adopt an official logo for SDAP and add it to the website > - > > Key: SDAP-491 > URL: https://issues.apache.org/jira/browse/SDAP-491 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Riley Kuttruff >Assignee: Riley Kuttruff >Priority: Major > Attachments: SDAP logo Apache TM.png, SDAP logo bold Apache TM.png, > SDAP logo bold.png, SDAP logo.png, more_sdap_logos.jpg, > sdap_logo_finalists.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website
[ https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767308#comment-17767308 ] Julian Hyde commented on SDAP-491: -- The most important thing is to reach consensus, and that's done by discussion. You can take a vote, if you wish, to record that consensus. Once there is consensus, the vote should be a formality. If the decision process is complicated, like choosing a logo, you can devise your methods for an online discussion. Maybe ask people to rank their top 3 choices? Maybe people will say 'I love design #2 but I wish it was blue'. In which case you generate some more logos and have a second round of discussion. Maybe just put the most popular 2 designs to a vote. > Adopt an official logo for SDAP and add it to the website > - > > Key: SDAP-491 > URL: https://issues.apache.org/jira/browse/SDAP-491 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Riley Kuttruff >Assignee: Riley Kuttruff >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-491) Adopt an official logo for SDAP and add it to the website
[ https://issues.apache.org/jira/browse/SDAP-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767245#comment-17767245 ] Julian Hyde commented on SDAP-491: -- I would expect to see a discussion or vote on the dev list about logo candidates. This is a project decision, not merely a code review. > Adopt an official logo for SDAP and add it to the website > - > > Key: SDAP-491 > URL: https://issues.apache.org/jira/browse/SDAP-491 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Riley Kuttruff >Assignee: Riley Kuttruff >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks
[ https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757144#comment-17757144 ] Julian Hyde commented on SDAP-483: -- I saw you merged [PR 85|https://github.com/apache/incubator-sdap-ingester/pull/85]. Now lots of new blue ink on the [incubator-sdap-ingester|https://github.com/apache/incubator-sdap-ingester] home page. Looks great! > Configure GitHub to automatically convert Jira references to hyperlinks > --- > > Key: SDAP-483 > URL: https://issues.apache.org/jira/browse/SDAP-483 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Julian Hyde >Assignee: Riley Kuttruff >Priority: Major > > Configure GitHub to automatically convert Jira references to hyperlinks. > GitHub calls this capability > [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources]. > For an example, see Calcite's [commit > history|https://github.com/apache/calcite/commits/main] and note that text > like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other > places, such as PR comments. > If you would like this functionality in SDAP, let me know, and I'll implement > it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks
[ https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756587#comment-17756587 ] Julian Hyde commented on SDAP-483: -- Thanks. I've added those 3 to the list. It's best that we have the same policy on all repositories, to avoid surprises. There's probably a process to retire/archive git repositories, but I'm not aware of the details. > Configure GitHub to automatically convert Jira references to hyperlinks > --- > > Key: SDAP-483 > URL: https://issues.apache.org/jira/browse/SDAP-483 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Julian Hyde >Priority: Major > > Configure GitHub to automatically convert Jira references to hyperlinks. > GitHub calls this capability > [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources]. > For an example, see Calcite's [commit > history|https://github.com/apache/calcite/commits/main] and note that text > like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other > places, such as PR comments. > If you would like this functionality in SDAP, let me know, and I'll implement > it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks
[ https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Hyde updated SDAP-483: - Issue Type: Task (was: Bug) > Configure GitHub to automatically convert Jira references to hyperlinks > --- > > Key: SDAP-483 > URL: https://issues.apache.org/jira/browse/SDAP-483 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Julian Hyde >Priority: Major > > Configure GitHub to automatically convert Jira references to hyperlinks. > GitHub calls this capability > [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources]. > For an example, see Calcite's [commit > history|https://github.com/apache/calcite/commits/main] and note that text > like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other > places, such as PR comments. > If you would like this functionality in SDAP, let me know, and I'll implement > it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks
[ https://issues.apache.org/jira/browse/SDAP-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756582#comment-17756582 ] Julian Hyde commented on SDAP-483: -- I have logged INFRA-24912. [~rkk], please check that I have the details correct. > Configure GitHub to automatically convert Jira references to hyperlinks > --- > > Key: SDAP-483 > URL: https://issues.apache.org/jira/browse/SDAP-483 > Project: Apache Science Data Analytics Platform > Issue Type: Bug >Reporter: Julian Hyde >Priority: Major > > Configure GitHub to automatically convert Jira references to hyperlinks. > GitHub calls this capability > [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources]. > For an example, see Calcite's [commit > history|https://github.com/apache/calcite/commits/main] and note that text > like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other > places, such as PR comments. > If you would like this functionality in SDAP, let me know, and I'll implement > it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SDAP-483) Configure GitHub to automatically convert Jira references to hyperlinks
Julian Hyde created SDAP-483: Summary: Configure GitHub to automatically convert Jira references to hyperlinks Key: SDAP-483 URL: https://issues.apache.org/jira/browse/SDAP-483 Project: Apache Science Data Analytics Platform Issue Type: Bug Reporter: Julian Hyde Configure GitHub to automatically convert Jira references to hyperlinks. GitHub calls this capability [autolinking|https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources]. For an example, see Calcite's [commit history|https://github.com/apache/calcite/commits/main] and note that text like "CALCITE-5640" is a blue hyperlink. Autolinking also happens in other places, such as PR comments. If you would like this functionality in SDAP, let me know, and I'll implement it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-424) Inclusion of precompiled code (gradle-wrapper.jar) in release
[
https://issues.apache.org/jira/browse/SDAP-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654319#comment-17654319
]
Julian Hyde commented on SDAP-424:
--
We had the same problem in CALCITE-4575. The solution was to exclude
{{gradlew.bat}}, {{gradlew}} and {{gradle/wrapper/*}} from the src.tar.gz file.
(We did not remove these files from the git repo).
We also modified the build instructions to say that if you were building from a
source tarball you must use '{{gradle build}}'. (If building from git you can
use '{{./gradlew build}}'.)
> Inclusion of precompiled code (gradle-wrapper.jar) in release
> -
>
> Key: SDAP-424
> URL: https://issues.apache.org/jira/browse/SDAP-424
> Project: Apache Science Data Analytics Platform
> Issue Type: Task
>Reporter: Riley Kuttruff
>Priority: Major
>
> In nexusproto
>
> This is not permitted by ASF policy
>
> See: https://issues.apache.org/jira/browse/LEGAL-570
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SDAP-422) Prefix release tarball paths with top level directory for easy cleanup post build
[
https://issues.apache.org/jira/browse/SDAP-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17654196#comment-17654196
]
Julian Hyde commented on SDAP-422:
--
A more conventional structure would be to use the base name of the tar file,
like this:
{code}
% tar -tf apache-sdap-ingester-1.0.0-src-incubating.tar.gz
apache-sdap-ingester-1.0.0-src-incubating/.github/workflows/github-dev-release.yml
apache-sdap-ingester-1.0.0-src-incubating/.github/workflows/pypi-tag-release.yml
apache-sdap-ingester-1.0.0-src-incubating/.gitignore
{code}
For extra credit -- feel free to skip this one if it's not easy -- the release
name is 'Apache SDAP Ingester 1.0.0 (incubating)' and therefore the prefix
should be 'apache-sdap-ingester-1.0.0-incubating-src'. This transposes 'src'
and 'incubating'.
> Prefix release tarball paths with top level directory for easy cleanup post
> build
> -
>
> Key: SDAP-422
> URL: https://issues.apache.org/jira/browse/SDAP-422
> Project: Apache Science Data Analytics Platform
> Issue Type: Task
>Reporter: Riley Kuttruff
>Priority: Minor
>
> This will require minor changes to release packaging workflow & the build
> documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SDAP-414) Release SDAP v1.0.0
[ https://issues.apache.org/jira/browse/SDAP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638009#comment-17638009 ] Julian Hyde commented on SDAP-414: -- Was this plan/decision made on any mailing list? The most recent email discussion that I am aware of is "[[DISCUSS] Towards release 0.4.5a56|https://lists.apache.org/thread/bfb2kgf601crh9gt4bwgnzqs8hrpsgfo];. > Release SDAP v1.0.0 > --- > > Key: SDAP-414 > URL: https://issues.apache.org/jira/browse/SDAP-414 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Nga Thien Chung >Assignee: Nga Thien Chung >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SDAP-414) Release SDAP v1.0.0
[ https://issues.apache.org/jira/browse/SDAP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637509#comment-17637509 ] Julian Hyde commented on SDAP-414: -- How much work needs to be done to get the code and doc into shape for a 1.0 release? I ask because, if the goal is to make an Apache release, it might be a lot less effort to just release the code that we have now. For an Apache release, there will be changes for legal reasons (e.g. licenses and file headers) and usability (e.g. a good README file) but no changes in functionality (bugs and feature requests) are required. So I would suggest releasing what we already have first, and only then move on to a 1.0 release. > Release SDAP v1.0.0 > --- > > Key: SDAP-414 > URL: https://issues.apache.org/jira/browse/SDAP-414 > Project: Apache Science Data Analytics Platform > Issue Type: Task >Reporter: Nga Thien Chung >Assignee: Nga Thien Chung >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
