Talk:Karstlink Applications - Applications Karstlink - Revision history

Furien at 13:43, 7 May 2024

2024-05-07T13:43:48Z

MattS: Question regarding data criteria

2024-04-22T01:42:17Z

Question regarding data criteria

Furien: Created page with "Mike: Criteria: At least 5 people contributed code Question: What is the reason behind this criteria? Even if only one or two persons created a Karslink applications level 1..."

2023-04-13T19:46:31Z

Created page with "Mike: Criteria: At least 5 people contributed code Question: What is the reason behind this criteria? Even if only one or two persons created a Karslink applications level 1..."

New page

Mike:
Criteria: At least 5 people contributed code
Question: What is the reason behind this criteria?
Even if only one or two persons created a Karslink applications level 1 application, and no one else contributed, even if those people left, as its open source others could step in to maintain it.
Answer: ??

Answer from Fred:
There are two reasons for this criteria:
- the first is clearly linked to continuity in the maintenance of the code. In our community there are many applications developed by one or two people, whose code is accessible but there is no one who can update quickly, if there are "enough" people who have contributed to the code, there is "enough" chance that development will continue. Applications for sharing data are online applications that require very regular maintenance.
- the second reason concerns the quality of the code which is an important question, but very difficult to evaluate. How to say that the code is too bad to be taken over by someone else? If "enough" people understood the code and made the effort to code it means that it was possible, that the code was not too bad.

← Older revision		Revision as of 13:43, 7 May 2024
Line 13:		Line 13:
	'''Criteria''': Data is freely accessible without logging in<br>		'''Criteria''': Data is freely accessible without logging in<br>
	'''Question''': Should the requirements around data be separate from those related to the software? In some instances the software (Topodroid and other utility apps) is not intended provide data in a publicly consumable manner, hence this (and possible other points) are not relevant.<br>		'''Question''': Should the requirements around data be separate from those related to the software? In some instances the software (Topodroid and other utility apps) is not intended provide data in a publicly consumable manner, hence this (and possible other points) are not relevant.<br>
		+
		+	Answer from Fred:
		+	Yes, this is a question we need to think about. Could it be stated that the data must be freely accessible if the application is intended to manage data?
		+	But this is a question that has been addressed by Topodroid and by Cave survey. For these two applications it is possible to archive the data on Grottocenter and make them freely accessible. So they respect this criterion

← Older revision		Revision as of 01:42, 22 April 2024
Line 9:		Line 9:
	- the first is clearly linked to continuity in the maintenance of the code. In our community there are many applications developed by one or two people, whose code is accessible but there is no one who can update quickly, if there are "enough" people who have contributed to the code, there is "enough" chance that development will continue. Applications for sharing data are online applications that require very regular maintenance.		- the first is clearly linked to continuity in the maintenance of the code. In our community there are many applications developed by one or two people, whose code is accessible but there is no one who can update quickly, if there are "enough" people who have contributed to the code, there is "enough" chance that development will continue. Applications for sharing data are online applications that require very regular maintenance.
	- the second reason concerns the quality of the code which is an important question, but very difficult to evaluate. How to say that the code is too bad to be taken over by someone else? If "enough" people understood the code and made the effort to code it means that it was possible, that the code was not too bad.		- the second reason concerns the quality of the code which is an important question, but very difficult to evaluate. How to say that the code is too bad to be taken over by someone else? If "enough" people understood the code and made the effort to code it means that it was possible, that the code was not too bad.
		+
		+	'''Matt''':<br>
		+	'''Criteria''': Data is freely accessible without logging in<br>
		+	'''Question''': Should the requirements around data be separate from those related to the software? In some instances the software (Topodroid and other utility apps) is not intended provide data in a publicly consumable manner, hence this (and possible other points) are not relevant.<br>