gitlab.alloy.finos.org

• Backup of GitLab RDS (every 7 days)
• Backup of EC2 Volume (every 7 days)
• Test restore procedure of EC2 instance
• Document restore procedure - simply follow https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-launch-snapshot.html and https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_RestoreFromSnapshot.html

alloy.finos.org

• Investigate standard way to achieve fully resilience using AWS EKS
• Apply changes
• Design and run simple test to prove full resilience

Define markdown docs to teach users to use the Pure/Alloy instance available on alloy.finos.org

Docs can be either hosted on .md files in a docs folder of this repo, or using https://github.com/finos-admin/alloy-config/wiki

Provide the ability to logout via /foundry app, and across all other applications (ie execution, sdlc, ...)

Work around: delete all cookies assigned to the /foundry host

Note sure how much work this is, or if it's even possible, but it would be great to integrate just the hubspot interest/question form at the bottom of https://www.finos.org/pure-alloy into the purealloy.finos.org microsite such that people can ask questions and also sign up for the hubspot subscription list.

Question presented via the form on the FINOS hosted Alloy/PURE overview & faq page, https://www.finos.org/pure-alloy

Rename https://github.com/finos/purealloy to https://github.com/finos/alloy

TBD

From DB: "Will there be any models published as part of the initial pilot?"

Develop Pilot Phase Terms of Service

Depends on following

• Microsite Infrastructure in Place
  • finos-admin/alloy-config#36 Decision on whether microsite will be built from Gitlab or Github repo (i.e., decision on Gitlab vs. Github for docs)

Before the transfer:

• get final approval from @brooklynrob and @gs-bracej
• check broken links on microsite
• switch the repo to public
• update travis build and badge url
• register purealloy in FINOS metadata

Re-organize https://github.com/finos/purealloy/tree/master/docs as follows:

• /docs

  • /docs/overview

    • intro.md
    • user-guide.md
    • why-purealloy.md

  • /docs/techdocs

    • /docs/techdocs/devdocs --> This where docs go for developers looking to extend and build out PURE/Alloy
      • /docs/techdocs/devdocs/PURE-lang (later new-name-lang)
      • /docs/techdocs/devdocs/alloy-platform (later new-name-platform)
    • /docs/techdocs/devopsdocs --> Systems engineering and deployment stuff
      • /docs/techdocs/devdocs/alloy-platform/aws-deploy

Question from DB: "Will we just be contributing back to GIT"

Interpreting this for now to mean - "How will the models be stored in Gitlab?" and "Will the models be available directly through the Gitlab UI (or terminal/command prompt) using standard git commands? Or only available through/via Alloy U/I?"

Conduct Documentation Site 101 Training Session with GS

Targeting Wednesday 2020.1.15 at 9:30am ET

At least until we have a bit more content on the microsite, and the homepage content written and built out more - can we add an "Under Construction" page to the microsite?

@brooklynrob to confirm

All GitLab users that are part of https://gitlab.com/groups/finos-foundation/-/group_members should be able to access to alloy.finos.org ; this also implies that access to anyone else should be denied.

Success criteria:

• Use gitlab.com as SDLC backend

See #22 for authorization

Right now, all docs/ contents are rendered in https://alloy.finos.org/docs/*.

The docs prefix seems to be redundant, although standard within Docusaurus installations.

It is possible to get rid of the docs URL prefix using the docsUrl setting in siteConfig.js (see finos/open-developer-platform@76ff9c9 as example)

Using this feature would actually break any existing URL that uses the docs/ prefix; to avoid that, we can create a redirect, following a similar approach to https://chillicream.com/blog/2018/11/07/docusaurus-docs-redirect ; it's not exactly the same case, but I think we can reuse some code.

Please stage the solution on a forked repository and provide a URL where the solution is staged.

Background

Visitors to the FINOS website will soon have the ability to sign-up for PURE/Alloy updates (e.g., dates for demos, new models available, schedule down times, etc.) on the FINOS website, including on https://www.finos.org/pure-alloy. They will receive these updates by email.

These updates are also, behind the scenes, an RSS feed.

Feature Request

Use this stream of PURE/Alloy updates from FINOS Hubspot to populate the blog/news section of the Docusaurus powered microsite.

Down the Road...

Stretch goal would be to make it possible for these posts from the RSS feed to be interspersed amongst other blog updates that might be made directly as .MD files within Docusaurus but that is firmly in the nice to have category right now.

Move https://github.com/finos/purealloy/project to https://github.com/orgs/finos/projects -- i.e., same place/level pan-PMC, FDC3, and Cloud Cert kanban boards are.

@maoo once it's done, please let Beeke know so she can register it in GS-OSS

FINOS to trademark new name once chosen.

Depends on choosing the name and getting the logo ID done.

Dependent on finos-admin/alloy-config#39 (I.e., need to choose new name first)

Will likely be done first and foremost by Megan Blume, FINOS' contract designer

Currently there is a short PURE/Alloy on https://developer.gs.com/ at https://developer.gs.com/docs/products/.

Once the microsite is ready to go, a longer overview of PURE/Alloy will be added to https://developer.gs.com/docs/products/ as well some additional content on FINOS.

• Identify GS counsel for Aaron Williamson (@copiesofcopies) to work with (@pierredebelen)

The current version of alloy.finos.org does not degrade well, especially to mobile devices. It looks like the responsiveness that is there by default in both Docusaurus and the FINOS blueprint, may have gotten lost along the way, or just not included.

I think it's important the site render well on mobile and would suggest that work be undertaken to improve the sites responsiveness and how the site renders on the mobile devices. In particular the font gets so small on a mobile phone it's almost impossible to read the copy.

Several of the participating pilot banks have asked for a diagram and/or technical documentation such that they could better understanding how the SDLC works, and in particular how contributions and actual underlying git commits work into the hosted GitLab instance beneath the interactive layer of Alloy Studio. One motivation for needing these is to give to legal and compliance folks in these banks who are assessing risk and evaluating ability of contributors to use Alloy.

Question from the interest form (Answer to be added to FAQ and/or Docs):

What platform(s) does the software run on?

From @brooklynrob - Question re Gitlab and PURE/Alloy

FINOS on Gitlab is https://gitlab.com/finos

Is that (https://gitlab.com/finos) the gitlab "org" into which any
PURE/Alloy models collaboratively developed in PURE will be found?

Question from the interest form:

What type of model can be define with PURE and how can it use different data storage type (RDBMS, File, Json, XML, No_SQL, Node database)?

This will be a page on the FINOS site, www.finos.org, specifically at https://www.finos.org/pure-alloy, which will provide an overview of PURE/Alloy, including how to get involved in the pilot.

@grizzwolf and @aitana16 to draft updated version of https://www.finos.org/pure-alloy that will go live when the documentation page goes live (consider developer.gs.com to ensure they're aligned and to avoid duplicated content)

Question from DB

"How will we access the sandbox deployed to AWS (during the pilot")?

We are getting these emails everytime someone logs in:

Hi @finos-admin,

On February 7th, 2020 at 13:38 (UTC) your application (Alloy) used an access token (with the User-Agent Faraday v0.15.4) as part of a query parameter to access an endpoint through the GitHub API:

https://api.github.com/user

Please use the Authorization HTTP header instead as using the `access_token` query parameter is deprecated.

Depending on your API usage, we'll be sending you this email reminder once every 3 days for each token and User-Agent used in API calls made on your behalf.
Just one URL that was accessed with a token and User-Agent combination will be listed in the email reminder, not all.

Visit https://developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters for more information.

Thanks,
The GitHub Team

We opened a ticket to GitLab Support; there's also an issue on https://gitlab.com/gitlab-org/gitlab/issues/202026 (please vote) /CC @gs-bracej @mcleo-d @brooklynrob

Is there a standard for monitoring for other FINOS apps?

I'm sure AWS can do this, or there's always uptimerobot.com

Currently we're using Github (right here where this issue exists) for collaboration -- e.g., issue/task management and documentation. Since the code will be on Gitlab, and PURE/Alloy is built on Gitlab, and keeping with the principle to keep docs as close to the code as possible, we should migrate the issues and docs we've been temporarily putting here in Github to Gitlab as soon as possible.

Produce Alloy Informational/Overview video:

• Identify topics
• Write script
• Do story board
• Produce Video
• Post and distribute video
  • Add video/link to video in microsite
  • Add video/link to video in www.finos.org/alloy

Add Google Analytics to Alloy (alloy.finos.org) microsite