Application: Project Aurras MVP - Phase 1

[MuhammedIrfan]

Grant Application Checklist

• The application-template.md has been copied, renamed ( "project_name.md") and updated.
• A BTC address for the payment of the milestones is provided inside the application.
• The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
• The total funding amount of the project is below CHF 30k at the time of submission.
• The initial PR contains only one commit (squash if needed before submitting your PR).

[CLAassistant]

All committers have signed the CLA.

[Noc2]

Thanks for the application. This looks good to me. I will share it with the rest of the team.

[BenWhiteJam]

@MuhammedIrfan thanks for the application:

• could you please add more details to 1d. & 1e. in the sense of what components you will add a Dockerfile for as well as which ones will be part of the Docker Compose config
• you mention to provide YAML files for the deployment of the stack, as you also mention Docker Compose, I would assume the general deployment configuration will target Docker Compose as deployment infrastructure. As there is nothing against using Docker Compose, I'm still wondering if it wouldn't be more beneficial to target Kubernetes as deployment infrastructure? The reason would be that I've heard more node infrastructure provider running the nodes on Kube rather then Docker Compose, but happy to discuss further.

[MuhammedIrfan]

Thanks for the application. This looks good to me. I will share it with the rest of the team.

@Noc2 Thank you.

@BenWhiteJam Thank you for the suggestions.

• could you please add more details to 1d. & 1e. in the sense of what components you will add a Dockerfile for as well as which ones will be part of the Docker Compose config

Sure I will add more details

• you mention to provide YAML files for the deployment of the stack, as you also mention Docker Compose, I would assume the general deployment configuration will target Docker Compose as deployment infrastructure. As there is nothing against using Docker Compose, I'm still wondering if it wouldn't be more beneficial to target Kubernetes as deployment infrastructure? The reason would be that I've heard more node infrastructure provider running the nodes on Kube rather then Docker Compose, but happy to discuss further.

The YAML file mentioned for the workflow composer component is used to compose multiple tasks/actions and the deployment is done through openwhisk which is different from the general deployment configuration. For deployment configuration we chose Docker Compose for ease of development and deployment since we are doing MVP, But as you pointed out Kubernetes should be used for production deployment infrastructure. We will make the necessary changes in the application to accommodate Kubernetes.

[BenWhiteJam]

@MuhammedIrfan thank you for the update, looking forward to it!

[mmagician]

@MuhammedIrfan The application looks good to me. I would only like to point out that we require teams to include a short write-up as part of the grant, see the application template. You might have forked the repo before this was added, so I'd appreciate you including the appropriate sub-clause in your milestone deliveries. I think in your case it makes sense to add it only for M3, rather than for each milestone. Thanks!

[MuhammedIrfan]

@MuhammedIrfan The application looks good to me. I would only like to point out that we require teams to include a short write-up as part of the grant, see the application template. You might have forked the repo before this was added, so I'd appreciate you including the appropriate sub-clause in your milestone deliveries. I think in your case it makes sense to add it only for M3, rather than for each milestone. Thanks!

@mmagician Thank you for the suggestion. We will update the application to include a Medium article of our grant journey.

[github-actions]

Congratulations! As part of the Open Grants Program, we want to help winning teams acknowledge their grants publicly while observing the foundation’s guidelines. To that end, we’ve created a badge for grant-winning teams. Here is a link to the download and guidelines.

Once you complete your first grant milestone, would you be interested in collaborating on an announcement about the work you’re doing? If so, then please get in touch with us at [email protected] prior to making the announcement (at least two weeks notice is preferred) so that we can coordinate on timing and content.

Please don’t announce the grant publicly before you finished at least the first milestone of the project.

[mmagician]

@MuhammedIrfan It's been a while since your last submission. Do you perhaps have any updates on the second milestone? Otherwise the grant will be terminated.

[MuhammedIrfan]

@MuhammedIrfan It's been a while since your last submission. Do you perhaps have any updates on the second milestone? Otherwise the grant will be terminated.

@mmagician we are working on milestone 2 and milestone 3 together as both are of the same component. As there were some unforeseen covid situations we might need a little extra time to submit.

[mmagician]

Could you provide links to the repos where you've been actively developing? I've noticed that your aurras- related repos have been inactive since your last submission.

[MuhammedIrfan]

Could you provide links to the repos where you've been actively developing? I've noticed that your aurras- related repos have been inactive since your last submission.

We are working within our internal repo. Please give us some time to push commits to our upstream aurras- repos

[mmagician]

In case of such long delays with the submission, we usually require teams to prove that they're still actively working on the project. Please either update your repos, or alternatively you can add me with view permissions to your private repos in the meantime.

I understand that there might have been unexpected circumstances. We are generally happy to extend the deadline for committed teams. Do you have a deadline for completing M2 & M3?

[MuhammedIrfan]

@mmagician thank you for considering the extension of deadline. We will submit the target date for M2&M3 combined tomorrow

[MuhammedIrfan]

@mmagician We will be able to deliver M2 and M3 combined by 16 Aug 2021.

[MuhammedIrfan]

@mmagician Please check the implementation (partial) for milestone 2 and 3. Kindly receive my sincere apology for submitting the project late than the target date.
This is due to unexpected diversion in solution implementation. Still there are few more component need to add to the solution, we working on these components and will delivery as soon as possible and update you regarding the same. Thank you.

[MuhammedIrfan]

@mmagician We sincerely apologize for the delay in delivery. We have completed the implementation. Kindly review it. Thank you.