Google Summer of Code 2022 proposed ideas - Ιστορικό εκδόσεων

Karounos: /* Integration of GitLab boards into Nextcloud Decks */

2022-03-24T13:49:38Z

Integration of GitLab boards into Nextcloud Decks

← Παλαιότερη αναθεώρηση		Αναθεώρηση της 13:49, 24 Μαρτίου 2022
Γραμμή 85:		Γραμμή 85:


	== ~~Integration~~ of GitLab boards ~~into~~ Nextcloud Decks ==		== Interoperability of GitLab boards with Nextcloud Decks ==

	==== Brief Explanation ====		==== Brief Explanation ====

Pkst στις 17:41, 22 Μαρτίου 2022

2022-03-22T17:41:44Z

← Παλαιότερη αναθεώρηση		Αναθεώρηση της 17:41, 22 Μαρτίου 2022
Γραμμή 85:		Γραμμή 85:


	== ~~SciDavis data Analysis and Visualization Program~~ ==		== Integration of GitLab boards into Nextcloud Decks ==

	==== Brief Explanation ====		==== Brief Explanation ====
	~~SciDAVis~~ is a free ~~interactive application aimed at data analysis and publication-quality plotting~~. ~~It combines a shallow learning curve and an intuitive, easy-to-use graphical user interface with powerful features such as scriptability and extensibility~~. ~~SciDAVis runs on GNU/Linux, Windows and MacOS X; possibly also on other platforms like *BSD, although this is untested. SciDAVis is similar in its field~~ of ~~application to proprietary Windows applications like Origin and SigmaPlot as well as free applications like QtiPlot, Labplot and Gnuplot. What sets SciDAVis apart from~~ the ~~above~~ is ~~its emphasis on providing a friendly and open environment (in the software as well as the project) for new and experienced users alike. Particularly~~, ~~this means~~ that we will try to provide good documentation on all levels, ranging from user’s manual over tutorials down to and including documentation of the internal APIs We encourage users to share their experiences on our forums and on our mailing lists.~~More information, including screenshots, reviews, current contributers can be found on the SourceForge project webpage~~.		Nextcloud is free software for cloud collaboration. Nextcloud consists of core functionality plus installable apps. One of the apps is "Deck", that provides Kanban boards. GitLab also provides Kanban boards.

	~~SciDAVis has been started as~~ a ~~fork off~~ of ~~QtiPlot~~ with ~~the aim of introducing some changes in design and establishing an open and friendly community~~. ~~The versions labelled SciDAVis 0.1.0~~ to 0.~~1.4 are still very close~~ to ~~QtiPlot 0.9.×. But many new features and a revision of existing ones have been introduced~~ in ~~release 0.2.0~~. ~~This~~ is ~~especially true for tables~~ and ~~matrices which have internally been rewritten almost completely~~.		There exists a Nextcloud "GitLab" app which provides some integration of GitLab with Nextcloud, but it does very little. Its only substantial functionality is to show a panel with "GitLab todos" in the Nextcloud dashboard (which serves as the user's home page). That is, it provides a list in the user's Nextcloud dashboard that shows the next things the user has to do in GitLab. Each "todo" is just a title and a link to GitLab.

	~~At some time in 2008, the developer teams of LabPlot and SciDAVis found their~~ project ~~goals to be very similar (and since LabPlot 2.x~~ is ~~based on~~ the ~~same library as SciDAVis, i.e., Qt4.x) decided to start a close cooperation. The current plans are to use a common backend with two frontends, one with full KDE4~~ integration ~~(called LabPlot 2.x) and one with no KDE dependencies (pure Qt~~ so ~~to say) for easier cross-platform use (called SciDAVis). This promises~~ a ~~faster development speed for both projects while focussing on slightly different audiences. From~~ the ~~user~~'s ~~point of view, there will still be two different applications~~.		This project is about extending the GitLab-Nextcloud integration so that a user can see and manage the GitLab boards in Nextcloud's Deck application.

	~~At the time of writing, SciDAVis is completely independent of LabPlot, whether the collaboration mentioned in the previous paragraph will ever happen is a moot point.~~

	By 2011, the original development team had moved on to other things, and development of SciDAVis stalled. Stewardship of SciDAVis has passed over to Russell Standish, aka High Performance Coder, an experienced SourceForge project manager. The immediate plan is to focus on bug fixes reported in the SourceForge ticket system, and creating regression tests, whilst the new development team get up to speed with the code base. Russell uses the Aegis source code repository system for managing the releases, so this has meant bumping the version number to 1. Releases within a version number are denoted by the delta number assigned to the code when it is successfully committed to Aegis. At the time of writing the current version is 1.D4, and the plans are for roughly 6 monthly releases, unless a critical bug is found and fixed to bring the release forward, or no development activity has taken place since the last release.

	==== Duration of the Project ====		==== Duration of the Project ====
	~~175~~ hours		350 hours

	==== Expected Results ====		==== Expected Results ====
	~~Extending the features~~ of ~~Scidavis open software~~ to ~~adapt the needs of scientific community~~ , ~~creating useful tutorial for the community, contributing~~ to ~~program documentation~~ and ~~translating program features~~ and ~~documentation in Greek~~		Some organizations use both Nextcloud and GitLab. Some of their kanban boards tend to be on GitLab and some other on Nextcloud. Developers tend to use more GitLab, while non-developers tend to use Nextcloud. This project is expected to reduce duplication and help developers and non-developers co-operate better.

	==== Related repositories ====		==== Related repositories ====
	~~http~~://~~scidavis~~.~~sourceforge~~.~~net~~/		<https://github.com/nextcloud/deck/>

			<https://github.com/nextcloud/integration\_gitlab>

	==== Knowledge Prerequisites ====		==== Knowledge Prerequisites ====
	~~C/C++~~, ~~Python~~, ~~Latex~~		JavaScript, PHP, Vue, Web APIs

	==== Mentors: ====		==== Mentors: ====
			Antonis Christofides

	== Label Buddy 2.0: Automated audio-tagging using transfer learning ==		== Label Buddy 2.0: Automated audio-tagging using transfer learning ==

Pkst: /* Brief Explanation */

2022-03-17T07:31:59Z

Brief Explanation

← Παλαιότερη αναθεώρηση		Αναθεώρηση της 07:31, 17 Μαρτίου 2022
Γραμμή 17:		Γραμμή 17:

	Points for contribution around the proposal include:		Points for contribution around the proposal include:
	- Adaptation of a coordinating logic on the node-red environment by creating a relevant flow that implements it. This flow may regulate how Openwhisk functions are invoked, results gathered and forwarded to new functions etc. Coordinating logic can be inspired by:		- Adaptation of a coordinating logic on the node-red environment by creating a relevant flow that implements it. This flow may regulate how Openwhisk functions are invoked, results gathered and forwarded to new functions etc. Coordinating logic can be inspired by: workflow constructs or primitives (e.g. https://www.researchgate.net/figure/Basic-workflow-constructs_fig1_226149698) parallel or distributed computing primitives (e.g. MPI-related patterns for distributing work http://www.mathcs.emory.edu/~cheung/Courses/355/Syllabus/92-MPI/group-comm.html) Cloud design patterns rationale (https://docs.microsoft.com/en-us/azure/architecture/patterns/), for which a relevant flow can be implemented to support them

	workflow constructs or primitives (e.g. https://www.researchgate.net/figure/Basic-workflow-constructs_fig1_226149698)
	parallel or distributed computing primitives (e.g. MPI-related patterns for distributing work http://www.mathcs.emory.edu/~cheung/Courses/355/Syllabus/92-MPI/group-comm.html)
	Cloud design patterns rationale (https://docs.microsoft.com/en-us/azure/architecture/patterns/), for which a relevant flow can be implemented to support them

	-Packaging of that flow as a subflow and adding parameters of operation and configuration (from the UI or through the incoming message fields)		-Packaging of that flow as a subflow and adding parameters of operation and configuration (from the UI or through the incoming message fields)



	==== Expected Results ====		==== Expected Results ====

Pkst στις 07:30, 17 Μαρτίου 2022

2022-03-17T07:30:32Z

@@ Γραμμή 9: / Γραμμή 9: @@
 ==== Brief Explanation ====
 Node-RED (<nowiki>https://nodered.org/</nowiki>) is a popular low code programming environment for event driven applications, particularly in the IoT world. It is based on a visual, browser based editor in which developers can write functions, wire them together to form a workflow, group a subset of functions into reusable and parametric subflows etc. Node-RED can interact with any API or service, thus its usage can be extended to be used in collaboration with other services, e.g. Function as a Service platforms, as an orchestrator.
 ==== Expected Results ====

Pkst στις 06:48, 7 Μαρτίου 2022

2022-03-07T06:48:48Z

← Παλαιότερη αναθεώρηση		Αναθεώρηση της 06:48, 7 Μαρτίου 2022
Γραμμή 166:		Γραμμή 166:

	==== Brief Explanation ====		==== Brief Explanation ====
			Despite the substantial progress in compiler testing, research endeavors have mainly focused on detecting
			compiler crashes and subtle miscompilations caused by bugs in the implementation of compiler optimizations.
			Surprisingly, this growing body of work neglects other compiler components, most notably the front-end. In
			statically-typed programming languages with rich and expressive type systems and modern features, such as
			type inference or a mix of object-oriented with functional programming features, the process of static typing (i.e., type checking)
			in compiler front-ends is complicated by a high-density of bugs. As a recent study has shown [1], such bugs can lead to the acceptance of
			incorrect programs (breaking code portability or the type system’s soundness), the rejection of correct (e.g.
			well-typed) programs, and the reporting of misleading errors and warnings.

	Hephaestus is a testing framework for validating compilers' type checkers,		Hephaestus is a testing framework for validating compilers' type checkers,
	which is based on both program generation and transformation-based		which is based on both program generation and transformation-based
Γραμμή 194:		Γραμμή 203:

	[1] https://dl.acm.org/doi/pdf/10.1145/3485500		[1] https://dl.acm.org/doi/pdf/10.1145/3485500

Pkst στις 06:21, 7 Μαρτίου 2022

2022-03-07T06:21:22Z

@@ Γραμμή 166: / Γραμμή 166: @@
 ==== Brief Explanation ====
-Despite the substantial progress in compiler testing, research endeavors have mainly focused on detecting compiler crashes and subtle miscompilations caused by bugs in the implementation of compiler optimizations. Surprisingly, this growing body of work neglects other compiler components, most notably the front-end. In statically-typed programming languages with rich and expressive type systems and modern features, such as type inference or a mix of object-oriented with functional programming features, the process of static typing in compiler front-ends is complicated by a high-density of bugs. As a recent study has shown [1], such bugs can lead to the acceptance of incorrect programs (breaking code portability or the type system's soundness), the rejection of correct (e.g. well-typed) programs, and the reporting of misleading errors and warnings.
+Hephaestus is a testing framework for validating compilers' type checkers,
 ==== Duration of the Project ====

Pkst στις 18:13, 25 Φεβρουαρίου 2022

2022-02-25T18:13:32Z

← Παλαιότερη αναθεώρηση		Αναθεώρηση της 18:13, 25 Φεβρουαρίου 2022
Γραμμή 331:		Γραμμή 331:

	==== Expected Results ====		==== Expected Results ====
	~~Write the expected results for the GSOC Project=~~A location based mobile		A location based mobile application (LBMA) with integrated emergency communications service
	application (LBMA) with integrated emergency communications service

	==== Duration of the Project ====		==== Duration of the Project ====

Pkst στις 18:11, 25 Φεβρουαρίου 2022

2022-02-25T18:11:11Z

@@ Γραμμή 302: / Γραμμή 302: @@
 ==== Mentors: ====
 Nikos Cheimarios, Vissarion Fisikopoulos
 [[Κατηγορία:GSOC2022]]
 [[Κατηγορία:GSOC]]

Pkst-1 στις 07:13, 25 Φεβρουαρίου 2022

2022-02-25T07:13:00Z

← Παλαιότερη αναθεώρηση		Αναθεώρηση της 07:13, 25 Φεβρουαρίου 2022
Γραμμή 12:		Γραμμή 12:
	==== Expected Results ====		==== Expected Results ====
	The purpose of the work is to exploit Node-RED's subflow and workflow features in order to implement reusable flows that can be shared through Node-RED's repository. The initial scope of the flows is around workflow primitives for easier workflow creation, parallelization patterns (e.g. migrating logic and patterns from MPI to node-red, implementation of orchestration logic for parallel AI operations and learning etc). This can be coupled with function creation for executing the workflows in state of the art function as a service environments like Openwhisk, for actual computational parallelism.		The purpose of the work is to exploit Node-RED's subflow and workflow features in order to implement reusable flows that can be shared through Node-RED's repository. The initial scope of the flows is around workflow primitives for easier workflow creation, parallelization patterns (e.g. migrating logic and patterns from MPI to node-red, implementation of orchestration logic for parallel AI operations and learning etc). This can be coupled with function creation for executing the workflows in state of the art function as a service environments like Openwhisk, for actual computational parallelism.

			==== Duration of the Project ====
			350 hours

	==== Related repositories ====		==== Related repositories ====
Γραμμή 36:		Γραμμή 39:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Can be either a short or a long-term project, depending on the scope and the technologies tackled.~~		350 hours

	==== Related repositories ====		==== Related repositories ====
Γραμμή 85:		Γραμμή 88:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Depending on the scope and the technologies tackled~~		175 hours

	==== Expected Results ====		==== Expected Results ====
Γραμμή 105:		Γραμμή 108:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Depending on the scope and the technologies tackled~~		350 hours

	==== Expected Results ====		==== Expected Results ====
Γραμμή 145:		Γραμμή 148:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Depending on the scope and the technologies tackled~~		350 hours

	==== Expected Results ====		==== Expected Results ====
Γραμμή 195:		Γραμμή 198:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Large Size Project~~		350 hours

	==== Related repositories ====		==== Related repositories ====
Γραμμή 223:		Γραμμή 226:
	In order for the Blockly integration to be possible, it is going to be essential for some parts of the existing code of the GSoC 2019-2021 robot to be rewritten. This means that back end code that runs in the Raspberry Pi and controls all the movements of the robot, will be improved. For that reason, I will create a custom functionality library (e.x. PID Controller) for special control of every electronic part and sensor. Based on the fact that the GSoC 2021 contributor introduced for the first time the logic of microservices, microservices and dockerization can be utilized so that different services run for controlling the robot movements as well as the communication between the Blockly desktop application and the Raspberry Pi.		In order for the Blockly integration to be possible, it is going to be essential for some parts of the existing code of the GSoC 2019-2021 robot to be rewritten. This means that back end code that runs in the Raspberry Pi and controls all the movements of the robot, will be improved. For that reason, I will create a custom functionality library (e.x. PID Controller) for special control of every electronic part and sensor. Based on the fact that the GSoC 2021 contributor introduced for the first time the logic of microservices, microservices and dockerization can be utilized so that different services run for controlling the robot movements as well as the communication between the Blockly desktop application and the Raspberry Pi.

			==== Expected Results ====

	Expected Results

	Within the months of the project the expected results are:		Within the months of the project the expected results are:

Γραμμή 236:		Γραμμή 236:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Large Size Project~~		350 hours

	==== Related Repositories ====		==== Related Repositories ====
Γραμμή 260:		Γραμμή 260:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Can be either a short or a long-term project, depending on the scope and the technologies tackled.~~		350 hours

	==== Expected Results ====		==== Expected Results ====
Γραμμή 292:		Γραμμή 292:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~depending on the scope and the technologies tackled.~~		350 hours

	==== Related repositories ====		==== Related repositories ====

Pkst-1 στις 07:10, 25 Φεβρουαρίου 2022

2022-02-25T07:10:25Z

← Παλαιότερη αναθεώρηση		Αναθεώρηση της 07:10, 25 Φεβρουαρίου 2022
Γραμμή 166:		Γραμμή 166:

	==== Duration of the Project ====		==== Duration of the Project ====
	~~Large Size Project~~		350 hours

	==== Expected Results ====		==== Expected Results ====