Re: [DISCUSS] Formal process for adding committers / PMC members

[Frank Greguska]

+1 to Nga's suggestion of default single tier including PMC membership with
individual option to opt-out and receive committer-ship only.

On Sun, Feb 25, 2024 at 4:18 PM Nga Chung  wrote:

> Thanks Riley, Julian.
>
> I wonder if it would make sense to go with the one tier, but
> optionally allow the invitee to opt out of PMC membership if they only
> want committership. This way we keep it simple, but also don't scare
> away potential contributors if PMC membership appears like more
> responsibility (even if it really isn't) than they are ready for.
>
> Best,
> Nga
>
> On Tue, Jan 16, 2024 at 3:43 PM Riley Kuttruff  wrote:
> >
> > I'm personally in favor of the two-tier solution as I think it would be
> more suitable for
> > growing our community. As Julian said it's a lower barrier to entry.
> >
> > On 2024/01/16 22:53:38 Julian Hyde wrote:
> > > In favor of one tier (everyone who is a committer is on the PMC):
> > >  * People perceive that there are two tiers to the project (and assume
> that the PMC is doing something nefarious, when in fact it is usually,
> quite correctly, doing very little).
> > >  * Simplicity.
> > >
> > > In favor of two tiers (some committers are not PMC members):
> > >  * The bar to committership is lowered. PMC members will give someone
> the commit bit after just two or three code contributions, or some nice
> work answering questions or giving conference talks.
> > >
> > > Julian
> > >
> > >
> > > > On Jan 16, 2024, at 2:47 PM, Nga Chung  wrote:
> > > >
> > > > I also like the DISCUSS thread example for talking about future
> > > > committers / PMC members.
> > > >
> > > > What is the pro / con of having committers who are not also a PMC
> member?
> > > >
> > > > Thanks,
> > > > Nga
> > > >
> > > > On Tue, Jan 16, 2024 at 7:13 AM Riley Kuttruff 
> wrote:
> > > >>
> > > >> Hi Julian,
> > > >>
> > > >> That makes a lot of sense as a better alternative to the whole
> nomination
> > > >> process.
> > > >>
> > > >> On 2024/01/11 23:56:13 Julian Hyde wrote:
> > > >>> I don't think the process needs to be very formal (e.g. included in
> > > >>> the bylaws) or agreed before graduation. But it does need to be an
> > > >>> organizational habit. This discussion thread, if it reaches
> consensus,
> > > >>> could be all the process we need.
> > > >>>
> > > >>> KVRocks' template email starts 'I nominate...'. I think it's
> important
> > > >>> to lower the bar to discussing new committers and PMC members, so
> we
> > > >>> can talk about people who "might be ready". Because often they
> *are*
> > > >>> ready. It could be a simple email to private@:
> > > >>>
> > >  [DISCUSS] Alex Doe for committer
> > > 
> > >  I think Alex Doe has been  doing some good work recently[1]. They
> have
> > >  made a couple of good PRs, one of which has been merged, and have
> > >  also been answering a lot of questions in the forums.
> > > 
> > >  Do you think Alex has earned enough merit, or should we wait a
> couple of months?
> > > 
> > >  [1]
> https://github.com/apache/incubator-sdap-nexus/commits?author=alexdoe
> > > >>>
> > > >>> In my experience, once there has been a good discussion, the voting
> > > >>> process is very straightforward.
> > > >>>
> > > >>> SDAP should also set a policy (if it doesn't have one) about
> whether
> > > >>> it is possible to be a committer without being a PMC member.
> > > >>>
> > > >>> Julian
> > > >>>
> > > >>> On Wed, Jan 10, 2024 at 12:57 PM Riley Kuttruff 
> wrote:
> > > 
> > >  Hi all,
> > > 
> > >  While working through the maturity model, I noticed SDAP doesn't
> seem to have a documented, formal process for adding committers or PMC
> members (at least, none that I could find). I think we should make an
> effort to establish and ratify a process for this. I think the one outlined
> here [1] would be fine.
> > > 
> > >  Let me know what you think or if you have any alternative
> processes in mind.
> > > 
> > >  Thanks,
> > >  Riley
> > > 
> > >  [1]
> https://kvrocks.incubator.apache.org/community/vote-a-core-developer/
> > > >>>
> > >
> > >
>

Re: [DISCUSS] Explore replacing conda/mamba as python environment manager

[Frank Greguska]

Few comments:

Fully support switching to poetry as the dependency management / build
tool. The main sticking point we may run into is whether or not all of our
dependencies are pure-python libraries. I don't recall specifics but I
thought there might be at least one dependency (shapely maybe?) that
requires specific c libraries be installed; which is why conda was chosen
in the first place. It's possible this is no longer the case and the
benefits of switching to poetry IMO justify the cost of looking at this
again. Additionally, I know there has been improved support between
conda/poetry in that poetry will recognize if it is within a conda
environment and use that environment instead of creating a new virtualenv.
So if we were able to identify which specific dependencies require
installation by conda, we could limit the conda dependencies to just those
libraries but have everything else managed by poetry.

With respect to combining the packages. The intent here was to move towards
a micro-services architecture where the various algorithms were independent
deployables with data-access maintained as a shared library used by all of
them. In reality, this has not played out and it seems installations of
sdap continue to use all the algorithms all the time. So, in my mind it is
a question of what the desired architecture for sdap is. I'm still of the
belief that a microservices style architecture is more flexible and
scalable; however, it does increase the maintenance burden required to
maintain all of the services. In the end, an uber-app is easier to manage
from an installation perspective.

- Frank

On Thu, Feb 29, 2024 at 8:39 AM Stepheny Perez  wrote:

> Riley,
>
> I think this is a good suggestion -- we need an easier way to manage SDAP
> dependencies and transitive dependencies, especially given the license
> issues we've come across multiple times now. This would also make building
> the software locally a lot easier. I'm a big fan of poetry in particular
> and think it would suit SDAP well.
>
> I'm also supportive of combining the analysis and data-access packages
> into a single package - the current organization makes development more
> tedious without much benefit -- especially because they are packaged
> together in the Docker container anyways.
>
> Stepheny
>
>
>
> On 2024/02/28 22:07:34 Riley Kuttruff wrote:
> > We currently use conda/mamba to install dependencies for the granule
> ingester and Nexus components in both local dev environments and for
> building Docker images. This seems to have unwanted consequences as Docker
> appears to be forcing inclusion of some GPL-licensed tools and libraries
> that we don't seem to use but likely block releases under ASF policy. This
> issue was brought up in our IPMC graduation discussion as needing to be
> solved.
> >
> > I'd like to propose replacing conda with another package manager like
> poetry or simply using pip. We could also take this opportunity to combine
> the two top-level Nexus modules so that they're not
> individual-yet-interdependent modules with their own dependencies, but
> rather two submodules of a single project with a single, shared list of
> dependencies.
> >
>

Re: [DISCUSS] Branching strategy in other repos

[Frank Greguska]

Agree it makes sense to match branching strategy across all the repos. The
nexusproto repo does not change frequently so it may be a little overkill
for that repository but I think the benefits of consistent development
strategy outweighs the slightly increased overhead.

- Frank

On Thu, Feb 29, 2024 at 8:33 AM Stepheny Perez  wrote:

> Riley,
>
> I support your proposed changes; we should ensure the branching strategy
> is consistent across all SDAP repos.
>
> Thanks,
> Stepheny
>
> On 2024/02/27 23:27:13 Riley Kuttruff wrote:
> > Hey everyone,
> >
> > Just wanted to bump this thread as I think we should have a bit more
> engagement on this
> > topic before I take it to infra.
> >
> > -Riley
> >
> > On 2024/02/20 23:37:11 Riley Kuttruff wrote:
> > > Hi all,
> > >
> > > As we've implemented an improved branching strategy in the Nexus repo
> [1], I think we should implement the same in the Ingester [2] and
> nexusproto [3] repos as well.
> > >
> > > This would require:
> > > - Setting the default branch for Nexus to be develop.
> > > - Renaming the dev branch in ingester to develop, bringing the master
> branch up to date with develop, and protecting it with .asf.yaml, making it
> the latest release branch
> > > - Creating a new branch, develop, from the master branch in
> nexusproto, making it the default and protecting it and master in .asf.yaml
> > >
> > > I'd like to hear your thoughts and opinions on these changes. Should
> we do this? If so, I can create a ticket with INFRA.
> > >
> > > Thanks,
> > > Riley
> > >
> >
>

Re: Updated Draft Graduation Resolution

[Frank Greguska]

I will join the SDAP PMC.

- Frank

On Wed, Dec 13, 2023 at 2:36 PM Nga Chung  wrote:

> For the record, I opt-in to the SDAP PMC as well.
>
> Thanks,
> Nga
>
> On Wed, Dec 13, 2023 at 9:02 AM Stepheny Perez  wrote:
> >
> > I'd like to opt-in to the SDAP PMC as well.
> >
> > Thanks!
> > Stepheny
> >
> > On 2023/12/13 16:56:56 Kevin Marlis wrote:
> > > I'll opt in to PMC membership.
> > >
> > > Kevin
> > >
> > > On 2023/12/13 15:08:31 Riley Kuttruff wrote:
> > > > In light of the finished PMC Chair vote [1], here's the updated
> draft resolution.
> > > >
> > > > Note, for PMC membership, I copied the current SDAP PPMC membership,
> > > > including mentors. If anyone does not wish to be on the SDAP PMC,
> please
> > > > let me know. I will be contacting everyone on the list if they wish
> to opt out.
> > > >
> > > > Draft resolution:
> > > > Establish the Apache SDAP Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> > > > the Foundation and consistent with the Foundation's purpose to
> establish
> > > > a Project Management Committee charged with the creation and
> maintenance
> > > > of open-source software, for distribution at no charge to the public,
> > > > related to an integrated data analytic center for Big Science
> problems.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache SDAP Project", be and hereby is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache SDAP Project be and hereby is responsible
> > > > for the creation and maintenance of software related to an
> integrated data
> > > > analytic center for Big Science problems; and be it further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache SDAP" be and
> > > > hereby is created, the person holding such office to serve at the
> > > > direction of the Board of Directors as the chair of the Apache SDAP
> > > > Project, and to have primary responsibility for management of the
> > > > projects within the scope of responsibility of the Apache SDAP
> > > > Project; and be it further
> > > >
> > > > RESOLVED, that the persons listed immediately below be and hereby are
> > > > appointed to serve as the initial members of the Apache SDAP Project:
> > > >
> > > > - Edward M Armstrong 
> > > > - Nga Thien Chung 
> > > > - Thomas Cram 
> > > > - Maya Debellis 
> > > > - Jocelyn Elya 
> > > > - Eamon Ford 
> > > > - Frank Greguska 
> > > > - Thomas Huang 
> > > > - Julian Hyde 
> > > > - Joseph C. Jacob 
> > > > - Jason Kang 
> > > > - Jörn Kottmann 
> > > > - Riley Kuttruff 
> > > > - Thomas G Loubrieu 
> > > > - Kevin Marlis 
> > > > - Lewis John McGibbney 
> > > > - Stepheny Perez 
> > > > - Wai Linn Phyo 
> > > > - Elizabeth Yam 
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Nga Thien Chung
> > > > be appointed to the office of Vice President, Apache SDAP, to serve
> in
> > > > accordance with and subject to the direction of the Board of
> Directors
> > > > and the Bylaws of the Foundation until death, resignation,
> retirement,
> > > > removal or disqualification, or until a successor is appointed; and
> be it
> > > > further
> > > >
> > > > RESOLVED, that the Apache SDAP Project be and hereby is tasked with
> > > > the migration and rationalization of the Apache Incubator SDAP
> > > > podling; and be it further
> > > >
> > > > RESOLVED, that all responsibilities pertaining to the Apache
> Incubator
> > > > SDAP podling encumbered upon the Apache Incubator PMC are hereafter
> > > > discharged.
> > > >
> > > > 
> > > >
> > > > Thanks,
> > > > Riley
> > > >
> > > > [1] https://lists.apache.org/thread/x8mt48gv82fm7kg3vf5vpthzkvf9ykq9
> > > > NOTE: The above thread is on private@
> > > >
> > >
>

Re: [DISCUSS] RC2 IPMC vote thread

[Frank Greguska]

I'll do my best.

Technically, SDAP has 10 repositories:
https://github.com/apache?utf8=%E2%9C%93=incubator-sdap==

A few of those should be archived/cleaned up at this point but that hasn't
been a priority. In general though, SDAP is not one piece of software. It
is a suite of software needed to accomplish the goal of running an
integrated data analytic center for Big Science problems. This has been the
subject of discussion for a while; should SDAP have one single major
version that encompasses all components or should they each be
versioned/packaged independently? We've decided for this first go around to
just create one artifact with the most important/commonly used components
needed to say SDAP is installed.

- Frank

On Tue, Jan 3, 2023 at 2:35 PM Julian Hyde  wrote:

> Can someone explain why SDAP has 3 separate GitHub repositories rather
> than one?
>
> It's not my place to suggest changes. But if the separate repositories
> are causing more pain than joy, it might be worth reconsidering.
> (Several times I have typed in
> https://github.com/apache/incubator-sdap/ and been surprised that
> there's nothing there.)
>
> Julian
>
> On Tue, Jan 3, 2023 at 2:20 PM Riley Kuttruff  wrote:
> >
> > Thanks. This change will require an update to the build instructions. I
> have an open pull request to get that done [1] that I would like to get
> approved and merged before trying the next rc.
> >
> > [1] https://github.com/apache/incubator-sdap-nexus/pull/225
> >
> > On 2023/01/03 21:50:30 Frank Greguska wrote:
> > > Makes sense to me.
> > >
> > > - Frank
> > >
> > > On Tue, Jan 3, 2023 at 1:16 PM Riley Kuttruff  wrote:
> > >
> > > > I've been looking into better structuring our release artifacts and
> was
> > > > wondering if anyone had any opinions on how I've updated it:
> > > >
> > > >
> > > > > (sdap-nexus) rileykk@MT-110978 apache-sdap-1.0.0-rc3 % tar -tf
> > > > apache-sdap-nexusproto-1.0.0-src-incubating.tar.gz
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/.gitignore
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/CONTRIBUTING.md
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/DISCLAIMER-WIP
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/LICENSE
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/NOTICE
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README.md
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/build.gradle
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle.properties
> > > > >
> > > >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.jar
> > > > >
> > > >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.properties
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew.bat
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/Jenkinsfile
> > > > >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/pipeline-syntax.gdsl
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/nexusproto.iml
> > > > > Apache-SDAP/apache-sdap-nexusproto-1.0.0/settings.gradle
> > > > >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/proto/DataTile.proto
> > > > >
> > > >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/__init__.py
> > > > >
> > > >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/serialization.py
> > > > >
> > > >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/setup.py
> > > > > (sdap-nexus) rileykk@MT-110978 apache-sdap-1.0.0-rc3 % tar -tf
> > > > apache-sdap-nexus-1.0.0-src-incubating.tar.gz
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/.gitignore
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/CHANGELOG.md
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/CONTRIBUTING.md
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/DISCLAIMER-WIP
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/LICENSE
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/NOTICE
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/README
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/README.md
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/VERSION.txt
> > > > > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.gitign

Re: [DISCUSS] RC2 IPMC vote thread

[Frank Greguska]

Makes sense to me.

- Frank

On Tue, Jan 3, 2023 at 1:16 PM Riley Kuttruff  wrote:

> I've been looking into better structuring our release artifacts and was
> wondering if anyone had any opinions on how I've updated it:
>
>
> > (sdap-nexus) rileykk@MT-110978 apache-sdap-1.0.0-rc3 % tar -tf
> apache-sdap-nexusproto-1.0.0-src-incubating.tar.gz
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/.gitignore
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/CONTRIBUTING.md
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/DISCLAIMER-WIP
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/LICENSE
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/NOTICE
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/README.md
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/build.gradle
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle.properties
> >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.jar
> >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradle/wrapper/gradle-wrapper.properties
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/gradlew.bat
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/Jenkinsfile
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/jenkins/pipeline-syntax.gdsl
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/nexusproto.iml
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/settings.gradle
> > Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/proto/DataTile.proto
> >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/__init__.py
> >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/serialization.py
> >
> Apache-SDAP/apache-sdap-nexusproto-1.0.0/src/main/python/nexusproto/setup.py
> > (sdap-nexus) rileykk@MT-110978 apache-sdap-1.0.0-rc3 % tar -tf
> apache-sdap-nexus-1.0.0-src-incubating.tar.gz
> > Apache-SDAP/apache-sdap-nexus-1.0.0/.gitignore
> > Apache-SDAP/apache-sdap-nexus-1.0.0/CHANGELOG.md
> > Apache-SDAP/apache-sdap-nexus-1.0.0/CONTRIBUTING.md
> > Apache-SDAP/apache-sdap-nexus-1.0.0/DISCLAIMER-WIP
> > Apache-SDAP/apache-sdap-nexus-1.0.0/LICENSE
> > Apache-SDAP/apache-sdap-nexus-1.0.0/NOTICE
> > Apache-SDAP/apache-sdap-nexus-1.0.0/README
> > Apache-SDAP/apache-sdap-nexus-1.0.0/README.md
> > Apache-SDAP/apache-sdap-nexus-1.0.0/VERSION.txt
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.gitignore
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/analysis.iml
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/encodings.xml
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/misc.xml
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/modules.xml
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/.idea/vcs.xml
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/README.md
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/__init__.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/conda-requirements.txt
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/package-list.txt
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/setup.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/static/index.html
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/test.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/README.md
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/__init__.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/StandardDeviationSearch_test.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/longitudelatitudemap_test.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/test_base_doms_handler.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms/test_subsetter.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms_spark/__init__.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms_spark/test_matchup.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/algorithms_spark/test_timeseriesspark.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/config/algorithms.ini
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/conftest.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/data/edge_response.json
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/integration/algorithms_spark/test_matchup.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/redirect/__init__.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/redirect/collections-config.yaml
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/redirect/test_RemoteSDAPCache.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/tests/webapp_test.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/webservice/Filtering.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/webservice/GenerateImageMRF.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/webservice/LayerConfig.py
> > Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/webservice/NexusHandler.py
> >
> Apache-SDAP/apache-sdap-nexus-1.0.0/analysis/webservice/NexusLivyHandler.py
> > 

Re: [DISCUSS] RC2 IPMC vote thread

[Frank Greguska]

My thoughts:

gradle-wrapper.jar and gradlew.bat can be removed from the actual release
artifacts.
I agree the project organization is a bit awkward, but I don't think we
can/should address that right now.
We have to update the copyright

The climatology directory all came from Brian Wilson. I don't know if it's
actively being used anywhere anymore so maybe we just remove it entirely?

- Frank

On Tue, Jan 3, 2023 at 10:04 AM Riley Kuttruff  wrote:

> Another issue that was pointed out is the climatology directory containing
> improperly(?) licensed code [1]. Are we using anything in there? Should it
> be excluded from releases?
>
> [1] https://lists.apache.org/thread/brr31mjz13xrgwf6h6fdnnl30tvr4hzy
>
> On 2023/01/03 02:36:14 Riley Kuttruff wrote:
> > Hello everyone,
> >
> > The IPMC vote has turned up a couple issues with our release:
> >
> > - The presence of a precompiled jar (gradle-wrapper.jar) in the
> nexusproto release [1]
> > - Our project organization is 'awkward' and 'cumbersome' [2]
> > - The copyright line in our NOTICE files is now out of date (2017-2022)
> [2] I'm worried this will necessitate a new release candidate.
> >
> > The vote is still technically ongoing, though I would like to start a
> discussion on a) how to resolve these issues and b) whether we should
> pursue a new release candidate.
> >
> > Thanks,
> > Riley
> >
> > [1] https://lists.apache.org/thread/5lq0hh5brs42o3t68sx4lv8jpmd3knb7
> > [2] https://lists.apache.org/thread/0jww8p4bjr51vbqo34w5gs22qy6qftkm
> >
>

[jira] [Commented] (SDAP-414) Release SDAP v1.0.0

[Frank Greguska (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637383#comment-17637383
 ] 

Frank Greguska commented on SDAP-414:
-

I'm thinking we should probably remove the old attempt at releasing 1.0.0 as 
well so we don't confuse ourselves later

 

[https://github.com/apache/incubator-sdap-nexus/tree/1.1.0-SNAPSHOT]

[https://github.com/apache/incubator-sdap-nexus/tree/v1.0.0-rc1]

[https://github.com/apache/incubator-sdap-nexusproto/tree/v1.0.0-rc1]

 

> 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)

Website Info

[Frank Greguska]

Some questions came up on how to build/modify the website and I just wanted
to share a few links that I found which explain the integration at least a
little bit:

https://incubator.apache.org/guides/sites.html
https://github.com/apache/apache-website-template

It is a Jekyll site and INFRA has setup the sync for us previously:

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

Also, as it pertains to graduation, we do need some updates to the website
before graduating

https://whimsy.apache.org/pods.cgi/project/sdap

- Frank

Re: Ex: [DISCUSS] Towards release 0.4.5a56

[Frank Greguska]

I believe we settled on 3 artifacts:

apache/sdap-nexus-webapp
apache/sdap-collection-manager
apache/sdap-granule-ingester

There was still some active discussion on if these should share a version
number or not. For sake of argument, let's say they do.

So tarball would be something like

   - apache-sdapv1.0.0
  - sdap-nexus-webapp
 - source code
 - sdap-collection-manager
 - source code
 - sdap-granule-ingester
 - source code


Github repos would all have v1.0.0 tags/releases
Docker repos would all have v1.0.0 tag

On Wed, Nov 2, 2022 at 3:52 PM Riley K. Kuttruff  wrote:

> Will there be a tarball corresponding to the Nexus & Ingester repos or
> will both be consolidated into one tatball?
>
> Sent from my Verizon, Samsung Galaxy smartphone
> Get Outlook for Android
> 
> From: Perez, Stepheny K (US 398F) 
> Sent: Wednesday, November 2, 2022 3:47:25 PM
> To: dev@sdap.apache.org 
> Subject: Ex: [DISCUSS] Towards release 0.4.5a56
>
> Hi everyone,
>
> I’d like to start the conversation regarding our first official Apache
> release. From what I can tell, these are the major items that need to be
> completed before we can move forward:
>
>
> 1.   Identify a release manager. Any volunteers?
>
> 2.   Create release tarball
>
> 3.   Write release notes
>
> 4.   Write installation instructions from source (Riley Kuttruff has
> started this work)
>
> 5.   Push docker images to Dockerhub (and update quickstart with these
> versions)
>
> Another important task before moving forward would be testing the latest
> SDAP analysis image 0.4.5a56. I have personally used this version without
> any issues. Has anyone else upgraded to this latest alpha version?
>
> Thank you!
> Stepheny
> CAUTION: This email was not sent from a Cal Poly Pomona service. Exercise
> caution when clicking links or opening attachments. Please forward
> suspicious email to suspectem...@cpp.edu.
>
>

Re: [DISCUSS] Steps to graduation

[Frank Greguska]

Hi Julian,

I am an active member but mostly just admin stuff at this point; not able
to provide much development support. I agree with Trevor's assessment that
the hardest part has been trying to get a release together for review by
Apache. There's a lot of history there I won't get into but I know there is
a current effort underway to try again.

- Frank

On Fri, Oct 14, 2022 at 9:52 AM Trevor Grant 
wrote:

> Based on what I've seen from the project for the last couple of years,
> here's my short synopsis of the status wrt graduating.
>
> To graduate, a project must cut an official release. This is the main point
> holding SDAP back from graduation. Apache as an organization was designed
> for creating and releasing Java projects, SDAP is a Python project.  (There
> are Python projects elsewhere in the ASF, but I will stand by my original
> statement, that Java is first class, everything else should adapt to Java).
> SDAP as a community has focused the majority of its cycles to supporting
> existing deployments of their software as opposed to refactoring to conform
> with ASF things. I don't think there exists undue stress from the ASF to
> conform- just a lack of documentation for non-Java paths.
>
> My recommendation in terms of cutting a release (and thus removing the
> largest hurdle to graduation) would be to
> 1. call a code freeze
> 2. tag / create a zip file of the current code base.
> 3. have various PPMC member test the code (what ever that means in relation
> to SDAP)
> 4. vote
> 5.manually push the zip file to whatever repository that is needed.
>
> I know there are lots of maven plugins that automate #5, that will be
> effectively unusable since this isn't a Java project. Just get ahold of
> someone at Infra and ask them what you need to do to manually release a
> source tar ball. Then document it, maybe put it on the website- and make a
> plan to do it again once a year to keep the board off your back. I know
> your real life users don't care about official releases anyway, so it's
> just a formality that has to happen every so often.
>
> My .02
>
> tg
>
>
> On Thu, Oct 13, 2022 at 1:17 PM Justin Mclean  wrote:
>
> > Hi Julian,
> >
> > Thanks for reaching out to the SDAP project, I also think it time this
> > project needs to consider graduating or the other option is retirement
> from
> > the ASF.
> >
> > Kind Regards,
> > Justin
> >
>

Fwd: Pending configuration of custom domain sdap.apache.org

[Frank Greguska]

Is someone trying to tie our domain to RTD? I'm all for it but just
checking if someone is actually actively taking these steps to set it up.

-- Forwarded message -
From: Read the Docs 
Date: Tue, Aug 30, 2022 at 8:18 AM
Subject: Pending configuration of custom domain sdap.apache.org
To: 


Hello,

The configuration of your custom domain sdap.apache.org

is pending. Make sure to follow the step from our documentation
 to complete the
process.

If you don't complete the configuration, we will stop trying to validate
your domain in 3 weeks, 1 day.
Keep documenting,
Read the Docs
Read the Docs
https://readthedocs.org

Re: Podling Sdap Report Reminder - July 2022

[Frank Greguska]

Thomas had started putting it together; will you be able to finish it today
Thomas?

- Frank

On Tue, Jul 5, 2022 at 12:05 PM Trevor Grant 
wrote:

> Is some one on this? it's due tomorrow.
>
>
> On Tue, Jun 28, 2022 at 9:03 PM  wrote:
>
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 20 July 2022.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, July 06).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers or
> > PPMC members in your report.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > *   Your project name
> > *   A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > *   A list of the three most important issues to address in the move
> > towards graduation.
> > *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > *   How has the community developed since the last report
> > *   How has the project developed since the last report.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/July2022
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Note: The format of the report has changed to use markdown.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
> >
>

Re: Podling Sdap Report Reminder - June 2022

[Frank Greguska]

I ran out of time today to put this together. Can someone else handle this?

- Frank

On Sun, May 29, 2022 at 7:11 PM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 15 June 2022.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 01).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/June2022
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Install Instructions

[Frank Greguska]

Anyone have any pointers for Trevor? I haven't tried the kubernetes install
in a while.

- Frank

On Sun, Feb 20, 2022 at 11:11 AM Trevor Grant 
wrote:

> Heya, I've seen a some PRs coming in about SDAP on k8s, was hoping to play
> with that this week.
>
> Is SDAP on k8s in working condition or should I fall back to the
> instructions from Frank?
>
> tg
>
> On Wed, Jul 24, 2019 at 11:46 AM Frank Greguska  wrote:
>
> > Hi Trevor,
> >
> > Our most comprehensive install doc is this one:
> >
> > https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html
> >
> > But the doc does need to be updated since we're not allowed to publish
> > (non-released) images to the "sdap" dockerhub. If you email me privately
> I
> > can share a different unofficial docker organization that is not in any
> way
> > related to Apache that happens to be building non-released versions of
> SDAP
> > NEXUS for general use.
> >
> > Also, please keep in mind, this only covers the NEXUS component of the
> SDAP
> > project. The search (mudrod) and edge components are not documented much
> > beyond what can be found in their respective README files.
> >
> > https://github.com/apache/incubator-sdap-edge
> > https://github.com/apache/incubator-sdap-mudrod
> >
> > Thanks,
> >
> > Frank
> >
> >
> >
> >
> >
> > On Wed, Jul 24, 2019 at 4:20 AM Trevor Grant 
> > wrote:
> >
> > > Hey all,
> > >
> > > If I want to install/use SDAP where is the 'getting started' ?
> > >
> > > I've looked and not found any docs, assuming they don't exist- I'd like
> > to
> > > write them.
> > >
> >
>

[jira] [Deleted] (SDAP-325) The main trends in the field of IT outsourcing

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-325:



> The main trends in the field of IT outsourcing
> --
>
> Key: SDAP-325
> URL: https://issues.apache.org/jira/browse/SDAP-325
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: developerIT
>Priority: Major
>
> Organizations outsource IT infrastructure maintenance for a variety of 
> reasons, from the desire for increased operational agility to the need for 
> new specialized skills and cost savings. However, market trends are changing. 
> Some outsourcing trends will become less significant in the future, according 
> to a GSA UK report.
>  
> *The state of the IT outsourcing industry*
> To assess the current state of the IT outsourcing industry, a list of IT 
> functions that are most often transferred to third-party companies will help. 
> It was prepared by Statista in 2017 and reflects current trends in this area.
> The functions are listed in descending order of popularity:
> development of web and mobile applications,
> software maintenance,
> data centers,
> IT infrastructure,
> customer support services,
> maintenance of networks,
> integration services,
> functions of the personnel department.
>  
> Today's IT outsourcing providers need to understand these changing market 
> trends 
> [https://www.dataxdev.com/blog/it-outsourcing-trends-and-it-outsourcing-statistics-in-2021/]
>  in order to understand the needs of today's customers. Leading partners will 
> appreciate the customer-centric approach, transparency and trust.
> In addition, the introduction of the latest technology and the protection of 
> data on behalf of the customer will soon be of great importance. Courage in 
> sharing risks can be the key to success and fruitful collaboration.
> Implementing new strategies and following the main trends in IT outsourcing 
> can be an excellent starting point for many market leaders in the next decade.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Deleted] (SDAP-329) Creating Shopify Themes

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-329:



> Creating Shopify Themes
> ---
>
> Key: SDAP-329
> URL: https://issues.apache.org/jira/browse/SDAP-329
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: developerIT
>Priority: Major
>
> More and more web designers are turning their skills to new and smart uses. 
> Whether it's icons, themes, fonts, T-shirts or prints, subsidizing customer 
> work by selling products and services online is on the rise, especially in 
> the web community.
> You can always take advantage of Shopify's custom theme development services 
> [https://www.makebecool.com/services/shopify-theme-development|https://www.makebecool.com/services/shopify-theme-development]
> A few years ago, opening an online store was a daunting and daunting task. 
> Fortunately, the process is much simpler today; for some platforms, it's as 
> easy as creating a theme using your knowledge of HTML, CSS, and JavaScript. 
> Even if you don't want to open your own store, having the skills to offer 
> ecommerce to your new and existing customers is a big plus.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Deleted] (SDAP-328) What CRM is - a complete beginner's guide

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-328:



> What CRM is - a complete beginner's guide
> -
>
> Key: SDAP-328
> URL: https://issues.apache.org/jira/browse/SDAP-328
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>Reporter: Giancarlo Esposito
>Priority: Major
>
> *CRM system concept and how it works*
> CRM-system (short for Customer Relationship Management), simple transcript 
> into Russian, customer relationship management. It is software designed to 
> automate customer (customer) interaction strategies. In particular, to 
> increase sales, optimize marketing and improve customer service by storing 
> information about customers and the history of relationships with them. 
> Establishing and improving business processes and then analyzing the results. 
> It sounds vague, CRM systems - what is it in simple words?
>  
> *CRM is a program for the sales department that allows you to:*
>  * organize and regulate the work of your managers,
>  * monitor their work,
>  * automate the process of a deal with a client,
>  * reduce the time spent on repetitive processes,
>  * control communication between managers and clients,
>  * analyze the level of involvement of your employees in the work,
>  * analyze the level of customer loyalty to your company,
>  * save the customer base and collect the history of interaction with them,
>  * not to lose a single client who showed interest in your company.
> If at least some of the items on the list are relevant to you, then you 
> cannot do without a CRM system. Now CRM is the minimum, without which it is 
> impossible for a company to remain competitive.
> All market leaders, without exception, use CRM systems in their sales! 
> However, CRM is not a magic pill. If you do not have a decent "product", then 
> no program will help to increase the company's sales.
> Typically, CRM systems are cloud-based online services that are provided by 
> subscription. You register in the CRM system, get a single account with all 
> the possibilities and sales tools. After setting up CRM, your employees / 
> managers are added to your account. You pay the tariff that suits you and 
> enjoy your work. You can work in CRM at any time and from any place where 
> there is Internet.
> CRM systems help sales departments by prompting managers what to do: respond 
> to a new request, call a client, plan the next action on the deal. Robot 
> programs themselves send letters and SMS to clients when the application is 
> in the desired status, automatically launch ads and much more.
> CRM allows you not to lose orders from new customers, systematize the work of 
> managers and control it, find points for optimization and further growth of 
> the company.
> CRM-system standardizes and automates processes in the sales department.
> You can tell a lot of beautiful things about how it would be great to 
> automate and increase sales, to manage a company while drinking cocktails on 
> tropical islands. These pictures are often manipulated by CRM implementation 
> consultants. These are empty unreasonable expectations.
> *How to understand if your company needs a CRM system?*
> A CRM system is needed by companies that sell their products or services 
> directly to customers through the sales department. Even if this department 
> consists of one manager, it is much more profitable to lead clients in a 
> systematic way in CRM.
> If for the sale of your service / product it is necessary to conduct pre-sale 
> work (negotiations, presentation, negotiation of conditions) and your sales 
> department receives new requests every day, you need a CRM.
> Only in CRM will it be possible to effectively work simultaneously on a large 
> number of applications that are in different stages of sale.
>  
> h3. Sales department checklist:
>  * The client base is kept in Excel
>  * At the moment of an incoming call, managers do not see the client's name
>  * Your managers do not record agreements with the client
>  * You do not know the following tasks for transactions
>  * Nobody knows exactly how many transactions are at what stage.
>  * Incoming requests from new customers are regularly lost
>  * Email correspondence is conducted from personal mailboxes
>  * No conversation records or conversation histories
>  * Are you tired of the chaos and mess
>  
> Do you recognize your sales department in at least one point?
> Do you want to develop your company, invest in business, invest in 
> adv

[jira] [Deleted] (SDAP-331) Outsourcing and Dedicated Teams: Comparing Two Development Models

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-331:



> Outsourcing and Dedicated Teams: Comparing Two Development Models
> -
>
> Key: SDAP-331
> URL: https://issues.apache.org/jira/browse/SDAP-331
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>Reporter: Giancarlo Esposito
>Priority: Major
>
> In a dynamically changing world, in order to produce a high-quality and 
> competitive product, it is no longer enough to write a detailed specification 
> (which will take at least 2-3 months), and then simply develop the necessary 
> product.
> Nowadays, the time requires close contact of the development team with 
> managers, marketers, business analysts, as well as constant feedback from 
> users.
> With this approach, classic outsourcing models can be ineffective, forcing 
> both customers and developers to look for new models of cooperation.
> This article is devoted to the analysis and comparison of two popular models 
> of software development - outsourcing and dedicated team. We will try not 
> only to consider the advantages and disadvantages of each of them, but also 
> to answer the question of which model will be preferable for certain types of 
> projects.
>  
> First of all, for a better understanding of the topic itself, we will give 
> them definitions.
> *Dedicated tea -* a model in which the work on the project is carried out 
> according to the tasks specified by the customer, who controls the workflow, 
> while the team is busy only with his project. In fact, he can hire and fire 
> employees and regulate the workload of the team. The company takes care of 
> all the worries associated with the office, communication and organization of 
> the workflow.
> *Outsourcing* - a model in which the company hires the necessary specialists 
> “from outside”, and the work process is determined by the internal processes 
> of the outsourcing company.
> Let's take a closer look at each of the models.
>  
> *Dedicated team*
> By choosing a dedicated team model for your project, you get full control 
> over its work. Specialists of the dedicated team are more deeply immersed in 
> the affairs of your organization, better understand the processes functioning 
> in it, its goals, and also almost always focus more on the result of the 
> project than the same specialists working in the framework of outsourcing.
> At the same time, the productivity of employees increases, and team cohesion 
> arises. Also, one of the main advantages of the dedicated team model is the 
> transparency of the communication process: you can fully control your 
> specialists, assign them a schedule convenient for you, distribute tasks 
> between them. Constant feedback allows us to take into account all the 
> requirements and comments of the client and make the necessary changes in 
> time.
> All the advantages of this model are especially well revealed in long and 
> complex projects.
>  
> *Outsourcing*
> With the outsourcing model, the work process takes place in accordance with 
> the regulations set by the outsourcing company, which means that the 
> specialists working on your product can be simultaneously employed on several 
> other projects.
> As a result, their work is often scheduled several weeks in advance, and 
> changes to the work schedule due to additional workload from other customers, 
> unforeseen difficulties, problems or delays often lead to significant time 
> and financial costs.
> The advantage of choosing this model is that prices with it are usually lower 
> than with a dedicated team model, however, it should be remembered that any 
> changes in the project, delays in developers entail changes in the budget, 
> and there is a share of risk in this.
> The outsourcing model usually has two payment options: on time (usually 
> hourly) or a fixed payment per volume of work. In the latter case, the team 
> performs strictly coordinated work, and any change in tasks is coordinated 
> separately, which sometimes takes a lot of time.
>  
> For clarity, let's classify all of the above.
> *Advantages of the Dedicated Team Model:*
>  * involvement of developers in the project - 100%;
>  * the ability of the employer to fully control the work of the team;
>  * a better understanding of the goals and objectives of the company itself 
> on the part of the developers;
>  * team cohesion;
>  * constant feedback;
>  * better and more complex execution of tasks;
>  * fixed monthl

[jira] [Deleted] (SDAP-330) What is an Explainer Video?

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-330:



> What is an Explainer Video?
> ---
>
> Key: SDAP-330
> URL: https://issues.apache.org/jira/browse/SDAP-330
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>Reporter: Giancarlo Esposito
>Priority: Major
>
> The first impression about the company today is created by the logo and 
> branding, and the second is built on the basis of watching a video telling 
> who you are and what your mission is. Such videos are called Explainer / 
> Promo Videos, and today they are seriously affecting the growth of the 
> customer base. Of course, someone achieves the same goal with the help of 
> marketing texts, but videos do it in a much more fun and simple manner, plus 
> they can be shared.
> But there is also a downside: video production takes a lot of resources that 
> you may not have. Especially for such companies with a limited budget, we 
> will present today's story on how to make an explanatory video yourself.
>  
> An Explainer Video is an informative video, usually less than 5 minutes in 
> length, describing what the company is doing or how the product works. This 
> is not a tutorial, but rather a persuasive marketing message. It draws 
> attention to the viewer's pain points and explains how a product / process 
> can become a solution. Sometimes these are animated videos, but a simple form 
> is also possible where a person speaks to the camera.
> Usually, promo videos are posted on a company's home page or landing page, 
> but they can also be shared on social media as advertising or as part of 
> crowdfunding campaigns.
>  
> *Which explanatory video is successful?*
> Good explainer video:
>  * short;
>  * understandable and easy to remember;
>  * personal and inspiring;
>  * consistent with the brand's characteristics;
>  * giving an answer for what the business was created;
>  * suitable for the target audience;
>  * as high quality as it could be done.
> A good video tells a good story. On the one hand, this is an explanation, but 
> on the other, this is the beginning of the viewer's journey - to your brand. 
> After watching it, the viewer should be interested, imbued with, attend to. 
> In general, do not remain indifferent.
> *Enough explanations! Get down to business!*
> It is quite possible to make an explanatory video yourself and make it so 
> that it looks decent. It's not about resources, it's about patience and care. 
> Spielberg's movie, of course, will not work, but it will look better than a 
> selfie on your smartphone. And of course, don't forget to add the video to 
> your landing page!
>  
> If you want to know more about the 5 types of explainer videos, then go to 
> this link 
> [https://explain.ninja/blog/the-5-best-explainer-video-examples-in-2021/ 
> |https://explain.ninja/blog/the-5-best-explainer-video-examples-in-2021/]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Deleted] (SDAP-337) Offshore software development

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-337:



> Offshore software development
> -
>
> Key: SDAP-337
> URL: https://issues.apache.org/jira/browse/SDAP-337
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>Reporter: Derek Lewis
>Priority: Major
>
> Offshore software development is when a company hires an overseas mobile app 
> development team. This approach tends to reduce costs and open access to 
> experts abroad. Offshore software development is a good solution for those 
> who want and can expand their production, but do not have a lot of resources 
> for this.
>  
> *How does offshore software development work?*
> The essence of this approach is to hire developers from other countries. Such 
> specialists work full time, but the cost of their services will be lower than 
> that of a full-time team.
>  
> *Difference between offshore and outsourcing*
> The definitions of outsourcing and offshore seem to be close, but in reality 
> they are completely different. When a company hires a third-party development 
> team, with experts in different niches, it's outsourcing. And when a company 
> opens its office in another country, because there are more favorable 
> conditions for growth - offshore.
>  
> *Who needs offshore software development?*
> Offshore software development is often preferred by non-tech companies. They 
> may be experts in their field, but to develop, for example, a website, they 
> need outside people. In order to understand the issues of mobile application 
> development, they need more people and resources. A company can hire 
> developers on a full-time basis for less cost.
> Such a team can be involved in the implementation of projects in the future. 
> In cases where a company wants to add value to its business and grow further, 
> and it is difficult and costly to find contractors, an offshore will be the 
> ideal solution.
>  
> *Benefits of offshore software development*
>  * A large number of experts
> It is more expensive to hire developers from developed countries than from 
> others, as their skills are more in demand. For example, in the United States 
> there are now more than 250 thousand developer vacancies, and this number is 
> growing. There are literally not enough programmers for all new startups in 
> the country.
> Offshore development opens the door to a world of highly experienced 
> developers. In addition, offshore partners have experience in international 
> projects for the development of mobile applications for other clients, they 
> understand and accept the rules of this game.
>  * Low cost
> Not everyone has the ability to hire and maintain a team of talented and 
> experienced developers. Offshore software development can save internal 
> resources and increase productivity.
> For example, an American entrepreneur wants to create a development team in 
> Bangladesh. If you count all the costs, including the place to work and 
> wages, it will be only half the cost if you create an in-house team. The 
> reason is the low standard of living in developing countries. The cost of 
> living in India is 3-4 times less than in the west.
>  * Time for other projects
> Offshore development allows you to focus on the core business strategy, 
> instead of worrying about team management, technical issues and a process 
> that is not easy to understand. This will help the company focus on the 
> project without extra burden.
>  * Fast scaling
> Hiring and training employees is an investment that can lead to financial 
> risk. Therefore, it is easier to turn to an offshore team. It's cheaper to 
> hire people in another country than to hire and train a full-time team. Such 
> a team can attract more people in a short time.
> An offshore team can take over the management of the subsidiary, cost 
> control, placement, insurance, and more.
>  
> *What is the bottom line*
> The key to software development is to test your idea in the real market. This 
> can be done with the help of an outsourced development team. They can provide 
> you with a huge database of independent contractors willing to participate in 
> your project at the lowest possible cost for quality work.
> At Diceus, we develop web, desktop and mobile apps from scratch and design UI 
> / UX interfaces for them. Our task is to help young startups launch MVPs in 
> order to test the idea and quickly "get used" to the market. So, if you have 
> an idea - click here 
> [https://diceus.com/services/offshore-web-development-company/] to leave your 
> contacts and fear nothing!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Deleted] (SDAP-336) Offshore software development

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-336:



> Offshore software development
> -
>
> Key: SDAP-336
> URL: https://issues.apache.org/jira/browse/SDAP-336
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>Reporter: Derek Lewis
>Priority: Major
>
> Offshore software development is when a company hires an overseas application 
> development team. This approach tends to reduce costs and open access to 
> experts abroad. Offshore software development is a good solution for those 
> who want and can expand their production, but do not have a lot of resources 
> for this.
>  
> *How does offshore software development work?*
> The essence of this approach is to hire developers from other countries. Such 
> specialists work full time, but the cost of their services will be lower than 
> that of a full-time team.
>  
> *Difference between offshore and outsourcing*
> The definitions of outsourcing and offshore seem to be close, but in reality 
> they are completely different. When a company hires a third-party development 
> team, with experts in different niches, it's outsourcing. And when a company 
> opens its office in another country, because there are more favorable 
> conditions for growth - offshore.
>  
> *Who needs offshore software development?*
> Offshore software development is often preferred by non-tech companies. They 
> may be experts in their field, but to develop, for example, a website, they 
> need outside people. In order to understand the issues of mobile application 
> development, they need more people and resources. A company can hire 
> developers on a full-time basis for less cost.
> Such a team can be involved in the implementation of projects in the future. 
> In cases where a company wants to add value to its business and grow further, 
> and it is difficult and costly to find contractors, an offshore will be the 
> ideal solution.
>  
> You can hire offshore developers at Diceus 
> [https://diceus.com/services/offshore-web-development-company/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Deleted] (SDAP-335) How to Make a Hyper Casual Game?

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-335:



>How to Make a Hyper Casual Game?
> ---
>
> Key: SDAP-335
> URL: https://issues.apache.org/jira/browse/SDAP-335
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>Reporter: Diceus
>Priority: Major
>
> *Introduction*
> The hyper casual games are simple and easy to control, addictive and don't 
> take long to play. Suitable for all ages and all genders. In the last couple 
> of years, they are considered the most popular genre of mobile games.
> These games usually have intuitive controls and simple mechanics that can 
> remain consistent throughout the gameplay. But it is possible to increase 
> slightly in difficulty as you progress through the game.
>  
> *4 simple principles of hyper casual games*
>  * Simplification - The gameplay is minimalistic and easy to learn. The 
> player is forgiven for mistakes. It should be hard to lose.
>  * Satisfaction - The player should receive rewards. These can be stars after 
> passing a level or a world leaderboard. The user must be motivated to come 
> back to the game again and again.
>  * Clickability - modern players have clip thinking. To retain the user's 
> attention, it is necessary to “sell” information that is easy to digest. 
> There is no training in hyper casuals. Understanding how to play should come 
> within 2-3 seconds at an intuitive level.
>  * Digestibility - Play sessions should be short. The user must be passionate 
> about the process and receive a release of endorphins upon passing the level.
>  
> *How hyper casual games are created*
> Let's consider the points how the development process goes
>  # *Prototype.* A small prototype of a game on Unity or on another game 
> engine is being created, which can contain no more than 10 levels, does not 
> have a main menu and much that is in ordinary games. The development process 
> should not be delayed, the main thing is to implement the basic mechanics and 
> hone it to a playable look, and the beauty can be brought up later.
>  # *Find a publisher.* Look for a publisher, of which there are enough today 
> with whom you will test the game. Check out the terms and conditions as much 
> as possible, as everyone has their own requirements for games and metrics.
>  # *Analytics integration*. Before launching the game for a test, you need to 
> build SDKs for various analytics services to track important metrics. Such as 
> the retention percentage of players who returned to the game and the CPI 
> price per install.
>  # *Creatives*. For the test, you will need commercials with the gameplay of 
> your game. Write down the most interesting moments in your opinion, 
> successful and unsuccessful passing of the levels. Sometimes the publisher 
> does this.
>  # *Test.* The most important and decisive stage is the launch of advertising 
> campaigns in social networks, which on average last from 2 to 3 days. At the 
> end of these days, it will become clear whether you made a Potential Hit or a 
> mediocre game, on which it makes no sense to work further.
> This process can be repeated over and over again until you make a really 
> worthwhile game.
>  
> *Ideas for hyper casual games*
> First of all, in games of this genre, the plot and the visual component are 
> not important, here the main mechanics are. Therefore, they can be borrowed 
> from other computer, browser or flash games and made the basis of the game. 
> Also, mechanics can be taken from real life, be it everyday activities, 
> hobbies or work.
>  
> *Basic mechanics*
> There are 3 main sub-genres in casual games. If you know them, you can 
> endlessly generate ideas for hyper casual games. Or leave it to the 
> professional [hyper casual game 
> developers|https://kevurugames.com/game-development/hyper-casual-game-development-services/]
>  who do a great job for you.
>  * Puzzles are simple games that create the illusion of a progression. The 
> player must feel his own superiority. This genre includes crosswords, 
> labyrinths, search for differences, 3 in a row and other entertainment.
>  * Clickers or idles - the essence of these toys is that the whole gameplay 
> is reduced to pressing one key.
>  * Runners - you need to overcome the route from point A to point B. The more 
> you run, the more points you earn. To keep players interested, it's worth 
> adding upgrades.
>  
> *How to promote hyper casual games*
> The attraction of users to the game occurs through the pur

[jira] [Deleted] (SDAP-334) Tips For Finding The Best Python Development Company

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-334:



> Tips For Finding The Best Python Development Company
> 
>
> Key: SDAP-334
> URL: https://issues.apache.org/jira/browse/SDAP-334
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>Reporter: Diceus
>Priority: Major
>
> h2. *Skills required for a Python developer*
> In addition to basic skills such as the ability to solve problems, create, 
> analyze and apply algorithms, and successfully debug code, a Python developer 
> must have in-depth knowledge [software 
> consulting|https://djangostars.com/services/software-consultancy/digital-transformation-services/]
>   and experience in the following areas:
>  * Python syntax and semantics;
>  * Basic Python Concepts;
>  * Object-relational mapping (ORM);
>  * Web Application Interface - CSS3, HTML5, JavaScript;
>  * Python multiprocessing architecture and the limitations of multithreading;
>  * RESTful API and Database Integration;
>  * Python Application Development;
>  * System administration.
> h2. *What candidates are looking for in Python jobs*
> To find and hire Python developers, you also need to understand how job 
> seekers evaluate the job opportunities available to them. Here are some 
> things you might want to consider before hiring someone for this job.
> h2. *Commitment to Open Source*
> this is a big advantage if companies use and maintain Open Source libraries, 
> such as fixing bugs in a project.
> h2. *Python rankings and prospects*
> One way to measure the popularity of a programming language is the TIOBE 
> index. It is calculated based on the number of searches on Google and other 
> search engines. Requests that include the name of programming languages ​​are 
> taken into account.
> According to the TIOBE Index, in November 2020, Python is ranked second on 
> the list of the most popular programming languages. It is ahead of 
> JavaScript, PHP, Swift and other mainstream languages.
> In the 2019 GitHub Octoverse ranking, Python is second only to JavaScript. 
> The Github Octoverse rating reflects the popularity of the language among 
> GitHub users.
> Python also ranks second in the RedMonk ranking. RedMonk co-founder James 
> Gaverner notes that Python is already the lingua franca for Data Science. 
> That is, this language has become the main one for this industry. 
> Nevertheless, Gaverner does not rule out that Python is currently at its peak 
> in popularity.
> h2. *Python as a first language for beginners: is it hard to learn*
> To answer this question, you need to go back to the history and philosophy of 
> [python development company|https://djangostars.com/]. As noted above, the 
> language developer Guido van Rossum wanted to create Python because other 
> languages ​​seemed too complicated and incomprehensible to him. Van Rossum 
> has managed to make a language that is fun to learn and work with.
> Python is considered one of the best and most user-friendly languages ​​for 
> learning. Does that mean it's easy to learn? Probably not. Learning to 
> program always requires discipline, diligence, concentration.
> When choosing your first programming language, the main advantage of Python 
> is its simple syntax. Among the shortcomings, one can note the difficulties 
> that beginner programmers face when switching to languages ​​with more 
> complex syntax.
> h2. *Python rankings and prospects*
> One way to measure the popularity of a programming language is the TIOBE 
> index. It is calculated based on the number of searches on Google and other 
> search engines. Requests that include the name of the programming languages 
> are taken into account.
> According to the TIOBE Index, in November 2021, Python is ranked second on 
> the list of the most popular programming languages. It is ahead of 
> JavaScript, PHP, Swift and other mainstream languages.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Deleted] (SDAP-333) A Complete Guide on How to Choose the Right Smartwatch for You

[Frank Greguska (Jira)]

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

Frank Greguska deleted SDAP-333:



> A Complete Guide on How to Choose the Right Smartwatch for You
> --
>
> Key: SDAP-333
> URL: https://issues.apache.org/jira/browse/SDAP-333
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>Reporter: Diceus
>Priority: Major
>
> Buying a smartwatch will make your life much easier. This is a universal 
> device that will not only show the time, but also remind you of upcoming 
> meetings, wake you up in the morning and notify you of incoming calls. Read 
> about these and other features, as well as how to choose a smartwatch, in our 
> article.
> h2. *What is a smartwatch and what are they like?*
> After the advent of smartphones, it became clear that other gadgets could 
> also be made smarter. First of all, this affected the watch. So how are 
> smartwatches different from ordinary watches and what can they do? It's 
> simple: they inherited many functions from modern phones and can enter into 
> symbiosis with them, simplifying work and eliminating the need to go into 
> your pocket for a smartphone every time. Learn more about development details 
> at 
> [https://diceus.com/expertise/wearable-app-development-services-and-solutions/].
> Instead of a dial, smartwatches have a modern electronic display, often in 
> color. In most devices, the screen is touch sensitive. Such devices allow you 
> to answer calls, send messages, surf the Internet, store information on them 
> like on a USB flash drive, and even take pictures, as well as scan the 
> owner's physical activity with them.
> The number of functions and capabilities of smartwatches directly depends on 
> their price. Sometimes the exception is gadgets, which can be expensive 
> simply because of the brand.
> There is no official classification of smartwatches, so it is rather 
> arbitrary. Smart watches can be divided into:
>  #  Watch-phone is an interesting variant of devices that does not require 
> connection to a smartphone, but at the same time you can make calls with 
> their help. They have a built-in micro or nano size SIM card slot. On such a 
> watch, you can install various applications, view documents and even photos 
> with their help.
>  #  Companion watch - this watch will already ask for connection to your 
> smartphone and without such symbiosis will not be able to function at its 
> full potential. But due to this connection, the watch-companion is much more 
> functional than its other brothers, since many operations are processed by 
> the processor of a smartphone, which is by far more powerful than the one 
> that can be put into a watch.
> Fitness bracelets and watches - this category includes universal devices that 
> not only perform some of the functions of a smartwatch, but are also designed 
> to collect various information about the owner's physical activity and the 
> state of his health. These gadgets are designed for sports and are not 
> intended to emphasize the status of the owner; therefore, they are 
> lightweight and can be of different colors and shapes.
> Fitness watches, as a rule, can count the owner's heart rate and the number 
> of steps taken, switch to workout mode in the gym, read GPS routes, and much 
> more. All received information is sent either to a smartphone via Bluetooth 
> or Wi-Fi, or to cloud services via the Internet, where it is stored for later 
> analysis.
> As for fitness bracelets, their functionality is slightly more modest than 
> that of watches, they are smaller in size and often do not have a display. 
> All control is carried out using a smartphone. However, in more modern 
> models, manufacturers still add convenient touchscreens, thanks to which it 
> is not at all necessary to carry a smartphone with you for jogging.
> h2. *Software platform or watch OS*
> Like any electronic device, smart watches work using the program installed in 
> them, so you can distinguish:
>  *          A watch without an operating system, in which the functionality 
> is limited to those options that were originally built into them by the 
> developer. There are no prerequisites for customization in them, so be 
> content with what you have. As a rule, this applies to watches from the cheap 
> segment and to fitness bracelets. You will not be able to install the 
> applications you like on them, only in some models you can slightly modify 
> the interface for a more convenient one. Sometimes manufacturers release new 
> fir

Fwd: [NOTICE] [Podlings] Git web site publishing to be done via .asf.yaml only as of July 1st

[Frank Greguska]

Heads up, the SDAP site is going to have to migrate.



-- Forwarded message -
From: Daniel Gruno 
Date: Mon, May 31, 2021 at 6:45 AM
Subject: [NOTICE] [Podlings] Git web site publishing to be done via
.asf.yaml only as of July 1st
To: Users 


TL;DR: if your project web site is kept in subversion, disregard this
email please. If your project web site is using git, and you have not
deployed it via .asf.yaml, you MUST switch before July 1st or risk your
web site goes stale.



Dear Apache projects,
In order to simplify our web site publishing services and improve
self-serve for projects and stability of deployments, we will be turning
off the old 'gitwcsub' method of publishing git web sites. As of this
moment, this involves 120 web sites. All web sites should switch to our
self-serve method of publishing via the .asf.yaml meta-file. We aim to
turn off gitwcsub around July 1st.


## How to publish via .asf.yaml:
Publishing via .asf.yaml is described at:
https://s.apache.org/asfyamlpublishing
You can also see an example .asf.yaml with publishing and staging
profiles for our own infra web site at:
https://github.com/apache/infrastructure-website/blob/asf-site/.asf.yaml

In short, one puts a file called .asf.yaml into the branch that needs to
be published as the project's web site, with the following two-line
content, in this case assuming the published branch is 'asf-site':

publish:
   whoami: asf-site


It is important to note that the .asf.yaml file MUST be present at the
root of the file system in the branch you wish to publish. The 'whoami'
parameter acts as a guard, ensure that only the intended branch is used
for publishing.


## Is my project affected by this?
The quickest way to check if you need to switch to a .asf.yaml approach
is to check out site source page at
https://infra-reports.apache.org/site-source/ - if your site is listed
in yellow, you will need to switch. This page will also tell you which
branch you are currently publishing as your web site. This is (should
be) the branch that you must add a .asf.yaml meta file to.

The web site source list updates every hour. If your project site
appears in green, you are already using .asf.yaml for publishing and do
not need to make any changes.


## What happens if we miss the deadline?
If you miss the deadline, don't fret. Your site will of course still
remain online as is, but new updates will not appear till you
create/edit the .asf.yaml and set up publishing.


## Who do we contact if we have questions?
Please contact us at us...@infra.apache.org if you have any additional
questions.


With regards,
Daniel on behalf of ASF Infra.

Re: [DISCUSS] What is holding back Release and graduation?

[Frank Greguska]

Trevor -

Yes it appears that going through the release process and addressing any
licensing concerns are the main thing preventing graduation. The only thing
I can say is that it hasn't been prioritized/defined when releases should
be executed/tagged.

- Frank

On Wed, Feb 3, 2021 at 2:26 PM Trevor Grant 
wrote:

> Hey-
>
> I'd like to start up another thread on what precisely is holding SDAP back
> from
>
> 1. Doing a release?
>
> It's my understanding (which is entirely possible it is wrong), that all
> that is required for an apache release is the code is created as an
> artifact some where (as well as checking licenses of dependencies, all the
> other checkboxes).  I know there were some issues about most of the release
> processes being Java specific, and this project is Python, but it's not
> like you have to release to PyPi for it to "count" as an apache release.
>
> Why not call a code freeze across all repos, create artifacts, upload them
> to nexus, PPMC votes, vote passes, IPMC votes, and boom SDAP 1.0.
>
> I ask this not as a rhetorical question- I am sure there are some reasons
> its not quite that simple- what are they?
>
> 2. graduation-
>
> Afaik - the major issue is no release. What aside from that is holding this
> project back?
>
> It can be hard to read tone in email, so please don't read this as "Why the
> heck haven't you graduated yet?!?!" but more as a "If graduation is the
> goal, and releases are holding us back from that- what is the shortest path
> to doing a release?"
>
> Just some thoughts I had to distract me from this other thing I was working
> on while reading the board report- respond as you like.
> tg
>

[REPORT] Submitted

[Frank Greguska]

Final report has been submitted. View it here:

https://cwiki.apache.org/confluence/display/INCUBATOR/February2021#sdap

- Frank

Re: [REPORT] [DRAFT] Due Tomorrow

[Frank Greguska]

Last call, anything to contribute to community development or issues?

On Tue, Feb 2, 2021 at 9:48 AM Frank Greguska  wrote:

> Our report is due tomorrow, I've put together the draft below. Does anyone
> have any comments to add? Any highlights to call out from the last 3 months?
>
> ## SDAP
>
> SDAP is an integrated data analytic center for Big Science problems.
>
> SDAP has been incubating since 2017-10-22.
>
> ### Three most important unfinished issues to address before graduating:
>
>  1. Make official SDAP (Incubating) Release
>  2. Improve committer participation
>  3. Improve/create user guide documentation
>
> ### Are there any issues that the IPMC or ASF Board need to be aware of?
>
>
> ### How has the community developed since the last report?
>
>
> ### How has the project developed since the last report?
>
> Bug Fixes
> - SDAP-302 Collection Manager crashes when Collections Config is updated
> while actively scanning S3 dirs
> - SDAP-290 Collection manager crashes when granule directory has wildcard
> - SDAP-301 Granule Ingester cannot process granules with missing 'units'
> attribute
> - SDAP-300 Collection Manager won't scan directories on local filesystem
> - SDAP-299 Update Helm dependency repo urls
> - SDAP-295 Hash dataset name in tile ID
> - SDAP-293 New ingestion system should convert Kelvin to Celsius
> - SDAP-288 support S3 new ingestion system
> - SDAP-286 ingestion should handle 0-360 longitudes
>
> New Features
> - SDAP-292 Add Cassandra authentication support to delete_by_query.py
> script
> - SDAP-298 Helm Chart 1.0.0
>
> Improvements
> - SDAP-294 Support date normalization on analysis side
> - SDAP-297 Update Collection Manager documentation
> - SDAP-296 Make deletebyquery script work out-of-the-box in docker image
>
> ### How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   - [ ] Initial setup
>   - [ x ] Working towards first release
>   - [ x ] Community building
>   - [ ] Nearing graduation
>   - [ ] Other:
>
> ### Date of last release:
>
>   -XX-XX
>
> ### When were the last committers or PPMC members elected?
>
> Two new committers were elected in April 2020.
>
> ### Have your mentors been helpful and responsive?
> Are things falling through the cracks? If so, please list any
> open issues that need to be addressed.
>
> Have not heard from Jörn in a while.
>
> ### Is the PPMC managing the podling's brand / trademarks?
> Are 3rd parties respecting and correctly using the podlings
> name and brand? If not what actions has the PPMC taken to
> correct this? Has the VP, Brand approved the project name?
>
> No, PPMC is not managing the podling's brand.
>
> ### Signed-off-by:
>
>   - [ ] (sdap) Jörn Rottmann
>  Comments:
>   - [ ] (sdap) Trevor Grant
>  Comments:
>

[REPORT] [DRAFT] Due Tomorrow

[Frank Greguska]

Our report is due tomorrow, I've put together the draft below. Does anyone
have any comments to add? Any highlights to call out from the last 3 months?

## SDAP

SDAP is an integrated data analytic center for Big Science problems.

SDAP has been incubating since 2017-10-22.

### Three most important unfinished issues to address before graduating:

 1. Make official SDAP (Incubating) Release
 2. Improve committer participation
 3. Improve/create user guide documentation

### Are there any issues that the IPMC or ASF Board need to be aware of?


### How has the community developed since the last report?


### How has the project developed since the last report?

Bug Fixes
- SDAP-302 Collection Manager crashes when Collections Config is updated
while actively scanning S3 dirs
- SDAP-290 Collection manager crashes when granule directory has wildcard
- SDAP-301 Granule Ingester cannot process granules with missing 'units'
attribute
- SDAP-300 Collection Manager won't scan directories on local filesystem
- SDAP-299 Update Helm dependency repo urls
- SDAP-295 Hash dataset name in tile ID
- SDAP-293 New ingestion system should convert Kelvin to Celsius
- SDAP-288 support S3 new ingestion system
- SDAP-286 ingestion should handle 0-360 longitudes

New Features
- SDAP-292 Add Cassandra authentication support to delete_by_query.py script
- SDAP-298 Helm Chart 1.0.0

Improvements
- SDAP-294 Support date normalization on analysis side
- SDAP-297 Update Collection Manager documentation
- SDAP-296 Make deletebyquery script work out-of-the-box in docker image

### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [ ] Initial setup
  - [ x ] Working towards first release
  - [ x ] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  -XX-XX

### When were the last committers or PPMC members elected?

Two new committers were elected in April 2020.

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

Have not heard from Jörn in a while.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

No, PPMC is not managing the podling's brand.

### Signed-off-by:

  - [ ] (sdap) Jörn Rottmann
 Comments:
  - [ ] (sdap) Trevor Grant
 Comments:

[jira] [Commented] (SDAP-154) Python 3

[Frank Greguska (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17277337#comment-17277337
 ] 

Frank Greguska commented on SDAP-154:
-

HI [~antwaneone] that would be great!

 

You can do the work in a branch called SDAP-154 and open a pull request to 
[https://github.com/apache/incubator-sdap-nexus/tree/master] when it's ready.

> Python 3
> 
>
> Key: SDAP-154
> URL: https://issues.apache.org/jira/browse/SDAP-154
> Project: Apache Science Data Analytics Platform
>  Issue Type: Wish
>    Reporter: Frank Greguska
>Priority: Minor
>
> Update all code to python 3.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [EXTERNAL] Re: [REPORT] Details Needed

[Frank Greguska]

Thanks Joe.

On Wed, Jun 3, 2020 at 11:30 AM Jacob, Joseph C (US 398H) <
joseph.c.ja...@jpl.nasa.gov> wrote:

> Correction:  Change "ESRI" to "Esri".
>
> Thanks,
>
> Joe
>
>
> On 6/3/20, 11:25 AM, "Jacob, Joseph C (US 398H)" <
> joseph.c.ja...@jpl.nasa.gov> wrote:
>
> Hi, Frank.  Thanks again for coordinating the report.  Just glancing
> at the incubator-sdap-nexus log, I would put the following as status:
>
> 1. Integrated SDAP analytics with ESRI ArcGIS front end.
> 2. Added new temporal variance (2D map) analytic algorithm.
> 3. Further improvements in Kubernetes-based deployment procedures.
>
> Thanks,
>
> Joe
>
>
> On 6/3/20, 11:19 AM, "lewis john mcgibbney" 
> wrote:
>
> +1.
> I am not in a position to summarize what has been done Frank.
>
> On Wed, Jun 3, 2020 at 11:15 AM Frank Greguska 
> wrote:
>
> > Hello,
> >
> > The report is due today. I will submit with "Development
> continues to be
> > tracked in JIRA" unless anyone else cares to summarize what
> development has
> > been done.
> >
> > - Frank
> >
> > On Mon, Jun 1, 2020 at 10:06 AM Armstrong, Edward M (US 398P)
>     >  wrote:
> >
> >> Hi Frank,
> >>
> >> I personally don’t have anything to contribute.
> >>
> >>
> >> -- Ed
> >>
> >>
> >> From: Frank Greguska 
> >> Reply-To: "priv...@sdap.apache.org" 
> >> Date: Monday, June 1, 2020 at 10:02 AM
> >> To: "dev@sdap.apache.org" 
> >> Cc: "priv...@sdap.apache.org" 
> >> Subject: [EXTERNAL] Re: [REPORT] Details Needed
> >>
> >> Hello,
> >>
> >> I've seen a lot of activity in JIRA, does anyone want to add
> information
> >> to the report? We missed our deadline last month and this one
> is due on
> >> Wednesday.
> >>
> >> - Frank
> >>
> >> On Wed, May 27, 2020 at 4:18 PM Frank Greguska <
> fg...@apache.org >> fg...@apache.org>> wrote:
> >> Hello,
> >>
> >> Please add details to the report below:
> >>
> >>
> >>
> >> ## SDAP
> >>
> >> SDAP is an integrated data analytic center for Big Science
> problems.
> >>
> >> SDAP has been incubating since 2017-10-22.
> >>
> >> ### Three most important unfinished issues to address before
> graduating:
> >>
> >>   1. Make official SDAP (Incubating) Release
> >>   2. Improve committer participation
> >>   3. Improve/create user guide documentation
> >>
> >> ### Are there any issues that the IPMC or ASF Board need to be
> aware of?
> >>
> >> Subscription of PPMC members to the @private mailing list
> should be
> >> resolved. All PPMC members should now be subscribed to
> @private. If this is
> >> not accurate, please advise.
> >>
> >> ### How has the community developed since the last report?
> >>
> >> New committers have been added.
> >>
> >> ### How has the project developed since the last report?
> >>
> >>
> >> ### How would you assess the podling's maturity?
> >> Please feel free to add your own commentary.
> >>
> >>   - [ ] Initial setup
> >>   - [x] Working towards first release
> >>   - [x] Community building
> >>   - [ ] Nearing graduation
> >>   - [ ] Other:
> >>
> >> ### Date of last release:
> >>
> >>   -XX-XX
> >>
> >> ### When were the last committers or PPMC members elected?
> >>
> >> Two new committers were elected in April 2020.
> >>
> >> ### Have your mentors been helpful and responsive?
> >> Are things falling through the cracks? If so, please list any
> >> open issues that need to be addressed.
> >>
> >> ### Is the PPMC managing the podling's brand / trademarks?
> >> Are 3rd parties respecting and correctly using the podlings
> >> name and brand? If not what actions has the PPMC taken to
> >> correct this? Has the VP, Brand approved the project name?
> >>
> >> PPMC is not managing the podling's brand / trademarks.
> >>
> >> ### Signed-off-by:
> >>
> >>   - [ ] (sdap) Jörn Rottmann
> >>  Comments:
> >>   - [ ] (sdap) Trevor Grant
> >>  Comments:
> >>
> >> ### IPMC/Shepherd notes:
> >>
> >>
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>
>
>

Re: [EXTERNAL] Re: [REPORT] Details Needed

[Frank Greguska]

Hello,

The report is due today. I will submit with "Development continues to be
tracked in JIRA" unless anyone else cares to summarize what development has
been done.

- Frank

On Mon, Jun 1, 2020 at 10:06 AM Armstrong, Edward M (US 398P)
 wrote:

> Hi Frank,
>
> I personally don’t have anything to contribute.
>
>
> -- Ed
>
>
> From: Frank Greguska 
> Reply-To: "priv...@sdap.apache.org" 
> Date: Monday, June 1, 2020 at 10:02 AM
> To: "dev@sdap.apache.org" 
> Cc: "priv...@sdap.apache.org" 
> Subject: [EXTERNAL] Re: [REPORT] Details Needed
>
> Hello,
>
> I've seen a lot of activity in JIRA, does anyone want to add information
> to the report? We missed our deadline last month and this one is due on
> Wednesday.
>
> - Frank
>
> On Wed, May 27, 2020 at 4:18 PM Frank Greguska  fg...@apache.org>> wrote:
> Hello,
>
> Please add details to the report below:
>
>
>
> ## SDAP
>
> SDAP is an integrated data analytic center for Big Science problems.
>
> SDAP has been incubating since 2017-10-22.
>
> ### Three most important unfinished issues to address before graduating:
>
>   1. Make official SDAP (Incubating) Release
>   2. Improve committer participation
>   3. Improve/create user guide documentation
>
> ### Are there any issues that the IPMC or ASF Board need to be aware of?
>
> Subscription of PPMC members to the @private mailing list should be
> resolved. All PPMC members should now be subscribed to @private. If this is
> not accurate, please advise.
>
> ### How has the community developed since the last report?
>
> New committers have been added.
>
> ### How has the project developed since the last report?
>
>
> ### How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   - [ ] Initial setup
>   - [x] Working towards first release
>   - [x] Community building
>   - [ ] Nearing graduation
>   - [ ] Other:
>
> ### Date of last release:
>
>   -XX-XX
>
> ### When were the last committers or PPMC members elected?
>
> Two new committers were elected in April 2020.
>
> ### Have your mentors been helpful and responsive?
> Are things falling through the cracks? If so, please list any
> open issues that need to be addressed.
>
> ### Is the PPMC managing the podling's brand / trademarks?
> Are 3rd parties respecting and correctly using the podlings
> name and brand? If not what actions has the PPMC taken to
> correct this? Has the VP, Brand approved the project name?
>
> PPMC is not managing the podling's brand / trademarks.
>
> ### Signed-off-by:
>
>   - [ ] (sdap) Jörn Rottmann
>  Comments:
>   - [ ] (sdap) Trevor Grant
>  Comments:
>
> ### IPMC/Shepherd notes:
>
>

Re: [REPORT] Details Needed

[Frank Greguska]

Hello,

I've seen a lot of activity in JIRA, does anyone want to add information to
the report? We missed our deadline last month and this one is due on
Wednesday.

- Frank

On Wed, May 27, 2020 at 4:18 PM Frank Greguska  wrote:

> Hello,
>
> Please add details to the report below:
>
>
>
> ## SDAP
>
> SDAP is an integrated data analytic center for Big Science problems.
>
> SDAP has been incubating since 2017-10-22.
>
> ### Three most important unfinished issues to address before graduating:
>
>   1. Make official SDAP (Incubating) Release
>   2. Improve committer participation
>   3. Improve/create user guide documentation
>
> ### Are there any issues that the IPMC or ASF Board need to be aware of?
>
> Subscription of PPMC members to the @private mailing list should be
> resolved. All PPMC members should now be subscribed to @private. If this is
> not accurate, please advise.
>
> ### How has the community developed since the last report?
>
> New committers have been added.
>
> ### How has the project developed since the last report?
>
>
> ### How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   - [ ] Initial setup
>   - [x] Working towards first release
>   - [x] Community building
>   - [ ] Nearing graduation
>   - [ ] Other:
>
> ### Date of last release:
>
>   -XX-XX
>
> ### When were the last committers or PPMC members elected?
>
> Two new committers were elected in April 2020.
>
> ### Have your mentors been helpful and responsive?
> Are things falling through the cracks? If so, please list any
> open issues that need to be addressed.
>
> ### Is the PPMC managing the podling's brand / trademarks?
> Are 3rd parties respecting and correctly using the podlings
> name and brand? If not what actions has the PPMC taken to
> correct this? Has the VP, Brand approved the project name?
>
> PPMC is not managing the podling's brand / trademarks.
>
> ### Signed-off-by:
>
>   - [ ] (sdap) Jörn Rottmann
>  Comments:
>   - [ ] (sdap) Trevor Grant
>  Comments:
>
> ### IPMC/Shepherd notes:
>
>

[REPORT] Details Needed

[Frank Greguska]

Hello,

Please add details to the report below:



## SDAP

SDAP is an integrated data analytic center for Big Science problems.

SDAP has been incubating since 2017-10-22.

### Three most important unfinished issues to address before graduating:

  1. Make official SDAP (Incubating) Release
  2. Improve committer participation
  3. Improve/create user guide documentation

### Are there any issues that the IPMC or ASF Board need to be aware of?

Subscription of PPMC members to the @private mailing list should be
resolved. All PPMC members should now be subscribed to @private. If this is
not accurate, please advise.

### How has the community developed since the last report?

New committers have been added.

### How has the project developed since the last report?


### How would you assess the podling's maturity?
Please feel free to add your own commentary.

  - [ ] Initial setup
  - [x] Working towards first release
  - [x] Community building
  - [ ] Nearing graduation
  - [ ] Other:

### Date of last release:

  -XX-XX

### When were the last committers or PPMC members elected?

Two new committers were elected in April 2020.

### Have your mentors been helpful and responsive?
Are things falling through the cracks? If so, please list any
open issues that need to be addressed.

### Is the PPMC managing the podling's brand / trademarks?
Are 3rd parties respecting and correctly using the podlings
name and brand? If not what actions has the PPMC taken to
correct this? Has the VP, Brand approved the project name?

PPMC is not managing the podling's brand / trademarks.

### Signed-off-by:

  - [ ] (sdap) Jörn Rottmann
 Comments:
  - [ ] (sdap) Trevor Grant
 Comments:

### IPMC/Shepherd notes:

Re: Podling Sdap Report Reminder - May 2020

[Frank Greguska]

Can someone else put together the report this month? I've got too much on
my plate at the moment.

Thanks,

Frank

On Tue, Apr 28, 2020 at 6:32 PM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 20 May 2020.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, May 06).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/May2020
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: [Report] Please Review

[Frank Greguska]

Trevor,

It's on the Wiki now, feel free to sign off on it.

- Frank

On Tue, Jan 21, 2020 at 8:50 AM Frank Greguska  wrote:

> Nope, it's not on the Wiki yet. Lewis being on there may be a hold over
> from past reports, I don't think he's an official mentor.
>
> On Fri, Jan 17, 2020 at 6:32 AM Trevor Grant 
> wrote:
>
>> Looks good. I'd like to help working on 1st release. I know there have
>> been
>> issues with it- but I've released python software in the past- and I know
>> that's one of if not _the_ major hurdle.
>>
>> Also- congrats (I'm sorry? lol) to Lewis on becoming a Mentor. (I've been
>> traveling a lot the last two months and must have missed the email.)
>>
>> I just logged in to the wiki and didn't see this, so guessing not posted
>> yet?
>>
>> Let me know when it is and I'll sign.
>>
>> tg
>>
>>
>> On Thu, Jan 16, 2020 at 11:38 AM Frank Greguska  wrote:
>>
>> > Hello,
>> >
>> > Please review the report below. In particular please provide details for
>> > any presentations you've given on SDAP (@Joe Jacob? do you have
>> anything to
>> > add there?)
>> >
>> > SDAP
>> >
>> > SDAP is an integrated data analytic framework for Big Science problems.
>> >
>> > SDAP has been incubating since 2017-10-22.
>> >
>> > Three most important issues to address in the move towards graduation:
>> >
>> >  1. Make official SDAP (Incubating) Release
>> >  2. Improve committer participation
>> >  3. Improve/create user guide documentation
>> >
>> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> > aware of?
>> >
>> > No.
>> >
>> > How has the community developed since the last report?
>> >
>> > We are continuing to attract new committers.
>> > *Presentations?*
>> >
>> > How has the project developed since the last report?
>> >
>> > Development of a helm chart for use when deploying to kubernetes has
>> been
>> > opened as a PR.
>> > Further development work has continued and existing installations are
>> being
>> > maintained.
>> >
>> > How would you assess the podling's maturity?
>> >
>> > There are several deployments of SDAP actively being used and interest
>> is
>> > high. However, active participation from project members is low. First
>> > source release should be coming soon.
>> >
>> > Please feel free to add your own commentary.
>> >
>> >   [X] Initial setup
>> >   [X] Working towards first release
>> >   [X] Community building
>> >   [ ] Nearing graduation
>> >
>> > Date of last release:
>> >
>> >   -XX-XX
>> >
>> > When were the last committers or PPMC members elected?
>> >
>> > Maya Debellis was elected as a committer on 2019-02-08
>> >
>> > Have your mentors been helpful and responsive or are things falling
>> > through the cracks? In the latter case, please list any open issues
>> > that need to be addressed.
>> >
>> > Mentors are helpful and responsive.
>> >
>> > Signed-off-by:
>> >
>> >   [ ](sdap) Jörn Kottmann
>> >  Comments:
>> >   [ ](sdap) Trevor Grant
>> >  Comments:
>> >   [ ](sdap) Lewis John McGibbney
>> >  Comments:
>> >
>>
>

Re: Podling Sdap Report Reminder - February 2020

[Frank Greguska]

Yes, it's ready to go I just forgot to put it on the wiki. I'll do it now.

On Wed, Feb 5, 2020 at 2:34 PM Justin Mclean  wrote:

> Hi,
>
> This report is now past due, is anyone working on it? If you fail to
> submit a report you'll be expected to report next month.
>
> Thanks,
> Justin
>

Re: [Report] Please Review

[Frank Greguska]

Nope, it's not on the Wiki yet. Lewis being on there may be a hold over
from past reports, I don't think he's an official mentor.

On Fri, Jan 17, 2020 at 6:32 AM Trevor Grant 
wrote:

> Looks good. I'd like to help working on 1st release. I know there have been
> issues with it- but I've released python software in the past- and I know
> that's one of if not _the_ major hurdle.
>
> Also- congrats (I'm sorry? lol) to Lewis on becoming a Mentor. (I've been
> traveling a lot the last two months and must have missed the email.)
>
> I just logged in to the wiki and didn't see this, so guessing not posted
> yet?
>
> Let me know when it is and I'll sign.
>
> tg
>
>
> On Thu, Jan 16, 2020 at 11:38 AM Frank Greguska  wrote:
>
> > Hello,
> >
> > Please review the report below. In particular please provide details for
> > any presentations you've given on SDAP (@Joe Jacob? do you have anything
> to
> > add there?)
> >
> > SDAP
> >
> > SDAP is an integrated data analytic framework for Big Science problems.
> >
> > SDAP has been incubating since 2017-10-22.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >  1. Make official SDAP (Incubating) Release
> >  2. Improve committer participation
> >  3. Improve/create user guide documentation
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > No.
> >
> > How has the community developed since the last report?
> >
> > We are continuing to attract new committers.
> > *Presentations?*
> >
> > How has the project developed since the last report?
> >
> > Development of a helm chart for use when deploying to kubernetes has been
> > opened as a PR.
> > Further development work has continued and existing installations are
> being
> > maintained.
> >
> > How would you assess the podling's maturity?
> >
> > There are several deployments of SDAP actively being used and interest is
> > high. However, active participation from project members is low. First
> > source release should be coming soon.
> >
> > Please feel free to add your own commentary.
> >
> >   [X] Initial setup
> >   [X] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >
> > Date of last release:
> >
> >   -XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> > Maya Debellis was elected as a committer on 2019-02-08
> >
> > Have your mentors been helpful and responsive or are things falling
> > through the cracks? In the latter case, please list any open issues
> > that need to be addressed.
> >
> > Mentors are helpful and responsive.
> >
> > Signed-off-by:
> >
> >   [ ](sdap) Jörn Kottmann
> >  Comments:
> >   [ ](sdap) Trevor Grant
> >  Comments:
> >   [ ](sdap) Lewis John McGibbney
> >  Comments:
> >
>

[Report] Please Review

[Frank Greguska]

Hello,

Please review the report below. In particular please provide details for
any presentations you've given on SDAP (@Joe Jacob? do you have anything to
add there?)

SDAP

SDAP is an integrated data analytic framework for Big Science problems.

SDAP has been incubating since 2017-10-22.

Three most important issues to address in the move towards graduation:

 1. Make official SDAP (Incubating) Release
 2. Improve committer participation
 3. Improve/create user guide documentation

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No.

How has the community developed since the last report?

We are continuing to attract new committers.
*Presentations?*

How has the project developed since the last report?

Development of a helm chart for use when deploying to kubernetes has been
opened as a PR.
Further development work has continued and existing installations are being
maintained.

How would you assess the podling's maturity?

There are several deployments of SDAP actively being used and interest is
high. However, active participation from project members is low. First
source release should be coming soon.

Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?

Maya Debellis was elected as a committer on 2019-02-08

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Mentors are helpful and responsive.

Signed-off-by:

  [ ](sdap) Jörn Kottmann
 Comments:
  [ ](sdap) Trevor Grant
 Comments:
  [ ](sdap) Lewis John McGibbney
 Comments:

Re: Podling Sdap Report Reminder - November 2019

[Frank Greguska]

Does anyone have anything they'd like to add to the report? I have no
updates beyond what was suggested last month so I've updated the wiki for
this month with similar information.

Trevor - please review and sign off if you agree.

https://cwiki.apache.org/confluence/display/INCUBATOR/November2019#sdap

Thanks

On Sun, Nov 3, 2019 at 12:57 PM Justin Mclean  wrote:

> Hi,
>
> Just a friendly reminder that this is due in a couple of days and I don't
> see any progress on it. It's best to work on the report in the open before
> it is due.
>
> Thanks,
> Justin
>

Re: [REPORT] Please Review -- Due Today

[Frank Greguska]

Report has been submitted.

Thanks,

-Frank

On Wed, Oct 2, 2019 at 12:10 PM Trevor Grant 
wrote:

> Looks good to me, thanks for putting it together!
> No comments.
>
> On Wed, Oct 2, 2019 at 12:12 PM Frank Greguska  wrote:
>
> > Hello,
> >
> > Please review the Podling report for SDAP below:
> >
> > SDAP
> >
> > SDAP is an integrated data analytic framework for Big Science problems.
> >
> > SDAP has been incubating since 2017-10-22.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >  1. Make official SDAP (Incubating) Release
> >  2. Improve/create user guide documentation
> >  3. Improve committer participation
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > No.
> >
> > How has the community developed since the last report?
> >
> > Interest in the project has increased after presentation at ApacheCon
> >
> > How has the project developed since the last report?
> >
> > Frank Greguska attended ApacheCon NA and presented an overview of SDAP.
> >
> > Discussion about what is necessary to produce a release were beneficial
> and
> > the path forward is clear. Goal is to get a source release before the end
> > of the year.
> >
> > How would you assess the podling's maturity?
> >
> > There are several deployments of SDAP actively being used and interest is
> > high. However, active participation from project members is low. First
> > source release should be coming soon.
> >
> > Please feel free to add your own commentary.
> >
> >   [X] Initial setup
> >   [X] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >
> > Date of last release:
> >
> >   -XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> > Maya Debellis was elected as a committer on 2019-02-08
> >
> > Have your mentors been helpful and responsive or are things falling
> > through the cracks? In the latter case, please list any open issues
> > that need to be addressed.
> >
> > Yes, mentors have been helpful and responsive.
> >
> > Signed-off-by:
> >
> >   [ ](sdap) Jörn Kottmann
> >  Comments:
> >   [ ](sdap) Trevor Grant
> >  Comments:
> >   [ ](sdap) Lewis John McGibbney
> >  Comments:
> >
>

[REPORT] Please Review -- Due Today

[Frank Greguska]

Hello,

Please review the Podling report for SDAP below:

SDAP

SDAP is an integrated data analytic framework for Big Science problems.

SDAP has been incubating since 2017-10-22.

Three most important issues to address in the move towards graduation:

 1. Make official SDAP (Incubating) Release
 2. Improve/create user guide documentation
 3. Improve committer participation

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No.

How has the community developed since the last report?

Interest in the project has increased after presentation at ApacheCon

How has the project developed since the last report?

Frank Greguska attended ApacheCon NA and presented an overview of SDAP.

Discussion about what is necessary to produce a release were beneficial and
the path forward is clear. Goal is to get a source release before the end
of the year.

How would you assess the podling's maturity?

There are several deployments of SDAP actively being used and interest is
high. However, active participation from project members is low. First
source release should be coming soon.

Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?

Maya Debellis was elected as a committer on 2019-02-08

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Yes, mentors have been helpful and responsive.

Signed-off-by:

  [ ](sdap) Jörn Kottmann
 Comments:
  [ ](sdap) Trevor Grant
 Comments:
  [ ](sdap) Lewis John McGibbney
 Comments:

[jira] [Commented] (SDAP-149) Generate images directly from data

[Frank Greguska (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942976#comment-16942976
 ] 

Frank Greguska commented on SDAP-149:
-

[~antwaneone] There is still interest in getting it working but development of 
the feature has stalled. The two developers who were working on it have been 
focusing on other tasks so I can't say for sure if they will pick it back up. 
There are still two open pull requests (#48  and #52) that contain most of the 
functionality but need some work before they can be merged.

> Generate images directly from data
> --
>
> Key: SDAP-149
> URL: https://issues.apache.org/jira/browse/SDAP-149
> Project: Apache Science Data Analytics Platform
>  Issue Type: New Feature
>  Components: nexus
>    Reporter: Frank Greguska
>Assignee: Kevin M Gill
>Priority: Major
>
> Develop the capability to generate images directly from Nexus data.
> Create services:
> /map - Generate colorized map given a dataset, time, and bounding box
> /wmts - Emulate a simple WMTS service
>  - EPSG4326 (equirectangular) support initially
>  - In Memory & S3 caching support
>  - Support for static, pregenerated layers (tiles, MRF)
> /colortables - Lists supported color tables and their specifications as 
> CMC-compatible JSON
> /layers - Creates a CMC-compatible layer configuration file
> /thumbnail - Creates a small thumbnail for a layer



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

New Slack Channel

[Frank Greguska]

Hello,

After realizing the ASF has a Slack workspace (the-asf.slack.com), I've
created an #sdap channel over there for general discussion and questions.
It's a little lonely at the moment so feel free to join me!

Thanks,

Frank

Re: [REPORT] Please review

[Frank Greguska]

Last minute change of plans, I'll be giving the talk on SDAP tomorrow.
Looking forward to meeting you all.

- Frank

On Thu, Sep 5, 2019 at 6:25 AM Trevor Grant 
wrote:

> Great- I think its lunch after Brian's talk- let's all plan on meeting
> there then we can go somewhere and grab a bite.
>
> tg
>
>
> On Thu, Sep 5, 2019 at 1:20 AM Julian Feinauer <
> j.feina...@pragmaticminds.de>
> wrote:
>
> > Hi all,
> >
> > I joined the sdap list a while back when you were looking for Mentors and
> > help for the initial release.
> > Since then I became IPMC member so I could also offer you to support in
> > the release (and, if still needed) as mentor as well.
> >
> > I will also be at ACNA so would be nice to get in contact and chat there!
> >
> > Julian
> >
> > Am 04.09.19, 22:49 schrieb "Trevor Grant" :
> >
> > Cool.
> >
> > Brian's talk is at the same time I'm supposed to be in / moderating
> > the IoT
> > room, but I'm going to try to sneak away for an hour to see that.
> >
> > Justin will be speaking first up in the IoT track so we can catch up
> > with
> > him down and chat there about release requirements. There are other
> > non-Java Apache projects but I also I've heard what non-incubator
> > projects
> > are allow to grandfather in vs what incubator projects must do can
> > sometimes be different.
> >
> > Re: wiki- I don't know- I've just asked on the incubator slack
> > channel, but
> > haven't had a response yet.  Do what you think is best(?) if I hear
> > something on there I'll respond.
> >
> > tg
> >
> >
> >
> > On Wed, Sep 4, 2019 at 2:18 PM Frank Greguska 
> > wrote:
> >
> > > Thanks Trevor.
> > >
> > > Since there are no further comments and deadline for submission is
> > today, I
> > > am comfortable with submitting this report. Am I supposed to edit
> > the wiki
> > > directly?
> > >
> > > wrt your questions:
> > > I believe Brian Wilson is planning on attending ApacheCon and
> > talking about
> > > SDAP and is currently working on putting together materials.
> > > I think we're ok with a 1.0 release because this version of the
> code
> > is
> > > running in a few different places. The main problem with the
> release
> > at
> > > this point is understanding and complying with all the legal
> > requirements
> > > Apache has to call it a release. Also the fact that we're not
> > releasing all
> > > components to Maven (because they aren't Java components) makes
> > > understanding the Apache release requirements documentation
> > challenging.
> > > Most of our release artifacts are actually docker images but we
> were
> > told
> > > we cannot push unreleased docker images to dockerhub, and it's
> still
> > > unclear what the process is then for releasing artifacts that are
> > not JAR
> > > files. This is the discussion that was kicked off due to that
> issue:
> > >
> > >
> >
> https://lists.apache.org/thread.html/9cdc55e46a6fe23e1c0fcbdee6032f4949572311b0ded10cf6353be0@%3Cgeneral.incubator.apache.org%3E
> > > but I did not have time to follow it entirely. Re-reading it now it
> > seems
> > > that there is still a bit of an open question as to what we're
> > actually
> > > supposed to do.
> > >
> > > - Frank
> > >
> > > On Tue, Sep 3, 2019 at 8:47 AM Trevor Grant <
> > trevor.d.gr...@gmail.com>
> > > wrote:
> > >
> > > > This looks good- thanks Frank.
> > > >
> > > > Improving/creating docs is always hard.  It might be advisable to
> > find
> > > > someone who can work on this and give them committer rights (I'm
> > seeing
> > > one
> > > > hasn't been added since Feb, not horrible, but we want to keep
> > growing
> > > the
> > > > community).  Improved docs will lead to more user adoption, which
> > will
> > > > create more committer incentives and a pool of people to draw
> > from.  Sort
> > > > of a chicken and egg problem.
> > > >
> > > > Has there been any advocacy for the project? (e.g. are there any
> > talks
> > > > coming up at Apache

Re: [REPORT] Please review

[Frank Greguska]

FYI - I've edited the Wiki directly to add our report to it.

- Frank

On Thu, Sep 5, 2019 at 6:25 AM Trevor Grant 
wrote:

> Great- I think its lunch after Brian's talk- let's all plan on meeting
> there then we can go somewhere and grab a bite.
>
> tg
>
>
> On Thu, Sep 5, 2019 at 1:20 AM Julian Feinauer <
> j.feina...@pragmaticminds.de>
> wrote:
>
> > Hi all,
> >
> > I joined the sdap list a while back when you were looking for Mentors and
> > help for the initial release.
> > Since then I became IPMC member so I could also offer you to support in
> > the release (and, if still needed) as mentor as well.
> >
> > I will also be at ACNA so would be nice to get in contact and chat there!
> >
> > Julian
> >
> > Am 04.09.19, 22:49 schrieb "Trevor Grant" :
> >
> > Cool.
> >
> > Brian's talk is at the same time I'm supposed to be in / moderating
> > the IoT
> > room, but I'm going to try to sneak away for an hour to see that.
> >
> > Justin will be speaking first up in the IoT track so we can catch up
> > with
> > him down and chat there about release requirements. There are other
> > non-Java Apache projects but I also I've heard what non-incubator
> > projects
> > are allow to grandfather in vs what incubator projects must do can
> > sometimes be different.
> >
> > Re: wiki- I don't know- I've just asked on the incubator slack
> > channel, but
> > haven't had a response yet.  Do what you think is best(?) if I hear
> > something on there I'll respond.
> >
> > tg
> >
> >
> >
> > On Wed, Sep 4, 2019 at 2:18 PM Frank Greguska 
> > wrote:
> >
> > > Thanks Trevor.
> > >
> > > Since there are no further comments and deadline for submission is
> > today, I
> > > am comfortable with submitting this report. Am I supposed to edit
> > the wiki
> > > directly?
> > >
> > > wrt your questions:
> > > I believe Brian Wilson is planning on attending ApacheCon and
> > talking about
> > > SDAP and is currently working on putting together materials.
> > > I think we're ok with a 1.0 release because this version of the
> code
> > is
> > > running in a few different places. The main problem with the
> release
> > at
> > > this point is understanding and complying with all the legal
> > requirements
> > > Apache has to call it a release. Also the fact that we're not
> > releasing all
> > > components to Maven (because they aren't Java components) makes
> > > understanding the Apache release requirements documentation
> > challenging.
> > > Most of our release artifacts are actually docker images but we
> were
> > told
> > > we cannot push unreleased docker images to dockerhub, and it's
> still
> > > unclear what the process is then for releasing artifacts that are
> > not JAR
> > > files. This is the discussion that was kicked off due to that
> issue:
> > >
> > >
> >
> https://lists.apache.org/thread.html/9cdc55e46a6fe23e1c0fcbdee6032f4949572311b0ded10cf6353be0@%3Cgeneral.incubator.apache.org%3E
> > > but I did not have time to follow it entirely. Re-reading it now it
> > seems
> > > that there is still a bit of an open question as to what we're
> > actually
> > > supposed to do.
> > >
> > > - Frank
> > >
> > > On Tue, Sep 3, 2019 at 8:47 AM Trevor Grant <
> > trevor.d.gr...@gmail.com>
> > > wrote:
> > >
> > > > This looks good- thanks Frank.
> > > >
> > > > Improving/creating docs is always hard.  It might be advisable to
> > find
> > > > someone who can work on this and give them committer rights (I'm
> > seeing
> > > one
> > > > hasn't been added since Feb, not horrible, but we want to keep
> > growing
> > > the
> > > > community).  Improved docs will lead to more user adoption, which
> > will
> > > > create more committer incentives and a pool of people to draw
> > from.  Sort
> > > > of a chicken and egg problem.
> > > >
> > > > Has there been any advocacy for the project? (e.g. are there any
> > talks
> > > > coming up at Apache Con t

Re: [REPORT] Please review

[Frank Greguska]

Thanks Trevor.

Since there are no further comments and deadline for submission is today, I
am comfortable with submitting this report. Am I supposed to edit the wiki
directly?

wrt your questions:
I believe Brian Wilson is planning on attending ApacheCon and talking about
SDAP and is currently working on putting together materials.
I think we're ok with a 1.0 release because this version of the code is
running in a few different places. The main problem with the release at
this point is understanding and complying with all the legal requirements
Apache has to call it a release. Also the fact that we're not releasing all
components to Maven (because they aren't Java components) makes
understanding the Apache release requirements documentation challenging.
Most of our release artifacts are actually docker images but we were told
we cannot push unreleased docker images to dockerhub, and it's still
unclear what the process is then for releasing artifacts that are not JAR
files. This is the discussion that was kicked off due to that issue:
https://lists.apache.org/thread.html/9cdc55e46a6fe23e1c0fcbdee6032f4949572311b0ded10cf6353be0@%3Cgeneral.incubator.apache.org%3E
but I did not have time to follow it entirely. Re-reading it now it seems
that there is still a bit of an open question as to what we're actually
supposed to do.

- Frank

On Tue, Sep 3, 2019 at 8:47 AM Trevor Grant 
wrote:

> This looks good- thanks Frank.
>
> Improving/creating docs is always hard.  It might be advisable to find
> someone who can work on this and give them committer rights (I'm seeing one
> hasn't been added since Feb, not horrible, but we want to keep growing the
> community).  Improved docs will lead to more user adoption, which will
> create more committer incentives and a pool of people to draw from.  Sort
> of a chicken and egg problem.
>
> Has there been any advocacy for the project? (e.g. are there any talks
> coming up at Apache Con to get people interested? If not maybe a lightning
> talk? Also blog posts). Advocacy can kick start the previously mentioned
> feedback loop.
>
> I'm seeing that we're pushing for v1.0 - i know ASF wide that is the thing
> everyone is pushing for, however it's probably OK to do a v0.x release
> first just to get the ball moving (in fact probably should have a 0.x
> release first to check for bugs before pushing 1.0, just my two cents).
>
> This is looking good and I'm signing off, those are my comments.
>
>
> On Tue, Sep 3, 2019 at 10:07 AM Frank Greguska  wrote:
>
> > Hello,
> >
> > Please review the Podling report for SDAP below:
> >
> >
> > SDAP
> >
> > SDAP is an integrated data analytic framework for Big Science problems.
> >
> > SDAP has been incubating since 2017-10-22.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >  1. Make official SDAP (Incubating) Release
> >  2. Improve/create user guide documentation
> >  3. Improve committer participation
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > No.
> >
> > How has the community developed since the last report?
> >
> > We are continuing to attract new committers.
> >
> > How has the project developed since the last report?
> >
> > SDAP is still working towards its first release. Work towards a
> repeatable
> > build pipeline has been started.
> >
> > New functionality has been added to the Distributed Oceanographic Matchup
> > Service (DOMS) and Extensible Data Gateway Environment (EDGE) components
> > that allow for filtering in situ measurements by a standardized quality
> > flag.
> >
> > How would you assess the podling's maturity?
> >
> > There are several deployments of SDAP actively being used and interest is
> > high. However, active participation from project members is low. A push
> is
> > needed to cross the t's and dot the i's in regards to meeting the
> > requirements Apache has for releasing software so that we can claim a 1.0
> > version of SDAP.
> >
> > Please feel free to add your own commentary.
> >
> >   [X] Initial setup
> >   [X] Working towards first release
> >   [X] Community building
> >   [ ] Nearing graduation
> >
> > Date of last release:
> >
> >   -XX-XX
> >
> > When were the last committers or PPMC members elected?
> >
> > Maya Debellis was elected as a committer on 2019-02-08
> >
> > Have your mentors been helpful and responsive or are things falling
> > through the cracks? In the latter case, please list any open issues
> > that need to be addressed.
> >
> > Yes, mentors have been helpful and responsive.
> >
> > Signed-off-by:
> >
> >   [ ](sdap) Jörn Kottmann
> >  Comments:
> >   [ ](sdap) Trevor Grant
> >  Comments:
> >   [ ](sdap) Lewis John McGibbney
> >  Comments:
> >
>

[REPORT] Please review

[Frank Greguska]

Hello,

Please review the Podling report for SDAP below:


SDAP

SDAP is an integrated data analytic framework for Big Science problems.

SDAP has been incubating since 2017-10-22.

Three most important issues to address in the move towards graduation:

 1. Make official SDAP (Incubating) Release
 2. Improve/create user guide documentation
 3. Improve committer participation

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No.

How has the community developed since the last report?

We are continuing to attract new committers.

How has the project developed since the last report?

SDAP is still working towards its first release. Work towards a repeatable
build pipeline has been started.

New functionality has been added to the Distributed Oceanographic Matchup
Service (DOMS) and Extensible Data Gateway Environment (EDGE) components
that allow for filtering in situ measurements by a standardized quality
flag.

How would you assess the podling's maturity?

There are several deployments of SDAP actively being used and interest is
high. However, active participation from project members is low. A push is
needed to cross the t's and dot the i's in regards to meeting the
requirements Apache has for releasing software so that we can claim a 1.0
version of SDAP.

Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?

Maya Debellis was elected as a committer on 2019-02-08

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Yes, mentors have been helpful and responsive.

Signed-off-by:

  [ ](sdap) Jörn Kottmann
 Comments:
  [ ](sdap) Trevor Grant
 Comments:
  [ ](sdap) Lewis John McGibbney
 Comments:

[jira] [Updated] (SDAP-208) ICOADS Plugin Misconfiguration

[Frank Greguska (Jira)]

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

Frank Greguska updated SDAP-208:

Resolution: Fixed
Status: Done  (was: To Do)

> ICOADS Plugin Misconfiguration
> --
>
> Key: SDAP-208
> URL: https://issues.apache.org/jira/browse/SDAP-208
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: edge
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> ICOADS plugin causing 400 error when trying to query using qualityFlag 
> parameter



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (SDAP-208) ICOADS Plugin Misconfiguration

[Frank Greguska (Jira)]

Frank Greguska created SDAP-208:
---

 Summary: ICOADS Plugin Misconfiguration
 Key: SDAP-208
 URL: https://issues.apache.org/jira/browse/SDAP-208
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
  Components: edge
Reporter: Frank Greguska
Assignee: Frank Greguska


ICOADS plugin causing 400 error when trying to query using qualityFlag parameter



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (SDAP-144) DOMS API to support filtering by quality

[Frank Greguska (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913531#comment-16913531
 ] 

Frank Greguska commented on SDAP-144:
-

Note: if upgrading an existing cluster, the following commands must be run on 
the cassandra tables in the 'doms' keyspace:

 

ALTER TABLE doms.doms_params ADD quality_flag int;

ALTER TABLE doms.doms_data ADD wind_speed_quality int;
ALTER TABLE doms.doms_data ADD wind_component_quality int;
ALTER TABLE doms.doms_data ADD sst_quality int;
ALTER TABLE doms.doms_data ADD sss_quality int;

> DOMS API to support filtering by quality
> 
>
> Key: SDAP-144
> URL: https://issues.apache.org/jira/browse/SDAP-144
> Project: Apache Science Data Analytics Platform
>  Issue Type: New Feature
>  Components: doms, nexus
>    Reporter: Frank Greguska
>Assignee: Elizabeth Yam
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The matchup algorithm can be modified to utilize quality filtering of in situ 
> data.
>  
> This method is a good place to start because it is used to query for insitu 
> data using EDGE.
> https://github.com/apache/incubator-sdap-nexus/blob/725ed5a7bb7db96662e5351f8cd373f4c54862d6/analysis/webservice/algorithms_spark/Matchup.py#L650



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Updated] (SDAP-207) GDAL Import error

[Frank Greguska (Jira)]

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

Frank Greguska updated SDAP-207:

Resolution: Fixed
Status: Done  (was: To Do)

> GDAL Import error
> -
>
> Key: SDAP-207
> URL: https://issues.apache.org/jira/browse/SDAP-207
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Getting an import error from GDAL at runtime:
>  
> Traceback (most recent call last):
>   File "/usr/local/anaconda2/lib/python2.7/runpy.py", line 174, in 
> _run_module_as_main
>     "__main__", fname, loader, pkg_name)
>   File "/usr/local/anaconda2/lib/python2.7/runpy.py", line 72, in _run_code
>     exec code in run_globals
>   File "/tmp/incubator-sdap-nexus/analysis/webservice/webapp.py", line 233, 
> in 
>     importlib.import_module(moduleDir)
>   File "/usr/local/anaconda2/lib/python2.7/importlib/__init__.py", line 37, 
> in import_module
>     __import__(name)
>   File "webservice/algorithms/doms/__init__.py", line 17, in 
>     import BaseDomsHandler
>   File "webservice/algorithms/doms/BaseDomsHandler.py", line 40, in 
>     import gdal
>   File "/usr/local/anaconda2/lib/python2.7/site-packages/gdal.py", line 2, in 
> 
>     from osgeo.gdal import deprecation_warn
>   File "/usr/local/anaconda2/lib/python2.7/site-packages/osgeo/__init__.py", 
> line 21, in 
>     _gdal = swig_import_helper()
>   File "/usr/local/anaconda2/lib/python2.7/site-packages/osgeo/__init__.py", 
> line 17, in swig_import_helper
>     _mod = imp.load_module('_gdal', fp, pathname, description)
> ImportError: libpoppler.so.71: cannot open shared object file: No such file 
> or directory



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (SDAP-207) GDAL Import error

[Frank Greguska (Jira)]

Frank Greguska created SDAP-207:
---

 Summary: GDAL Import error
 Key: SDAP-207
 URL: https://issues.apache.org/jira/browse/SDAP-207
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
  Components: nexus
Reporter: Frank Greguska
Assignee: Frank Greguska


Getting an import error from GDAL at runtime:

 

Traceback (most recent call last):

  File "/usr/local/anaconda2/lib/python2.7/runpy.py", line 174, in 
_run_module_as_main

    "__main__", fname, loader, pkg_name)

  File "/usr/local/anaconda2/lib/python2.7/runpy.py", line 72, in _run_code

    exec code in run_globals

  File "/tmp/incubator-sdap-nexus/analysis/webservice/webapp.py", line 233, in 


    importlib.import_module(moduleDir)

  File "/usr/local/anaconda2/lib/python2.7/importlib/__init__.py", line 37, in 
import_module

    __import__(name)

  File "webservice/algorithms/doms/__init__.py", line 17, in 

    import BaseDomsHandler

  File "webservice/algorithms/doms/BaseDomsHandler.py", line 40, in 

    import gdal

  File "/usr/local/anaconda2/lib/python2.7/site-packages/gdal.py", line 2, in 


    from osgeo.gdal import deprecation_warn

  File "/usr/local/anaconda2/lib/python2.7/site-packages/osgeo/__init__.py", 
line 21, in 

    _gdal = swig_import_helper()

  File "/usr/local/anaconda2/lib/python2.7/site-packages/osgeo/__init__.py", 
line 17, in swig_import_helper

    _mod = imp.load_module('_gdal', fp, pathname, description)

ImportError: libpoppler.so.71: cannot open shared object file: No such file or 
directory



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Updated] (SDAP-203) Update docker build files

[Frank Greguska (Jira)]

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

Frank Greguska updated SDAP-203:

Resolution: Fixed
Status: Done  (was: To Do)

> Update docker build files
> -
>
> Key: SDAP-203
> URL: https://issues.apache.org/jira/browse/SDAP-203
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Docker build should accept Java RPM URL as a build time argument.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Commented] (SDAP-203) Update docker build files

[Frank Greguska (Jira)]

[ 
https://issues.apache.org/jira/browse/SDAP-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16911762#comment-16911762
 ] 

Frank Greguska commented on SDAP-203:
-

Can no longer download Oracle JDK 8 without logging in. Switching to OpenJDK 8

> Update docker build files
> -
>
> Key: SDAP-203
> URL: https://issues.apache.org/jira/browse/SDAP-203
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
>
> Docker build should accept Java RPM URL as a build time argument.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Updated] (SDAP-203) Update docker build files

[Frank Greguska (Jira)]

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

Frank Greguska updated SDAP-203:

Summary: Update docker build files  (was: Make Java RPM URL a build Arg)

> Update docker build files
> -
>
> Key: SDAP-203
> URL: https://issues.apache.org/jira/browse/SDAP-203
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
>
> Docker build should accept Java RPM URL as a build time argument.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (SDAP-203) Make Java RPM URL a build Arg

[Frank Greguska (Jira)]

Frank Greguska created SDAP-203:
---

 Summary: Make Java RPM URL a build Arg
 Key: SDAP-203
 URL: https://issues.apache.org/jira/browse/SDAP-203
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
  Components: nexus
Reporter: Frank Greguska
Assignee: Frank Greguska


Docker build should accept Java RPM URL as a build time argument.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

[jira] [Created] (SDAP-202) Edge Doesn't filter based on qualitFlag parameter

[Frank Greguska (Jira)]

Frank Greguska created SDAP-202:
---

 Summary: Edge Doesn't filter based on qualitFlag parameter
 Key: SDAP-202
 URL: https://issues.apache.org/jira/browse/SDAP-202
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
  Components: edge
Reporter: Frank Greguska
Assignee: Elizabeth Yam


EDGE does not seem to be filtering results according to the qualityFlag query 
parameter:

[http://doms.coaps.fsu.edu:8890/ws/search/samos?qualityFlag=1=sst]

Returns the same results as

[http://doms.coaps.fsu.edu:8890/ws/search/samos|http://doms.coaps.fsu.edu:8890/ws/search/samos?qualityFlag=1=sst]

 

I think it is because qualityFlag is not configured as a parameter for the 
plugin:

[https://github.com/apache/incubator-sdap-edge/blob/master/src/main/python/plugins/samos/json/plugin.conf#L6]

Same for icoads:

[https://github.com/apache/incubator-sdap-edge/blob/master/src/main/python/plugins/icoads/json/plugin.conf#L6]



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Re: Install Instructions

[Frank Greguska]

Hi Trevor,

Our most comprehensive install doc is this one:

https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html

But the doc does need to be updated since we're not allowed to publish
(non-released) images to the "sdap" dockerhub. If you email me privately I
can share a different unofficial docker organization that is not in any way
related to Apache that happens to be building non-released versions of SDAP
NEXUS for general use.

Also, please keep in mind, this only covers the NEXUS component of the SDAP
project. The search (mudrod) and edge components are not documented much
beyond what can be found in their respective README files.

https://github.com/apache/incubator-sdap-edge
https://github.com/apache/incubator-sdap-mudrod

Thanks,

Frank





On Wed, Jul 24, 2019 at 4:20 AM Trevor Grant 
wrote:

> Hey all,
>
> If I want to install/use SDAP where is the 'getting started' ?
>
> I've looked and not found any docs, assuming they don't exist- I'd like to
> write them.
>

[jira] [Updated] (SDAP-196) Account for time when finding closest match

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-196:

Resolution: Fixed
Status: Done  (was: In Progress)

> Account for time when finding closest match
> ---
>
> Key: SDAP-196
> URL: https://issues.apache.org/jira/browse/SDAP-196
> Project: Apache Science Data Analytics Platform
>  Issue Type: Improvement
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> [https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms_spark/Matchup.py#L467-L484]
>  
> As you can see, we do only take into account spatial distance, not time 
> distance. This would be where we need to modify the code to also take into 
> account time distance when trying to find the closest match.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Updated] (SDAP-196) Account for time when finding closest match

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-196:

Status: In Progress  (was: To Do)

> Account for time when finding closest match
> ---
>
> Key: SDAP-196
> URL: https://issues.apache.org/jira/browse/SDAP-196
> Project: Apache Science Data Analytics Platform
>  Issue Type: Improvement
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
>
> [https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms_spark/Matchup.py#L467-L484]
>  
> As you can see, we do only take into account spatial distance, not time 
> distance. This would be where we need to modify the code to also take into 
> account time distance when trying to find the closest match.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (SDAP-196) Account for time when finding closest match

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-196:
---

 Summary: Account for time when finding closest match
 Key: SDAP-196
 URL: https://issues.apache.org/jira/browse/SDAP-196
 Project: Apache Science Data Analytics Platform
  Issue Type: Improvement
  Components: nexus
Reporter: Frank Greguska
Assignee: Frank Greguska


[https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms_spark/Matchup.py#L467-L484]

 

As you can see, we do only take into account spatial distance, not time 
distance. This would be where we need to modify the code to also take into 
account time distance when trying to find the closest match.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Updated] (SDAP-144) DOMS API to support filtering by quality

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-144:

Summary: DOMS API to support filtering by quality  (was: DOMS to support 
filtering by quality)

> DOMS API to support filtering by quality
> 
>
> Key: SDAP-144
> URL: https://issues.apache.org/jira/browse/SDAP-144
> Project: Apache Science Data Analytics Platform
>  Issue Type: New Feature
>  Components: doms, nexus
>    Reporter: Frank Greguska
>Assignee: Elizabeth Yam
>Priority: Major
>
> The matchup algorithm can be modified to utilize quality filtering of in situ 
> data.
>  
> This method is a good place to start because it is used to query for insitu 
> data using EDGE.
> https://github.com/apache/incubator-sdap-nexus/blob/725ed5a7bb7db96662e5351f8cd373f4c54862d6/analysis/webservice/algorithms_spark/Matchup.py#L650



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

[jira] [Commented] (SDAP-144) DOMS to support filtering by quality

[Frank Greguska (JIRA)]

[ 
https://issues.apache.org/jira/browse/SDAP-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873473#comment-16873473
 ] 

Frank Greguska commented on SDAP-144:
-

This class 
([https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms_spark/Matchup.py#L323])
 is used as a generic “DomsPoint” that can represent either an in situ or a 
satellite measurement. The “from_edge_point” 
[https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms_spark/Matchup.py#L398]
 function is responsible for translating from a document from edge into a 
DomsPoint.

 

This function then goes from DomsPoint to dict: 
[https://github.com/apache/incubator-sdap-nexus/blob/master/analysis/webservice/algorithms_spark/Matchup.py#L301]

Which is what eventually gets passed to the storage module: 
[https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms/doms/ResultsStorage.py#L65]

Additionally, the doms data table will have to have a new column added to it in 
order to store the quality flag 
[https://github.com/apache/incubator-sdap-nexus/blob/584b2f5b91300fd0952cb4de32068a008c551936/analysis/webservice/algorithms/doms/DomsInitialization.py#L111]

 

 

All of these will need to be updated to keep track of the quality flags in 
order to be able to put them in the output file.

> DOMS to support filtering by quality
> 
>
> Key: SDAP-144
> URL: https://issues.apache.org/jira/browse/SDAP-144
> Project: Apache Science Data Analytics Platform
>  Issue Type: New Feature
>  Components: doms, nexus
>    Reporter: Frank Greguska
>Assignee: Elizabeth Yam
>Priority: Major
>
> The matchup algorithm can be modified to utilize quality filtering of in situ 
> data.
>  
> This method is a good place to start because it is used to query for insitu 
> data using EDGE.
> https://github.com/apache/incubator-sdap-nexus/blob/725ed5a7bb7db96662e5351f8cd373f4c54862d6/analysis/webservice/algorithms_spark/Matchup.py#L650



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

Re: [REPORT] Please review

[Frank Greguska]

Got it. Thanks for clarifying.

- Frank

On Tue, May 7, 2019 at 3:18 AM Julian Feinauer 
wrote:

> Hi Frank,
>
> I can jump in here a bit.
> This time, the wiki was moved to confluence, so the new place is
> https://cwiki.apache.org/confluence/display/INCUBATOR/May2019.
> As it did not work that flawless with some permissions on the confluence
> site Justin posted our Report for the Edgent project there, and I saw he
> did the same with your version from the List.
>
> So I think he meant that no one "answered" to your Review request, and
> thus took that as "final" version.
>
> Julian
>
> Am 06.05.19, 18:18 schrieb "Frank Greguska" :
>
> Justin -
>
> Can you explain how this is supposed to work? The "Podling Report
> Reminder"
> email indicates we are supposed to submit the report by adding it to
> the
> wiki page: https://cwiki.apache.org/confluence/INCUBATOR/May2019 but
> that
> page did not and still does not exist so I just sent it to the mailing
> list. The email also indicates that mentors are supposed to sign off
> on the
> report on the wiki page. So I assume as long as the report is on the
> wiki
> page 2 weeks prior to the meeting it gives everyone enough time to
> review.
> Is that correct? Who do we contact if the wiki page is not available 2
> weeks prior to the board meeting?
>
> Thanks,
>
> Frank
>
> On Sat, May 4, 2019 at 7:44 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > This is now several days passed it due date so I've added it the teh
> > incubator report.
> >
> > Thanks,
> > Justin
> >
>
>
>

Re: [REPORT] Please review

[Frank Greguska]

Justin -

Can you explain how this is supposed to work? The "Podling Report Reminder"
email indicates we are supposed to submit the report by adding it to the
wiki page: https://cwiki.apache.org/confluence/INCUBATOR/May2019 but that
page did not and still does not exist so I just sent it to the mailing
list. The email also indicates that mentors are supposed to sign off on the
report on the wiki page. So I assume as long as the report is on the wiki
page 2 weeks prior to the meeting it gives everyone enough time to review.
Is that correct? Who do we contact if the wiki page is not available 2
weeks prior to the board meeting?

Thanks,

Frank

On Sat, May 4, 2019 at 7:44 PM Justin Mclean  wrote:

> Hi,
>
> This is now several days passed it due date so I've added it the teh
> incubator report.
>
> Thanks,
> Justin
>

[REPORT] Please review

[Frank Greguska]

Hello,

Please review the Podling report for SDAP below:


SDAP

SDAP is an integrated data analytic framework for Big Science problems.

SDAP has been incubating since 2017-10-22.

Three most important issues to address in the move towards graduation:

 1. Make official SDAP (Incubating) Release
 2. Improve/create user guide documentation
 3. Improve committer participation

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No.

How has the community developed since the last report?

Committership has been accepted by a community member. SDAP was presented
at a Data Science Workshop @ JPL

How has the project developed since the last report?

SDAP is still working towards its first release. Mentors have provided some
suggestions that will be taken into consideration for the Java parts of the
project, but the python release process also needs to be better understood.

A new tool has been published that helps with reading the output produced
from the Matchup algorithm.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [X] Initial setup
  [X] Working towards first release
  [X] Community building
  [ ] Nearing graduation

Date of last release:

  -XX-XX

When were the last committers or PPMC members elected?

Maya Debellis was elected as a committer on 2019-02-08

Have your mentors been helpful and responsive or are things falling
through the cracks? In the latter case, please list any open issues
that need to be addressed.

Yes, mentors have been helpful and responsive.

Signed-off-by:

  [ ](sdap) Jörn Kottmann
 Comments:
  [ ](sdap) Trevor Grant
 Comments:
  [X](sdap) Lewis John McGibbney
 Comments:

[jira] [Created] (SDAP-193) Spark job continues after connection close

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-193:
---

 Summary: Spark job continues after connection close
 Key: SDAP-193
 URL: https://issues.apache.org/jira/browse/SDAP-193
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
  Components: nexus
Reporter: Frank Greguska


When the client closes a connection, the spark job continues to execute.

The Spark job should be killed when the client closes the connection because 
even if the job finishes, it is impossible to get the results back to the 
client anymore.



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

[jira] [Updated] (SDAP-191) Remove Access-Control-Allow-Origin :*

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-191:

Resolution: Fixed
Status: Done  (was: To Do)

> Remove Access-Control-Allow-Origin :*
> -
>
> Key: SDAP-191
> URL: https://issues.apache.org/jira/browse/SDAP-191
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Critical
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The web server should not be setting Access-Control-Allow-Origin: *
>  
> https://github.com/apache/incubator-sdap-nexus/blob/be19c1d567301b09269e851cc5b5af55fea02c5d/analysis/webservice/webapp.py#L59



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

Re: ... / Let me introduce myself

[Frank Greguska]

Welcome Julian, glad to have you on board.

On Mon, Apr 1, 2019 at 8:25 AM Lewis John McGibbney 
wrote:

> Hi Julian,
> Sounds great.
> Is there any particular part of SDAP that your interested in?
> The community is working towards its first incubating release so hopefully
> you will be able to try it out soon. Reviewing the release candidate when
> it is prepared would be a real big help.
> Lewis
>
> On 2019/03/29 08:49:40, Julian Feinauer 
> wrote:
> > Hi all,
> >
> > please excuse this mail.. this was some miscommunication between my mail
> client and me during subscription to the list.
> > So let me introduce myself for short… my name is Julian and I am
> mathematician (did my PhD in stochastics).
> > I live in germany and am the founder of a StartUp where we do a lot of
> data analytics, especially on “industrial data” and stream processing.
> > I’m involved in other incubating projects in this area as well, namely
> PLC4X, Edgent and IoTDB (and I do minor contributions to other projects).
> > Thus, I am very interested in what you guys do here and can hopefully
> contribute a bit : )
> >
> > Julian
> >
> > On 2019/03/29 08:26:45, Julian Feinauer  > wrote:
> > >
> > >
> >
>

[jira] [Created] (SDAP-184) Entrypoint to use named instead of positional args

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-184:
---

 Summary: Entrypoint to use named instead of positional args
 Key: SDAP-184
 URL: https://issues.apache.org/jira/browse/SDAP-184
 Project: Apache Science Data Analytics Platform
  Issue Type: Improvement
  Components: nexus
Reporter: Frank Greguska


The entrypoint script should use named arguments instead of positional 
arguments to download the configuration and the granule from s3.

 

[https://github.com/apache/incubator-sdap-ningester/blob/master/docker/aws/entrypoint.sh#L25]

[https://github.com/apache/incubator-sdap-ningester/blob/master/docker/aws/entrypoint.sh#L28]

 



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

[jira] [Created] (SDAP-183) Remove query by polygon from SolrProxy

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-183:
---

 Summary: Remove query by polygon from SolrProxy
 Key: SDAP-183
 URL: https://issues.apache.org/jira/browse/SDAP-183
 Project: Apache Science Data Analytics Platform
  Issue Type: Improvement
  Components: nexus
Reporter: Frank Greguska


We've determined that using Intersects(POLYGON) is too expensive for Solr. 
Instead, SolrProxy should always query using [lon,lat TO lon,lat] and the 
masking to polygon should happen in the nexustiles service.



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

[jira] [Updated] (SDAP-183) Remove query by polygon from SolrProxy

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-183:

Resolution: Duplicate
Status: Done  (was: To Do)

> Remove query by polygon from SolrProxy
> --
>
> Key: SDAP-183
> URL: https://issues.apache.org/jira/browse/SDAP-183
> Project: Apache Science Data Analytics Platform
>  Issue Type: Improvement
>  Components: nexus
>    Reporter: Frank Greguska
>Priority: Minor
>
> We've determined that using Intersects(POLYGON) is too expensive for Solr. 
> Instead, SolrProxy should always query using [lon,lat TO lon,lat] and the 
> masking to polygon should happen in the nexustiles service.



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

[jira] [Updated] (SDAP-167) Make shard key configureable

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-167:

Description: 
Currently the dataset name is used as the prefix for the compositeId used for 
routing

[https://lucene.apache.org/solr/guide/7_4/shards-and-indexing-data-in-solrcloud.html#document-routing]

This is done in the SolrStore writer

[https://github.com/apache/incubator-sdap-ningester/blob/12e60f2c0f11be33026808d98623d5cbe136179d/src/main/java/org/apache/sdap/ningester/writer/SolrStore.java#L94]
 

 

This might not be appropriate for every case (for example, if only one dataset 
is ever going to be ingested). It would be nice to make this configureable.

 

Also need to expose the key as a configuration option for SolrProxy in 
data-access during query time (also, 'shard_keys' needs to be changed to 
'_route_').

https://github.com/apache/incubator-sdap-nexus/blob/master/data-access/nexustiles/dao/SolrProxy.pyx#L631

  was:
Currently the dataset name is used as the prefix for the compositeId used for 
routing

[https://lucene.apache.org/solr/guide/7_4/shards-and-indexing-data-in-solrcloud.html#document-routing]

This is done in the SolrStore writer

[https://github.com/apache/incubator-sdap-ningester/blob/12e60f2c0f11be33026808d98623d5cbe136179d/src/main/java/org/apache/sdap/ningester/writer/SolrStore.java#L94]
 

 

This might not be appropriate for every case (for example, if only one dataset 
is ever going to be ingested). It would be nice to make this configureable.


> Make shard key configureable
> 
>
> Key: SDAP-167
> URL: https://issues.apache.org/jira/browse/SDAP-167
> Project: Apache Science Data Analytics Platform
>  Issue Type: Improvement
>  Components: nexus
>    Reporter: Frank Greguska
>Priority: Minor
> Fix For: 1.1
>
>
> Currently the dataset name is used as the prefix for the compositeId used for 
> routing
> [https://lucene.apache.org/solr/guide/7_4/shards-and-indexing-data-in-solrcloud.html#document-routing]
> This is done in the SolrStore writer
> [https://github.com/apache/incubator-sdap-ningester/blob/12e60f2c0f11be33026808d98623d5cbe136179d/src/main/java/org/apache/sdap/ningester/writer/SolrStore.java#L94]
>  
>  
> This might not be appropriate for every case (for example, if only one 
> dataset is ever going to be ingested). It would be nice to make this 
> configureable.
>  
> Also need to expose the key as a configuration option for SolrProxy in 
> data-access during query time (also, 'shard_keys' needs to be changed to 
> '_route_').
> https://github.com/apache/incubator-sdap-nexus/blob/master/data-access/nexustiles/dao/SolrProxy.pyx#L631



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

Re: [REPORT] Please review

[Frank Greguska]

Thanks Lewis.

Our mentors have answered any questions that have been asked.

- Frank

On Tue, Feb 5, 2019 at 7:51 PM lewis john mcgibbney 
wrote:

> Hi Folks,
> I provided a report from us to the IPMC -
> https://wiki.apache.org/incubator/February2019
>
> @mentors please review and approve
>
> @dev, can someone please answer the question "...Have your mentors been
> helpful and responsive or are things falling through the cracks? In the
> latter case, please list any open issues that need to be addressed."
>
> Thanks
>
>
>
> SDAP
>
> SDAP is an integrated data analytic center for Big Science problems.
>
> SDAP has been incubating since 2017-10-22.
>
> Three most important issues to address in the move towards graduation:
>
>  1. Make official SDAP (Incubating) Release
>  2. Improve/create user guide documentation
>  3. Grow Community
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> A member of the SDAP podling stepped up to the release manager role which
> is great. It shows the the podling is maturing.
> Unfortunately, the release candidate which was produced was not in
> compliance with the ASF release policy, thankfully Justin highlighted
> this and we are in the process of rolling the RC back. Lewis (SDAP
> champion)
> and the release manager are working to resolve this and get the first
> incubating release candidate finished.
>
> How has the community developed since the last report?
>
> Two VOTE's have been made over on private@sdap regarding extending
> PPMC and Committership to two community contributors. This is very
> positive.
>
> How has the project developed since the last report?
>
> SDAP is on the verge of it's first release. With some persistence
> the podling will have a release candidate for community VOTE soon.
>
> How would you assess the podling's maturity?
> Please feel free to add your own commentary.
>
>   [X] Initial setup
>   [X] Working towards first release
>   [X] Community building
>   [ ] Nearing graduation
>   [X] Other: One the release management process is documented we will be
>pushing for graduation.
>
> Date of last release:
>
>   -XX-XX
>
> When were the last committers or PPMC members elected?
>
> Kevin M Gill was elected on 2018-03-05
>
> Have your mentors been helpful and responsive or are things falling
> through the cracks? In the latter case, please list any open issues
> that need to be addressed.
>
> Signed-off-by:
>
>   [ ](sdap) Jörn Rottmann
>  Comments:
>   [ ](sdap) Suneel Marthi
>  Comments:
>   [X](sdap) Lewis John McGibbney
>  Comments:
>
> IPMC/Shepherd notes:
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>

NEXUS Release Candidate

[Frank Greguska]

Hello,

I have cut a release candidate for version 1.0.0 for the following SDAP
projects:

https://github.com/apache/incubator-sdap-nexus/releases/tag/v1.0.0-rc1
https://github.com/apache/incubator-sdap-ningesterpy/releases/tag/v1.0.0-rc1
https://github.com/apache/incubator-sdap-ningester/releases/tag/v1.0.0-rc1
https://github.com/apache/incubator-sdap-nexusproto/releases/tag/v1.0.0-rc1

This includes the following docker images on dockerhub in the sdap
organization (https://cloud.docker.com/u/sdap/repository/list):

- sdap/cassandra:1.0.0-rc1
- sdap/solr:1.0.0-rc1
- sdap/solr-singlenode:1.0.0-rc1
- sdap/solr-cloud:1.0.0-rc1
- sdap/solr-cloud-init:1.0.0-rc1
- sdap/spark-mesos-base:1.0.0-rc1
- sdap/spark-mesos-master:1.0.0-rc1
- sdap/spark-mesos-agent:1.0.0-rc1
- sdap/nexus-webapp:mesos.1.0.0-rc1
- sdap/nexus-webapp:standalone.1.0.0-rc1
- sdap/ningester:1.0.0-rc1

While I believe we are still short of some of the Apache requirements
needed for a release, this release candidate is functional and is targeted
for deployment to test infrastructure.

Documentation (which is admittedly still sparse) can be found here:
https://incubator-sdap-nexus.readthedocs.io/en/v1.0.0-rc1/

Thanks,

Frank

[jira] [Created] (SDAP-175) computespeeddirfromuv should have the option of replacing tile data

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-175:
---

 Summary: computespeeddirfromuv should have the option of replacing 
tile data
 Key: SDAP-175
 URL: https://issues.apache.org/jira/browse/SDAP-175
 Project: Apache Science Data Analytics Platform
  Issue Type: Improvement
  Components: nexus
Reporter: Frank Greguska
Assignee: Elizabeth Yam


The processor computespeeddirfromuv

[https://github.com/apache/incubator-sdap-ningesterpy/blob/master/sdap/processors/computespeeddirfromuv.py]

Should be able to replace the current tile data with either the computed 
wind_speed or wind_dir if desired.



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

[jira] [Assigned] (SDAP-172) TimeAvgMapSpark includes mean of 0 elements

[Frank Greguska (JIRA)]

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

Frank Greguska reassigned SDAP-172:
---

Assignee: Joseph Jacob

> TimeAvgMapSpark includes mean of 0 elements
> ---
>
> Key: SDAP-172
> URL: https://issues.apache.org/jira/browse/SDAP-172
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: nexus
>    Reporter: Frank Greguska
>Assignee: Joseph Jacob
>Priority: Minor
>
> Some results being returned from TimeAvgMapSpark indicate a count of 0 (a 
> mean was taken over 0 numbers). This results in reporting a mean of 0.
> Example query:
> timeAvgMapSpark?ds=MUR-JPL-L4-GLOB-v4.1=-134.9925=-140.0025=5.0025=10.0125=1538352000=1540944000
> In the results, search for "cnt": 0,
> Need to investigate why no measurements went into these means. These results 
> should be eliminated.
> May be related to SDAP-116



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

[jira] [Assigned] (SDAP-144) DOMS to support filtering by quality

[Frank Greguska (JIRA)]

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

Frank Greguska reassigned SDAP-144:
---

Assignee: Elizabeth Yam

> DOMS to support filtering by quality
> 
>
> Key: SDAP-144
> URL: https://issues.apache.org/jira/browse/SDAP-144
> Project: Apache Science Data Analytics Platform
>  Issue Type: New Feature
>  Components: doms, nexus
>    Reporter: Frank Greguska
>Assignee: Elizabeth Yam
>Priority: Major
>
> The matchup algorithm can be modified to utilize quality filtering of in situ 
> data.
>  
> This method is a good place to start because it is used to query for insitu 
> data using EDGE.
> https://github.com/apache/incubator-sdap-nexus/blob/725ed5a7bb7db96662e5351f8cd373f4c54862d6/analysis/webservice/algorithms_spark/Matchup.py#L650



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

[jira] [Updated] (SDAP-166) Update SolrCloud Docker Image

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-166:

Resolution: Fixed
Status: Done  (was: In Progress)

> Update SolrCloud Docker Image
> -
>
> Key: SDAP-166
> URL: https://issues.apache.org/jira/browse/SDAP-166
> Project: Apache Science Data Analytics Platform
>  Issue Type: Improvement
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
> Fix For: 1.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We need an updated SolrCloud image that will allow us to launch an instance 
> of SolrCloud.



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

[jira] [Created] (SDAP-172) TimeAvgMapSpark includes mean of 0 elements

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-172:
---

 Summary: TimeAvgMapSpark includes mean of 0 elements
 Key: SDAP-172
 URL: https://issues.apache.org/jira/browse/SDAP-172
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
  Components: nexus
Reporter: Frank Greguska


Some results being returned from TimeAvgMapSpark indicate a count of 0 (a mean 
was taken over 0 numbers). This results in reporting a mean of 0.

Example query:

timeAvgMapSpark?ds=MUR-JPL-L4-GLOB-v4.1=-134.9925=-140.0025=5.0025=10.0125=1538352000=1540944000

In the results, search for "cnt": 0,

Need to investigate why no measurements went into these means. These results 
should be eliminated.

May be related to SDAP-116



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

[jira] [Created] (SDAP-171) Implement cursor based paging for Solr

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-171:
---

 Summary: Implement cursor based paging for Solr
 Key: SDAP-171
 URL: https://issues.apache.org/jira/browse/SDAP-171
 Project: Apache Science Data Analytics Platform
  Issue Type: Improvement
  Components: nexus
Reporter: Frank Greguska
Assignee: Frank Greguska


Need to use a cursor based retrieval for documents from Solr.



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

[jira] [Created] (SDAP-170) More Documentation

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-170:
---

 Summary: More Documentation
 Key: SDAP-170
 URL: https://issues.apache.org/jira/browse/SDAP-170
 Project: Apache Science Data Analytics Platform
  Issue Type: Task
  Components: nexus
Reporter: Frank Greguska
Assignee: Frank Greguska


Need more documentation and link it to the incubator website.



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

[jira] [Created] (SDAP-169) Update passthrough plugin to use defaults for some HTTP headers

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-169:
---

 Summary: Update passthrough plugin to use defaults for some HTTP 
headers
 Key: SDAP-169
 URL: https://issues.apache.org/jira/browse/SDAP-169
 Project: Apache Science Data Analytics Platform
  Issue Type: Bug
  Components: edge
Reporter: Frank Greguska
Assignee: Maya DeBellis


The passthrough EDGE plugin should set a default for some HTTP headers:

"User-Agent": "Tornado"

"Accept": "*"

 

Changes should be implemented here: 
[https://github.com/apache/incubator-sdap-edge/blob/master/src/main/python/libraries/edge/httputility.py]
 



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

[jira] [Commented] (SDAP-169) Update passthrough plugin to use defaults for some HTTP headers

[Frank Greguska (JIRA)]

[ 
https://issues.apache.org/jira/browse/SDAP-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16726267#comment-16726267
 ] 

Frank Greguska commented on SDAP-169:
-

Note from 
[https://www.tornadoweb.org/en/stable/httpclient.html#tornado.httpclient.AsyncHTTPClient]

 

All 
[{{AsyncHTTPClient}}|https://www.tornadoweb.org/en/stable/httpclient.html#tornado.httpclient.AsyncHTTPClient]
 implementations support a {{defaults}} keyword argument, which can be used to 
set default values for 
[{{HTTPRequest}}|https://www.tornadoweb.org/en/stable/httpclient.html#tornado.httpclient.HTTPRequest]
 attributes. For example:
AsyncHTTPClient.configure( None, defaults=dict(user_agent="MyUserAgent")) # or 
with force_instance: client = AsyncHTTPClient(force_instance=True, 
defaults=dict(user_agent="MyUserAgent"))

> Update passthrough plugin to use defaults for some HTTP headers
> ---
>
> Key: SDAP-169
> URL: https://issues.apache.org/jira/browse/SDAP-169
> Project: Apache Science Data Analytics Platform
>  Issue Type: Bug
>  Components: edge
>Reporter: Frank Greguska
>Assignee: Maya DeBellis
>Priority: Minor
>
> The passthrough EDGE plugin should set a default for some HTTP headers:
> "User-Agent": "Tornado"
> "Accept": "*"
>  
> Changes should be implemented here: 
> [https://github.com/apache/incubator-sdap-edge/blob/master/src/main/python/libraries/edge/httputility.py]
>  



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

[jira] [Created] (SDAP-168) Update shapely library

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-168:
---

 Summary: Update shapely library
 Key: SDAP-168
 URL: https://issues.apache.org/jira/browse/SDAP-168
 Project: Apache Science Data Analytics Platform
  Issue Type: Improvement
  Components: nexus
Reporter: Frank Greguska


We are set at shapely version 1.5.16

If we try using a newer version, we receive this import error:

Traceback (most recent call last) :
 File "webservice/algorithms_spark/__init__.py", line 39, in 
 import Matchup
 File "webservice/algorithms_spark/Matchup.py", line 34, in 
 from shapely.geos import ReadingError
ImportError: cannot import name ReadingError

 

Need to make our code compatible with latest version of Shapely.



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

[jira] [Created] (SDAP-167) Make shard key configureable

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-167:
---

 Summary: Make shard key configureable
 Key: SDAP-167
 URL: https://issues.apache.org/jira/browse/SDAP-167
 Project: Apache Science Data Analytics Platform
  Issue Type: Improvement
  Components: nexus
Reporter: Frank Greguska
 Fix For: 1.1


Currently the dataset name is used as the prefix for the compositeId used for 
routing

[https://lucene.apache.org/solr/guide/7_4/shards-and-indexing-data-in-solrcloud.html#document-routing]

This is done in the SolrStore writer

[https://github.com/apache/incubator-sdap-ningester/blob/12e60f2c0f11be33026808d98623d5cbe136179d/src/main/java/org/apache/sdap/ningester/writer/SolrStore.java#L94]
 

 

This might not be appropriate for every case (for example, if only one dataset 
is ever going to be ingested). It would be nice to make this configureable.



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

[jira] [Updated] (SDAP-164) Refactor Webapp Instantiation of Spark Context

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-164:

Resolution: Fixed
Status: Done  (was: In Progress)

> Refactor Webapp Instantiation of Spark Context
> --
>
> Key: SDAP-164
> URL: https://issues.apache.org/jira/browse/SDAP-164
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
> Fix For: 1.0
>
>
> We want to enable multiprocessing for the webapp so it can handle multiple 
> user requests simultaneously. We've decided to create one spark context per 
> process and need to refactor webapp.



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

[jira] [Created] (SDAP-164) Refactor Webapp Instantiation of Spark Context

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-164:
---

 Summary: Refactor Webapp Instantiation of Spark Context
 Key: SDAP-164
 URL: https://issues.apache.org/jira/browse/SDAP-164
 Project: Apache Science Data Analytics Platform
  Issue Type: Task
  Components: nexus
Reporter: Frank Greguska
Assignee: Frank Greguska
 Fix For: 1.0


We want to enable multiprocessing for the webapp so it can handle multiple user 
requests simultaneously. We've decided to create one spark context per process 
and need to refactor webapp.



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

[jira] [Updated] (SDAP-164) Refactor Webapp Instantiation of Spark Context

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-164:

Status: In Progress  (was: To Do)

> Refactor Webapp Instantiation of Spark Context
> --
>
> Key: SDAP-164
> URL: https://issues.apache.org/jira/browse/SDAP-164
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
> Fix For: 1.0
>
>
> We want to enable multiprocessing for the webapp so it can handle multiple 
> user requests simultaneously. We've decided to create one spark context per 
> process and need to refactor webapp.



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

[jira] [Updated] (SDAP-137) webapp should have a mesos and a standalone image

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-137:

Resolution: Fixed
Status: Done  (was: In Progress)

> webapp should have a mesos and a standalone image
> -
>
> Key: SDAP-137
> URL: https://issues.apache.org/jira/browse/SDAP-137
> Project: Apache Science Data Analytics Platform
>  Issue Type: Improvement
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Major
> Fix For: 1.0
>
>
> We want 2 versions of the nexus webapp image. One should be able to run with 
> mesos and the other just as a standalone app.



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

[jira] [Updated] (SDAP-163) create build for search components

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-163:

Issue Type: Sub-task  (was: New Feature)
Parent: SDAP-15

> create build for search components
> --
>
> Key: SDAP-163
> URL: https://issues.apache.org/jira/browse/SDAP-163
> Project: Apache Science Data Analytics Platform
>  Issue Type: Sub-task
>    Reporter: Frank Greguska
>Priority: Major
>




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

[jira] [Created] (SDAP-163) create build for search components

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-163:
---

 Summary: create build for search components
 Key: SDAP-163
 URL: https://issues.apache.org/jira/browse/SDAP-163
 Project: Apache Science Data Analytics Platform
  Issue Type: New Feature
Reporter: Frank Greguska






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

[jira] [Created] (SDAP-162) Create build for nexus-webapp

[Frank Greguska (JIRA)]

Frank Greguska created SDAP-162:
---

 Summary: Create build for nexus-webapp
 Key: SDAP-162
 URL: https://issues.apache.org/jira/browse/SDAP-162
 Project: Apache Science Data Analytics Platform
  Issue Type: Sub-task
Reporter: Frank Greguska






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

[jira] [Updated] (SDAP-160) Document ingestion steps

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-160:

Fix Version/s: 1.0

> Document ingestion steps
> 
>
> Key: SDAP-160
> URL: https://issues.apache.org/jira/browse/SDAP-160
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>  Components: nexus
>    Reporter: Frank Greguska
>Priority: Minor
> Fix For: 1.0
>
>
> Need documentation on how ingestion works and steps for ingesting data.



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

[jira] [Assigned] (SDAP-160) Document ingestion steps

[Frank Greguska (JIRA)]

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

Frank Greguska reassigned SDAP-160:
---

Assignee: Frank Greguska

> Document ingestion steps
> 
>
> Key: SDAP-160
> URL: https://issues.apache.org/jira/browse/SDAP-160
> Project: Apache Science Data Analytics Platform
>  Issue Type: Task
>  Components: nexus
>    Reporter: Frank Greguska
>    Assignee: Frank Greguska
>Priority: Minor
> Fix For: 1.0
>
>
> Need documentation on how ingestion works and steps for ingesting data.



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

[jira] [Updated] (SDAP-95) TimeAvgMapSpark

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-95:
---
Resolution: Fixed
Status: Done  (was: To Do)

> TimeAvgMapSpark
> ---
>
> Key: SDAP-95
> URL: https://issues.apache.org/jira/browse/SDAP-95
> Project: Apache Science Data Analytics Platform
>  Issue Type: Sub-task
>  Components: nexus
>    Reporter: Frank Greguska
>Priority: Minor
>
> Determine necessary updates to and document API.



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

[jira] [Updated] (SDAP-93) HofMoellerSpark

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-93:
---
Resolution: Fixed
Status: Done  (was: To Do)

> HofMoellerSpark
> ---
>
> Key: SDAP-93
> URL: https://issues.apache.org/jira/browse/SDAP-93
> Project: Apache Science Data Analytics Platform
>  Issue Type: Sub-task
>  Components: nexus
>    Reporter: Frank Greguska
>Priority: Minor
>
> Determine necessary updates to and document API.



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

[jira] [Updated] (SDAP-96) TimeSeriesSpark

[Frank Greguska (JIRA)]

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

Frank Greguska updated SDAP-96:
---
Resolution: Fixed
Status: Done  (was: To Do)

> TimeSeriesSpark
> ---
>
> Key: SDAP-96
> URL: https://issues.apache.org/jira/browse/SDAP-96
> Project: Apache Science Data Analytics Platform
>  Issue Type: Sub-task
>  Components: nexus
>    Reporter: Frank Greguska
>Priority: Minor
>
> Determine necessary updates to and document API.



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