12-03-2018 06:00 PM
For each project, you should consider addressing the following:
We encourage you to keep your project idea short and if necessary provide any additional details in separate document or blog post within the Collaborate space. This may also allow you to coordinate with potential team members via the comments there without being mixed in with any discussions on this page.
Please feel free to add your name to any project(s) you are interested in participating. Don't hesitate to add your name to multiple projects if you are considering multiple at this point. We encourage you to use this platform to contact the owner of an idea to discuss any details you are unsure about or even improve upon the idea.
Apart from any plans you make with the owner of an idea, you are not bound to actually participate in the project you indicated here. The final teams typically constituate themselves on the day of the event based on in-person presentation of the ideas and other factors.
Idea owner: <your Name>, ideally linked like this: Axel Faust
Description: This is just an example of how to structure your project idea. Please give as much detail about your idea here, i.e. if this is something new or a continuation of a previous project, what the benefits would be. Essentially, you want to inspire people with this description to join your efforts on the day of the hack-a-thon.
Prep work: Describe what you think people should do to prepare for this project so you can cut directly to the chase and start working when the hack-a-thon starts.
Interested parties:
Idea owner: TBD
Description: TBD
Prep work: TBD
Interested parties:
Idea owner: Michael Suzuki
Description: Create a Sentiment Analysis application that is able to take in a corpus and categorise the attitude as positive, negative, or neutral.
Prep work: None! it might be useful to know Spring Boot or Apache OpenNLP.
Probably we can also consider previous work from Activiti Team: GitHub - Activiti/ttc-connectors-processing: Activiti Cloud BluePrint: Trending Topic Campaigns Conn...
And it should be fun also to integrate some tool from local NLP group EdinburghNLP
Status: We have completed the application using spring boot and StanfordNLP.
The project can be viewed at GitHub - Alfresco/SentimentAnalysis.
We hope to add the OpenNLP endpoint and compare the results between OpenNLP and StanfordNLP.
Interested parties:
Michael Suzuki
Angel Borroy
Matteo Mazzola
Sam Cheshire
Nick Burch
Idea owner: Axel Faust
Description: Given how tricky it can be for community members / customers to switch over to the new approach without any prior experience, I would say that any guides / documentation that we as the Order could collaboratively put together would be much more valuable/needed at this point than simply revisiting the pre-bundled build. As both the Docker Compose scripts and Helm charts from Alfresco should only be considered as a starting point / reference rather than a ready-to-use setup, we might also want to look into providing improved variants for these (Helm may
be a lower priority as it/Kubernetes likely is not relevant for most community users). I know that Angel has already done work in the area of an improved compose reference (https://github.com/keensoft/docker-alfresco) - maybe that could be a starting point to flesh out / improve upon...
Prep work: Docker, Docker Compose
Interested parties:
Results:
Idea owner: Axel Faust / #alfresco Discord + IRC members
Description: As some people have discussed on IRC / Discord on January 10th, instead of building something "new" / "shiny", the community could band together and simply search + destroy / hunt + fix various bugs in Alfresco, both (very, very) old and new.
Prep work: Familiarisation with Alfresco GitHub PR process, checkout of all individual Alfresco repositories and build (incl. familiarisation with running tests as best as possible)
Interested parties:
Idea owner: Axel Faust
Description: Alfresco does not have any plans to support Keycloak-based authentication (supported in ACS since 6.0) in Share, in order to (not really subtly) force customers / users to switch to ADF sooner rather than later. As Share already supports external authentication and does not really care about how it is handled by the backend (as long as we can determine the current user name), it should not be difficult to add support for Keycloak in Share as a community-sourced extension. This would help customers that need more time to migrate their previous investments into Share to an ADF-based (or alternative) UI (especially if the limited feature set of ADF does not yet support their use case), and still embrace the new / improved authentication mechanism(s).
As mentioned by Alfresco employee Paul Roth on the platform-services Gitter channel, an Alfresco engineer has already added support for Keycloak to Alfresco Share for an Enterprise customer, building upon an Apache HTTPd module for OpenID Connect. Maybe this hack-a-thon project could come up with a way that integrates directly in Share and is not restricted to OpenID Connect.
Prep work: Familiarisation with keycloak integration, Share/ACS authentication components
Interested parties:
Idea owner: Filip Bruska
Description: A few days ago beta of SDK 4.0 was released. I would like to test it and see how easy is to develop a new feature for ACS 6.0.
Prep work: alfresco-sdk/README.md at sdk-4.0 · Alfresco/alfresco-sdk · GitHub
Participants: Filip Bruska Brahmaiah926 _ Muralidharan Deenathayalan, Jeff Potts, omar ounou, Krzysztof, Mitchell Brodsky and others 🙂
Results/Notes:
Description: An extension of the previous idea, the goal of this was to document the steps necessary to upgrade from 3.0.1 to 4.0.0. Once the steps were documented, script the upgrade so that existing add-ons can be upgraded easily.
Participants: Jeff Potts plus all of the folks on the Get Familiar project, above.
Results:
* Pull Request to add upgrade documentation to SDK docs
* New open source project that contains the start of an SDK upgrade script
Idea owner: Łukasz Tworek
Description: Statistics show that the number of smart speaker users is rising. These devices are becoming cheaper, have better voice recognision and every day they have more and more avaliable skills. For several weeks I have been using Amazon's voice assistant - Alexa at home. This kind of devices are more useful than I thought, therefore I would like to prepare an AMP module which will allow developers to easily create a new Alexa's skill integrated with Alfresco. In order to achieve this goal I would like to use the official Java SDK provided by Amazon. In this scenario ACS will be an endpoint for the skill. So let's try to use our voice to complete simple tasks or search for some documents. We can also think about e.g. new documents notifications (Alexa's notification feature has not been made public yet, but we can use Notify Me skill instead).
Prep work: You can read about the Alexa custom skill, the API and take a look at some earlier examples of integration here and here.
Results: Project on github
Interested parties:
Idea owner: Asgeir Frimannsson
Description: Understanding and writing clients for JSON/REST apis is a major cause of depression amongst developers, second only to writing and documenting your own home-grown I-think-this-is-REST api. RPC is back in fashion, and gRPC is in many ways a more natural fit to what REST apis try to achieve, with elegant solution to interface definitions, code generation and versioning. Perhaps a natural fit for consuming and extending Alfresco in a Kubernetes environment? I'd like to explore building an extension in Alfresco that exposes an extensible gRPC service, and compare and contrast this to using the REST api.
Prep work: Get familiar with gRPC, learn about some existing APIs, perhaps figure out how to use SDK 4.x to build an Alfresco extension.
Interested parties:
Idea owner: Bartosz Skotarek
Description: Sometimes, there is a need to execute a piece of code on a running server - checking the correctness of returned results, repairing permissions or verifying an idea. The most popular way is to use Rhino. Unfortunately, this solution has several disadvantages: weak IDE support, the lack of comfortable debugging, no easy access to Spring context and the need to transform the code from Java to JavaScript and back.
The target of the project is to implement an extension which executes sent Java source code on JVM where Alfresco is running. The implementation should be convenient for a programmer – no external dependencies or meeting special contracts. It would be nice, if the extension supports additional facilities - for example, injecting bean by Spring annotations.
Prep work: Kotlin (Java is also acceptable), how class loading works, sending data via Web Scripts.
Results: You can see the code and the description on GitHub - Skotar/java-code-executor.
Interested parties:
Idea owner: Bindu Wavell
Description: Currently generator-alfresco support SDK 2 and 3. As SDK 4 beta was released recently, I plan to add support for SDK 4 support to generator-alfresco. If time permits I may also use information provided by Jeff Potts to create something to upgrade from SDK 3 to SDK 4.
First pass at generating projects based on SDK 4. Worked around an issue with archetype
processing code by re-writing the archetype-metadata.xml file. Still need to add code to
add and remove modules using the new docker based running infrastructure.
Branch with this work is here: https://github.com/binduwavell/generator-alfresco/tree/sdk4-beta-1
Interested parties:
Idea owner: TBD
Description: TBD
Prep work: TBD
Interested parties:
Idea owner: Mauricio Salatino
Description: Improving Trending Topics Campaign (ttc-docs/workshop.md at develop · Activiti/ttc-docs · GitHub ) example with GraphQL new notification services.
Prep work: If you want to run the example or play around with projects you will need your own GKE cluster that you can obtain by getting free credit here: https://console.cloud.google.com/freetrial You can also look at our Activiti Cloud Getting Started Guide: Getting Started - Activiti Cloud - Activiti & Activiti Cloud Developers Guide
We got notifications integrated into the example and were able to see them in the graphiql client
Keywords: Kubernetes, Cloud Native, Containers, Spring Cloud, Activiti Cloud
Interested parties:
Idea owner: Marcello Teodori
Description: Adapt the full example application of Activiti Cloud to work just using AWS managed services, so EKS for Kubernetes, Aurora for PostgreSQL and Kinesis as implementation of Spring Cloud Stream rather than RabbitMQ.
Prep work: AWS account with rights to perform above actions.
Interested parties:
Idea owner: TBD
Description: TBD
Prep work: TBD
Interested parties:
Idea owner: TBD
Description: TBD
Prep work: TBD
Interested parties:
Idea owner: Leonardo Mattioli
Description: I want to produce an example Angular app that use ADF components. The app can be as easy as a Calendar with some attachment held in the repository, can be a Chat or even a multi-channel Chat (Discord like).
Note: I am a newbie in Angular, so I am also looking for some experienced developer
Prep work: Angular, ADF
The project can be viewed at GitHub
Interested parties:
Idea owner: mgrunenberg
Description: Electron is a Framework for developing cross platform desktop applications using JavaScript and a WebEngine. We would like to try it out and implement a Desktop application based on ADF. For example it would be nice to see how filesystem access and so on is handled in Electron and which features it provides.
Prep work: Angular, ADF, Code Editor, NPM
Interested parties:
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.